← Back to catalogue
Published

Return / Refund

vr.wm-eco-025 · wm-eco-025-return-refund

Represent a governed return and refund case so agents can distinguish request, eligibility, authorization, reverse movement, inspection, disposition, financial obligation and refund execution without confusing the case with order, fulfilment, shipment, invoice, payment, warranty, recall or dispute masters.

World Models Society, people and institutions SOC.ECO.RET

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Case identity, origin, parties and policy Groups case identity, origin, parties and policy without duplicating authoritative sibling lifecycles.

Case identity, classification and trigger

Groups case identity, classification and trigger for the governed return/refund case.

Case ID, version head, profile, status and master system

Records case id, version head, profile, status and master system as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish case id, version head, profile, status and master system? identity
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of case id, version head, profile, status and master system applies, to what scope, under which rule and authority? spatial
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support case id, version head, profile, status and master system, and what remains unknown or disputed? evidence

Request origin, reason, defect, withdrawal, recall, goodwill and evidence

Records request origin, reason, defect, withdrawal, recall, goodwill and evidence as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish request origin, reason, defect, withdrawal, recall, goodwill and evidence? classification
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of request origin, reason, defect, withdrawal, recall, goodwill and evidence applies, to what scope, under which rule and authority? provenance
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support request origin, reason, defect, withdrawal, recall, goodwill and evidence, and what remains unknown or disputed? quality

Source transaction, parties, roles and authority

Groups source transaction, parties, roles and authority for the governed return/refund case.

Order, contract, fulfilment, delivery, entitlement and payment reference

Records order, contract, fulfilment, delivery, entitlement and payment reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish order, contract, fulfilment, delivery, entitlement and payment reference? relationship
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of order, contract, fulfilment, delivery, entitlement and payment reference applies, to what scope, under which rule and authority? ownership
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support order, contract, fulfilment, delivery, entitlement and payment reference, and what remains unknown or disputed? validation

Claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role

Records claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role? ownership
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role applies, to what scope, under which rule and authority? authority
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role, and what remains unknown or disputed? security
Eligibility, remedy and authorization Groups eligibility, remedy and authorization without duplicating authoritative sibling lifecycles.

Rule version, window, conditions and exceptions

Groups rule version, window, conditions and exceptions for the governed return/refund case.

Policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version

Records policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version? constraint
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version applies, to what scope, under which rule and authority? requirement
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version, and what remains unknown or disputed? privacy

Goods, service, digital access, condition, use, exclusion, proof and eligibility assertion

Records goods, service, digital access, condition, use, exclusion, proof and eligibility assertion as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish goods, service, digital access, condition, use, exclusion, proof and eligibility assertion? validation
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of goods, service, digital access, condition, use, exclusion, proof and eligibility assertion applies, to what scope, under which rule and authority? constraint
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support goods, service, digital access, condition, use, exclusion, proof and eligibility assertion, and what remains unknown or disputed? retention

Requested remedy, decision, authorization and instructions

Groups requested remedy, decision, authorization and instructions for the governed return/refund case.

Refund, exchange, repair, replacement, price reduction, credit and no-remedy request

Records refund, exchange, repair, replacement, price reduction, credit and no-remedy request as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish refund, exchange, repair, replacement, price reduction, credit and no-remedy request? decision
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of refund, exchange, repair, replacement, price reduction, credit and no-remedy request applies, to what scope, under which rule and authority? process
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support refund, exchange, repair, replacement, price reduction, credit and no-remedy request, and what remains unknown or disputed? access

Authorization, RMA, decision, reason, scope, instructions, label, deadline and expiry

Records authorization, rma, decision, reason, scope, instructions, label, deadline and expiry as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish authorization, rma, decision, reason, scope, instructions, label, deadline and expiry? authority
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of authorization, rma, decision, reason, scope, instructions, label, deadline and expiry applies, to what scope, under which rule and authority? event
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support authorization, rma, decision, reason, scope, instructions, label, deadline and expiry, and what remains unknown or disputed? exception
Returned subject, reverse movement and receipt Groups returned subject, reverse movement and receipt without duplicating authoritative sibling lifecycles.

