Use case: Shopify — subscription cancellation / credit not processed
Pain: a customer says the subscription was canceled or a credit was not processed, while the merchant relies on scattered cancellation emails and usage logs. Reviewers lose time reconstructing whether the service was actually used after the claimed cancellation point.
3-step fix (receiver-aware review rail)
- Intake contract: require the cancellation-policy version that applied at purchase time and the customer cancellation request timestamp.
- Data join: connect the cancellation message to the last service-usage event, account access log, or renewal event.
- Decision-ready rail: export one bundle that shows policy snapshot → cancellation request → post-cancellation usage trail, without overclaiming outcome certainty.
Why it matters: if service usage continued after the claimed cancellation, the reviewer sees a structured consumption trail instead of two disconnected screenshots. That moves the conversation from “stories” to reason-path satisfaction.
Reality Audit
—