The pricing-app horror story
You change a wholesale tier. Half an hour later, a stockist messages: "Why is my price showing as $42? It should be $34." You look at the rule. The rule looks right. You can't tell whether you changed it five minutes ago or last month. You can't tell whether the customer was tagged correctly. You don't know what the rule was an hour ago, so you can't roll it back.
You spend an hour reconstructing the change, manually edit the rule back to what you think it was, and apologize to the stockist. Three days later it happens again with a different customer.
Why this happens
Most pricing apps treat rules as state, not as a versioned log. The current configuration is the only configuration that exists. There's no diff between yesterday's rules and today's. There's no record of which rule fired for which customer last Tuesday. When something goes wrong, you can't replay it.
What proper pricing governance looks like
1. Audit log of every change
Every rule edit, publish, or rollback is logged with: who, what changed, when, and a one-line note. The log goes back at least 90 days.
2. Version-aware rules
Each rule has a version number. When you publish a change, the previous version is archived, not overwritten. The current rule and all previous versions are queryable.
3. One-click rollback
If a rule change broke something, you click "roll back" on a previous version and it becomes the current version. No manual reconstruction.
4. Per-order rule attribution
Every order knows which rule version produced its price. When a refund question comes in, you can look at the order and see the exact rule and version that fired.
5. Diff view between versions
"What changed between v3 and v4?" should be a one-screen answer, not a 20-minute investigation.
Why this matters more than it sounds
Pricing is one of the few systems where customer trust is the cost of an error. A bug in your shipping app might cost you a refund; a bug in pricing means a customer paid the wrong amount. Even if you fix it within a day, the next time you change a tier, your team is going to ask "are you sure?" and slow down. Your velocity at the pricing layer is bounded by your team's confidence in being able to undo a mistake.
That's why governance — audit, versioning, rollback — isn't a "nice to have." It's the load-bearing feature that lets you move at all.
How to evaluate a pricing app on governance
Three questions to ask any pricing app before you install it:
- "Show me your audit log. Can I see every change made in the last 30 days, with who and when?"
- "How do I roll back to a previous version of a rule?"
- "For an order placed last week, can I tell which rule version produced the price?"
If the answer is "we don't have that yet" or "you can email support" — that app is fine for a small store, but it will hurt you at scale.
What this looks like in TagTier
The audit log + version + rollback flow is one of the six features we lead with on the homepage, not a back-office afterthought. Every rule change is logged, every version is archived, every order knows which version priced it, and rollback is one click. See pricing →