When Cin7, Unleashed, or Katana isn't the right answer: an inventory architecture framework for Australian multi-channel sellers

Quick answer: for most Australian multi-channel sellers the answer is to pick one of Cin7, Unleashed, or Katana and connect it to your sales channels via the platform’s native integrations. Each platform has a category fit: Cin7 for omnichannel retail and 3PL-heavy operations, Unleashed for AU-based light manufacturing with strong accounting integration, Katana for product makers needing manufacturing BOM and shop-floor tracking. The shapes where these platforms break — and where custom inventory architecture earns its place — are multi-warehouse with picking complexity, made-to-order with variable BOMs, B2B and B2C sharing one stock pool with different priority logic, marketplace-specific stock buffers, or genuine omnichannel where the POS is the source of truth and ecommerce is the satellite. This piece walks through which platform fits which business shape, where each one stops, and what the custom path actually involves. Sits alongside our broader API integration practice.

If you sell across more than one channel — Shopify plus a physical store, Shopify plus marketplaces, WooCommerce plus a wholesale relationship — you’ve already hit the inventory question. The reflexive answer (and the right one for most stores) is to pick an Inventory Management System (IMS), make it the source of truth for stock, and let it sync to each sales channel. The three platforms that dominate the Australian market for this are Cin7, Unleashed, and Katana.

Each platform has a clear fit. Each platform also has shapes it doesn’t handle well, which is where the stock visibility problems show up six or twelve months after the platform was implemented. The stories we hear when stores come to us looking at custom inventory architecture have a consistent shape: “we’ve been on [platform X] for two years, it does 80% of what we need, the other 20% is killing us.”

This piece is about which platform fits which business shape, what each one doesn’t do well, and the conditions under which custom architecture — usually a thin inventory layer between the channels and the source of truth, not a full IMS replacement — earns its place.

Cin7: omnichannel retail and 3PL operations

Cin7 (now operating as Cin7 Core and Cin7 Omni after the 2024 product split) sits at the operational-complexity end of the AU inventory market. Per published pricing in mid-2026, AU plans start around A$500/month and scale up based on user count and connected sales channels. Cin7 has an AU office in Ringwood, Victoria with local support.

Where Cin7 fits:

• Multi-channel retailers running physical stores + ecommerce + marketplaces where the volume across channels justifies the platform cost and the operational complexity. Cin7 handles the routing logic for which warehouse fulfils which channel cleanly.
• 3PL-integrated operations where the inventory lives at a third-party logistics provider that has a Cin7 integration. The 3PL becomes a Cin7 warehouse and the platform handles the dispatch instructions.
• Light manufacturing at modest BOM complexity. Cin7’s manufacturing module handles bills of materials, assembly tracking, and component allocation reasonably well.
• Cross-border ecommerce where the platform’s multi-currency and multi-tax handling matters.

Where Cin7 stops:

• Made-to-order with variable BOMs. Cin7’s manufacturing model expects relatively stable BOMs. If every order has a customer-specific BOM (custom furniture, configure-to-order industrial products), the platform’s assembly workflow doesn’t fit.
• High-frequency catalogue change. Cin7’s sync model assumes a relatively stable catalogue. Brands with seasonal or weekly catalogue refreshes (fashion, beauty, anything with a tight calendar) often find the sync overhead higher than expected.
• POS-led omnichannel where the POS is the source of truth. Cin7 wants to be the source of truth; if you’re running Lightspeed Retail or Square as the master and Shopify as a satellite, the integration topology fights against the platform’s assumptions.
• Genuinely small businesses. The per-month cost and the operational requirement to use Cin7 properly (someone whose job includes understanding the platform) make it overkill for stores doing under approximately $50K/month in revenue.

Unleashed: AU-based light manufacturing with strong Xero integration

Unleashed is the platform AU manufacturers most often pick when they need real production capability without going to NetSuite or SAP. Per published pricing, AU plans start around A$350/month and scale up. The platform has strong AU presence and a deeply-integrated relationship with Xero.

