Skip to content

Platform guide — Operations, Inventory & Finance

You can't merchandise inventory you can't see.

Brands that manufacture — or assemble, or kit — carry a problem pure resellers don't: available-to-sell depends on components, production capacity and lead time, not just a warehouse count.

Katana addresses that specific shape of problem: production planning and inventory for makers, connected to the storefront.

Explore Katana

Partner disclosure: Gapstow may receive referral compensation if you sign up or purchase through links on this page. This does not change what you pay or how we evaluate the platform.

What it does

Katana in one paragraph

Katana tracks raw materials, components and finished goods, plans and schedules production orders, and maintains real-time available-to-sell across sales channels including Shopify.

It also handles the make-to-order versus make-to-stock distinction, purchase orders and supplier lead times — the parts of the operation that spreadsheets model badly once SKU counts rise.

Notable capabilities

  • Bill of materials and production

    Component-level tracking so finished-goods availability reflects what can actually be built.

  • Real-time inventory sync

    Stock levels reconciled across channels, which is the difference between a stockout and an oversell.

  • Make-to-order and make-to-stock

    Different workflows for different product lines, without forcing everything into one model.

  • Purchasing and lead times

    Supplier orders tied to demand, which is where most avoidable stockouts actually originate.

Where it fits

Every platform decision is a decision about who owns a stage.

Where Katana sits across the eCommerce stack
  1. Storefront
  2. Customer
  3. CRM & Retention
  4. OperationsKatana
  5. FulfillmentKatana
  6. ReportingKatana

This is upstream of the storefront. When it's right, product availability on-site is accurate; when it's wrong, you oversell and the support queue finds out first.

Commonly touches

  • Shopify
  • ERP or accounting
  • 3PL
  • Purchasing
  • Reporting

Judgment

Two lists, and the second one matters more.

When we’d look at it

  • You manufacture, assemble or kit, and finished-goods counts don't tell you what you can actually sell.
  • Production planning currently lives in a spreadsheet that one person maintains.
  • Overselling or unexpected stockouts happen regularly during promotions.
  • You sell across multiple channels and inventory truth is ambiguous.
  • Purchasing decisions are reactive because component visibility is poor.

When we’d question it

  • You don't manufacture. A reseller with a 3PL has a different problem and this is the wrong shape of tool.
  • An ERP already owns inventory and production. Two systems claiming the same source of truth is worse than one imperfect system.
  • SKU and component counts are low enough that the spreadsheet genuinely works. Complexity should follow the business, not lead it.
  • The underlying problem is process discipline — receiving isn't recorded, counts aren't done. Software will digitize the inaccuracy.
  • Nobody on the team will own daily data entry. Inventory systems fail from neglect, not from features.

Before you implement

Questions to answer first

  1. 01

    Which system is the source of truth for inventory — the store, the ERP, or this?

  2. 02

    What is our definition of available-to-sell, and does it account for allocated and in-production stock?

  3. 03

    Who performs receiving, counts and production updates, and on what cadence?

  4. 04

    How does inventory reach the storefront, and how fast must that sync be during a promotion?

  5. 05

    What happens when the sync fails — does the store keep selling, and against what number?

  6. 06

    How do returns and damaged goods re-enter inventory?

Implementation

What tends to go wrong

  • Sync direction and conflict rules must be decided explicitly. Bi-directional inventory sync without a defined winner produces drift.
  • Opening balances and BOM setup are the bulk of the implementation effort, and they're not glamorous.
  • Promotional spikes are the real test of sync latency. Model peak, not average.
  • If a 3PL is also involved, map who owns which stage of custody before configuring anything.

Inventory accuracy is an operating habit that software can support and cannot create. Before evaluating a system, spend a week finding out where the count actually goes wrong — it is almost never where people assume.

Vendor material

The software company publishes its own customer stories. We include one here because it’s a useful data point, clearly attributed and summarized rather than reproduced. It is not Gapstow work and we make no claim about the engagement.

Partner / vendor case study — published by Katana, not Gapstow work

Paper Republic's production planning on Katana

Katana's own customer story describes leather goods manufacturer Paper Republic reporting a 60% improvement in production planning and a 29% increase in inventory accuracy after implementation. Gapstow was not involved in this engagement.

  • Reported 60% improvement in production planning
  • Reported 29% increase in inventory accuracy
  • Make-to-order and make-to-stock workflows separated
Read the original on Katana's site

Related Gapstow capabilities

Adding a platform is the easy part.

If Katana is on the table, the useful conversation is about the process and architecture around it — not the software itself.