Sales Order

A customer's order for one or more products, scheduled to a ship date, with shipping and payment attached.

Compile note. Confirmed: orders have a NextShipDate, reach ship-to state via DestinationContact → MailingAddress, and use a W-prefixed document number for web orders. The status lifecycle and built-in actions below are ‹confirm› — read the real state machine and action set from the live model.

Fields

Field Type Description
Id GUID Unique identifier.
DocumentNumber text Human-readable order number. Web orders are W-prefixed.
Customer relation → Customer The account that placed the order. ‹confirm›
Status enum Current lifecycle state (see below). ‹confirm›
NextShipDate date Ship date the order is scheduled/fulfilled against. Primary filter field for ship-date queries.
DestinationContact relation → Contact Ship-to contact; expand → MailingAddress for the state/address.
ShippingMethod relation → Shipping Method Carrier/service (e.g., USPS 5c4ce365-0bb4-4d90-aa2f-091636bffbe8).
PackageType relation → Package Type Container/configuration used. ‹confirm›
Lines collection → Order Line Products and quantities on the order. ‹confirm›
PriceLevel relation → Price Level Price level applied (from the customer). ‹confirm›
Total currency Order total. ‹confirm›
…additional fields ‹confirm› Full field list to be read from the live model.

Order line (sub-entity)

Field Type Description
Product relation → Product Chick type ordered. ‹confirm›
Quantity integer Number of chicks. ‹confirm›
UnitPrice currency Price per unit at the applied price level. ‹confirm›
…additional fields ‹confirm› To be read from the live model.

Status lifecycle

‹confirm the real states and transitions›. Placeholder shape:

Draft ──▶ Confirmed ──▶ Scheduled ──▶ Shipped ──▶ Completed
   └────────────────────────────────▶ Cancelled
Status Meaning
‹confirm› ‹confirm›

Built-in actions

‹confirm the real action set›. Likely candidates to verify:

Web orders