Order-to-Delivery Operations Guide

Use one owned flow from order to closure

1. Create the shipment work itemLink the authoritative order, selected shipping decision, expected service context, owner, priority, and due time. Hold rather than guess when the order, address, inventory, payment, cancellation, or fraud state is unresolved.
2. Build the shipping packetGive the warehouse the minimum useful order, ship-from, ship-to, item, planned handling-unit, accessorial, document, and instruction record with a version or hash. Avoid uncontrolled spreadsheets and duplicate tickets.
3. Pick, protect, pack, measure, and verifyThe warehouse confirms the right items and quantities, selects approved materials, records actual handling units, dimensions, scale weight, condition, photos, and exceptions, then signs the checklist.
4. Rate and tender the actual shipmentRe-rate when the verified package or service requirement differs. An authorized operator chooses service, tenders once under an idempotent reference, produces the required label or bill of lading, and records pickup details.
5. Track exceptions through deliveryKeep carrier identifiers, status events, expected delivery, appointment, exception owner, proof of delivery, and recipient condition feedback together. Late or duplicate events do not erase a later authoritative state.
6. Reconcile and closeAttach the final bill, compare quoted and actual freight/accessorials, open a dispute or claim when supported, update learning only from reviewed evidence, and close the record with an owner and retention state.

Build the shipping package once

Freeze the packet for every billable or irreversible action. If the address, quantity, ship-from, package, accessorial, or service changes, create a new reviewed revision. Do not let a late response from an older packet overwrite newer truth.

Organize the floor for speed without losing proof

• One queue and ownerUse the exact app states order_received, assembling, packed, ready_for_pickup, shipped, delivered, billing_review, closed, and exception. Assigned, picking, held, verified, and booked may be merchant-local checkpoints, but they never replace the exact source state. A person owns the next action.
• Work by cutoff and constraintPrioritize carrier cutoff, appointment, inventory completeness, equipment, special handling, and promised date—not whichever ticket is easiest to reach.
• Stage by shipmentKeep products, materials, documents, and completed units physically separated and labeled so two orders cannot merge.
• Measure at the endRecord dimensions and scale weight after protection, boxing, banding, or palletization. A catalog dimension is not a final package dimension.
• Use two checks for high-risk workA second person verifies SKU/quantity, handling-unit count, condition, labels/BOL, accessorials, and photo evidence for the scope defined by the merchant.
• Hold visiblyDamage, missing inventory, address conflict, pack mismatch, unsafe unit, rate variance, missing document, or ambiguous booking produces a named hold. It does not disappear into a note.
• Close the handoffRecord driver/carrier, pickup time, unit count, signed document or reference, tracking/PRO, and operator. A printed label alone is not proof of pickup.

Book, label, and tender the verified shipment

1. Confirm authorityOnly the named role can create a billable booking. Confirm the connector identity, credential scope, account, merchant, and current shipment revision.
2. Compare appropriate servicesUse the verified origin, destination, handling units, mode, class where applicable, declared value, accessorials, timing, and merchant service rules. Do not select on rate alone.
3. Tender exactly onceUse one durable action record and idempotency key. A timeout or ambiguous response is reconciled against the same provider before any retry or alternate booking.
4. Verify the resultRead back carrier, service, booking/PRO/tracking, pickup, price where returned, and document references. A success screen without a durable receipt is not enough.
5. Print and inspectPrint the packing slip and any connector-generated labels. Obtain the BOL through the approved carrier/TMS workflow unless a named, tested BOL connector has been accepted; record its reference in the private operations system. Inspect legibility, barcode, unit sequence, address, service and old-label removal; record reprints and voids.
6. Complete pickupConfirm dock readiness, equipment, appointment/window, carrier arrival, handling-unit count, signed handoff, and tracking activation.

Track the promise, not just the scan

• Expected deliveryStore the date or window as an estimate with its source and last update. Do not present an estimate as a guarantee.
• MilestonesBooked, picked up, in transit, appointment needed, out for delivery, delivered, exception, refused, damaged, returned, or unknown should each have occurred and received times.
• Exception ownershipAssign appointment, delay, address, damage, shortage, loss, refusal, carrier, or recipient-action exceptions with the next update time.
• Customer communicationWhen a connector is configured, send useful event-driven updates with preferences, frequency caps, failure receipts, and suppression. Do not send a stream of raw scans.
• Proof of deliveryRetain only the approved delivery reference or evidence needed for service and claims; restrict signatures/photos and apply retention/deletion rules.
• Final billMatch carrier invoice to the booked shipment, explain accessorial or weight/class changes, and keep unresolved differences provisional.

Know which path is active

Run the daily fulfillment huddle

1. New and dueReview new orders, carrier cutoffs, promised/expected dates, appointments, priorities, and assignments.
2. Held and agingName owner, issue, next action, deadline, customer impact, and escalation for every hold.
3. Packing and tenderReview inventory, materials, equipment, verified units, documents, booking ambiguity, pickups, and tracking activation.
4. In transit and deliveryReview exceptions, appointments, overdue scans, expected-delivery changes, condition feedback, and damage/claim urgency.
5. Finance and evidenceReview final bills, disputes, claims, missing photos/POD, quote-to-bill variance, and records safe to close.
6. ImproveSelect one repeated source of touch time or error, change one controlled step, and measure the result without weakening verification.

Stop and escalate when the external effect is unclear

Pause the affected shipment or action when a packet revision, tenant/account, address, handling unit, label, BOL, booking, tracking reference, customer message, evidence object, or final bill is ambiguous. Preserve the record and contact the named merchant support owner. Do not send credentials, customer labels, private rates, or unrestricted evidence through the public form or ordinary email.