Head-to-head
OpsUI vs Katana
Modular ERP, WMS & CRM versus a manufacturing-led inventory and light-MRP platform
Start with operational scope
List the workflows, users and connected systems the product needs to support. Compare the required configuration rather than product labels.
Read the evidence alongside it
Checked pricing facts are cited. Other vendor details remain marked for verification; unknown information is not a missing capability.
The decision in context.
Katana is purpose-built for product makers. The core workflow is BOM-driven: define what you make, define what it is made from, and Katana handles purchase order generation, production scheduling, and inventory reservation against open work orders. It is genuinely strong at light-manufacturing and make-to-stock workflows.
OpsUI is broader. For operators whose pain spans manufacturing plus warehouse, CRM, shipping, and operational reporting, OpsUI consolidates those into one modular product rather than stitching Katana to a separate WMS, CRM, and shipping tool.
The honest split: if your operational world is dominated by "what we make and how we plan it", Katana is a strong choice. If manufacturing is one layer of a broader operations problem, picking, dispatch, returns, customer management. OpsUI covers more of it natively.
Editorial context from the original analysis. Confirm current vendor-specific details against the applicable proposal.
Like-for-like requirements
Put the same questions to each product.
| Requirement | OpsUI | Katana |
|---|---|---|
| Pricing model | Published module subscriptions and Essential, Control, Command and Apex packages. Compare included users, additional seats and separately priced integration connectors. Catalogue context · confirm deployment fit | Current plan, included allowances and commercial terms are not verified here. Request an itemised proposal. Current vendor detail: not independently verified |
| Core scope | Modular ERP, WMS & CRM across 20 operational modules + 5 integration connectors Catalogue context · confirm deployment fit | Inventory, multi-level BOM, production planning, light MRP, shop-floor visibility Current vendor detail: not independently verified |
| Manufacturing depth | Review light-production planning, work orders and BOM requirements. Full MRP and finite-capacity scheduling are not established by the module catalogue. Catalogue context · confirm deployment fit | Strong — multi-level BOMs, production orders, routing, batch tracking, shop-floor app Current vendor detail: not independently verified |
| Warehouse management depth | Dedicated WMS modules (wave picking, slotting, cycle counts, dock scheduling, scanner-driven) Catalogue context · confirm deployment fit | Basic, bin tracking, pick lists, stock takes; advanced WMS via integration partners Current vendor detail: not independently verified |
| CRM | Native CRM module with sales pipeline and customer history Catalogue context · confirm deployment fit | Customer records, no dedicated sales CRM Current vendor detail: not independently verified |
| Accounting integration | NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account. Catalogue context · confirm deployment fit | Xero (deep), QuickBooks Online Current vendor detail: not independently verified |
| Shipping integration | NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account. Catalogue context · confirm deployment fit | Via ShipStation, Starshipit, or carrier add-ons Current vendor detail: not independently verified |
| ANZ data residency | Confirm the applicable deployment controls, locations and evidence during a security review. Catalogue context · confirm deployment fit | AWS-hosted, region not separated by domain Current vendor detail: not independently verified |
| Headquarters | NZ-built, NZ-owned, sold direct Catalogue context · confirm deployment fit | Tallinn, Estonia (Katana Technologies) Current vendor detail: not independently verified |
Pricing model
- OpsUI
- Published module subscriptions and Essential, Control, Command and Apex packages. Compare included users, additional seats and separately priced integration connectors.
Catalogue context · confirm fit
- Katana
- Current plan, included allowances and commercial terms are not verified here. Request an itemised proposal.
Current vendor detail: not independently verified
Core scope
- OpsUI
- Modular ERP, WMS & CRM across 20 operational modules + 5 integration connectors
Catalogue context · confirm fit
- Katana
- Inventory, multi-level BOM, production planning, light MRP, shop-floor visibility
Current vendor detail: not independently verified
Manufacturing depth
- OpsUI
- Review light-production planning, work orders and BOM requirements. Full MRP and finite-capacity scheduling are not established by the module catalogue.
Catalogue context · confirm fit
- Katana
- Strong — multi-level BOMs, production orders, routing, batch tracking, shop-floor app
Current vendor detail: not independently verified
Warehouse management depth
- OpsUI
- Dedicated WMS modules (wave picking, slotting, cycle counts, dock scheduling, scanner-driven)
Catalogue context · confirm fit
- Katana
- Basic, bin tracking, pick lists, stock takes; advanced WMS via integration partners
Current vendor detail: not independently verified
CRM
- OpsUI
- Native CRM module with sales pipeline and customer history
Catalogue context · confirm fit
- Katana
- Customer records, no dedicated sales CRM
Current vendor detail: not independently verified
Accounting integration
- OpsUI
- NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account.
Catalogue context · confirm fit
- Katana
- Xero (deep), QuickBooks Online
Current vendor detail: not independently verified
Shipping integration
- OpsUI
- NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account.
Catalogue context · confirm fit
- Katana
- Via ShipStation, Starshipit, or carrier add-ons
Current vendor detail: not independently verified
ANZ data residency
- OpsUI
- Confirm the applicable deployment controls, locations and evidence during a security review.
Catalogue context · confirm fit
- Katana
- AWS-hosted, region not separated by domain
Current vendor detail: not independently verified
Headquarters
- OpsUI
- NZ-built, NZ-owned, sold direct
Catalogue context · confirm fit
- Katana
- Tallinn, Estonia (Katana Technologies)
Current vendor detail: not independently verified
Commercial structure
Keep the assumptions visible.
Compare subscriptions, user allowances, integration work and implementation responsibilities. Preserve the currency and billing period of each offer.
Essential
NZ$499per month
2 users included
2 operational modules
Control
NZ$1,499per month
5 users included
5 operational modules
Command
NZ$2,999per month
15 users included
11 operational modules
Apex
NZ$11,990per month
Unlimited users
20 operational modules
Published monthly subscriptions in NZD. Existing annual pricing and package allowances apply. Additional seats are NZ$99 per month beyond the applicable allowance; integration connectors are separate add-ons.
Review the full packages and configure pricing →Where each approach may fit.
When Katana is the better fit
You are a product maker and your central operational concern is what you produce, how it is planned, and how production tracks against inventory, true manufacturing pain, not warehouse or CRM pain.
You need multi-level BOMs, routing across work centres, and shop-floor visibility (production status, operator views) as core functionality, not as a future module.
You are happy to keep Xero or QuickBooks for finance and add a manufacturing-first inventory layer rather than buying a broader ERP.
You already use the Katana app on the shop floor or have an existing implementation and the switching cost outweighs broader-scope upside.
Your operational complexity outside manufacturing is modest, single warehouse, simple dispatch, no real CRM need.
When OpsUI is the better fit
Manufacturing is one layer of a broader operations problem. You also need warehouse picking, dispatch, returns, CRM, or analytics, and you would rather buy one modular product than stitch Katana to four others.
Your manufacturing footprint is light assembly or make-to-stock with single-level or simple multi-level BOMs, not full MRP, and the broader operations scope matters more than manufacturing depth.
You want first-party NZ Couriers and Australia Post integration sitting in the same product as inventory and orders, rather than via Starshipit or ShipStation.
Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.
You value vendor proximity, NZ-built, NZ-owned, NZ business hours support, rather than a Tallinn-headquartered global product.
Implementation and local context.
Katana has strong ANZ adoption among small NZ and AU makers but is built and operated from Estonia. Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.
Agree data preparation, configuration, training, cutover and recovery responsibilities. Confirm the relevant accounting and carrier connections, rather than assuming they are included in the licence.
Questions buyers ask.
Is Katana an ERP?
Not in the traditional sense. Katana is a manufacturing-led inventory and light-MRP platform. It does production planning and stock control extremely well, but it does not include native CRM, accounting, HR, or full warehouse management. Most Katana customers pair it with Xero or QuickBooks for finance and run it as the manufacturing system within a multi-tool stack rather than as a single ERP.
Does OpsUI replace Katana for manufacturers?
For light-assembly and make-to-stock manufacturers with single-level or simple multi-level BOMs, yes. OpsUI's Manufacturing module covers the same scope plus warehouse, CRM, and shipping in one product. For manufacturers whose central need is multi-level BOM routing, finite-capacity scheduling, and shop-floor visibility, Katana is the stronger fit today. The right call is to be honest about manufacturing complexity.
Is OpsUI cheaper than Katana?
Compare the required modules, users, order allowances, integration work and implementation responsibilities before comparing prices. OpsUI’s current package structure is shown on this page. Current competitor prices and terms need confirmation with the vendor; historical estimates are not a current quote.
Can OpsUI integrate with Katana?
OpsUI exposes a REST API and could in principle be wired to Katana, but most operators pick one or the other for their core operational system rather than running both. The exception is operators with a heavily Katana-driven production floor who want OpsUI as a CRM or shipping layer above it.
Does OpsUI have a shop-floor app like Katana?
Not today. OpsUI ships Bluetooth scanner support and warehouse-floor workflows in the Warehouse module, but a dedicated production-floor app (operator-screen views, work order check-in / check-out) is not currently shipped. For manufacturers where that visibility is load-bearing, Katana is the better choice.
Sources and verification scope.
Checked facts apply only to the scope described next to each source. Other vendor details in the editorial analysis remain unverified for a current purchase decision. Confirm them with the vendor and record the applicable plan, version and proposal date.
Current primary-source verification of this vendor’s detailed capabilities and prices is pending. An unknown is not a missing feature.
Further reading: Katana alternatives, neutral roundup
OpsUI integration delivery and scope · Security review information · Published OpsUI packages
Related comparisons and guides.
Your next step
Evaluate the fit against your operation.
Bring the workflows and dependencies that will decide the choice. We’ll review what OpsUI covers and what needs further confirmation.