Table of Contents
For product businesses, the critical distinction is stock on a shelf versus stock that can actually be promised.
Research-based editorial analysis · Sources checked November 4, 2026. The scenarios, calculations and acceptance exercises are proposed evaluation tools; they are not reports of hands-on product tests. How we research · Commercial disclosure
Our assessment of Katana
Katana’s strongest use case is a product business whose customer promise depends on components and production, not simply a finished-goods total. The current Free and Advantage structure also changes the buying discussion: Free is limited to 30 SKUs after its initial exploration period, while Advantage is a personalized commercial arrangement. We would trial a shared-component shortage before a large catalogue import. The system needs to explain which order can be made and when—not merely display an attractive inventory board.
| Fit | Decision context |
|---|---|
| Worth shortlisting | A brand managing components, finished goods and repeatable production, with an operator responsible for purchasing and inventory accuracy. |
| A weaker starting choice | A merchant who only needs to buy shipping labels, or a team expecting software to resolve inconsistent SKUs and missing opening balances without operational cleanup. |
Published capabilities and plan boundaries
| Dimension | What the primary material establishes |
|---|---|
| Free catalogue | The published Free limit is 30 SKUs after a 15-day unlimited-SKU exploration period. |
| Account capacity | Free lists unlimited users and inventory locations, plus API access. |
| Commerce connection | The current Free-plan FAQ identifies Shopify as its ecommerce integration. |
| Advantage | Custom pricing and guided implementation replace a simple universal self-service price. |
Primary references: Katana plan details.
The product decisions that matter
Thirty SKUs is a meaningful catalogue boundary
A small sample can fit the free allowance while a real assortment cannot. Count the actual component and variant structure the business will maintain; do not equate thirty product ideas with thirty operational records. A manufacturer with sizes, components and assemblies can reach the boundary quickly. The limited scope is useful for a coherent trial, not evidence that a complex catalogue will operate free of charge.
Use an item family with a shared input rather than thirty unrelated easy products. That selection exposes allocation and production behaviour while keeping the physical sample inspectable. It gives the paid discussion a concrete basis: the business knows which operating relationship it needs to preserve as the catalogue expands.
Component availability is different from a stock count
A finished product can be unavailable despite abundant unrelated material. Two customer orders can also compete for the same component. Katana’s inventory-and-manufacturing positioning is relevant because those relationships belong in the operating picture. We would judge the usefulness of its configuration through the shortage explanation and the revised production choice.
The important definitions are the material physically present, the quantity already committed and the expected receipt. Treating those as one stock number can create a false customer promise. A supplier delay is therefore a more informative demonstration than a fully stocked assembly with no competing order.
Guided implementation must leave an operable system
Advantage’s implementation proposition can be valuable when the business needs help connecting item data and work practices. The result should include decisions the team understands: item units, component relationships, reservation policy and responsibility for corrections. A setup completed by an expert is not sufficient if normal staff cannot explain it.
Compare Finale around warehouse execution and Unleashed around the wider purchasing-and-cost relationship. The distinction is not a claim that only one product supports manufacturing. It identifies the hard transaction that should lead the demonstration and the team whose work must become clearer.
Units and yield determine whether a production plan is credible
A bill of materials can look complete while expressing the wrong quantity relationship. A supplier may sell a material in packs, purchasing may record those packs and production may consume individual pieces. The item model must state the conversion. If a pack of twelve is accidentally treated as one usable unit, the shortage picture changes dramatically even though every transaction follows the configured rule.
Production output also deserves a physical interpretation. An illustrative run consuming twenty units but producing eighteen acceptable finished items has a different result from a perfect twenty-unit run. Record what happened to the remaining material under the business’s actual process. Do not force an unexplained difference into a stock adjustment merely to make the board agree with the target. The team needs to understand usable output and the reason for variance.
We would treat these definitions as prerequisites for Katana’s production-oriented value. The software should help keep purchasing, components and finished goods related, but the business supplies the physical model. A small reconciled assembly is a stronger basis for expansion than a large catalogue whose units nobody has checked. The recommendation becomes more confident when the same definitions support both the work order and the customer promise.
A business case for the evaluation
A small manufacturer sells assembled gift sets through a store and to wholesale customers. Three sets use the same component. A large trade order arrives while a retail promotion is running. The operator needs to see which commitments consume that component, what can be made from the remainder and which supplier delivery changes the promise date. A raw total across the warehouse is not sufficient to answer those questions.
What a useful result would show
Measure inventory variance, shortage-related order changes, promise-date reliability and time spent resolving allocation questions. Track whether operators can reconstruct the cause of a stock change without relying on one expert who remembers the transaction.
A focused way to evaluate this configuration
- Clean the item model. Define the difference between components, finished products and sellable kits. Align names, units and variants before connecting live channels.
- Establish opening stock. Count a manageable physical sample and identify damaged, reserved and unavailable items. Document the reason for any adjustment.
- Model one assembly. Choose a representative bill of materials with a shared component. Include the units needed and the expected output.
- Receive a supplier order. Exercise a partial receipt and a late balance. Check whether the operations team can explain the remaining shortage.
- Allocate and produce. Enter competing customer orders, commit stock and complete a partial production run. Inspect what can still be promised.
- Close the loop. Ship the finished order and reconcile the stock change and accounting handoff. Preserve an explanation for the operator who reviews the transaction later.
Interpreting the full cost
Request the current Advantage configuration using the real catalogue, production scope and integrations. Older named-plan prices should not be recycled as today’s quote. Separate implementation from recurring cost and identify what happens when the free trial scope expands. A higher subscription can be justified by fewer shortage and reconciliation problems; those benefits need a record from the business rather than a vendor’s general productivity statement.
Primary references: Katana plan details.
The tradeoffs to keep in the decision
Assembly logic is only as good as the item data
A wrong unit conversion can make an accurate-looking plan impossible to execute. Validate one complete product from raw units to finished output before importing a large catalogue.
Availability is a business policy
Teams can disagree about whether incoming stock, uncompleted work or reserved quantities should count toward a promise. Agree the rule before treating a dashboard as the answer.
Accounting and operations have different timing
A physical receipt, supplier invoice and production completion may occur on different days. Demonstrate the accounting connection instead of assuming every operational event immediately equals a financial posting.
A 26-record trial becomes a 32-record operating catalogue
As a planning example, a business maintains twelve finished-item variants, eight component records and six packaging records. That is twenty-six records in the proposed sample model. Six seasonal variants would bring the model to thirty-two. The business must confirm how its actual items are represented, but the example shows why a thirty-SKU boundary deserves attention before the catalogue expands.
The commerce requirement can also decide the configuration independently of the count: the current Free FAQ identifies Shopify as its ecommerce integration. A merchant whose real brief depends on another channel should not infer eligibility simply because a small sample fits. Evaluate the actual paid proposal using both the catalogue and connection requirements.
Other tools to compare with this requirement
- Finale Inventory — Finale Inventory belongs in the comparison when warehouse execution, multichannel stock and operational inventory control dominate the brief.
- Unleashed — Unleashed is relevant for product businesses evaluating purchasing, assembly or production and stock-cost relationships.
- Goflow — Goflow is a different emphasis when multichannel order flow and channel coordination are the main constraint.
Related analysis: Katana vs Finale Inventory vs Unleashed: Production, Warehouse Control or Stock Costs?.
Questions specific to this purchase
Is the initial unlimited-SKU period the continuing Free allowance?
No. The published FAQ distinguishes the initial exploration period from the later 30-SKU limit.
Which trial best represents a manufacturer?
Use competing orders sharing a component, a partial receipt and a changed arrival date. The resulting promise should be understandable to both production and sales.
