EM-RTL-02 · Subject model · W-IND
Assortment and listing
Which items are offered at which selling locations and channels, for which period, with the listing status, range role and shelf or display placement. Item definitions and stock belong to neighboring contours.
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
- Assortment
- AssortmentVersion
- Listing
- RangeRole
- Planogram
- Delisting
Deep research questions
- How is a listing distinguished from stock availability?
- How are local exceptions to a central assortment recorded?
- What happens to open orders and returns when an item is delisted?
Verifiable invariants
- A listing names the item, the location or channel and the validity period
- A delisted item stays returnable according to the return policy
- Local exceptions reference the central assortment version
End-to-end acceptance scenario
For a synthetic chain of three stores and a web shop, publish a seasonal assortment, add one local exception, delist two items mid-season and keep returns of those items possible.
Negative case
Items with stock in a store are treated as listed there, so discontinued items reappear online when a return comes back.
Approaches to compare
- GS1 Global Data Synchronisation Network: item data between trading partners
- schema.org: Offer and ItemList
- Category management and planogram practice
Candidates in the live catalogue
- WM-OBJ-002 · Product Type / Catalog Item · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-DAT-008 · Data Product / Product Catalog Record · 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.