Katana

Warehouse tasks/role views are documented, now with separate operator login, first-start assignment, limited cost visibility and specific task-eligibility conditions. The Warehouse Management module must be enabled; precise client device guidance is separately cited. No independent device/offline test or universal native-mobile compatibility is implied.

The Stock screen distinguishes on-hand, expected and committed stock. Material commitments depend on sales/manufacturing availability and recipe requirements; this is not a physical-stock guarantee or an independent inventory test.

Calculated stock is in stock minus committed plus expected minus safety stock. Safety/calculated columns appear only for a specific location; quick-add purchase/manufacturing orders require the location Buy/Make functions to be enabled.

Locations maintain their own inventory, order lists and schedules. Make, Sell and Buy are enabled per location; a warehouse location is distinct from a shelf/bin inside it.

A make-to-order sales order and its manufacturing order must use the same location. The default Main location cannot be deleted; storage bins are optional and linked to item variants.

These are documented workflow features. They do not establish certification, regulatory compliance, guaranteed recall performance or universal industry suitability.

Native Shopify, Amazon and QBO are product-level integrations. Shopify mandatory location mapping/manual activation and QBO accounting-flow/Bills requirements are now read separately. QuickBooks Online is explicitly not Desktop; QBO Essentials is a QBO subscription prerequisite for Bills, not a Katana plan. Free ecommerce remains Shopify-only.

Free and Advantage advertise API access, while Advantage includes scoped custom integration work maintained by the vendor. The separately read Authentication page distinguishes custom API-key access from public-app OAuth2.0. API availability does not make every ERP, POS,3PL or partner connection a native included connector or establish quotas and geographic/accounting-edition eligibility.

The current Free FAQ says only Shopify currently integrates with Free for ecommerce, despite broader unlimited-integrations wording. This does not remove preserved Amazon/QuickBooks product-level facts or assign their entitlement to Free; no pricing record is changed.

The official page identifies Katana Cloud Inventory. This is cloud positioning, not proof of a self-hosted server, a native desktop installation, data residency, disconnected transactions or all-client parity.

Warehouse is a mobile-friendly browser client, not an installableAndroid/iOS app. Its own guide permits modern camera devices and identifies QR/6-digit login; Shop Floor has a separate guide and browser list. MinimumOS/browser versions, every scanner model and disconnected transactions are not established.

Manufacturing and outsourced production are vendor-described workflows. Customer stories and navigation to particular industries are not evidence of guaranteed sector outcomes or regulatory certification.

The vendor positions Advantage for businesses of any size with scoped workflows and Free for a small catalog. The JanuaryFree help adds conflicting3location/archived-SKU wording versus current unlimited-location pricing; a February paid-plan help article mentionsmonthly/annual while current Advantage isannual. These are unresolved dated entitlement terms, not employee thresholds or new price admissions.

The native product page describes one or multiple Shopify stores and POS/order/inventory flow. The separately read integration overview requires authorization, configuration, mapping every Shopify location and explicit sync activation. Inventory and fulfillment toggles/directions are separate; paid orders import by default, payment-pending orders can be included. No runtime guarantee of no oversells or hands-on sync test is asserted; current Free ecommerce remains Shopify-only.

Amazon fulfillable inventory is pulled into a dedicated Katana location with scheduled or on-demand reconciliation; FBA sales arrive as Delivered. FBA and FBM SKUs can be mapped to one Katana product. This differs from pushing merchant-fulfilled stock to Amazon; Free ecommerce is not extended beyond Shopify.

FBM orders arrive Open for merchant pick/pack/ship; shipment tracking and status write back to Amazon, and Katana stock is pushed to FBM. The setup describes authorizing an Amazon Seller account and matching SKUs. No account authorization, fulfillment or synchronization test was performed; country/marketplace and plan eligibility are not globally inferred.

QBO is a native accounting integration, explicitly not QuickBooks Desktop. The separately read basic overview documents valuation/accounting flows, invoices, bills/expenses and contacts; Bills require QBO Essentials+. Marketing inventory-balance wording is not a stock-quantity parity guarantee, and regional/current-plan eligibility beyond the explicit prerequisite is not generalized.

