EM-RTL-05 · Subject model · W-IND
Return, exchange and refund
A customer's request to return goods, its authorization, receipt and inspection, the grading of condition, the disposition of the goods and the refund or exchange given. The original sale and the payment are referenced, not changed.
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
- ReturnAuthorization
- ReturnLine
- ReturnReceipt
- ConditionGrade
- ReturnDisposition
- Refund
- Exchange
Deep research questions
- How is a return linked to the original sale when the receipt is missing?
- Which return policy version applies, the one at purchase or the one at return?
- How is the disposition of the goods kept apart from the refund decision?
Verifiable invariants
- A refund never exceeds the amount paid for the returned lines unless an approved exception is recorded
- Returned quantity per line never exceeds sold quantity
- A disposition is recorded for every received return line
End-to-end acceptance scenario
For a synthetic online order of three items, authorize a return of two, receive one damaged and one resellable, refund one and exchange the other, and show the stock and payment records.
Negative case
A refund is issued as soon as the courier label is created, and the goods never arrive.
Approaches to compare
- schema.org: MerchantReturnPolicy and ReturnAction
- GS1 identification of returned goods and logistic units
- Consumer withdrawal and warranty rules
Candidates in the live catalogue
- WM-ECO-025 · Return / Refund · 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.