Subject identity, quantity, condition and digital state

Groups subject identity, quantity, condition and digital state for the governed return/refund case.

Product, service, content, entitlement, unit, lot, serial, version and component reference

Records product, service, content, entitlement, unit, lot, serial, version and component reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish product, service, content, entitlement, unit, lot, serial, version and component reference? relationship
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of product, service, content, entitlement, unit, lot, serial, version and component reference applies, to what scope, under which rule and authority? measurement
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support product, service, content, entitlement, unit, lot, serial, version and component reference, and what remains unknown or disputed? interoperability

Requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition

Records requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition? measurement
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition applies, to what scope, under which rule and authority? evidence
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition, and what remains unknown or disputed? decision

Reverse logistics, custody, handover and receipt

Groups reverse logistics, custody, handover and receipt for the governed return/refund case.

Return method, label, package, shipment, route, location, cost responsibility and deadline reference

Records return method, label, package, shipment, route, location, cost responsibility and deadline reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish return method, label, package, shipment, route, location, cost responsibility and deadline reference? process
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of return method, label, package, shipment, route, location, cost responsibility and deadline reference applies, to what scope, under which rule and authority? quality
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support return method, label, package, shipment, route, location, cost responsibility and deadline reference, and what remains unknown or disputed? identity

Handover, carrier custody, attempt, loss, delay, delivery, receipt and proof

Records handover, carrier custody, attempt, loss, delay, delivery, receipt and proof as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish handover, carrier custody, attempt, loss, delay, delivery, receipt and proof? event
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of handover, carrier custody, attempt, loss, delay, delivery, receipt and proof applies, to what scope, under which rule and authority? validation
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support handover, carrier custody, attempt, loss, delay, delivery, receipt and proof, and what remains unknown or disputed? classification
Inspection, disposition and refund calculation Groups inspection, disposition and refund calculation without duplicating authoritative sibling lifecycles.

Receipt, inspection, conformity and disposition

Groups receipt, inspection, conformity and disposition for the governed return/refund case.

Inspection method, actor, condition, defect, damage, completeness, authenticity and evidence

Records inspection method, actor, condition, defect, damage, completeness, authenticity and evidence as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish inspection method, actor, condition, defect, damage, completeness, authenticity and evidence? evidence
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of inspection method, actor, condition, defect, damage, completeness, authenticity and evidence applies, to what scope, under which rule and authority? security
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support inspection method, actor, condition, defect, damage, completeness, authenticity and evidence, and what remains unknown or disputed? composition

Accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference

Records accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference? lifecycle
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference applies, to what scope, under which rule and authority? privacy
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference, and what remains unknown or disputed? relationship

Refund basis, allocation, deductions and rounding

Groups refund basis, allocation, deductions and rounding for the governed return/refund case.

Paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input

Records paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input? measurement
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input applies, to what scope, under which rule and authority? retention
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input, and what remains unknown or disputed? state

Partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation

Records partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation? other
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation applies, to what scope, under which rule and authority? access
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation, and what remains unknown or disputed? lifecycle
Refund execution, exceptions, reconciliation and closure Groups refund execution, exceptions, reconciliation and closure without duplicating authoritative sibling lifecycles.

Adjustment, instruction, execution, settlement and notification

Groups adjustment, instruction, execution, settlement and notification for the governed return/refund case.

Credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference

Records credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference? relationship
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference applies, to what scope, under which rule and authority? exception
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference, and what remains unknown or disputed? temporal

Refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification

Records refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification? state
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification applies, to what scope, under which rule and authority? interoperability
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification, and what remains unknown or disputed? spatial

Failure, fraud, dispute, reconciliation and closure

Groups failure, fraud, dispute, reconciliation and closure for the governed return/refund case.

Failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation

Records failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation? exception
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation applies, to what scope, under which rule and authority? decision
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation, and what remains unknown or disputed? provenance

Item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation

Records item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation? validation
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation applies, to what scope, under which rule and authority? identity
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation, and what remains unknown or disputed? ownership
Governance, provenance, time, access and interoperability Groups governance, provenance, time, access and interoperability without duplicating authoritative sibling lifecycles.

Source, provenance, access, privacy, retention and correction

Groups source, provenance, access, privacy, retention and correction for the governed return/refund case.

Owner, steward, source system, actor, activity, derivation, revision, conflict and audit

Records owner, steward, source system, actor, activity, derivation, revision, conflict and audit as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish owner, steward, source system, actor, activity, derivation, revision, conflict and audit? provenance
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of owner, steward, source system, actor, activity, derivation, revision, conflict and audit applies, to what scope, under which rule and authority? classification
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support owner, steward, source system, actor, activity, derivation, revision, conflict and audit, and what remains unknown or disputed? authority

Purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone

Records purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone? privacy
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone applies, to what scope, under which rule and authority? composition
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone, and what remains unknown or disputed? requirement

Event clocks, validation and loss-aware projections

Groups event clocks, validation and loss-aware projections for the governed return/refund case.

Purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time

Records purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time? temporal
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time applies, to what scope, under which rule and authority? relationship
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time, and what remains unknown or disputed? constraint

Identity, eligibility, sequence, quantity, condition, amount, policy, privacy, UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS, Schema.org, PROV and API validation

Records identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.

  1. Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation? interoperability
  2. Which requested, asserted, observed, authorized, rejected, corrected or superseded state of identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation applies, to what scope, under which rule and authority? state
  3. What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation, and what remains unknown or disputed? process

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
aggregate
Navigation path
NAV.SOC.ECO.RET
Domain
SOC.ECO.RET
Industry
Cross-industry
Tags
returnrefundsoc.eco.ret

What it is Filled

Owns case identity, versions, profiles and state; trigger, reason and evidence; order, fulfilment, entitlement and payment bindings; claimant, merchant, seller, provider, payer, refund recipient, carrier and authority roles; rule version, jurisdiction, window, conditions, exclusions and eligibility assertions; requested remedies, alternatives, authorization and instructions; subject, quantity, lot, serial, component, condition and digital-access observations; reverse movement, custody, handover and receipt evidence; inspection, acceptance and disposition assertions; refund basis, taxes, fees, discounts, deductions, allocation, currency and rounding inputs; credit, refund obligation, instruction, execution, settlement and notification references; failures, duplicates, fraud signals, chargeback, appeals, disputes, reconciliation and closure assertions; distinct clocks, provenance, privacy, retention, validation and loss-aware projections. External commerce, logistics, inventory, financial, legal and records masters remain authoritative.

In scope

  • Case identity, trigger, source-transaction and party bindings, eligibility, remedy request, decision, authorization, subject, quantity, condition, reverse movement, receipt and inspection evidence
  • Disposition, financial calculation, refund obligation and execution references, exceptions, reconciliation, closure, clocks, provenance, access, retention and projections

Out of scope

  • Owning Order, Contract, Fulfilment, Party, Product, Service, Inventory, Shipment, Package, Location, Entitlement, Invoice, Credit Note, Payment, Account, Warranty, Recall, Dispute, Adjudication, Waste or Records masters
  • Treating item return, authorization, receipt, inspection, credit adjustment, payment instruction, execution, settlement or closure as universal proof of refund entitlement, customer receipt or legal finality
  • Autonomous legal eligibility, return authorization, custody transfer, condition judgment, disposition, credit issuance, payment execution, disclosure or record destruction

Why it exists Filled

Represent a governed return and refund case so agents can distinguish request, eligibility, authorization, reverse movement, inspection, disposition, financial obligation and refund execution without confusing the case with order, fulfilment, shipment, invoice, payment, warranty, recall or dispute masters.

