When a supplier ships a PO in two batches on two different dates, every line used to show the same header-level ETA. Now each PO line can carry its own estimated delivery date, independent of the PO-level date.
How it works:
- The per-line date is nullable — existing POs and lines remain valid with no required backfill. If a line has no per-line date set, the PO-level date still applies as before.
- Users can view and edit the line estimated delivery date in the PO line workflow for draft and open POs. Partial receiving does not clear or overwrite the line date.
- Different lines on the same PO can carry different dates, so a three-line PO arriving in three separate shipments is representable without splitting the PO.
- The per-line date appears in purchase order detail, reports and exports, and over the API — so downstream tools (integrations, the forecasting layer, external systems like Jacobs Digital) see the accurate SKU-level ETA, not a single date for the whole order.
- The existing PO-level estimated delivery date behavior is unchanged. Per-line dates are additive.
Splitting a PO line is still the recommended path if you need to track multiple separate future shipments of the same line item.