Where Unleashed fits:

• AU-based food & beverage, supplements, and consumables manufacturers where the production model is batch-based with clear BOMs and the accounting integration to Xero matters operationally.
• Light manufacturing with consistent assembly processes. Unleashed handles BOM management, assembly orders, and component allocation cleanly when the production model is repeatable.
• Brands running Shopify as one channel among several (own retail, wholesale, marketplaces) where Unleashed sits behind everything and feeds each channel.
• B2B-heavy operations with a smaller B2C component. Unleashed’s sales-order workflow is genuinely useful for the wholesale side; the B2C feeds work for satellite ecommerce channels.

Where Unleashed stops:

• High-channel-count retail-led operations. If you have a physical store with a Lightspeed POS as the operational core, plus Shopify, plus marketplaces, the integration topology starts to fight against Unleashed’s assumption that it’s the operational centre.
• Heavy ecommerce with rapid catalogue refresh. Same caveat as Cin7 — Unleashed’s sync model assumes catalogue stability.
• Complex multi-warehouse picking. Unleashed supports multi-warehouse but its picking and dispatch flows are simpler than the warehouse management system (WMS) you’d need for a serious distribution operation.
• MYOB-led accounting. While Unleashed integrates with MYOB, the depth of the Xero integration is materially better. Brands committed to MYOB usually pick differently.

Katana: product makers with manufacturing BOMs and shop floor

Katana is the platform for businesses where the manufacturing is the operational centre and the ecommerce is downstream. Per published pricing, plans start around US$199/month and scale up by feature tier and user count.

Where Katana fits:

• Product makers selling DTC — jewellery, apparel-made-to-order, hardware kits, anything where the maker is also the seller. Katana’s production scheduling, shop floor tracking, and component allocation are built for this shape.
• Light assembly with parts and assemblies tracking. Katana’s BOM model handles multi-level assemblies cleanly.
• Storage floor / production floor visibility where the brand wants to see WIP, available capacity, and production scheduling alongside finished-goods inventory.

Where Katana stops:

• Pure resale operations with no manufacturing component. The platform is built around production; resellers pay for capability they don’t use.
• Large-scale manufacturing. Katana fits up to mid-scale production. Brands doing serious production volume usually graduate to dedicated manufacturing systems.
• Heavy multi-channel B2C without manufacturing focus. If you’re a brand selling assembled goods across many channels and the manufacturing is upstream, Cin7 or Unleashed will typically fit better.
• Strong accounting integration requirements beyond QuickBooks or Xero. Katana’s accounting integration is real but less deeply featured than Unleashed’s.

The decision framework

For most AU multi-channel sellers, the decision is one of these three platforms. The choice depends on three questions:

1. What’s the operational centre? If it’s production or assembly, Katana or Unleashed depending on scale. If it’s retail (physical store + ecommerce), Cin7. If it’s wholesale (B2B sales with ecommerce as a satellite), Unleashed.
2. What’s the accounting system? Strong Xero integration is non-negotiable for most AU businesses; Unleashed and Cin7 both deliver this; Katana’s Xero integration is adequate but less deep.
3. What’s the channel mix? If genuinely omnichannel (physical store + ecommerce + marketplaces + wholesale), Cin7’s routing capabilities matter. If channel mix is simpler (production into one or two ecommerce channels), Unleashed or Katana.

The honest pattern is that most AU brands at the scale where they need an IMS at all will fit one of these three platforms cleanly. The cases where they don’t are the cases this article is about.

Where custom inventory architecture earns its place

The shapes where the off-the-shelf IMS doesn’t fit cleanly — and where we’ve built custom inventory architecture as the answer:

Multi-warehouse with picking complexity

The IMS platforms support multi-warehouse but typically model warehouses as “stock locations,” not as operations with their own picking, packing, and dispatch logic. Brands running serious multi-warehouse operations — particularly with split-shipment rules (orders containing items from multiple warehouses split into multiple parcels) or stock-and-customer-location-based fulfilment routing — usually hit the ceiling of what the IMS expresses in configuration.

