Reference · built on requestConnectorERP & finance

Katana Cloud Inventory

Sales, manufacturing, and purchase orders, stock by variant and location, and webhook events from Katana Cloud Inventory.

Request accessPricing ↗

About

Katana Cloud Inventory is manufacturing and inventory software for small and mid-sized makers. Its REST API at api.katanamrp.com/v1 covers sales orders and their fulfillments, manufacturing orders with operation rows and productions, purchase orders and receipts, stock per variant and location with batches and bins, products, materials, variants, and bills of materials. Webhooks push named events when orders, manufacturing, or inventory change.

An operator on Fibric watches quantity_committed against quantity_in_stock and quantity_expected, then proposes a purchase order, a manufacturing order, or a new safety stock level for your approval. You see the reason and the undo path before anything is written.

This is a reference listing. It documents what Fibric would read from Katana Cloud Inventory and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sales orders with status, ingredient_availability, production_status, and invoicing_status, plus their rows, fulfillments, and returns
  • Manufacturing orders with operation rows, productions, recipe rows, and queue rank
  • Purchase orders and outsourced purchase orders with rows, receipts, and additional cost rows
  • Current inventory per variant and location: quantity_in_stock, quantity_committed, quantity_expected, quantity_missing_or_excess, and safety_stock_level
  • Inventory movements, replenishment signals, variants with negative stock, batch stock, and bin inventory levels
  • Products, variants, materials, BOM rows, price lists, customers, suppliers, and locations
  • Webhook events such as sales_order.packed, purchase_order.received, manufacturing_order.blocked, and current_inventory.product_out_of_stock

Proposed actions

  • Target capability: propose a purchase order and, once goods arrive, its receipt
  • Target capability: propose a manufacturing order, including a make-to-order one tied to a sales order row
  • Target capability: propose a stock adjustment, a stock transfer, or a stocktake
  • Target capability: propose a new safety stock level for a variant at a location
  • Target capability: propose a sales order fulfillment or a sales return

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Buy before the line stops

    Watch quantity_missing_or_excess turn negative on a material and propose a purchase order to its supplier with the expected arrival date filled in.

    With Stockout Forecast, Purchase Order Draft

  • Reset safety stock from what actually moved

    Read inventory movements by location and propose a new safety_stock_level for the variants that ran short last period.

    With Safety Stock

  • Rank the shop floor by who is waiting

    When a manufacturing_order.blocked event arrives, find the sales order rows it feeds and propose a new rank for the manufacturing queue.

    With Backlog Priority

  • Chase a purchase order that is running late

    Compare each open purchase order's expected arrival with today and propose the supplier follow-up before the sales order it feeds slips.

    With PO Chase

Requirements

  • A Katana account on the Professional plan or higher; those plans can generate API keys
  • An API key from Settings > API > API keys, kept on your server and never in client-side code
  • An HTTPS endpoint for webhooks; Katana accepts only URLs matching https://*
  • Locations and variants set up in Katana, since inventory is tracked per variant per location
Authentication
A Katana API key created under Settings > API and sent as Authorization: Bearer on every request; OAuth 2.0 is documented separately for public apps.

Limits

  • 60 requests per 60 seconds per API key; Katana answers 429 with a Retry-After header when the quota is exceeded
  • List endpoints page with limit (default 50) and page (default 1), so full history loads are paced
  • The reorder_point field is deprecated; safety_stock_level is the value to read and write
  • invoicing_status describes the invoice Katana generates through its own accounting sync to Xero or QuickBooks Online, not your ledger

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Katana Cloud Inventory ↗

Questions and answers

Which Katana plans include API access?
Katana states that API access requires the Professional plan or higher. Professional and Professional Plus accounts can generate API keys under Settings > API.
What is the API rate limit?
60 requests per 60 seconds per API key. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. A 429 response includes Retry-After, and Katana asks clients to wait that long before retrying.
What can a Katana webhook tell me?
You subscribe an HTTPS URL to named events. Examples: sales_order.packed, sales_order.delivered, purchase_order.partially_received, manufacturing_order.done, manufacturing_order_recipe_row.ingredients_in_stock, and current_inventory.material_out_of_stock. Katana returns a token with each webhook you create.
Ask about Katana Cloud Inventory

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Katana Cloud Inventory through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy