Some features are never glamorous — until the moment you need them. And by then it's too late to build them.
An audit log is one of those features.
What it's about
WeUniteBrands is a multi-tenant platform: multiple brands work in the same system, each in their own walled-off environment. That brings real advantages — shared infrastructure, faster iteration, lower cost per brand — but it demands something extra in terms of trust.
When a brand says "this price was different yesterday" or "who adjusted this stock count?", you need to be able to show them. Not approximately. Exactly.
What we built
Central to the platform now sits an audit layer that automatically captures all meaningful changes: price adjustments, stock corrections, user switches, order status changes, discount campaigns toggled on or off. For each action we record who, what, when, from which device, and — crucially — what the value was before and after.
Brands see their own audit log in their admin. We, as platform operator, have a broader view for when an incident needs our help.
Why now, rather than waiting until someone asked
Two reasons.
One: building an audit log retroactively is brutal. You miss the history from before the build, and backfilling logs on existing data is almost always incomplete. If you never end up needing it, you've spent a few days. If you need it without having built it, you can spend months trying to solve the gap — and in the worst case, lose a customer's trust.
Two: it makes compliance conversations with larger brands significantly easier. Any brand with a serious procurement process asks about it. "How can we see who changed what?" For us, the answer is now: "here, look." Rather than: "we could build that."
The lesson
The best audit logs are installed quietly. Nobody applauds them. But the moment a question shows up you couldn't have answered without one, they've paid for themselves many times over.
We'd rather build trust before we need it than try to rebuild it after losing it.