Shipment

What It Is

A shipment is the warehouse work that organizes physical units leaving an order's stock allocation. It groups units at one warehouse and carries the destination and shipping choice associated with the order. Staff progress that work through picking and packing before handing it to a carrier or a collecting buyer. The shipment gives warehouse activity its own record without changing the identity of the sale.

A single order can require several shipments. Stock ready now can leave while backordered units wait for replenishment and a later wave. Shipment lines identify the quantities being handled, and parcels describe how those quantities are packed. A pickup uses the same broad departure accounting while following a collection path without carrier labels. History records the sequence of warehouse and carrier-related events so staff can reconstruct the handling of a particular shipment.

What It Is Not

A shipment is not a parcel: one shipment can contain several packages with separate labels and tracking. It is also not the order's delivery obligation, although departure completes the physical units' obligations. The order remains responsible for the commercial sale. A return authorization belongs to the post-sale document workflow; receiving and label work account for the goods moving under that authorization.

How It Is Used

Warehouse staff create a shipment from eligible order allocations, release work to the floor and organize picking. They record shortages rather than treat every planned quantity as found. Packing creates the parcels that carrier work uses. Staff then label and manifest carrier shipments or record pickup collection. The console currently exposes a limited shipment entry point, so the full floor workflow remains service-driven. Refused handover needs attention before any goods leave.

Its Facets

Shipment line. A shipment line groups a contiguous range of an order line's units and follows their handling state. Understanding shipment line in the shipment workflow.

Pick list. A warehouse picking batch identifies its picker and records full or short quantities. Understanding pick list in the shipment workflow.

Parcel. A packed parcel groups contents with weight and label information. Understanding parcel in the shipment workflow.

Carrier label. Carrier purchase attempts retain the label, tracking and charged cost and support voiding. Understanding carrier label in the shipment workflow.

Shipping zone and strategy. Zones and charging strategies supply destination coverage and shipping or collection choices. Understanding shipping zone and strategy in the shipment workflow.

Carrier account. The account identifies a carrier connection without holding its credentials. Understanding carrier account in the shipment workflow.

Pick-up. Collection completes through a named recipient at the counter instead of carriage. Understanding pick-up in the shipment workflow.

Cancellation fence. Cancellation fencing prevents the same unit range from departing unchecked during cancellation. Understanding cancellation fence in the shipment workflow.

Return receipt and return label. Incoming labels and receipts support authorized return arrival, inspection and disposition. Understanding return receipt and return label in the shipment workflow.

History. Immutable events explain warehouse and carrier progression. Understanding history in the shipment workflow.

How It Relates

Orders supply sold quantities and saved shipping choices. Stock allocations supply the particular units, and handover changes their ledger state. Obligations provide delivery authorization and completion. Cost relief is invoked at departure through the configured provider, while carrier integration uses Platform connections. Stock findings retain warehouse and label problems outside the operations queue.

What It Could Become

The product should supply the picking, packing, handover and receiving screens needed for ordinary warehouse work. Tracking automation, label storage and returned-to-sender handling remain open delivery edges. Design also needs clear evidence for carrier behavior beyond local fixtures before staff rely on the integration operationally.