LAB / 01 — DOMAIN
A parcel is a record.
Its state has meaning.
The model separates a package from the shipment that later contains it. A hold, payment and tracking event each belong to a specific workflow.
Package lifecycle
| State | Meaning |
|---|---|
expected | A customer pre-alert exists; the parcel has not been received into storage. |
received | The warehouse has received the parcel; storage or matching is incomplete. |
matched | The parcel is associated with its customer or pre-alert. |
stored | The parcel is stored and available for services or shipment selection. |
service_requested | An optional warehouse service is in progress. |
service_completed | The service finished; the parcel can return to the storage workflow. |
selected_for_shipment | The parcel is selected for a shipment draft. |
included_in_shipment | The parcel is linked to a shipment and cannot be freely selected. |
hold | An operational or compliance review blocks the parcel. |
returned / discarded | Terminal handling recorded by an authorized operator. |
A missing detail is a task, not a guess.
- Intake. Associate the customer, pre-alert and receiving event.
- Exception. Identify the missing value or document and the person responsible.
- Review. Have an authorized operator accept or correct the information.
- Resolution. Record the decision and update the customer from the reviewed context.
This sequence is illustrated on the product walkthrough. It does not automatically clear a compliance hold or authorize dispatch.
Shipment lifecycle
created pending_declaration ready_for_packing packed measured priced awaiting_payment paid ready_for_dispatch dispatched
Tracking may then report sorting, transit and delivery. Returns, holds, failed payments and cancellations require their own decisions; the happy path is not the whole process.
This is a human-readable summary of the private Core workflow documentation, reviewed October 27, 2026. It is not a live API contract or a promise that every transition is enabled in a customer deployment.