Distinguishing features Filled

  • A case covering request, eligibility, reverse movement, inspection, disposition and refund.
  • Differs from a warranty claim, a chargeback or a product recall, though it may link to them.
  • Keeps refund obligation, instruction, execution and settlement as separate states.
  • Differs from fulfilment, which moves goods forward.

What robots and AI may and may not do Filled

Must not

  • Determine legal eligibility or reject statutory rights.
  • Authorize returns or refunds without delegation.
  • Judge item condition or choose disposition.
  • Execute refunds to a different account than the original payer.
  • Disclose claimant data.

Only with a human decision

  • Rejecting a return.
  • Approving refunds above limits.
  • Disposition of unsafe or recalled goods.

May

  • Register a return request with reason and evidence.
  • Check eligibility rules and propose a remedy.
  • Track reverse shipment and inspection.
  • Calculate a refund for review.

Moral aspects Filled

  • Consumers have statutory return rights that must not be obscured.
  • Returned goods may be unsafe and need safe handling.
  • Disposal of returns has environmental cost.

Who is affected

  • Consumers
  • Merchants and sellers
  • Workers handling returned goods

Owners Filled

Steward

Dimension owner, namespace authority, accountable return owner and delegated commercial, logistics, inspection, finance, legal, privacy and safety authorities

Roles

Return/refund owner
Own purpose, scope, profile, lifecycle, compatibility and accountable use.
Commercial and policy steward
Own order bindings, policy versions, eligibility inputs, remedy terms, price and adjustment references.
Logistics and custody steward
Own authorization, return instructions, reverse movement, custody and receipt bindings.
Inspection and disposition authority
Own inspection criteria, condition evidence, acceptance and disposition decisions.
Finance and payment steward
Own credit, refund obligation, payment instruction, execution, settlement and reconciliation references.
Legal, privacy and safety authority
Own jurisdiction, disputes, protected commerce data, product safety, access and retention limitations.
Interoperability and records steward
Own mappings, conformance evidence, declared loss, legal hold and disposition policy.

Links to other meta-models Filled

references

  • WM-ECO-024 - Resolve the provisional fulfilment parent signal without granting containment or cascade mutation authority.
  • Order, Contract, Party, Product, Service, Inventory, Shipment, Package, Location, Entitlement, Invoice, Credit Note, Payment, Account, Warranty, Recall, Dispute, Adjudication, Waste and Records models - Resolve external identities, states, operations and evidence without duplicating their masters.

aligned

  • UBL 2.3; UN/EDIFACT RETANN and RETINS; ISO 20022 PaymentReturnV15; scoped EU consumer, goods, digital and product-safety law; IFRS 15; EPCIS and CBV 2.0; Schema.org; RFC 3339; PROV-O; DQV; ODRL; OpenAPI 3.1.1 - Project version-pinned commerce, logistics, finance, legal, accounting, traceability, discovery, temporal, provenance, quality, policy and API views with declared loss.

neighbor

  • WM-ECO-024 Fulfilment / Delivery - The unified registry supplies only a provisional parent signal. Fulfilment owns forward obligation-performance evidence; this model owns the requested or required reverse case and remedy evidence without a settled containment edge.
  • Order, item, shipment, inventory, entitlement, invoice and payment - These systems own commercial commitments, object identity, movement execution, stock, access, accounting documents and funds. This model stores typed references and subject-specific assertions.
  • Warranty, product recall, chargeback, complaint, dispute and adjudication - These lifecycles can trigger or challenge a remedy but remain external; return/refund evidence does not decide their authority or final state.
  • UBL, UN/EDIFACT, ISO 20022, EU law, IFRS, EPCIS, CBV, Schema.org, RFC, PROV, DQV, ODRL and OpenAPI - Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.

parent

  • WM-ECO-024

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier for return/refund case, version, request, authorization, subject line, movement, receipt, inspection, disposition, adjustment, refund or artifact, qualified by namespace and kind.
  • Governed globally resolvable case or artifact IRI.
  • Dimension UUID or ULID when neither preceding identifier exists.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A return case names an original order or item, a claimant, a reason, a remedy and a status.
  • Often confused with a chargeback, a credit note, a warranty claim or a complaint.

