SAP S/4HANA Cloud, public edition

What Spadoom delivers

Spadoom is SAP CX-first. We deliver Sales Cloud V2, Service Cloud V2, Commerce, Marketing, CDP, CIAM, Loyalty, CPQ, and FSM as our core lanes. Around those lanes, S/4HANA Public Cloud is the ERP backbone our customers increasingly land on, and we are deliberately fluent in how it works.

What that means in practice: we advise on the integration architecture between S/4HANA Public Cloud and SAP CX, design the data flows that need to move both ways, and build the BTP-side extensions that keep custom logic out of the ERP. We do not lead full S/4HANA Public Cloud rollouts on our own. For that work we partner with specialised S/4HANA implementation firms and coordinate from day one of the rollout.

If your organisation is moving onto S/4HANA Public Cloud and you also need a connected SAP CX layer — sales, service, commerce, marketing — that is the conversation to have with us. We bring the CX delivery and the integration architecture; the ERP partner brings the public-cloud rollout discipline.

Where SAP CX meets S/4HANA Public Cloud

The integration story between S/4HANA Public Cloud and SAP CX is well-defined and, when respected, low-drama.

Customer master data flows from S/4HANA into the CX systems — accounts, contacts, addresses, hierarchies. Sales orders flow the other way: a quote priced in CPQ, accepted by the customer in Sales Cloud or Commerce, posted as a sales order into S/4HANA. Pricing and discount logic live where they belong — list pricing in S/4HANA, deal-level discounting in CPQ, with the negotiated price posting back. Invoicing happens in S/4HANA, with invoice and payment status visible in the CX 360° view so the rep is not surprised by an aged receivable.

The clean-core principle changes how this integration is built. Custom logic does not go inside S/4HANA. It does not go inside Sales Cloud V2 either, frankly — that platform has its own plug-in architecture for the same reason. Integration logic, transformations, validations, and event-driven flows live in SAP BTP: Integration Suite, Build, Event Mesh, and Cloud Application Programming. The ERP and the CX system both stay upgrade-clean, and the custom layer is where it can be evolved without breaking either side.

What clean core actually means in practice

Clean core is not a slogan. In a public-cloud ERP it is enforced architecture.

No Z-tables in the ERP. No user-exits. No enhancements bolted onto standard objects. Every customisation a previous generation of consultants would have written into the ERP itself moves to BTP as a side-by-side extension. Quarterly releases land without a regression suite the size of a small product organisation.

For CX integration design, the practical implication is straightforward: the integration layer must stay above the line. APIs and events are the contract; transformations and validations live in Integration Suite and Build. If a CX-driven requirement seems to need a change inside S/4HANA, that is the signal to redesign — not the signal to open a Z-table conversation.

Working with implementation partners

We are deliberate about scope. The CX layer is Spadoom’s lane and we own it end to end. The ERP layer in a full S/4HANA Public Cloud rollout is delivered by a partner who does that work for a living. We coordinate with that partner from the start of the programme on three things: integration architecture between ERP and CX, data migration alignment so customer and product master flow cleanly, and the clean-core boundary so neither side carries customisation it should not.

The pattern works because the lanes are clear. Customers who try to make one firm own everything either get a CX layer that is an afterthought, or an ERP rollout that is a CX afterthought. We have seen both. The version that works has each partner owning their lane and the integration designed jointly from week one.

If you are scoping a programme that pairs S/4HANA Public Cloud with SAP CX and want to talk through how that handoff works in practice, that is the conversation we are set up for.