Reference · built on requestOperator by FibricInventory & supply

Supplier Fill Rate

Scores each vendor on fill rate, short-ships and on-time receipts from PO and receiving records, then proposes shifting volume.

Request accessPricing ↗

About

What a vendor promised is on the purchase order. What they delivered is on the receipt. Supplier Fill Rate reads both, line by line: ordered quantity, received quantity, rejected quantity where the warehouse records it, the expected receipt date, and the date the receipt was posted. Where your ERP history is exported to a warehouse, it reads the tables there instead.

It rolls the lines up into a score per vendor per period: fill rate, short-ship count, and on-time receipts. It proposes the scorecard for a sourcing lead to publish, and where an item has two vendors whose scores have diverged, it proposes changing the preferred vendor or splitting the next period's volume. Nothing changes on an item record without approval.

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

  • Purchase order lines with quantity, receivedQuantity, and expectedReceiptDate in Business Central
  • Business Central purchase receipts and receipt lines, dated by postingDate and tied to an orderNumber
  • NetSuite purchase orders and the item receipts created from them
  • ShipHero purchase order line items with quantity, quantity_received, and quantity_rejected
  • Katana purchase orders in NOT_RECEIVED, PARTIALLY_RECEIVED, or RECEIVED status with received_date per row
  • Order and receipt history tables in Snowflake, BigQuery, or PostgreSQL where your ERP exports them

Proposed actions

  • Target capability: propose a vendor scorecard per period with fill rate, short-ship count, and on-time receipts, for the sourcing lead to publish
  • Target capability: propose changing the preferred vendor on an item record when another vendor on that item scores better
  • Target capability: propose a split of next period's volume between two vendors on the same item
  • Target capability: propose a review task for a vendor whose short-ships have grown, with the affected orders attached

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

What you can build

  • Score vendors from Business Central receipts

    Purchase order lines against purchase receipts give fill rate and on-time receipts per vendor. History beyond the API window comes from the Snowflake export. The sourcing lead approves the scorecard.

    With Microsoft Dynamics 365 Business Central, Snowflake

  • Shift the preferred vendor on a dual-sourced item

    A NetSuite item with two vendors whose scores have diverged over the period gets a proposed preferred-vendor change, with both vendors' orders and receipts shown to the buyer.

    With NetSuite, BigQuery

  • Count rejections at the 3PL

    ShipHero quantity_rejected on purchase order lines and Katana order status feed a vendor whose rejections have grown. A review task with the affected orders is proposed for the buyer.

    With ShipHero, Katana Cloud Inventory

Requirements

  • Purchase orders with ordered quantities and expected dates, in Business Central, NetSuite, Katana, or ShipHero
  • Receipts against those orders with received quantities and posting dates
  • More than one vendor on at least some items, or the volume proposals have nowhere to go
  • A sourcing lead or buyer named to approve scorecards and vendor changes
Authentication
Read access to purchase orders and receipts in your ERP or WMS, read-only warehouse credentials for exported history, and item update rights where a preferred vendor is changed.

Limits

  • Fill rate is received over ordered per line. Rejections count only where the WMS records them, as ShipHero does with quantity_rejected.
  • On time means received on or before the expected receipt date on the line. A line without one is scored on fill alone.
  • A vendor with few orders in the period is shown without a rank.
  • Price is not in the score. The buyer weighs it when deciding.

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 Supplier Fill Rate ↗

Questions and answers

What does the sourcing lead approve?
Two kinds of proposal. A scorecard for the period, which they can publish or hold. A vendor change on an item, shown with both vendors' scores and the orders behind them. Either can be edited or declined.
How are the scores computed?
Per line: received quantity divided by ordered quantity, a short-ship where received is below ordered, and on time where the receipt date is on or before the expected date. Lines roll up per vendor and period. The method is printed on each scorecard.
Does it move volume itself?
No. A preferred vendor change is written to the item record only after approval, and the next purchase order draft follows it. A receipt records the scores, the change, who approved it, and the previous vendor so it can be put back.
Ask about Supplier Fill Rate

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