Procurement Supplier Partial Shipment Visibility Lag

A supplier ships half a component order but the buyer continues planning as though the whole quantity is on its way. Procurement supplier partial shipment visibility lag measures the delay before the buyer can see the shipped and outstanding balances.

Define the start event as verified supplier dispatch or a reliable supplier notice, depending on the available evidence, since a planned ship date is not proof of actual movement. Define the endpoint as updated, actionable buyer-side visibility of shipped quantity, expected arrival and remaining open quantity, because an invoice alone might not supply all three.

Oracle describes multiple advance shipment notices against open purchase orders, which supports the idea that a single order may have several distinct shipments. Link every partial shipment to the exact PO line, schedule, supplier item and unit of measure, since a header-level shipped flag can hide differences between lines.

Check whether the supplier marked the remainder as backordered, cancelled or due later, because these states lead to different replenishment decisions. If the first shipment is below a production threshold, planning may still need to reschedule, as visibility is useful only when quantity and arrival can be acted on.

For serialised goods, record which serials or lots shipped if the process requires them, since a quantity total may not satisfy a customer or quality requirement. Compare advance shipment notice, carrier pickup and supplier confirmation, because an ASN can be created before physical dispatch and should not be mistaken for delivery.

When an ASN is revised, retain the earlier version and reason, since a later lower quantity should not erase the time at which planners relied on the first notice. If the supplier sends a partial shipment without prior approval, log both visibility and the commercial exception, as fast updates do not mean the split was permitted.

For freight consolidation, clarify whether goods left the supplier plant or are waiting at a forwarder, since the transport milestone can affect estimated receipt, and keep time zones consistent across supplier and buyer systems, because a dispatch at 23:00 supplier time may appear on a different buyer calendar date. If an EDI interface fails, monitor the failed message and manual fallback, since a supplier portal green status does not guarantee the buyer system received it.

For high-risk components, notify production planners before the expected shortage date, because a delayed report after the line stops is a material outcome even if the data later corrects. Distinguish a split at the supplier from a split at the buyer receiving dock, since the first affects supply promise while the second may only reflect unloading or inspection, and when the second shipment is cancelled update the open order balance and any replacement sourcing so two plans are not created for the same demand.

Define the denominator as partial-shipment events affecting open purchase-order lines, excluding full shipments under a stated rule, and use the median, a high percentile and overdue critical lag, because a fast average can hide one silent split that affects a sole-source part. Classify the cause as supplier late notice, bad ASN data, carrier delay, integration failure or buyer review backlog, audit selected events from dispatch evidence through ASN, PO balance and planner view, check physical receipt against the shipped claim, and report current outstanding quantity and ETA uncertainty with the lag, so false assumptions about supply are prevented during a split delivery.