The custom pattern is a routing layer that sits between the IMS and the warehouses, evaluating each order against the available stock per warehouse, customer location, freight cost per warehouse, and any contractual SLAs (Customer X always ships from Warehouse A) before producing the fulfilment instructions.

Made-to-order with variable BOMs

Configure-to-order industrial products, custom furniture, anything where the customer’s order changes the BOM. The IMS platforms assume BOMs are relatively stable and assembled in batches. When every order is its own BOM, the IMS’s assembly workflow becomes overhead rather than enablement.

The custom pattern is an order configuration system that produces the BOM at order time, allocates components against forecasted demand, and pushes the production instruction to the shop floor. The IMS underneath still tracks raw materials and finished goods, but the production layer above it knows how to build the variable BOMs.

B2B + B2C sharing one stock pool with priority logic

The brand sells the same SKUs to wholesale customers and DTC customers. The wholesale customer placed an order this morning; the DTC customer placed an order this afternoon. Who gets the stock when there’s only enough for one?

Most IMS platforms treat this as “first in, first allocated.” The brand’s actual policy might be “wholesale orders above $5K always take priority,” or “wholesale orders that committed before the close-of-business deadline take priority over DTC orders placed after,” or “hold N units of safety stock for B2C against forecasted demand and only release to B2B above that threshold.”

The custom pattern is an allocation engine that runs against the IMS’s stock numbers, applies the brand’s prioritisation rules, and produces allocation decisions per order. The IMS still holds the stock; the allocation layer decides who gets what.

Marketplace-specific stock buffers

Selling on Catch, Kogan, MyDeal, or Amazon Australia, the brand wants to hold buffer stock against the marketplace channels separately from the DTC stock pool. The reasons are operational: marketplaces have higher returns rates, fulfilment SLAs that penalise stock-outs more heavily, and reputational risk from overselling.

Some IMS platforms support “virtual warehouse” buffers; most don’t express this cleanly. The custom pattern is a stock-buffer layer that holds the brand’s buffer rules per channel, applies them to the IMS’s available stock, and produces channel-specific stock levels that get synced to each marketplace.

POS-led omnichannel where the POS is the source of truth

Lightspeed Retail (X-Series), Square, or Vend running the physical store, with Shopify as the satellite ecommerce channel. The POS’s stock numbers are the operational truth (the POS is what staff use, what the morning stock-take feeds into, what the physical-shop-floor reality matches). The IMS sits awkwardly because it wants to be the master.

The honest answer here is that you can run with Lightspeed-as-master + Shopify-as-satellite using the platforms’ native integration, and many brands do exactly that — no IMS at all. The custom pattern enters when you have more than one POS location, marketplace channels alongside Shopify, or wholesale relationships, and you need a thin inventory layer that respects the POS as source of truth while syncing to all the other channels.

What custom inventory architecture actually looks like

When we build custom inventory layers for AU brands, the shape is typically:

• One designated source of truth — often the IMS the brand already uses, sometimes a POS, sometimes the ERP, occasionally a warehouse management system. The source of truth is the system that holds the “real” numbers and that operational staff actually update.
• A thin inventory abstraction layer that reads from the source of truth, applies the brand’s business rules (allocation priority, marketplace buffers, multi-warehouse routing, channel-specific availability), and produces per-channel stock levels.
• Channel sync workers that push the calculated per-channel levels to each sales channel (Shopify, WooCommerce, marketplaces) on whatever cadence each channel supports.
• Reconciliation jobs that periodically compare the channel stock levels to the source-of-truth levels and catch drift before it becomes a stock-out.
• An admin layer where the operations team can see the rule outputs and override when needed.

The pattern is similar in shape to the carrier-agnostic shipping layer — a thin internal abstraction that holds the business rules and talks to whatever channels you’ve integrated to. The custom build doesn’t replace the IMS; it sits between the IMS and the channels to express the rules the IMS can’t.

What this costs

