Skip to content
Comparison · Katana Manufacturing

OpsUI vs Katana

Modular ERP, WMS & CRM versus a manufacturing-led inventory and light-MRP platform

In one line

OpsUI is a modular ERP, WMS & CRM with 20 operational modules and 5 integration connectors, each priced individually, spanning warehouse, orders, CRM and finance sync, while Katana is a manufacturing-led inventory and light-MRP platform built for product makers, with multi-level BOMs, production orders, routing, and live shop-floor status, plus 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.

Side by side

OpsUI vs Katana, feature by feature.

OpsUIKatana
Pricing modelPer module, public on /pricing (from NZ$299 / A$299 per module, packs from NZ$499 / A$499 / mo)Tiered plans, public pricing, Essential / Advanced / Professional, per-user fees stack above the base
Core scopeModular ERP, WMS & CRM across 20 operational modules + 5 integration connectorsInventory, multi-level BOM, production planning, light MRP, shop-floor visibility
Manufacturing depthManufacturing 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 depthDedicated WMS modules (wave picking, slotting, cycle counts, dock scheduling, scanner-driven)Basic, bin tracking, pick lists, stock takes; advanced WMS via integration partners
CRMNative CRM module with sales pipeline and customer historyCustomer records, no dedicated sales CRM
Accounting integrationNetSuite (live), REST API (live), Xero / MYOB (bidirectional sync, wired during rollout)Xero (deep), QuickBooks Online
Shipping integrationNZ Couriers live in the Shipping module today; Australia Post and other AU carriers configured during rolloutVia ShipStation, Starshipit, or carrier add-ons
ANZ data residencyNZ data in NZ, AU data in AU, separate domainsAWS-hosted, region not separated by domain
HeadquartersNZ-built, NZ-owned, sold directTallinn, Estonia (Katana Technologies)
Honest pick

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.
Where OpsUI wins

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.
ANZ context

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.

Common questions

What buyers ask before choosing.

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?
For Katana's Essential plan, prices are similar at the entry tier. For Advanced and Professional tiers (multi-user manufacturers), OpsUI is usually competitive or cheaper, particularly when you include the WMS, CRM, and shipping modules that Katana customers typically buy separately. Honest comparison: bundle the full toolkit cost, not just the manufacturing line.
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.

Last updated

See the modules. Decide for yourself.

Public pricing on the page. No discovery call required to know what OpsUI costs.