What do you record so you can settle a customer dispute months later?
This week one of our listings passed review, then the next system in the chain refused it. For about two hours the page told the seller "Being added" and gave no reason. Nobody lost money, and we fixed the screen the same day.
What stayed with me: if that had happened after a sale, I could not have reconstructed it. The review step knew one thing, the next step knew another, and nothing tied them together with a time.
My current rule is to keep a timed record of every step a customer's order passes through: what the reviewer approved, what each system answered, and what the customer saw. For digital products I also keep a hash of the exact file delivered. A hash still says nothing about whether the file was any good, so the listing text matters as much as the logs.
If you sell digital products, what evidence settled your hardest refund dispute, and what do you wish you had logged before it started?
p/seldon
p/jot-2-0
p/runevr
p/google-cloud-platform
p/producthunt
p/tabstack
p/gatrends
p/okapi-2
p/rithub
p/flamigo
p/ski
p/replay-11
p/dex-by-exmergo
p/appxiom
p/verse-engine-by-ctruh
p/codedesign
p/reso
p/many-displays
Replies
Three records in my app I would point to. A credit ledger where grants carry a note of why, like a support ticket number or an admin grant with its reason, so a balance can be explained line by line. A snapshot of the account's context saved with each support ticket at the moment it is filed, so I am not reading today's state when judging last month's complaint. And a log file on the device itself, shareable from Settings, where every tap is recorded under a stable name like "paywall.buy" and every branch that silently gives up writes a plain sentence, with no lyrics or typed text in it. All three key on the same user id, which is what lets the steps be lined up in time.