The API introduction describes public endpoints, code examples and OpenAPI3.0. The separately read Authentication page now distinguishes custom API-key use from OAuth2.0 for publicly available apps. No schema, endpoint or example code was executed; API access marketing does not grant a native connector, unrestricted quotas or product licensing-country eligibility.

The integration describes one Katana product record carrying its FBA and FBM Amazon SKUs and buildable kit/bundle stock. This is conditional on the configured Amazon integration; it is not a guarantee of accepted listings, account health, Buy Box performance or error-free inventory.

The Warehouse app is explicitly mobile-friendly and web-based, not a native Android/iOS package. Separate Warehouse and Shop Floor device guides are now read. Warehouse uses a modern browser/camera with QR/6-digit login; no version-specific OS/browser minimum, every-scanner support or offline behavior is established.

Shopify authorization/configuration and explicit manual activation precede live sync; every Shopify location must map to a Katana location, with reuse allowed. Stock sent to Shopify Available is In stock minus Committed. Orders remain on during active sync, while inventory and fulfillment have separate toggles; fulfillment can flow either/both ways. Initial stock import requires inactive sync, imported products and mapped locations. Multiple stores have independent states. No store installation, authorization or synchronization was performed; current Free ecommerce remains Shopify-only.

The documentation requires a valid key on custom-integration requests and OAuth2.0 for publicly available apps accessing other users data. It recommends server-side key handling. This read does not generate/use credentials, execute the example request or establish account permission/region/quotas. Free/Advantage API marketing is separate from connector inclusion and the intended API usage must remain authorized.

Warehouse Operators are separate from Shop Floor Operators, have dedicated logins without simultaneous sessions, and do not see pricing/cost details. Ready-for-packing sales orders and receivablePO/OPO items appear as tasks; the first operator starting a task is assigned automatically. Product-level transfers or manufacturing features are not promised inside this limited Warehouse client.

The Warehouse Management add-on and feature toggles enable pick/pack and purchase/OPO receiving; Warehouse Operators must be added. System-generated Unbatched batches cannot be selected for Pick&Pack. The documented stock-adjustment workaround is not performed here, nor generalized to a missing product-level batch feature.

Shop Floor is not a native Android/iOS app. The guide recommends tablets, names Chrome/Firefox/Safari/Edge and requires a working camera for QR login and barcode capture. Browser versions are unspecified; stable internet is recommended for login/task updates. These are Shop Floor-specific recommendations, not Warehouse device requirements or proof of offline operation.

Warehouse is not a native iOS/Android app. It is accessed in a modern browser with a QR code and6-digit operator login code; the UI adapts to screen size. No minimum OS/browser version or universal scanner SDK/model support is enumerated. This is separate from Shop Floor browser recommendations; no device or login test was performed.

The explicit language FAQ says Katana does not officially support non-English languages. Browser GoogleTranslate is described as a machine-generated workaround that may have errors, not native localization or a supported additional app-language list. No extension, login or translation was installed/tested; screen-by-screen client parity is not independently verified.

The overview explicitly excludes QuickBooks Desktop. It documents PO bills/expenses, SO invoices, payment-status return and customer/supplier imports; inventory synchronization is described as valuation/accounting data. Bills require QBO Essentials or higher, which is an accounting subscription requirement, not a Katana plan name. It describes non-inventory item creation/reuse to avoid duplication. No stock-quantity parity, every-QBO-plan/region eligibility, accounting action or runtime connector test is inferred.

The Jan30,2026 help article states30SKUs and3locations with all features/add-ons, while current pricing advertises unlimited locations. It calls the limit30activeitems yet says SKU counting includes archived variants; these details are not reconciled here. The source also describes a15-day grace behavior, distinct from the pricing page initial trial wording. This is dated/conflicting entitlement evidence, not a replacement current rate or an employee threshold.

The add-on describes Warehouse web access, mobile pick/pack, PO receiving, barcode validation and default bin assignments. Current pricing/help must be read together for entitlement; no separate add-on amount, included device count, universal mobile transfers or implementation outcome is established.

