OpsUI vs Katana
Modular ERP, WMS & CRM versus a manufacturing-led inventory and light-MRP platform
OpsUI is a modular ERP, WMS & CRM with 21 individually-priced modules covering operations end-to-end, while Katana is a manufacturing-led inventory and light-MRP platform built for product makers — multi-level BOMs, production orders, routing, and shop-floor visibility, with Xero / QuickBooks accounting integration.
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.
OpsUI vs Katana, feature by feature.
| OpsUI | Katana | |
|---|---|---|
| Pricing model | Per module, public on /pricing (from NZ$399 / A$399 per module, packs from NZ$1,499 / A$1,499 / mo) | Tiered plans, public pricing — Essential / Advanced / Professional, per-user fees stack above the base |
| Core scope | Modular ERP, WMS & CRM across 21 modules | Inventory, multi-level BOM, production planning, light MRP, shop-floor visibility |
| Manufacturing depth | Manufacturing module (BOMs, work orders; routing and finite-capacity scheduling not yet shipped) | Strong — multi-level BOMs, production orders, routing, batch tracking, shop-floor app |
| Warehouse management depth | Dedicated WMS modules (wave picking, slotting, cycle counts, dock scheduling, scanner-driven) | Basic — bin tracking, pick lists, stock takes; advanced WMS via integration partners |
| CRM | Native CRM module with sales pipeline and customer history | Customer records, no dedicated sales CRM |
| Accounting integration | NetSuite (live), REST API (live), Xero / MYOB (bidirectional sync, wired during rollout) | Xero (deep), QuickBooks Online |
| Shipping integration | NZ Couriers, Australia Post first-party in the Shipping module | Via ShipStation, Starshipit, or carrier add-ons |
| ANZ data residency | NZ data in NZ, AU data in AU, separate domains | AWS-hosted, region not separated by domain |
| Headquarters | NZ-built, NZ-owned, sold direct | Tallinn, Estonia (Katana Technologies) |
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.
- You want NZ data hosted in NZ and AU data hosted in AU on separate domains.
- You value vendor proximity — NZ-built, NZ-owned, NZ business hours support — rather than a Tallinn-headquartered global product.
Katana has strong ANZ adoption among small NZ and AU makers but is built and operated from Estonia. OpsUI is NZ-built, NZ-hosted (for NZ customers), AU-hosted (for AU customers), and handles GST, NZ Couriers, and Australia Post natively without third-party shipping middleware.
What buyers ask before choosing.
Is Katana an ERP?
Does OpsUI replace Katana for manufacturers?
Is OpsUI cheaper than Katana?
Can OpsUI integrate with Katana?
Does OpsUI have a shop-floor app like Katana?
Last updated
Other ANZ ERP comparisons.
See the modules. Decide for yourself.
Public pricing on the page. No discovery call required to know what OpsUI costs.