Change history
"Who changed this price?" and "when did this order's status actually move?" are the questions that surface when a number looks wrong. Traide records a change history against the records where those questions get asked, so you can answer them from the dashboard instead of guessing.
Where to find it
Change history appears as an Events view on the record itself:
| Record | Where |
|---|---|
| Order | The order's Events tab |
| Seller order | The seller order's Events tab, within the marketplace order |
| Seller | The seller's Events tab |
| Seller agreement | The agreement's Events tab |
What an entry tells you
Each entry in the list carries:
- What happened — the event type, and a message describing the change.
- Who did it — the staff member, seller or app responsible.
- When — the date and time, plus how long ago it was.
Longer messages are shortened in the list and can be expanded in place, so a busy timeline stays readable while the detail is still one click away.
Stock movements appear in these timelines too, which is what connects an inventory discrepancy to the action that caused it.
Sellers see the history of their own records. Where an action was taken by marketplace staff, sellers see that it happened without seeing internal staff identities.
History from before the feature shipped
The timelines merge Traide's newer audit trail with the activity Traide already recorded historically — order events, stock events, seller events, product status changes and customer activity.
In practice this means the view does not start empty on the day change history was introduced. You can look back at records created well before it.
Beyond the dashboard
Traide records change history against considerably more than the four records listed above — products, variants, customers, refunds, invoices, payouts and payout batches, and CSV import and export jobs all carry one.
Those histories are currently available through the API rather than as dashboard tabs. If you need to build reporting, a compliance export, or an internal audit view on top of them, they are there for your developers to query. See the developer guide.
Practical notes
- Change history is a record, not an undo. It tells you what happened and who did it; reversing a change is still done through the normal editing flow.
- Use it before assuming a bug. A surprising value very often has a perfectly ordinary action behind it, and the timeline is the fastest way to find out which.