Release and fulfillment: push to WMS or ship standalone

Release action, push-to-WMS, split and multi-warehouse dispatch, standalone shipping, packing lists and labels.

Release is the handoff to fulfillment. What happens next depends on the inventory source: wms_sync orders are pushed to WMS as outbound shipments; standalone orders are shipped directly from OMS.

The release action#

• release moves allocated → released and requires ship_mode (parcel / ltl / ftl).
• A release voucher row is written to oms_allocations; if that write fails, the status change is rolled back.

Push to WMS (wms_sync mode)#

• push-to-wms works on confirmed or allocated orders with a warehouse set; it creates WMS outbound shipment(s) in commit status, which locks inventory.
• It is idempotent: pushing twice returns PUSHED_ALREADY instead of duplicating.
• Split: one OMS order can become multiple outbound shipments; the order detail page lists them all. Multi-warehouse dispatch: preview the split, then execute to create one shipment per warehouse; already-dispatched orders return DISPATCHED_ALREADY.
• OMS has no wave concept of its own — waves live on the WMS side. Watch WMS progress on the order’s WMS timeline (committed → picking → picked → packed → shipped).

Ship standalone (oms_standalone mode)#

• The ship action moves confirmed / allocated / released → shipped. You pick a connected carrier account and service; ATP is re-checked per line.
• The tracking number is generated locally (carrier prefix + date + random digits) and OMS inventory is deducted with reason "ship".
• batch-ship ships up to 100 orders at once, auto-matching each order to a connected carrier account, with per-order results.

Packing list and label#

• Packing list: generates a payload (order + lines + code128 barcode data) saved to oms_packing_lists; the page renders it for printing. It never calls a real printer.
• Label: available once shipped with a tracking number; returns a 4×6 payload (carrier, service, tracking barcode, ship-to/from, pieces, weight) rendered by a print overlay.
• There is no pack verification step on the OMS side — pack checks happen in WMS.