Reference · built on requestOperator by FibricInventory & supply

Kit Availability

Checks the component stock behind every kit and bundle and proposes an order or a listing hold when one part runs short first.

Request accessPricing ↗

About

A kit sells as one item and ships as several. Kit Availability reads the bill of materials for each kit or bundle from your ERP or inventory system, then compares each component's on-hand, committed, and on-order quantities with the rate the kit sells at. The component that runs out first sets how many kits you can still sell.

When that number falls below the open demand, it proposes either a purchase order for the short component or a hold on the bundle listing. A buyer or merchandiser approves. The proposal names the kit, the limiting component, the date it runs out, and the quantity that closes the gap.

This is a reference listing. It documents what Fibric would read from Kit Availability 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

  • Bills of materials per kit: component variants and quantity per parent, from Katana BOM rows or a Business Central production or assembly BOM
  • Component on-hand, committed, and on-order quantities at each location from your inventory system
  • Open purchase orders and their requested receipt dates for components
  • Bundle and kit sales from storefront orders, filtered by SKU, from Shopify or BigCommerce
  • Listed quantity and availability of each bundle on the storefront
  • Open sales orders that already commit components to other kits

Proposed actions

  • Target capability: propose a purchase order for the component that runs out first, sized to the open bundle demand
  • Target capability: propose a hold on a bundle listing: reduce the listed quantity or mark it unavailable until the component arrives
  • Target capability: propose an assembly or manufacturing order to build kits from components already on hand
  • Target capability: propose moving a component from a slower kit's allocation to a faster one, with both kits' cover shown

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

What you can build

  • Find the part that caps a bundle

    Each bundle shows its limiting component, the kits still buildable, and the date they run out, read from Katana BOM rows and Shopify sales.

    With Katana Cloud Inventory, Shopify

  • Hold the listing before it oversells

    When buildable kits fall below open orders, a listing hold is proposed on the BigCommerce product with the component's expected receipt date, so a merchandiser can decide.

    With BigCommerce, Cin7 Core

  • Order the short component in time

    A purchase order draft for the limiting component lands in Business Central with the quantity that covers the bundle demand until the next receipt.

    With Microsoft Dynamics 365 Business Central, Magento

Requirements

  • A system that holds the bill of materials for each kit (Katana Cloud Inventory, Cin7 Core, NetSuite, or Business Central)
  • Component quantities and open purchase orders with expected dates from that same system or your ERP
  • A storefront connector with bundle sales and listing quantities (Shopify, BigCommerce, or Magento)
  • A buyer to approve orders and a merchandiser to approve listing holds
Authentication
Your ERP or inventory system's API key or OAuth app, plus a storefront token with read access to orders and inventory and write access to product availability, held per deployment.

Limits

  • A kit with no bill of materials on record gets no projection. It is listed as unmapped until someone adds one.
  • Run-out dates use the sales rate over a window you set. A promotion that changes the rate shows up only after it starts.
  • Substitute components count only if your bill of materials lists them. It does not guess at alternates.
  • It does not send a purchase order to a vendor. It drafts one for a buyer to approve and send.

Access and pricing

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

Request Kit Availability ↗

Questions and answers

What does a person approve?
Two kinds of proposal. A buyer approves a component purchase order with vendor, quantity, and date. A merchandiser approves a bundle hold with the listed quantity it would set. Either can change the numbers or decline.
How does it pick the limiting component?
It divides each component's available quantity, plus receipts due before the run-out date, by the quantity per kit on the bill of materials. The smallest result is the limiting component.
What record does it leave?
A receipt per proposal: the kit, the limiting component, the quantities it read, the action approved, who approved it, and how to reverse it. Declined proposals are kept with the reason given.
Ask about Kit Availability

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. 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