Maintaining Model Integrity: SAP VC/AVC to Tacton CPQ Post-Go-Live

You’re live. Data is converted. Tests passed. Everyone breathes out. Then three months later, someone in sales says:

“Why can I still pick that option? We stopped selling it last quarter.”

That’s when you realize the job didn’t end at go-live.

Where it actually breaks

SAP changes quietly. A material gets blocked. A variant gets added. Someone tweaks a dependency. None of it is dramatic. No big release. Just small, continuous change. CPQ doesn’t see any of it unless you push it through.

So the gaps start:

• Old components still selectable
• New variants missing
• Rules no longer matching reality

At first, people work around it. Then they stop trusting it. I’ve seen teams go back to Excel within six months. Not because the CPQ was bad. Because it wasn’t kept in sync.

What actually works

You don’t need a big framework. You need a loop that people follow even when things get busy.

Track what you build from
If you can’t point to the exact SAP snapshot behind your current model, you’re guessing. That catches up with you fast.

Run the tests when nothing “big” changed
Most issues come from small changes. The ones nobody flagged. That’s exactly what your test suite is for.

Don’t review changes alone
A modeler will say “this compiles.”
A product owner will say “this makes no sense.”
You need both voices before anything goes out.

Make changes visible
Side-by-side comparisons beat documentation every time. When you see that 12 variants disappeared, the conversation gets real very quickly.

What this looks like in reality

The teams that get this right don’t talk about governance. They just have a habit:

SAP change → extract → compare → validate → release

No drama. No long meetings. Just a routine that runs. The teams that struggle treat every update like a mini project. That’s where delays and mistakes creep in.

If you ignore it

Nothing breaks immediately. That’s the problem. It degrades.

Sales double-checks more. Then they stop checking. Then they stop using it. And once a configurator loses trust, it’s very hard to win back. Even if you fix the model.

Bottom line

A CPQ model that isn’t maintained is already wrong. It just hasn’t been noticed yet. Keep SAP and CPQ moving together. Or accept that people will find another way to sell.