{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-eco-020","code":"wm-eco-020-sales-order","url":"https://ver.cy/models/wm-eco-020-sales-order/","name":"Sales Order","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.ECO.ORD"],"industry":["Cross-industry"],"navPath":"NAV.SOC.ECO.ORD","tags":["sales","order","soc.eco.ord"],"facets":{}},"whatItIs":"The sales order as held by the seller: the order record and its lines; the party roles and authority that bind it; the priced, delivery and payment terms it carries; the seller's disposition of the order (acceptance, amendment, rejection, counter-offer); state, change, cancellation and hold control; allocation and despatch linkage; delivered-versus-outstanding accounting; post-delivery claims; and closure. It carries references, bindings and recorded outcomes for neighbouring concerns and never reproduces their lifecycles or enforcement semantics.","purpose":"Give an agent the context needed to understand, create, inspect and operate a seller-side sales order across acceptance, commitment, fulfilment and closure, independent of storage format or interface.","scope":{"in":["Seller-assigned order identity, versioning and line structure","Party roles on the order and the authority under which it was committed or changed","Priced quantities, allowances and charges, currencies, and the delivery and payment terms carried on the order","Seller disposition at header and line level, including counter-offer and conditional acceptance","Order and line state, permitted transitions, holds, blocks and exception paths","Availability promise, allocation and fulfilment schedule lines derived from accepted lines","Despatch linkage to order lines and delivered, outstanding and oversupply quantity accounting","Post-delivery claims recorded against order lines, and order completion and closure","Validation rule and code list bindings with recorded outcomes","Provenance of the inbound order message and separation of event time from ingestion time","Sensitivity classification, disclosable subsets and retention bindings for the order record"],"out":["Buyer-side requisition, approval and procurement budget lifecycle","Invoice, credit note, tax determination and fiscal reporting","Payment instrument issuance, settlement, dunning and credit scoring","Carrier booking, transport documents, customs declarations and physical movement","Inventory ledger balances, replenishment and warehouse location lifecycle","Trade item master, classification and catalogue lifecycle","Party master identity, deduplication and identifier-scheme registration","Quotation negotiation and framework agreement lifecycle","Reverse logistics execution and refund settlement","Execution of validation rules, policy enforcement and audit-trail storage","Revenue recognition and performance-obligation accounting"],"boundaries":[{"neighbor":"Buyer-side purchase order and procurement model","distinction":"The same order document is read from the opposite role. This model begins when the seller receives or captures the order and owns only seller-side disposition, commitment and fulfilment; requisition, approval and buyer budget control stay with the procurement model."},{"neighbor":"Invoice and credit note model","distinction":"Order tax totals and anticipated monetary totals are indicative buyer expectations, not fiscal determinations. The legally binding priced document, tax determination and e-invoicing compliance obligations belong to the invoice model."},{"neighbor":"Despatch, shipment and transport execution model","distinction":"The order holds despatch and consignment references and the delivered, outstanding and oversupply accounting per line. Shipment structure, carrier detail and physical transport execution are owned by the despatch and transport models."},{"neighbor":"Quotation, contract and framework agreement model","distinction":"The order cites the upstream commercial basis and any call-off parameters, but negotiation, agreement lifecycle and term precedence remain with the agreement model."},{"neighbor":"Trade item and trade party master models","distinction":"Order lines and party roles carry scheme-qualified references plus the snapshot actually agreed at order time. Master attribute stewardship and identifier-scheme governance stay with those models."},{"neighbor":"Trade term rule set (delivery terms classifier)","distinction":"The order binds a coded trade term rule to a named place and records the resulting obligation split. The rule set's content, versioning and interpretation are owned by its publisher, and transfer of title falls outside it."},{"neighbor":"Applicable sales law and consumer protection regimes","distinction":"The order records an applicability determination and citation only. Uniform international sales law does not cover consumer sales, so consumer duties come from jurisdictional instruments this model references but does not restate."},{"neighbor":"Records management, data protection and audit models of the adopting Dimension","distinction":"This model declares classification, retention triggers, tombstone content and evidence pointers. Execution of retention, erasure and audit-trail storage and immutability is owned by those models."}]},"distinguishingFeatures":["The seller-side order record across acceptance, commitment, fulfilment and closure.","Acceptance is the only act creating a commercial commitment.","Unlike a purchase order, it is owned by the seller.","Unlike an invoice or shipment, it references these outcomes without owning them."],"structure":{"bundles":[{"id":"order-identity-and-scope","name":"Order Identity and Scope","description":"What a sales order record is, how it is identified, what it points at, and how its lines are structured and addressed.","layers":[{"id":"order-identification-and-references","name":"Identification and Outbound References","description":"Identifiers borne by the sales order and the references that place it inside a wider trade transaction.","findings":[{"id":"order-identifier-set","name":"Order identifier set and authoritative key","description":"The distinct identifiers a sales order carries - the buyer's order document identifier, the seller-assigned sales order identifier, an optional surrogate and buyer cross-references - and which one is authoritative for the seller.","questions":[{"text":"Which identifier is the seller's authoritative master-system key for this order, and which are secondary cross-references?","id":"oid-authoritative-key","kind":"identity"},{"text":"Within which namespace, issuing entity and time window must the order identifier be unique?","id":"oid-uniqueness-scope","kind":"constraint"},{"text":"When neither an authoritative nor a governed identifier exists, what surrogate is minted and by whom?","id":"oid-surrogate-minting","kind":"provenance"},{"text":"How are buyer-supplied references carried so they cannot be mistaken for the seller's own key?","id":"oid-cross-reference-carriage","kind":"interoperability"}]},{"id":"order-document-references","name":"Outbound commercial and supporting document references","description":"References from the sales order to quotations, contracts and framework agreements, catalogues, originating requisitions, prior order versions and supporting attachments.","questions":[{"text":"Which upstream commercial document establishes the terms this order draws on?","id":"odr-upstream-basis","kind":"relationship"},{"text":"How much of a referenced document may be restated on the order, and what governs a conflict between the two?","id":"odr-restatement-rule","kind":"composition"},{"text":"How are supporting attachments referenced and what integrity evidence accompanies them?","id":"odr-attachment-integrity","kind":"evidence"}]}]},{"id":"order-typing-and-line-structure","name":"Typing and Line Structure","description":"Classification of the order as a whole and the compositional structure of its addressable lines.","findings":[{"id":"order-type-and-sales-channel","name":"Order type, buyer segment and commercial pattern","description":"How the order is classified: order type code, sales channel and originating actor, whether the buyer acts as a business or a consumer, and the commercial pattern such as call-off, blanket, consignment or drop-ship.","questions":[{"text":"Which order type code and pinned code list classify this order?","id":"otc-type-code","kind":"classification"},{"text":"Is the buyer acting in a business or consumer capacity, and what evidence supports that determination?","id":"otc-buyer-segment","kind":"decision"},{"text":"What commercial pattern does the order follow and which pattern-specific parameters apply?","id":"otc-commercial-pattern","kind":"classification"},{"text":"Through which sales channel and originating actor did this order reach the seller?","id":"otc-channel-origin","kind":"provenance"}]},{"id":"order-line-structure","name":"Order line and sub-line structure","description":"The compositional structure of order lines: line identity and numbering, sub-lines for kits and bundles, the item reference, and the integrity rules that make line-level state and fulfilment addressable.","questions":[{"text":"How is an individual order line identified so that responses, despatches and claims can address it precisely?","id":"ols-line-identity","kind":"identity"},{"text":"How are kits, bundles and component sub-lines composed beneath a parent line?","id":"ols-sub-line-composition","kind":"composition"},{"text":"How does a line point at the trade item without restating item master data?","id":"ols-item-reference","kind":"relationship"},{"text":"What integrity rule ties the declared line count to the lines actually present?","id":"ols-line-count-integrity","kind":"validation"}]}]}]},{"id":"parties-and-commercial-terms","name":"Trade Parties and Commercial Terms","description":"Who the order binds, who may commit and change it, and the priced, delivery, risk and payment terms it carries.","layers":[{"id":"trade-parties-and-ordering-authority","name":"Party Roles and Ordering Authority","description":"The party roles present on a sales order and the authority under which it was committed and may be amended.","findings":[{"id":"party-roles-on-the-order","name":"Party roles and identification schemes","description":"The distinct roles a party can occupy on one order - buyer customer, seller supplier, originator, accounting customer, delivery party or consignee, invoicee, freight forwarder - and how each is identified under a declared scheme.","questions":[{"text":"Which party roles are populated on this order and which are mandatory under the agreed profile?","id":"pr-role-inventory","kind":"relationship"},{"text":"Under which identifier scheme is each party identified, and is that scheme declared explicitly on the value?","id":"pr-identification-scheme","kind":"identity"},{"text":"What applies when one legal entity occupies several roles, or when a role is delegated to a third party?","id":"pr-multi-role-conflict","kind":"exception"},{"text":"When party details recorded on the order differ from the party master record, which prevails?","id":"pr-snapshot-precedence","kind":"quality"}]},{"id":"ordering-authority-and-mandate","name":"Ordering authority, mandate and signature evidence","description":"The authority basis under which the order was committed: who may place, change or cancel it, the mandate or agreement supporting that, and the signature or approval evidence bound to the order.","questions":[{"text":"Who is authorised to commit the buyer to this order and under what mandate or value ceiling?","id":"oa-commit-authority","kind":"authority"},{"text":"Who may subsequently amend or cancel the order, and does that differ from who placed it?","id":"oa-change-authority","kind":"ownership"},{"text":"What signature or approval evidence is bound to the order and exactly what content does it attest?","id":"oa-signature-scope","kind":"evidence"},{"text":"How is an order handled when authority cannot be established or is later withdrawn?","id":"oa-authority-failure","kind":"exception"}]}]},{"id":"priced-delivery-and-payment-terms","name":"Priced, Delivery and Payment Terms","description":"Quantities, prices and totals carried on the order, the delivery terms bound to it, and the risk, title and payment conditions it references.","findings":[{"id":"quantity-price-and-monetary-terms","name":"Quantity, price, adjustments and monetary totals","description":"Ordered quantity with its unit of measure, net price and price base quantity, line and document allowances and charges, the document, pricing and tax currencies with exchange rates, and the anticipated versus confirmed totals.","questions":[{"text":"In which unit of measure and to what precision is each ordered quantity expressed?","id":"qp-quantity-measure","kind":"measurement"},{"text":"What is the net price, over what base quantity, and after which line-level allowances?","id":"qp-price-basis","kind":"measurement"},{"text":"Which currencies apply to the document, pricing and tax, and what exchange rates are recorded?","id":"qp-currency-and-rate","kind":"constraint"},{"text":"How is a divergence between the buyer's anticipated total and the seller's confirmed total recorded and resolved?","id":"qp-total-divergence","kind":"decision"}]},{"id":"delivery-terms-risk-and-payment","name":"Delivery terms, risk and title basis, and payment conditions","description":"The trade term rule and named place bound to the order, the resulting cost, insurance and clearance split, the recorded basis on which risk and separately title pass, and the payment means, payment terms and credit decision the order references.","questions":[{"text":"Which delivery term rule applies, at which precisely named place, and under which rule set version?","id":"dt-rule-and-place","kind":"spatial"},{"text":"How do cost, insurance and export or import clearance obligations divide between seller and buyer under the chosen rule?","id":"dt-obligation-split","kind":"requirement"},{"text":"At which event does risk of loss pass, and which legal source determines when property in the goods passes?","id":"dt-risk-and-title","kind":"state"},{"text":"Which payment means and terms are stated on the order, and which credit or risk decision gates its acceptance?","id":"dt-payment-and-credit","kind":"requirement"},{"text":"What governs when header delivery terms conflict with line-level instructions or with a framework agreement?","id":"dt-term-precedence","kind":"constraint"}]}]}]},{"id":"order-lifecycle-and-state","name":"Order Lifecycle and State","description":"How a sales order is dispositioned, how header and line state evolve, how change, cancellation and holds are controlled, and which time points must be recorded.","layers":[{"id":"acceptance-and-contract-formation","name":"Acceptance and Contract Formation","description":"The seller's disposition of an incoming order and the evidence that a contract was formed on stated terms.","findings":[{"id":"order-response-disposition","name":"Order response and disposition codes","description":"The seller's response to an order at header level (received, accepted, accepted with amendment, rejected) and line level (added, changed, accepted, not accepted, already delivered), including counter-offers and response sequencing.","questions":[{"text":"What header-level disposition does the seller assert and which pinned code list defines it?","id":"ord-header-disposition","kind":"decision"},{"text":"Which disposition applies to each order line, and under what condition must all lines be restated?","id":"ord-line-disposition","kind":"state"},{"text":"When a response amends quantity, price, item or delivery period, what makes it a counter-offer rather than an acceptance?","id":"ord-counter-offer","kind":"decision"},{"text":"How are multiple responses to one order sequenced, and which is currently effective?","id":"ord-response-sequencing","kind":"lifecycle"}]},{"id":"contract-formation-evidence","name":"Contract formation and confirmation evidence","description":"Which message constituted the offer and which the acceptance, the immutable snapshot of agreed terms retained at that moment, and the durable confirmation issued to the buyer.","questions":[{"text":"Which message constituted the offer and which the acceptance, and at what instants did each occur?","id":"cf-offer-acceptance","kind":"event"},{"text":"What immutable snapshot of agreed terms is retained at the moment of formation?","id":"cf-agreed-snapshot","kind":"evidence"},{"text":"What confirmation was issued to the buyer, through which channel, and was its receipt evidenced?","id":"cf-confirmation-delivery","kind":"provenance"},{"text":"How is a dispute about whether a contract was formed recorded against the order?","id":"cf-formation-dispute","kind":"exception"}]}]},{"id":"state-change-and-exception-control","name":"State, Change and Exception Control","description":"The state vocabulary of an order and its lines, and the controls over amendment, cancellation and blocking conditions.","findings":[{"id":"order-and-line-state-model","name":"Order and line state vocabulary and transitions","description":"The state vocabulary for the order header and for each line, the permitted transitions and terminal states, how header state is derived from mixed line states, and where mapping to external status enumerations is lossy.","questions":[{"text":"Which state vocabulary governs the order header and which governs each individual line?","id":"sm-state-vocabulary","kind":"state"},{"text":"Which transitions are permitted, which are terminal, and what event triggers each?","id":"sm-permitted-transitions","kind":"lifecycle"},{"text":"How is header state derived when lines are in mixed states such as partly despatched and partly cancelled?","id":"sm-header-derivation","kind":"constraint"},{"text":"How does the internal state vocabulary map to externally published order status enumerations, and where is that mapping lossy?","id":"sm-external-mapping","kind":"interoperability"}]},{"id":"change-and-cancellation-control","name":"Change and cancellation control","description":"How a buyer-requested change or cancellation is received, versioned, dispositioned and reflected on committed quantities, including the cut-off beyond which amendment is refused.","questions":[{"text":"What change is requested, against which order version, and on which lines and elements?","id":"cc-change-target","kind":"process"},{"text":"How are successive order versions identified and which version is currently effective?","id":"cc-versioning","kind":"lifecycle"},{"text":"At which fulfilment point does the order become unchangeable, and who may override that?","id":"cc-change-cutoff","kind":"constraint"},{"text":"How is a partial cancellation represented so that the remaining lines stay valid and totals stay consistent?","id":"cc-partial-cancellation","kind":"composition"}]},{"id":"holds-blocks-and-exceptions","name":"Holds, blocks and exception handling","description":"Conditions that suspend progression of an order or line - credit hold, stock exception, screening block, validation failure - recorded as order state with a pointer to the deciding authority rather than as a decision made here.","questions":[{"text":"Which hold or block types may be applied to this order or its lines, and at which scope?","id":"hb-hold-taxonomy","kind":"classification"},{"text":"Which model or authority decided the hold, and where is that decision evidenced?","id":"hb-decision-owner","kind":"ownership"},{"text":"What conditions release a hold, who may release it, and within what maximum duration?","id":"hb-release-conditions","kind":"process"},{"text":"What effect does an active hold have on allocated stock and on promised delivery dates?","id":"hb-commitment-effect","kind":"state"}]}]},{"id":"time-points-and-commitments","name":"Time Points and Service Commitments","description":"The instants and periods a sales order must record and the delivery commitment derived from them.","findings":[{"id":"order-time-points-and-commitments","name":"Order time points, clock rules and delivery commitment","description":"The distinct time points on a sales order - issue, receipt, acceptance, requested and promised delivery periods, validity, despatch and delivery - and the clock rules that make them comparable and auditable.","questions":[{"text":"Which distinct time points must this order record, and which of them are mandatory?","id":"tp-point-inventory","kind":"temporal"},{"text":"Where do event time and observation or ingestion time diverge, and are both retained?","id":"tp-event-versus-ingestion","kind":"provenance"},{"text":"In which format and with what offset are instants recorded, and how are date-only values kept distinct?","id":"tp-format-rule","kind":"constraint"},{"text":"How does the requested delivery period differ from the promised period, and which one binds?","id":"tp-requested-versus-promised","kind":"requirement"},{"text":"What happens to an order whose validity period expires before any acceptance is issued?","id":"tp-validity-expiry","kind":"lifecycle"}]}]}]},{"id":"fulfilment-and-delivery","name":"Fulfilment and Delivery","description":"How accepted lines are sourced, promised and scheduled, how despatch is linked back to lines, and how delivered, outstanding, disputed and returned quantities resolve into closure.","layers":[{"id":"allocation-and-despatch","name":"Allocation, Scheduling and Despatch Linkage","description":"The seller's commitment of supply to accepted lines and the linkage from those lines to despatch events.","findings":[{"id":"availability-allocation-and-schedule","name":"Availability promise, allocation and fulfilment schedule","description":"How available supply is promised and allocated to accepted lines, how substitutions and splits are recorded, from which location each portion ships, and how competing claims on the same stock are resolved.","questions":[{"text":"On what availability basis was the delivery promise made, and when was it computed?","id":"al-promise-basis","kind":"measurement"},{"text":"What quantity is allocated to this line, from which sourcing location, and is that allocation firm or provisional?","id":"al-allocation-firmness","kind":"state"},{"text":"Under what conditions may an item be substituted, and how is the replacement recorded against the original line?","id":"al-substitution-permission","kind":"decision"},{"text":"Is partial shipment permitted, and how are competing claims on the same stock between orders resolved and recorded?","id":"al-split-and-contention","kind":"exception"}]},{"id":"despatch-and-shipment-linkage","name":"Despatch and shipment linkage","description":"How a despatch event binds to specific order lines: despatch advice reference at header or line level, shipment and consignment identifiers, logistic unit keys, and any lot, serial or expiry data carried at line level.","questions":[{"text":"How does each despatch line reference the originating order and line, including when one despatch covers several orders?","id":"ds-order-linkage","kind":"relationship"},{"text":"Which shipment, consignment and logistic unit identifiers are recorded, and under which schemes?","id":"ds-shipment-keys","kind":"identity"},{"text":"What lot, serial, expiry or best-before data is recorded for despatched items, and for what purpose?","id":"ds-instance-data","kind":"provenance"},{"text":"How is a despatch handled when no order line reference exists, and what placeholder convention applies?","id":"ds-unmatched-despatch","kind":"exception"}]}]},{"id":"delivery-outcome-and-closure","name":"Delivery Outcome, Claims and Closure","description":"Quantity accounting against ordered lines, discrepancy resolution, post-delivery claims, and the criteria that close an order.","findings":[{"id":"delivered-outstanding-and-discrepancy","name":"Delivered, outstanding and discrepancy accounting","description":"The quantity accounting that tracks delivered, outstanding and over-supplied quantities per line, the reason for any shortfall, and reconciliation against the buyer's confirmed receipt.","questions":[{"text":"For each line, what quantity is delivered, what remains outstanding, and what was supplied in excess?","id":"dd-quantity-accounting","kind":"measurement"},{"text":"Why is a quantity outstanding, and does a further delivery remain planned for it?","id":"dd-shortfall-reason","kind":"exception"},{"text":"How is the buyer's confirmed receipt reconciled against what the seller despatched?","id":"dd-receipt-reconciliation","kind":"validation"},{"text":"Who decides the disposition of a confirmed discrepancy and which outcomes are permitted?","id":"dd-discrepancy-disposition","kind":"decision"}]},{"id":"claims-and-order-closure","name":"Post-delivery claims and order closure","description":"Return requests, statutory withdrawal in consumer sales and non-conformity notices recorded against delivered lines, and the criteria and authority that close the order.","questions":[{"text":"What type of post-delivery claim is raised, against which lines and quantities, and within what period from which triggering event?","id":"cl-claim-type-and-window","kind":"classification"},{"text":"What authorisation must exist before goods may be returned, and who issues it?","id":"cl-claim-authorisation","kind":"authority"},{"text":"Which conditions must hold for the order to count as complete rather than merely despatched?","id":"cl-completion-criteria","kind":"constraint"},{"text":"How are residual outstanding quantities treated at closure, and under what conditions may a closed order reopen?","id":"cl-residual-and-reopening","kind":"lifecycle"},{"text":"Which parts of a return are recorded here and which are executed by the logistics and settlement models?","id":"cl-execution-boundary","kind":"interoperability"}]}]}]},{"id":"control-evidence-and-compliance","name":"Control, Evidence and Compliance","description":"The rule and code list bindings applied to an order, the provenance of its record, and the jurisdictional obligations attached to it.","layers":[{"id":"validation-and-conformance","name":"Validation and Conformance Bindings","description":"Rule sets, code list pinning and the recorded outcome of validating a sales order or response.","findings":[{"id":"validation-and-code-list-conformance","name":"Validation rule bindings and code list conformance","description":"Which rule sets and code list versions a sales order is validated against, how outcomes are recorded, who executes validation, and what disposition follows a failure.","questions":[{"text":"Which rule sets and specification versions is this order validated against?","id":"vc-rule-binding","kind":"validation"},{"text":"Which code lists constrain coded values on the order, and which versions are pinned?","id":"vc-code-list-pinning","kind":"interoperability"},{"text":"How is a validation outcome recorded, including severity and the locator of the failing element?","id":"vc-outcome-record","kind":"quality"},{"text":"Which component executes validation, and where does this model's responsibility end?","id":"vc-execution-owner","kind":"ownership"},{"text":"What is the disposition of an order that fails validation, and may it be corrected in place?","id":"vc-failure-disposition","kind":"exception"}]}]},{"id":"provenance-and-obligations","name":"Provenance and Jurisdictional Obligations","description":"Where the order record came from, and which legal regime and obligations attach to it.","findings":[{"id":"order-provenance-and-message-trail","name":"Order provenance and inbound message trail","description":"The origin of the order record: inbound channel and capture method, syntax and version, sender and receiver identifiers, envelope reference, payload digest, and the separation of issue time from receipt time.","questions":[{"text":"Through which channel, capture method and syntax did this order enter the seller's system?","id":"pv-origin-channel","kind":"provenance"},{"text":"Which sender and receiver identifiers and envelope references accompany the inbound message?","id":"pv-sender-receiver","kind":"identity"},{"text":"What transformation was applied between the received message and the stored record, and is the original retained?","id":"pv-transformation-trail","kind":"evidence"},{"text":"Which provenance facts does this model emit, and which audit-trail guarantees are owned elsewhere?","id":"pv-audit-boundary","kind":"ownership"}]},{"id":"jurisdictional-sales-obligations","name":"Applicable legal regime and jurisdictional obligations","description":"The determination of which sales-law regime governs the order, whether uniform international sales law applies or is excluded, and which consumer-facing duties attach - recorded as citable bindings, with unevidenced obligations flagged.","questions":[{"text":"Which legal regime governs this sale, and on what basis was that determined?","id":"js-applicable-regime","kind":"authority"},{"text":"Does uniform international sales law apply here, or is it excluded by the parties or by the nature of the sale?","id":"js-uniform-law-applicability","kind":"constraint"},{"text":"Which consumer-facing duties attach before and after order placement in the applicable jurisdiction?","id":"js-consumer-duties","kind":"requirement"},{"text":"Which asserted obligations lack a primary legal source and must be re-grounded before they are relied on?","id":"js-evidence-gap","kind":"evidence"}]}]}]},{"id":"interoperability-and-record-governance","name":"Interoperability and Record Governance","description":"How the order binds to external syntaxes and profiles, how repeated interchange is controlled, and how the record itself is classified and retained.","layers":[{"id":"alignment-and-interchange","name":"Standard Alignment and Interchange Control","description":"Declared external alignments and the control of repeated, duplicated or out-of-order interchange.","findings":[{"id":"standard-alignment-and-profile-binding","name":"Standard alignment and profile binding","description":"Declared alignments to external order vocabularies and syntaxes, the customization and profile identifiers that pin an agreed subset, the evidence required before a conformance claim, and where mapping loses meaning.","questions":[{"text":"To which external order vocabularies and syntaxes is this model aligned, and at which versions?","id":"sa-alignment-inventory","kind":"interoperability"},{"text":"Which customization and profile identifiers pin the agreed subset for a given exchange?","id":"sa-profile-pinning","kind":"constraint"},{"text":"What evidence must exist before conformance to an external specification may be asserted?","id":"sa-conformance-evidence","kind":"evidence"},{"text":"Where does mapping between aligned specifications lose or distort meaning, and what mitigates it?","id":"sa-mapping-loss","kind":"quality"}]},{"id":"interchange-idempotency-and-duplicates","name":"Idempotency, sequencing and duplicate control","description":"How repeated, out-of-order or duplicated order, change, cancellation and response messages are recognised and reconciled to a single sales order record without re-triggering commitments.","questions":[{"text":"Which key determines that two inbound messages describe the same order or the same response?","id":"ii-idempotency-key","kind":"identity"},{"text":"How are messages ordered when issue instants collide or arrive out of sequence?","id":"ii-ordering-rule","kind":"temporal"},{"text":"When several responses or versions exist, which one is effective and how is that determined?","id":"ii-effective-record","kind":"state"},{"text":"What prevents a replayed message from re-triggering allocation, despatch or acceptance?","id":"ii-replay-safety","kind":"security"}]}]},{"id":"confidentiality-and-retention","name":"Record Confidentiality and Retention","description":"Sensitivity classification of order content and the retention and disposition bindings that apply to the seller's own order records.","findings":[{"id":"order-confidentiality-and-retention","name":"Order record sensitivity, disclosure and retention bindings","description":"How order content is classified for sensitivity, which subset may be disclosed to fulfilment partners, which retention rules apply and from which trigger, and how erasure requests reconcile with retention obligations.","questions":[{"text":"Which sensitivity classes apply to elements of the order, including personal data in consumer orders?","id":"cr-sensitivity-classes","kind":"privacy"},{"text":"Which subset of order content may be disclosed to a carrier, warehouse or drop-ship supplier?","id":"cr-partner-disclosure","kind":"access"},{"text":"How long must each class of order record be retained and from which triggering event does that period run?","id":"cr-retention-trigger","kind":"retention"},{"text":"Who executes disposition when retention expires, and what tombstone remains behind?","id":"cr-disposition-execution","kind":"ownership"},{"text":"How is an erasure request reconciled with an open statutory retention obligation on the same order?","id":"cr-erasure-conflict","kind":"exception"}]}]}]}]},"agentConduct":{"may":["Capture and validate an incoming order.","Check availability and propose a schedule.","Record despatch against order lines.","Reconcile delivery and close the order."],"mustNot":["Allocate stock or start fulfilment before acceptance.","Accept an order outside delegated authority.","Pass more personal data to fulfilment partners than needed.","Ignore consumer withdrawal rights recorded for the order.","Claim conformance to a specification without evidence."],"requiresHuman":["Accepting non-standard terms or prices.","Refusing or cancelling an order with legal effect for a consumer."]},"ethics":{"considerations":["Consumers have statutory rights such as withdrawal and clear pricing.","Orders contain personal data such as addresses that must be minimised and protected."],"affectedParties":["Customers including consumers","Seller staff","Fulfilment and carrier partners"]},"owners":{"steward":"Name a single accountable owner and a named deputy for the sales order package, because acceptance decisions create binding commercial commitments.","roles":[{"name":"Sales order model steward","responsibilities":["Maintains scope, boundary notes, out-of-scope list and composition links","Reviews and re-pins external specification and code list versions on a recorded schedule","Adjudicates whether a proposed element belongs in this model or in a sibling model"]},{"name":"Order acceptance authority","responsibilities":["Issues header and line dispositions, including rejection and counter-offer","Authorises overrides of the change cut-off and records the justification","Owns the evidence that a contract was formed on stated terms"]},{"name":"Fulfilment planner","responsibilities":["Commits availability and produces fulfilment schedule lines","Decides substitutions and split shipments within declared permissions","Records short-close and carry-forward decisions on residual quantities"]},{"name":"Interoperability custodian","responsibilities":["Maintains syntax and profile bindings and pinned code list versions","Registers alignment entries and records known mapping loss","Publishes the validation outcomes that support any conformance claim"]},{"name":"Records and data protection custodian","responsibilities":["Classifies order content sensitivity and maintains disclosable subsets per partner role","Applies retention triggers and requests disposition under the adopting Dimension's policy","Reconciles erasure requests against open statutory and contractual retention obligations"]}],"masterSystems":[]},"relations":[{"target":"WM-ECO-006","type":"child","note":"Positions the seller-side sales order as one phase of the broader trade transaction held by the parent model, which owns the end-to-end buy-ship-pay arc and the cross-phase agreement and party context."},{"target":"Buyer-side purchase order and procurement model","type":"aligned","note":"The same order document is read from the opposite role, so element-for-element alignment is required; requisition, approval and buyer budget lifecycle remain entirely with the procurement model."},{"target":"Invoice and credit note model","type":"references","note":"The order carries indicative tax and anticipated totals and points at billing documents; tax determination, the fiscal document and its compliance obligations stay with the invoice model."},{"target":"Despatch, shipment and transport execution model","type":"references","note":"The order holds despatch and consignment references plus delivered and outstanding accounting; carrier booking, transport documents and physical movement remain with the shipment model."},{"target":"Trade party master model","type":"references","note":"Party roles resolve to master identities under declared schemes; party lifecycle, deduplication and scheme registration remain with the party model."},{"target":"Trade item and catalogue model","type":"references","note":"Order lines reference trade items by seller and standard identifiers; item attributes, classification and catalogue lifecycle remain with the item model."},{"target":"Quotation, contract and framework agreement model","type":"references","note":"The order cites its upstream commercial basis and any call-off parameters; negotiation, agreement lifecycle and term precedence remain with the agreement model."},{"target":"Payment, credit and settlement model","type":"references","note":"The order carries proposed payment means and terms and a credit decision reference; scoring, instrument issuance, settlement and dunning remain with the payment model, which owns their evaluation and enforcement."},{"target":"Inventory and availability model","type":"references","note":"Availability promises and allocations reference stock positions and sourcing locations; ledger balances, replenishment and location lifecycle remain with the inventory model."},{"target":"Validation rule-set and conformance model","type":"references","note":"Supplies rule sets, pinned code list versions and the component that evaluates them; this model stores only the binding and the recorded outcome and never owns rule evaluation or enforcement."},{"target":"Incoterms trade term rule set","type":"aligned","note":"Delivery terms bind to a published trade term rule and named place with its cost, insurance and clearance split; the rule set's content and versioning stay with its publisher, and transfer of title falls outside it."},{"target":"Schema.org Order and OrderStatus vocabulary","type":"aligned","note":"Provides a public web vocabulary for consumer-facing order publication; the mapping is partial and its status enumeration is not adopted as this model's internal state machine."},{"target":"RFC 3339 timestamp profile","type":"aligned","note":"Fixes serialisation of every instant recorded here, including the explicit offset requirement and the unknown-offset convention; the profile is owned by its publishing body."},{"target":"Uniform international sales law regime","type":"references","note":"Supplies default rules on offer and acceptance, delivery, conformity and passing of risk where applicable; applicability determination, exclusions and remedies adjudication remain outside this model."},{"target":"Records management, data protection and audit models of the adopting Dimension","type":"references","note":"Own execution of retention, erasure, tombstoning and audit-trail storage and immutability for order records; this model declares classification, trigger events, tombstone content and evidence pointers only."},{"target":"Buyer-side purchase order and procurement model","type":"neighbor","note":"The same order document is read from the opposite role. This model begins when the seller receives or captures the order and owns only seller-side disposition, commitment and fulfilment; requisition, approval and buyer budget control stay with the procurement model."},{"target":"Invoice and credit note model","type":"neighbor","note":"Order tax totals and anticipated monetary totals are indicative buyer expectations, not fiscal determinations. The legally binding priced document, tax determination and e-invoicing compliance obligations belong to the invoice model."},{"target":"Despatch, shipment and transport execution model","type":"neighbor","note":"The order holds despatch and consignment references and the delivered, outstanding and oversupply accounting per line. Shipment structure, carrier detail and physical transport execution are owned by the despatch and transport models."},{"target":"Quotation, contract and framework agreement model","type":"neighbor","note":"The order cites the upstream commercial basis and any call-off parameters, but negotiation, agreement lifecycle and term precedence remain with the agreement model."},{"target":"Trade item and trade party master models","type":"neighbor","note":"Order lines and party roles carry scheme-qualified references plus the snapshot actually agreed at order time. Master attribute stewardship and identifier-scheme governance stay with those models."},{"target":"Trade term rule set (delivery terms classifier)","type":"neighbor","note":"The order binds a coded trade term rule to a named place and records the resulting obligation split. The rule set's content, versioning and interpretation are owned by its publisher, and transfer of title falls outside it."},{"target":"Applicable sales law and consumer protection regimes","type":"neighbor","note":"The order records an applicability determination and citation only. Uniform international sales law does not cover consumer sales, so consumer duties come from jurisdictional instruments this model references but does not restate."},{"target":"Records management, data protection and audit models of the adopting Dimension","type":"neighbor","note":"This model declares classification, retention triggers, tombstone content and evidence pointers. Execution of retention, erasure and audit-trail storage and immutability is owned by those models."},{"target":"WM-ECO-006","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier: the sales order identifier assigned by the seller's system of record for orders, scoped to the issuing seller legal entity, is the primary key for every artifact in this model.","Governed global identifier or IRI: a scheme-qualified identifier issued under an external governed scheme - such as a party, location or trade item key resolved under its declared scheme - or a dereferenceable IRI minted in the owning Dimension's registered namespace.","UUID or ULID assigned by the adopting Dimension where neither an authoritative master-system identifier nor a governed global identifier exists, recorded together with its minting authority and minting instant.","Buyer order references, customer references and accounting cost codes are cross-references only and must never be promoted to a primary key. A date, a delivery period, an issue date or a version effective-from instant is never an identifier."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A sales order has a seller-assigned identifier, a customer, lines, prices, delivery terms and an acceptance state.","Often confused with a purchase order, a quotation, an invoice and a shipment."]},"capabilities":{"applicability":"required","items":["Capture sales order: Record an inbound buyer order or a seller-captured order as a sales order, assign the seller's authoritative identifier and retain inbound provenance.","Validate sales order: Bind an order or response to a named rule set and pinned code list versions and record the resulting outcome; execution is performed by the referenced validation component.","Issue order disposition: Issue the seller's response to an order - acknowledgement, acceptance, acceptance with amendment, rejection or counter-offer - at header and line level.","Confirm contract formation: Record formation of the contract and issue the durable confirmation of agreed terms to the buyer.","Apply order change or cancellation: Record a buyer-requested amendment or cancellation against a target order version, disposition it, and produce the resulting effective version.","Commit availability and schedule: Promise and allocate supply to accepted order lines and derive the fulfilment schedule lines.","Record despatch against order: Bind a despatch event to specific order lines and update delivered and outstanding quantity accounting.","Reconcile delivery and close order: Compare received against despatched quantities, record discrepancies and their disposition, resolve residual quantities and close the order."]},"hazards":{"applicability":"required","items":["Overselling from commitments before acceptance.","Consumer law breaches.","Personal data leaks to partners."]},"interfaces":{"applicability":"required","items":["UBL 2 Order and OrderResponse.","UN/EDIFACT ORDERS and ORDRSP.","GS1 GTIN and GLN.","Incoterms 2020."]},"context":{"applicability":"required","items":["The ordering and despatch profiles are European public-procurement oriented and authoritative only within that network; their disposition codes and business rules should not be assumed elsewhere.","The uniform international sales law instrument applies only to international business-to-business sales between Contracting States, is subject to party exclusion and to state reservations, and expressly does not cover consumer sales.","The e-invoicing compliance framework cited binds EU public contracting authorities; the order-versus-invoice boundary it evidences is argued to generalise, but the obligation itself does not.","Consumer distance-selling duties - pre-contractual information, explicit order acknowledgement, durable-medium confirmation, withdrawal periods and statutory delivery deadlines - are jurisdiction-specific and carried here only as flagged bindings without primary textual support.","North American ordering practice, which relies on a different transaction set family, is not represented; adopters in that region should expect additional identity and acknowledgement semantics."]}},"sources":[{"title":"Universal Business Language Version 2.4","url":"https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html","note":"OASIS Open"},{"title":"UBL-Order-2.4.xsd (UBL 2.4 Order document schema)","url":"https://docs.oasis-open.org/ubl/os-UBL-2.4/xsd/maindoc/UBL-Order-2.4.xsd","note":"OASIS Open"},{"title":"UBL-OrderResponse-2.4.xsd (UBL 2.4 Order Response document schema)","url":"https://docs.oasis-open.org/ubl/os-UBL-2.4/xsd/maindoc/UBL-OrderResponse-2.4.xsd","note":"OASIS Open"},{"title":"Peppol BIS Ordering 3.3","url":"https://docs.peppol.eu/poacc/upgrade-3/profiles/28-ordering/","note":"OpenPeppol AISBL"},{"title":"Peppol BIS Despatch Advice 3.1","url":"https://docs.peppol.eu/poacc/upgrade-3/profiles/30-despatchadvice/","note":"OpenPeppol AISBL"},{"title":"Order - Schema.org Type","url":"https://schema.org/Order","note":"Schema.org Community Group"},{"title":"OrderStatus - Schema.org Type","url":"https://www.schema.org/OrderStatus","note":"Schema.org Community Group"},{"title":"RFC 3339: Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"},{"title":"United Nations Convention on Contracts for the International Sale of Goods (CISG)","url":"https://uncitral.un.org/en/texts/salegoods/conventions/sale_of_goods/cisg","note":"United Nations Commission on International Trade Law (UNCITRAL)"},{"title":"Incoterms 2020 rules","url":"https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/","note":"International Chamber of Commerce"},{"title":"UN/CEFACT Web Vocabularies (Buy-Ship-Pay)","url":"https://vocabulary.uncefact.org/","note":"United Nations Economic Commission for Europe (UN/CEFACT)"},{"title":"EN 16931 compliance","url":"https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467108950/EN+16931+compliance","note":"European Commission, DIGITAL Building Blocks (eInvoicing)"}],"openQuestions":["Retry the eight declared retrieval failures that were caused by transport errors rather than absence: UN/EDIFACT ORDERS and ORDRSP directories with UNTDID code lists 1001, 1225 and 4343 (HTTP 403), ASC X12 850, 855, 860, 865, 869 and 870, GS1 EDI Order and General Specifications identification keys (HTTP 403), and EPCIS 2.0 with the Core Business Vocabulary (unparsable binary payload).","Retrieve primary consumer-protection legislative text to close the single checklist gap, so that pre-contractual information, explicit order acknowledgement, durable-medium confirmation, withdrawal periods and statutory delivery deadlines can be grounded rather than carried as flagged bindings.","Deepen access, privacy, security and retention coverage: the 100-question set contains one access, one privacy, one retention and one security question for an aggregate that carries consumer personal data, signature evidence, payment terms and a partner disclosure subset. Determine whether the thinness is a tagging artefact or genuine under-coverage before promotion.","Resolve the inventory and availability boundary: retrieve a primary availability-to-promise or allocation source so that promise basis, allocation firmness, substitution and cross-order contention can be attributed to a named neighbouring model rather than absorbed by the order.","Register the neighbouring models by ID — invoice, despatch and transport, procurement, quotation and framework agreement, trade item and party master, inventory, payment and credit, returns, records management — and populate the relationship contract, aligned_model_ids and the composition role beneath parent WM-ECO-006.","Add hold application and release, and post-delivery claim capture, as functions in a follow-up pass; both were identified here but could not be added under the single-provider waiver rules.","Ground order status inquiry and status report messaging patterns, and the subscription, standing-order and service-order specialisations, which the result acknowledges are only lightly covered by the commercial pattern classification.","No primary retrieval of UN/EDIFACT ORDERS and ORDRSP message directories or UNTDID code lists 1001, 1225 and 4343; the UNECE service host returned HTTP 403. Disposition semantics are grounded via the Peppol profile instead.","No primary retrieval of ASC X12 850, 855, 860, 865, 869 or 870; the published transaction set page did not expose the supply chain subcommittee entries, leaving North American EDI ordering practice unrepresented.","No primary retrieval of GS1 EDI Order or the GS1 General Specifications identification keys; gs1.org returned HTTP 403. GS1 key usage (GTIN, GLN, SSCC, GSIN, GINC) is evidenced only indirectly through the Peppol despatch advice profile.","No primary retrieval of EPCIS 2.0 or the Core Business Vocabulary; the reference host served an unparsable binary. Traceability linkage is grounded only through line-level lot, serial and expiry data in the despatch profile.","No primary retrieval of consumer-protection legislative text; the EU legal database returned an empty document body, so consumer duties are carried as flagged bindings only.","Revenue recognition and performance-obligation accounting are entirely absent and belong to a finance model.","Subscription, recurring and standing-order specialisations, and service orders for non-goods deliverables, are only lightly covered by the commercial pattern classification.","Order status inquiry and order status report messaging patterns are not grounded in any retrieved primary source."],"resources":{"spec":"/models/wm-eco-020-sales-order/spec.yaml","agents":"/models/wm-eco-020-sales-order/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-020"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-eco-020-sales-order/spec.yaml","ver-cy/world-models/card-supplements/wm-eco-020-sales-order.json"],"providers":["Claude"],"researchStatus":"reviewable-draft","generatedAt":"2026-08-29T20:03:09Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}