EM-RTL-03 · Subject model · W-IND
Price and promotion rule
Regular prices, markdowns and promotion rules by item, location, channel and customer group, with validity, mechanics, eligibility and the price actually charged. Campaign planning and attribution belong to the sales and marketing contour.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- PriceList
- ItemPrice
- Markdown
- PromotionRule
- PromotionEligibility
- AppliedPriceAdjustment
Deep research questions
- How is the shelf or displayed price reconciled with the price charged at checkout?
- Which promotions may stack, and in which order are they applied?
- How is a prior reference price kept for price reduction claims?
Verifiable invariants
- At one time, location and channel an item has exactly one regular price
- Each applied adjustment references the rule that produced it
- A price reduction claim references a recorded prior price
End-to-end acceptance scenario
For a synthetic item, set a regular price, a markdown and a buy two get one promotion with an extra discount for loyalty members, process three baskets, and show for each line which rules applied.
Negative case
A promotion is set up with an end date only in the marketing calendar, so the checkout keeps applying the discount after the promotion ends.
Approaches to compare
- schema.org: PriceSpecification and Offer
- UN/CEFACT: price and allowance elements in trade documents
- Consumer price indication and price reduction rules
Candidates in the live catalogue
- WM-ECO-002 · Price / Valuation · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ECO-028 · Advertisement / Promotion · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.