Here's what CENT looks like from the user's seat. Both stories are things that happen every week in a real retail business — and in both, the person changing data simply hits Save. The rest of the company just... knows.
Tom in pricing changes the gross price on a single article. Within seconds — without him doing anything else — every dependent price in the catalog has been recalculated.
It's Friday morning. Tom drops the gross price on Premium Olive Oil 750ml from € 8.49 to € 7.99, effective the 15th. He clicks Save in his usual SAP screen.
From his point of view, the work is done. He moves on to the next article on his list.
The Pricing Cockpit is one of the things that listens to CENT for price changes. The moment Tom's save commits, the cockpit gets the signal and starts recalculating every dependent price — country variants, pack-size variants, promotion bundles — all of it.
No one had to remember to "trigger the recalc". No nightly job that maybe ran, maybe didn't. The cascade happens because it was configured to happen, and the engine watching for it never sleeps.
One save. Twelve dependent prices recalculated. Zero manual handoffs. Tom's day continues.
When an article reaches end-of-life, store ops, supply chain, and replenishment all need to act — but on different things, on different timelines. CENT lets each of them find out from the same source of truth, in the same place.
In the central master-data system, a steward marks Glass Cleaner Spray 750ml at DC-003 as discontinued, effective end of June. One field, one click, one Save.
From the steward's seat, that's the entire job. They don't email anyone. They don't open a ticket. They don't update a spreadsheet.
MyHub is one of the things that listens to CENT for article-status changes. Within seconds, three different receiver groups in MyHub each get an inbox message — written for them specifically, with the next-step action they need to take:
Each team picks up the message in MyHub, acknowledges it, and gets on with their part of the work. No one finds out from a stockout three weeks later.
The steward changed the data they were supposed to. Everyone downstream got told what they needed to know. CENT did the in-between bit so quietly that nobody noticed it was there.
Both stories above are powered by the same fan-out pipeline. The architecture page shows what that pipeline looks like on the inside — how the parallelism happens, and why one slow consumer can't slow everyone down.