• Warehouse execution, roles, task eligibility, named-batch and bin constraints are documented. Location and Free-plan limits remain source/version-dependent; original accepted capabilities are retained rather than silently withdrawn or generalized to every client.
• Partial receiving, Access-controlled warehouse operator views — Warehouse tasks/role views are documented, now with separate operator login, first-start assignment, limited cost visibility and specific task-eligibility conditions. The Warehouse Management module must be enabled; precise client device guidance is separately cited. No independent device/offline test or universal native-mobile compatibility is implied. · Checked 2026-10-30
• Stock availability by item variant, Committed and expected stock, Inventory value and average cost — The Stock screen distinguishes on-hand, expected and committed stock. Material commitments depend on sales/manufacturing availability and recipe requirements; this is not a physical-stock guarantee or an independent inventory test. · Checked 2026-10-30
• Safety stock levels, Calculated replenishment stock — Calculated stock is in stock minus committed plus expected minus safety stock. Safety/calculated columns appear only for a specific location; quick-add purchase/manufacturing orders require the location Buy/Make functions to be enabled. · Checked 2026-10-30
• Location-specific Make, Sell and Buy permissions — Locations maintain their own inventory, order lists and schedules. Make, Sell and Buy are enabled per location; a warehouse location is distinct from a shelf/bin inside it. · Checked 2026-10-30
• Location-constrained make-to-order fulfillment — A make-to-order sales order and its manufacturing order must use the same location. The default Main location cannot be deleted; storage bins are optional and linked to item variants. · Checked 2026-10-30
• Lot and serial traceability, Expiry date management — These are documented workflow features. They do not establish certification, regulatory compliance, guaranteed recall performance or universal industry suitability. · Checked 2026-10-30
• Amazon FBA and FBM SKU aliasing — The integration describes one Katana product record carrying its FBA and FBM Amazon SKUs and buildable kit/bundle stock. This is conditional on the configured Amazon integration; it is not a guarantee of accepted listings, account health, Buy Box performance or error-free inventory. · Checked 2026-10-30
• Task-scoped Warehouse Operator access and attribution — Warehouse Operators are separate from Shop Floor Operators, have dedicated logins without simultaneous sessions, and do not see pricing/cost details. Ready-for-packing sales orders and receivablePO/OPO items appear as tasks; the first operator starting a task is assigned automatically. Product-level transfers or manufacturing features are not promised inside this limited Warehouse client. · Checked 2026-10-30
• Warehouse task enablement and named-batch constraints — The Warehouse Management add-on and feature toggles enable pick/pack and purchase/OPO receiving; Warehouse Operators must be added. System-generated Unbatched batches cannot be selected for Pick&Pack. The documented stock-adjustment workaround is not performed here, nor generalized to a missing product-level batch feature. · Checked 2026-10-30
• Warehouse Management add-on execution and bin tools — The add-on describes Warehouse web access, mobile pick/pack, PO receiving, barcode validation and default bin assignments. Current pricing/help must be read together for entitlement; no separate add-on amount, included device count, universal mobile transfers or implementation outcome is established. · Checked 2026-10-30
• Receiving, Picking and packing, Stock transfers, Bin locations, Barcode scanning, Serial and lot tracking, Expiry tracking · Checked 2026-10-28

