Reference · built on requestOperator by FibricInventory & supply

Inbound Delay

Tracks open POs and inbound shipments. When a slipped ETA crosses a projected stockout date, it proposes an expedite or a second source.

Request accessPricing ↗

About

A late shipment matters only if the shelf empties before it arrives. Inbound Delay holds both dates side by side. It reads open purchase order lines and their expected receipt dates, the inbound shipment or tracking record behind each one, and the stock and sales rate per SKU and location that set the day the item runs out.

When a new ETA, a stalled status, or a passed date pushes arrival past that day, it proposes one of three things: an expedite request for the line, a purchase order draft to a second vendor already on the item, or a transfer from a location with cover. A buyer picks, edits, or declines. A receipt keeps the ETA it saw and the date it projected.

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

  • Open purchase order lines with expectedReceiptDate and receivedQuantity in Business Central, or Katana orders in NOT_RECEIVED and PARTIALLY_RECEIVED status
  • NetSuite inbound shipment records with shipmentstatus and quantityexpected per purchase order line
  • Shipment tracking and ETA updates on inbound freight through project44 or FourKites, including webhooks on status change
  • Parcel tracking status for smaller inbound orders through AfterShip
  • Inventory levels per location from your store, with available, committed, and incoming quantities
  • Units sold per SKU and location from your store's orders, to project the day stock runs out

Proposed actions

  • Target capability: propose an expedite request to the vendor or carrier for a line whose new ETA falls after the projected stockout date
  • Target capability: propose a purchase order draft to a second vendor on the item record for the gap quantity
  • Target capability: propose a transfer from a location that holds stock to the one that will run short first
  • Target capability: propose a delivery date change on the listing when neither expedite nor second source closes the gap

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

What you can build

  • Catch the ETA slip before the shelf is empty

    A project44 ETA change on ocean freight is set against the Business Central expected receipt date and Shopify inventory per location. Where the new ETA passes the stockout date, an expedite is proposed.

    With project44, Microsoft Dynamics 365 Business Central, Shopify

  • Fall back to the second vendor on the item

    A NetSuite inbound shipment stalls in transit while FourKites shows no movement. The item record lists a second vendor, so a purchase order draft for the gap quantity is proposed.

    With NetSuite, FourKites

  • Move stock when a parcel replenishment runs late

    An inbound parcel tracked in AfterShip shows an exception, the Katana order is still not received, and Magento sales say the location runs out first. A transfer from another location is proposed.

    With AfterShip, Katana Cloud Inventory, Magento

Requirements

  • Open purchase orders with expected receipt dates, in Business Central, NetSuite, or Katana
  • Inbound tracking: NetSuite inbound shipments, a visibility platform such as project44 or FourKites, or AfterShip for parcels
  • Per-location stock and a sales rate from your store or ERP, so a stockout date can be projected
  • A buyer or planner named to approve expedites, second-source drafts, and transfers
Authentication
ERP read access to purchase orders and inbound shipments, a project44, FourKites, or AfterShip account for tracking, and a store token with inventory and order read access.

Limits

  • An order with no tracking and no inbound shipment record is watched by its expected date alone. It shows as late the day after.
  • A second source is proposed only when a second vendor is already on the item record.
  • Expedite cost is not quoted. The proposal names the line and the days at stake, and the buyer asks the carrier.
  • The projected stockout uses sales over a window you set. A promotion that starts tomorrow is not in it.

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 Inbound Delay ↗

Questions and answers

What triggers a proposal?
A new ETA, a shipment status that stops moving, or an expected receipt date that passes without a receipt. Each is compared with the projected stockout date for the SKU and location. A proposal is raised only when the arrival falls after that date.
What does the buyer choose between?
One of three things: an expedite request, a purchase order draft to a second vendor, or a transfer. The proposal shows the line, the old and new ETA, the stockout date, and the gap quantity. The buyer picks one, edits it, or declines.
Does it contact the carrier or vendor?
No. It drafts the expedite request or purchase order for the buyer, who sends it. A receipt records the ETA it saw, the stockout date it projected, what was approved, by whom, and how to cancel the draft.
Ask about Inbound Delay

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