Carrier labels

A carrier label belongs to a customer order and operating organization. It holds a status, revision, carrier, package weight, tracking number and decision date. The label starts as Draft, can be Submitted for review and then Approved or Rejected. Completed records the later label outcome. A label revision is frozen for the review decision so the reviewer knows which package and carrier details were considered.

• Prepare the packed order. Confirm the order and its line quantities before a label is submitted.
• Review the revision. The reviewer checks carrier, package weight and the order context against the submitted version.
• Keep dispatch separate. A label can be approved without recording a Shipped fulfillment event.

The review decision record carries the source revision, reviewer, decision, reason and operation key. Use it to explain a rejected label as clearly as an approved one. If the package changes after submission, create a new revision and require a fresh decision. The tracking number may help the team connect carrier messages to the order, but the event history records what was actually shipped and delivered.

Agree the packing data staff need before they submit a label and who is allowed to correct it. Define the carrier connection used to issue a label, including how the operation key is passed to the provider and how a timeout is reconciled. A carrier name on the record identifies the intended provider; the provider connection and its response govern the external result. Choose a separate label reviewer so the person preparing a revision does not approve that same revision.

Set a rule for a rejected label: the team should preserve the old decision and prepare a corrected version rather than overwriting its details. Rehearse a late package-weight correction and inspect the new revision. Decide when a label may become Completed and which carrier acknowledgement is needed for that state.

An operator packs a partial order and prepares a label with the carrier and package weight. The label moves from Draft to Submitted. The reviewer sees the order, line quantities and the frozen label revision. If the weight is wrong, the reviewer rejects it with a reason. The operator corrects the package and submits a new revision. The reviewer approves that revision, leaving the first decision intact.

Now simulate a provider timeout. The team inspects the operation receipt and carrier response before trying another issuance. Reusing the same operation key should resolve to the same external effect where the provider supports it. The order should not be marked Shipped just because a label exists. A separate shipping event and line quantity change show dispatch.

• Labels awaiting review — Submitted revisions ready for an independent decision.
• Label status board — Draft, reviewed and completed label work by order and carrier.
• Order review decisions — Reasons and source revisions behind earlier outcomes.

Label review shows the approval path. Allocation to delivery follows the shipment after that decision. Review the integrations for carrier setup.