• Native Shopify/FBA/FBM, API custom-key versus public-app OAuth, and QBO accounting-flow prerequisites are read. QBO Essentials+ is required for Bills, not every possible operation or a Katana tier; Desktop and quantity-parity claims are excluded. Regional eligibility, APIquotas and every partner connector are not established.
• Shopify, Amazon, QuickBooks Online — Native Shopify, Amazon and QBO are product-level integrations. Shopify mandatory location mapping/manual activation and QBO accounting-flow/Bills requirements are now read separately. QuickBooks Online is explicitly not Desktop; QBO Essentials is a QBO subscription prerequisite for Bills, not a Katana plan. Free ecommerce remains Shopify-only. · Checked 2026-10-30
• Custom API and scoped integrations — Free and Advantage advertise API access, while Advantage includes scoped custom integration work maintained by the vendor. The separately read Authentication page distinguishes custom API-key access from public-app OAuth2.0. API availability does not make every ERP, POS,3PL or partner connection a native included connector or establish quotas and geographic/accounting-edition eligibility. · Checked 2026-10-30
• Shopify ecommerce integration on Free — The current Free FAQ says only Shopify currently integrates with Free for ecommerce, despite broader unlimited-integrations wording. This does not remove preserved Amazon/QuickBooks product-level facts or assign their entitlement to Free; no pricing record is changed. · Checked 2026-10-30
• Native Shopify store and POS order integration — The native product page describes one or multiple Shopify stores and POS/order/inventory flow. The separately read integration overview requires authorization, configuration, mapping every Shopify location and explicit sync activation. Inventory and fulfillment toggles/directions are separate; paid orders import by default, payment-pending orders can be included. No runtime guarantee of no oversells or hands-on sync test is asserted; current Free ecommerce remains Shopify-only. · Checked 2026-10-30
• Native Amazon FBA inventory and delivered-order synchronization — Amazon fulfillable inventory is pulled into a dedicated Katana location with scheduled or on-demand reconciliation; FBA sales arrive as Delivered. FBA and FBM SKUs can be mapped to one Katana product. This differs from pushing merchant-fulfilled stock to Amazon; Free ecommerce is not extended beyond Shopify. · Checked 2026-10-30
• Native Amazon FBM order, stock and tracking integration — FBM orders arrive Open for merchant pick/pack/ship; shipment tracking and status write back to Amazon, and Katana stock is pushed to FBM. The setup describes authorizing an Amazon Seller account and matching SKUs. No account authorization, fulfillment or synchronization test was performed; country/marketplace and plan eligibility are not globally inferred. · Checked 2026-10-30
• Native QuickBooks Online accounting integration — QBO is a native accounting integration, explicitly not QuickBooks Desktop. The separately read basic overview documents valuation/accounting flows, invoices, bills/expenses and contacts; Bills require QBO Essentials+. Marketing inventory-balance wording is not a stock-quantity parity guarantee, and regional/current-plan eligibility beyond the explicit prerequisite is not generalized. · Checked 2026-10-30
• Public OpenAPI 3.0-described API — The API introduction describes public endpoints, code examples and OpenAPI3.0. The separately read Authentication page now distinguishes custom API-key use from OAuth2.0 for publicly available apps. No schema, endpoint or example code was executed; API access marketing does not grant a native connector, unrestricted quotas or product licensing-country eligibility. · Checked 2026-10-30
• Shopify integration with explicit location mapping and manual activation — Shopify authorization/configuration and explicit manual activation precede live sync; every Shopify location must map to a Katana location, with reuse allowed. Stock sent to Shopify Available is In stock minus Committed. Orders remain on during active sync, while inventory and fulfillment have separate toggles; fulfillment can flow either/both ways. Initial stock import requires inactive sync, imported products and mapped locations. Multiple stores have independent states. No store installation, authorization or synchronization was performed; current Free ecommerce remains Shopify-only. · Checked 2026-10-30
• Custom API-key authentication and public-app OAuth 2.0 — The documentation requires a valid key on custom-integration requests and OAuth2.0 for publicly available apps accessing other users data. It recommends server-side key handling. This read does not generate/use credentials, execute the example request or establish account permission/region/quotas. Free/Advantage API marketing is separate from connector inclusion and the intended API usage must remain authorized. · Checked 2026-10-30
• QuickBooks Online-only accounting flow with Bills prerequisite — The overview explicitly excludes QuickBooks Desktop. It documents PO bills/expenses, SO invoices, payment-status return and customer/supplier imports; inventory synchronization is described as valuation/accounting data. Bills require QBO Essentials or higher, which is an accounting subscription requirement, not a Katana plan name. It describes non-inventory item creation/reuse to avoid duplication. No stock-quantity parity, every-QBO-plan/region eligibility, accounting action or runtime connector test is inferred. · Checked 2026-10-30
• QuickBooks Online, Shopify, Amazon · Checked 2026-10-28

• Cloud inventory and two separate web-based operator clients are documented. They are not native Android/iOS packages. Self-hosted server/data residency and universal disconnected deployment remain unestablished.
• Cloud inventory platform — The official page identifies Katana Cloud Inventory. This is cloud positioning, not proof of a self-hosted server, a native desktop installation, data residency, disconnected transactions or all-client parity. · Checked 2026-10-30