Capabilities and actions required Filled

  • Register return/refund case: Governed operation to register return/refund case without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Assess eligibility: Governed operation to assess eligibility without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Propose remedy: Governed operation to propose remedy without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Authorize return and issue instructions: Governed operation to authorize return and issue instructions without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Record handover and receipt: Governed operation to record handover and receipt without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Inspect and select disposition: Governed operation to inspect and select disposition without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Calculate refund obligation: Governed operation to calculate refund obligation without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Record refund instruction and execution: Governed operation to record refund instruction and execution without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Reconcile exceptions and close: Governed operation to reconcile exceptions and close without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.
  • Correct, project, retain and audit: Governed operation to correct, project, retain and audit without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.

Hazards and failure modes required Filled

  • Refund fraud.
  • Refunds never arriving.
  • Unsafe goods resold.

Standards and interfaces required Filled

  • UN/EDIFACT RETANN and RETINS messages.
  • ISO 20022 PaymentReturn messages.
  • GS1 EPCIS 2.0.
  • OASIS UBL 2.3 Credit Note.
  • Schema.org MerchantReturnPolicy.

Context of use required Filled

  • Eligibility, windows, evidence, cost allocation, deductions, tax treatment, refund means, deadlines and remedies depend on governing law, party type, contract, channel, sector and payment scheme.
  • CISG and EU consumer, digital and product-safety rules are scoped profiles, not universal governing law; IFRS is accounting evidence, not legal entitlement.

Sources Filled

  1. Universal Business Language Version 2.3 - OASIS Open
  2. UN/EDIFACT Announcement for returns message - United Nations Economic Commission for Europe
  3. UN/EDIFACT Instruction for returns message - United Nations Economic Commission for Europe
  4. ISO 20022 Message Definitions: PaymentReturnV15 - ISO 20022 Registration Authority
  5. Directive 2011/83/EU on consumer rights - European Union
  6. Directive EU 2019/771 on contracts for the sale of goods - European Union
  7. Directive EU 2019/770 on digital content and digital services - European Union
  8. IFRS 15 Revenue from Contracts with Customers - IFRS Foundation
  9. EPCIS Standard 2.0.1 - GS1
  10. Core Business Vocabulary 2.0 - GS1
  11. MerchantReturnPolicy - Schema.org Community Group
  12. International Sale of Goods CISG and related transactions - United Nations Commission on International Trade Law
  13. Regulation EU 2023/988 on general product safety - European Union
  14. Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  15. PROV-O: The PROV Ontology - World Wide Web Consortium
  16. Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
  17. ODRL Information Model 2.2 - World Wide Web Consortium
  18. OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

  • Canonically adjudicate the WM-ECO-024 parent signal and register return/refund relations to order, fulfilment, shipment, inventory, invoice, payment, warranty, recall, chargeback, dispute and waste models.
  • Create consumer, business, marketplace, subscription, travel, digital, regulated-goods, hazardous-material and cross-border return profiles.
  • Conformance-test return, receipt, inspection, disposition, adjustment, payment and projection mappings against concrete implementations.
  • Validate organization-specific eligibility, evidence, fraud, tax, accounting, payment-route, safety, privacy, retention and exception policies.
  • Obtain authorized legal, consumer, finance, tax, logistics, product-safety and records review before jurisdiction-specific claims.
  • Obtain independent external research review before promotion beyond reviewable-draft assurance.
  • Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
  • WM-ECO-024 is only a provisional parent signal and the frozen candidate relation ledger contains no settled WM-ECO-025 edge.
  • Consumer, business, marketplace, subscription, travel, financial, healthcare, food, hazardous-goods and cross-border returns need separate profiles.
  • National contract, tax, accounting, product-safety, privacy, signature, payment-scheme, chargeback and records rules require jurisdiction or scheme review.
  • UNECE and IFRS source pages had direct-access limitations, and every UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS and Schema.org mapping needs release-pinned conformance tests.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-025-return-refund/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-025-return-refund.json