Shipment

What It Models

A shipment gathers an order’s physical units at one warehouse for a dispatch wave or customer collection. Its lines, parcels, pick lists and labels retain the warehouse’s progress. Return receiving records what comes back, and shipping configuration determines the options offered to buyers.

Identity and Attributes

Shipments, pick lists and return receipts use workspace numbering. A shipment line identifies a contiguous unit range. Parcels have sequences within a shipment, and each carrier-label attempt retains its own purchase key and outcome. Shipping configuration uses stable configuration identities.

Relationships

Allocation units identify the stock assigned to each shipment line. Handoff writes stock movements and completes matching delivery obligations. Return receipts link to an Orders-owned authorization and, where available, the outbound shipment line used to restore cost.

Invariants

The handoff transaction coordinates stock, cost-provider calls, order shipping quantities and matching obligation completion. Its authorization check refuses an invalid matching obligation but does not prove that every allocation has a matching obligation. Carrier purchase recovery retains uncertainty rather than starting another purchase blindly.

How It Is Stored and Shared

Shipping owns warehouse work and shipping configuration. It invokes Inventory and Fulfillment persistence inside its transactions and delegates costing through a provider. Orders controls cancellation and return documents, while carrier credentials remain with the Integration Platform.

Open Design Questions

Warehouse lifecycle enforcement, missing obligation coverage, concurrent pick lists and lost return-finance continuation remain implementation gaps. The shipment dialog also collects values that its request discards.