• Warehouse modern-browser/camera and QR/6-digit-login guidance is distinct from Shop Floor camera/tablet/browser recommendations. No minimum OS/browser version, universal scanner compatibility or independent cross-device feature-parity test is established.
• Mobile access to the Katana Warehouse app — Warehouse is a mobile-friendly browser client, not an installableAndroid/iOS app. Its own guide permits modern camera devices and identifies QR/6-digit login; Shop Floor has a separate guide and browser list. MinimumOS/browser versions, every scanner model and disconnected transactions are not established. · Checked 2026-10-30
• Mobile-friendly web-based Warehouse app — The Warehouse app is explicitly mobile-friendly and web-based, not a native Android/iOS package. Separate Warehouse and Shop Floor device guides are now read. Warehouse uses a modern browser/camera with QR/6-digit login; no version-specific OS/browser minimum, every-scanner support or offline behavior is established. · Checked 2026-10-30
• Browser-based Shop Floor Control app, Tablets, camera phones and camera-equipped laptops/desktops — Shop Floor is not a native Android/iOS app. The guide recommends tablets, names Chrome/Firefox/Safari/Edge and requires a working camera for QR login and barcode capture. Browser versions are unspecified; stable internet is recommended for login/task updates. These are Shop Floor-specific recommendations, not Warehouse device requirements or proof of offline operation. · Checked 2026-10-30
• Browser-based Warehouse app, Camera smartphones, rugged scanners, tablets and laptops — Warehouse is not a native iOS/Android app. It is accessed in a modern browser with a QR code and6-digit operator login code; the UI adapts to screen size. No minimum OS/browser version or universal scanner SDK/model support is enumerated. This is separate from Shop Floor browser recommendations; no device or login test was performed. · Checked 2026-10-30

• The exact device, overview, enablement and app-module bodies describe web clients, real-time status and stable-internet guidance, but do not establish disconnected transaction capture, caching or reconciliation. No precise unread offline-specific destination was exposed by this bounded set; offline remains unknown, not false.

• Manufacturing/product workflows remain supported by source bodies. Customer cases, source navigation and app guidance do not prove universal sector suitability or regulatory certification.
• Manufacturing and product operations — Manufacturing and outsourced production are vendor-described workflows. Customer stories and navigation to particular industries are not evidence of guaranteed sector outcomes or regulatory certification. · Checked 2026-10-30
• Manufacturing · Checked 2026-10-28

• Small-catalog Free and scoped any-sizeAdvantage positioning are explicit. Free help3locations/archived SKU wording and monthly/annual help versus current pricing require agreement-specific confirmation; no employee threshold or tested capacity is inferred.
• Product businesses with scoped workflows — The vendor positions Advantage for businesses of any size with scoped workflows and Free for a small catalog. The JanuaryFree help adds conflicting3location/archived-SKU wording versus current unlimited-location pricing; a February paid-plan help article mentionsmonthly/annual while current Advantage isannual. These are unresolved dated entitlement terms, not employee thresholds or new price admissions. · Checked 2026-10-30
• Free-plan catalog and location limits in the January2026 help article — The Jan30,2026 help article states30SKUs and3locations with all features/add-ons, while current pricing advertises unlimited locations. It calls the limit30activeitems yet says SKU counting includes archived variants; these details are not reconciled here. The source also describes a15-day grace behavior, distinct from the pricing page initial trial wording. This is dated/conflicting entitlement evidence, not a replacement current rate or an employee threshold. · Checked 2026-10-30

• The actual language FAQ explicitly says non-English UI is not officially supported. English is established; browser machine translation is separate and can contain errors. This is documentation evidence, not a screen-by-screen translation/client test.
• English — The explicit language FAQ says Katana does not officially support non-English languages. Browser GoogleTranslate is described as a machine-generated workaround that may have errors, not native localization or a supported additional app-language list. No extension, login or translation was installed/tested; screen-by-screen client parity is not independently verified. · Checked 2026-10-30

• Actualproduct, plan, settings, client and QBO sources do not establish a licensing-country eligibility list. EnglishUI, tax/multicurrency settings and accounting subscription names are not country availability. No global-availability or global-absence claim.