Order, subscription and consumption right
Order and lines, subscription, changes and the consumer's entitlement. Invoice, payment, software license and usage are kept separate.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 9 questions
Order What the customer ordered and what has been fulfilled.
Order and lines
The order with its lines and the offer version it references.
Order reference
The order tied to a version of the offer and a party.
- Which offer version and price does the order reference?
- Which party placed the order, under which contract?
Line fulfilment
Fulfilment status per line, separate from payment.
- Which lines are delivered, partly delivered or open?
- Is any line marked delivered only because an invoice was paid?
Subscription and entitlement Recurring commitments and the right to use.
Subscription lifecycle
Start, changes, suspension and renewal over time.
Subscription state
The current plan and its history of changes.
- Which plan is active, and since when?
- How was a mid-cycle plan change applied?
- Was a renewal at a new price recorded without rewriting past periods?
Entitlement
The right to use, limited by subject and period.
Entitlement scope
Who may use what, and for which period.
- Which subject and period does the entitlement cover?
- How does the entitlement compare with actual recorded usage?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseCOM
- Industry
- Cross-industry
- Tags
- EM-COM-03W2subjectOrderOrderLineSubscriptionEntitlementRenewal
What it is Filled
Order and lines, subscription, changes and the consumer's entitlement. Invoice, payment, software license and usage are kept separate.
Why it exists Filled
Order and lines, subscription, changes and the consumer's entitlement. Invoice, payment, software license and usage are kept separate.
Distinguishing features Filled
- An order references a specific version of an offer, and its lines are fulfilled independently.
- A subscription can exist without the next payment having been made.
- An entitlement is a right to use limited by subject and period, separate from actual usage.
- Distinct from invoice, payment and software licence, which are kept as separate records.
What robots and AI may and may not do Filled
Must not
- Treat payment of an invoice as delivery of every order line.
- Rewrite past subscription periods when the price or plan changes.
- Grant an entitlement beyond the subject or period it covers.
- Cancel or suspend a subscription without the required notice or approval.
Only with a human decision
- Suspending or terminating a customer subscription.
- Granting credits or entitlements outside the ordered terms.
May
- Report fulfilment status per order line.
- Compare entitlements with recorded usage and flag gaps.
- Record plan changes and renewals as new dated entries.
Moral aspects Filled
- Customers can suffer financial harm when billing and delivery are confused.
- Silent suspension of services can cut off people from what they paid for.
Who is affected
- Customers and their users
- Order and billing staff
- Service teams
Owners Filled
Steward
The commercial director who answers for customer, supplier and partner relationships.
Master systems
- CRM
- Order management system
- Service desk
Links to other meta-models Filled
neighbor
- EM-COM-01
- EM-FIN-03
- EM-OPS-05
- EM-PRD-01
references
- WM-ECO-020 - conceptual-candidate
- WM-ECO-022 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by order number with line numbers, and subscriptions by subscription identifier.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- An order record lists lines, an offer version and a fulfilment status per line.
- Often confused with the invoice issued for it or with the payment received.
Capabilities and actions required Filled
- Partial delivery, suspension and renewal can be tracked without rewriting history.
- Entitlements can be checked against usage for compliance and billing.
Hazards and failure modes required Filled
- Marking undelivered lines as fulfilled because the invoice was paid.
- Retroactive price changes that alter past periods.
- Entitlements left active after cancellation.
Standards and interfaces required Filled
- OASIS UBL Order and Order Response documents.
- TM Forum SID product and customer order entities.
- UN/CEFACT Cross Industry Order message.
Context of use required Filled
- Used in order management, subscription billing and service provisioning.
- Consumer subscriptions are subject to consumer protection rules on renewal and cancellation.
Sources Filled
- TM Forum SID: party/customer/product/service
- OASIS UBL: trade documents and exchange
- CRM/CPQ/order management practice: stages and source boundaries
- OASIS Universal Business Language Version 2.3 - Checked live (HTTP 200) on 2026-10-07.
- OASIS Universal Business Language (UBL) Technical Committee - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to link partial fulfillment to payment?
- How does the right to use differ from actual usage?
- How to apply a mid-cycle plan change?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-com-03/brief.json, ver-cy/world-models/card-supplements/em-com-03.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.