For an AU brand with one IMS (or POS) as source of truth and 3–5 sales channels, custom inventory architecture typically lands in the $30,000–$80,000 range. The cost scales with the complexity of the allocation rules, the number of channels, and the depth of the admin tooling.

The conditions where this is worth the spend:

• Channel revenue above $500K annually with stock issues actively costing money (stockouts, overselling, returns from late dispatch).
• The off-the-shelf IMS can’t express specific operational rules that the brand needs to run on. The rules aren’t “nice to have” — they’re commercially material.
• The operations team is spending 15+ hours a week manually adjusting stock levels across channels because the IMS sync doesn’t reflect the brand’s actual policy.
• The brand has named accounts or marketplace relationships with explicit stock commitments that the IMS can’t express natively.

Below those conditions, the right answer is usually to make better use of the IMS the brand has, with maybe one or two targeted integrations to fill specific gaps.

The crossover question with the off-the-shelf IMS

Brands often ask whether they should replace their IMS or build custom alongside it. In our experience, the answer is almost always “keep the IMS, add a thin custom layer for the gap.”

The reasons:

• The IMS handles 80%+ of the work cleanly. Replacing it with custom code means rebuilding all that capability.
• The IMS has the integrations that matter (accounting, payment, common channels). The custom layer slots in alongside.
• The IMS’s vendor handles upgrades, security patches, integration maintenance. Replacing it transfers all that operational burden in-house.
• The brand’s operations team already knows the IMS. Replacing it means retraining and changed processes.

The custom layer between the IMS and the channels is the high-leverage build. Replacing the IMS rarely is.

Common questions

Which IMS should I pick if I’m starting from scratch in 2026? For most AU brands the question is between Cin7, Unleashed, and Katana, with the choice depending on whether the operational centre is retail (Cin7), manufacturing (Katana or Unleashed depending on scale), or wholesale (Unleashed). The published pricing for each varies through 2026; check current rates at cin7.com, unleashedsoftware.com, and katanamrp.com for your specific configuration.

What if I’m on Xero and want native inventory in the accounting system? Xero’s built-in inventory is intentionally basic — it handles simple stock counts for accounting purposes but isn’t designed as an operational IMS. Brands that try to run multi-channel inventory in Xero hit limits quickly. The right pattern is to use Xero for accounting and an IMS (Cin7, Unleashed, Katana) for inventory operations, with the IMS feeding Xero via the integration each platform supports.

Can I just use Shopify’s inventory? Shopify’s native inventory works for single-channel Shopify-only operations and degrades quickly when you add a second sales channel. The platform doesn’t cleanly support marketplace stock buffers, multi-warehouse routing, or B2B priority allocation. For multi-channel operations, an IMS sitting upstream of Shopify is almost always the right architecture.

What about NetSuite, SAP, or Microsoft Dynamics? The enterprise ERPs handle inventory at a different scale and with a different cost profile. They’re the right answer for brands with hundreds of staff, multi-entity operations, or genuinely complex manufacturing. For AU brands in the $1M–$50M revenue range, the dedicated AU IMS platforms (Cin7, Unleashed) typically deliver more value for less cost and operational burden.

How do I migrate from one IMS to another? IMS migrations are generally painful regardless of the destination platform — the data model differences are real, the historical-data preservation question is hard, and operational continuity through the cut-over is a workstream of its own. Expect 3–6 months for a meaningful migration with several weeks of parallel-running. The honest test before starting is whether the destination platform genuinely solves a problem the current one doesn’t — if the answer is “we just want better features,” the migration cost usually exceeds the benefit.

Does the custom inventory layer replace the IMS’s native channel integrations? Yes — the custom layer takes over the channel sync, and the IMS’s native channel integrations get disabled. The IMS keeps its role as source of truth; the custom layer handles the per-channel rules and synchronisation.

If you’re running multi-channel inventory in AU and the current setup is producing more workarounds than the IMS was supposed to solve, start a project and we’ll model the architecture against your specific channel mix and operational rules.