Reference · built on requestOperator by FibricInventory & supply

Stockout Forecast

Projects days of cover per SKU and location from sales rate, on-hand and inbound stock, then proposes which items to expedite first.

Request accessPricing ↗

About

Every SKU at every location has a date on which it runs out. Stockout Forecast computes that date. It reads units sold per SKU and location from your store's orders, the available, committed, incoming, and on-hand quantities your inventory system holds, and the open purchase order lines and inbound shipments due to land, with their expected dates.

From those it projects days of cover per SKU and location and ranks the items that fall short soonest. It proposes an expedite list for a planner to approve, and for single items it proposes a receipt date change, a transfer from a location with cover, or a low-stock flag on the listing. Each approval leaves a receipt with the figures it rested on.

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

  • Orders and line items from your store, through the Shopify Admin API orders query, to compute a sales rate per SKU and location
  • Inventory levels per location with available, committed, incoming, and on_hand quantities from Shopify InventoryLevel
  • Quantity on hand per item from the Business Central item resource, or per location from the NetSuite item record
  • Open purchase order lines with quantity, receivedQuantity, and expectedReceiptDate in Business Central
  • Inbound shipment records in NetSuite with shipmentstatus and quantityexpected per purchase order line
  • Committed and expected quantities from the Katana inventory object, and expected_arrival_date on Katana purchase orders

Proposed actions

  • Target capability: propose an expedite list ranked by projected stockout date, for a planner to approve
  • Target capability: propose moving a purchase order line's expected receipt date forward, for a buyer to take up with the vendor
  • Target capability: propose a transfer from a location that holds cover to the one that runs out first
  • Target capability: propose a low-stock flag on the listing so merchandising can decide whether to keep selling

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

What you can build

  • Rank this week's expedites

    Shopify orders and inventory levels give a sales rate and on-hand per location. Business Central purchase order lines give inbound dates. The planner approves a ranked list of the SKUs that run out before their inbound lands.

    With Shopify, Microsoft Dynamics 365 Business Central

  • Watch inbound shipments against run-out dates

    NetSuite inbound shipment records carry quantityexpected and a status. When a shipment stops moving, the run-out date for its items is recomputed and the planner sees which ones now fall short.

    With NetSuite, Magento

  • Warn merchandising before a listing goes dark

    Katana in-stock, committed, and expected quantities against the BigCommerce sales rate. When cover falls below the days you set, a low-stock flag on the listing is proposed for merchandising.

    With Katana Cloud Inventory, BigCommerce

Requirements

  • A store or inventory system with per-location quantities: Shopify, BigCommerce, Magento, Business Central, NetSuite, or Katana
  • Open purchase orders carrying an expected receipt date, or inbound shipment records, in your ERP or WMS
  • Enough order history to compute a sales rate for each SKU at each location over the window you set
  • A planner named to approve the expedite list and any date, transfer, or listing proposal
Authentication
A store token with order and inventory read access (a Shopify Admin API access token), plus ERP credentials for purchase orders and inbound shipments (a Business Central OAuth app or a NetSuite REST integration).

Limits

  • Days of cover is on-hand less committed, divided by the sales rate over a window you set. A launch or promotion is not forecast.
  • A SKU with no sales in the window gets no cover figure. It is listed as no rate.
  • Inbound stock counts only when a purchase order line or inbound shipment carries an expected date. Undated lines are left out.
  • It expedites nothing itself. A buyer contacts the vendor or carrier after approving the proposal.

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 Stockout Forecast ↗

Questions and answers

What does the planner approve on the expedite list?
A ranked expedite list. Each row shows the SKU, location, on-hand, committed, inbound quantity with its date, the sales rate, and the projected stockout date. The planner can reorder rows, drop items, or approve the list. Date changes, transfers, and listing flags are approved one at a time.
How is the sales rate calculated?
Units sold per SKU per location over a window you set, read from your store's orders. Cancelled and refunded lines are excluded where your store marks them. No seasonality or trend is applied. The window and the rate are shown on every proposal.
What record is left?
A receipt per approved list: the SKUs, the quantities and dates read, the rate used, the ranking, who approved it, and when. Each date change, transfer, or flag that follows references that receipt and states how to reverse it.
Ask about Stockout Forecast

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