# Spadoom AG
> Spadoom is a Swiss SAP Gold Partner for Cloud ERP and Customer Experience. Our own teams implement SAP S/4HANA Cloud Public Edition, Sales and Service Cloud V2, Commerce and integration on SAP BTP. We deliver in stages, with named responsibilities and transparent project budgets.
Brand: We Do SAP. Cloud ERP at the core. Customer experience in every channel.
Founded in 2018. Headquartered in Zug, Switzerland. SAP Commerce is our origin; our practice now includes in-house Cloud ERP delivery. Dario Pedol is spokesperson of the DSAG Customer Experience working group in Switzerland.
AI supports our delivery workflow and selected customer processes. Product availability, data requirements and human approval are assessed for each use case. A demonstration is not a production reference. CX integration projects are not evidence of an ERP implementation by Spadoom.
## Transformation and Readiness
### ECC to S/4HANA Public Cloud Transformation
URL: https://www.spadoom.com/en/transformation/
A phased transformation connecting S/4HANA Public Cloud, SAP CX and an ECC archive on AWS through SAP Integration Suite.
### S/4HANA Public Cloud Readiness
URL: https://www.spadoom.com/services/s4hana-readiness/
A five-day assessment covering system inventory, greenfield decision, AWS archive concept, phases and costs. From CHF 12'000.
## Solutions — Full Content
### Cloud ERP
SAP Product: SAP S/4HANA Cloud, public edition
URL: https://www.spadoom.com/en/solutions/s4hana-cloud-public/
Description: Cloud ERP at the core. Customer experience in every channel. Our own S/4HANA team implements your ERP and connects it with sales, service and commerce.
## We deliver the core.
Spadoom implements SAP S/4HANA Cloud Public Edition with its own team. We lead fit-to-standard workshops, configure the agreed processes, migrate data and build the integration with SAP CX. One programme connects the ERP core and the customer-facing systems. Your named project team owns the agreed scope.
Our practice grew from cloud commerce and customer experience into Cloud ERP. The colleagues in our ERP team bring experience in public-cloud architecture, finance, procurement and logistics. Their experience is distinct from the customer projects published below.
[Plan your readiness check](/services/s4hana-readiness/)
## What is SAP Cloud ERP?
SAP S/4HANA Cloud Public Edition is SAP’s public-cloud ERP for processes including finance, procurement and operations. SAP operates the software and provides updates. We assess the available scope items, country requirements and integration needs with you. Product features and licence entitlements depend on your contract and release.
## A transformation, delivered in stages
We start with the business process, not a list of products. ERP-first establishes the master data and finance processes. CX-first can deliver earlier value but may require an interim integration with ECC. Parallel delivery needs shared milestones and key-user capacity. The assessment determines which sequence fits your business.
## Clean core leaves room for your business
Clean core does not mean “no configuration” or “all custom code must move to BTP”. Public Edition supports configuration, released key-user and developer extensions, and side-by-side extensions on BTP. We choose the supported option for each requirement and include integration and regression testing in the release plan.
## ECC: plan the transition with the right dates
SAP’s mainstream maintenance for the last three enhancement packages of Business Suite 7 ends in 2027. Optional extended maintenance runs to the end of 2030 under SAP’s conditions. That is not an automatic shutdown of ECC. Public Edition requires a new implementation rather than an in-place ECC conversion. We assess data retention and an archive, potentially on AWS, separately: access, legal retention, licences and operating costs must work before the old system is retired.
## What the customer references show
intelligentfood demonstrates our Sales & Service Cloud V2 delivery and Cloud ERP integration, including work in parts of MM and SD. The three-month figure relates to the Sales & Service platform. Meier Tobler demonstrates our Integration Suite hub. SkyCell is a Public Cloud reference from Actum Digital Schweiz: a five-month project whose team now works mostly at Spadoom. The SkyCell reference describes the experience of our current team at its previous employer.
## Scope, cost and your first decision
Start with the readiness check: five consulting days, from CHF 12,000, with a fixed price agreed for the assessment scope. You receive findings, a target architecture, priorities and a phased plan with a cost range. Implementation, SAP subscriptions, extensions, migration, travel and ongoing operation are scoped separately. A full ERP programme has no blanket 14-week promise. We agree timing after process, data and country scope are understood.
[Plan your readiness check](/services/s4hana-readiness/) · [Explore the transformation](/en/transformation/)
### SAP
- [SAP Cloud ERP](https://www.sap.com/swiss/products/erp/s4hana.html)
- [SAP maintenance strategy](https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy/s4hana-business-suite7.html)
- [SAP clean-core extensibility](https://learning.sap.com/courses/practicing-clean-core-extensibility-for-sap-s-4hana-cloud/explaining-extensibility-model-best-practices_e290f382-800e-40ef-a203-85a13115f487)
---
### Sales
SAP Product: SAP Sales Cloud V2
URL: https://www.spadoom.com/en/solutions/sales-cloud/
Description: SAP Sales Cloud V2 — the cloud-native B2B CRM that closes the gap between pipeline fantasy and reality. Spadoom is the SAP Sales Cloud V2 implementation partner across Switzerland, Germany, Austria and Italy, with a 14-week median go-live and adoption rates that hold six months post-launch.
## What is SAP Sales Cloud V2?
SAP Sales Cloud V2 is SAP's cloud-native B2B CRM — a ground-up rebuild of SAP C4C / Sales Cloud V1, not an upgrade. It runs on [SAP Business Technology Platform](https://www.sap.com/products/technology-platform.html), uses a plug-in extension architecture so custom logic survives upgrades, and ships with [Joule](https://www.sap.com/products/artificial-intelligence/ai-assistant.html) — SAP's native AI assistant — embedded directly in the sales workspace. Pre-built integration with [SAP S/4HANA](https://help.sap.com/docs/CX_NG_SALES) brings live pricing, stock, and order history into the CRM. Quarterly zero-downtime releases replace V1's bi-annual upgrade cycles. SAP's [official product page](https://www.sap.com/engage/sscv2.html) is the canonical reference.
Spadoom is an SAP partner specialising in Sales Cloud V2 implementation across Switzerland, Germany, Austria, and Italy. The rest of this page covers what we deliver, what it costs, how V2 compares to V1, and where we've put it into production. Our DACH CX practice is led by Dario Pedol, spokesperson of the DSAG (German-speaking SAP user group) CX working group Switzerland.
Spadoom in numbers · SAP Sales Cloud V2
14 weeks
Median V2 go-live (Spadoom DACH projects)
12+
V2 go-lives delivered since 2023
92%
User adoption sustained at 6 months
2×
Pipeline review meeting time saved
Based on Spadoom's SAP Sales Cloud V2 implementations across Switzerland, Germany, Austria and Italy. SAP-reported benchmarks for V2 (SAP Value Stories 2025) align with our observed outcomes.
## Case study — pipeline visibility at Nussbaum
After replacing legacy spreadsheets and a half-used V1 instance, **Nussbaum** (Swiss industrial distributor) cut pipeline-review time from 90 minutes to under 25 and gave regional managers a single forecast their CFO trusts. Read the [full Nussbaum implementation story](/en/blog/nussbaum-pipeline-visibility-sales-cloud-v2/) — and the parallel [field-service rollout](/en/success-stories/nussbaum-field-service/).
A second example: at **Miltenyi Biotec** (German biotech with global sales and service operations) we rolled out Sales Cloud V2 alongside [Service Cloud V2](/en/solutions/service-cloud/) across multiple regions — sales reps and service agents share a unified customer view. Read the [full Miltenyi rollout](/en/success-stories/miltenyi-biotec-sales-service/).
## What Spadoom delivers
We've implemented SAP Sales Cloud V2 for manufacturers, medical device companies, and industrial distributors across Switzerland, Germany, Austria, and Italy. As an SAP partner based in the DACH region, we bring local presence and hands-on project delivery — no offshore handoffs.
Our implementations include custom pipeline configurations, integration with SAP ERP and S/4HANA, territory and quota management, and end-user training that gets people using the system on day one. Adoption is not an afterthought. Our delivery follows [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hyper-care — adapted for Sales Cloud V2 projects.
We also run SAP Sales Cloud V2 for our own sales pipeline. Every workflow we recommend to a client, we've tested on ourselves first. For a full overview of the platform, see our [SAP Sales Cloud V2 handbook](/en/blog/your-complete-sap-sales-cloud-handbook/).
## ROI you can measure
SAP reports that organisations using Sales Cloud V2 see concrete results:
- **2× higher lead conversion rates** — with AI-scored leads and guided selling, reps focus on deals that actually close (source: SAP Value Stories, 2025)
- **75% less effort responding to customer queries** — Joule AI handles routine lookups so reps spend time selling (source: SAP Community, 2026)
- **2× improvement in forecasting efficiency** — managers spend less time chasing status and more time coaching (source: SAP Value Stories, 2025)
These are not theoretical gains. Our clients in manufacturing and distribution report pipeline review meetings dropping from 90 minutes to 20, and new reps reaching quota-carrying status in half the onboarding time. [Calculate your projected ROI](/en/roi-calculator/) based on your deal size and team size.
## Joule AI in SAP Sales Cloud V2
SAP Sales Cloud V2 ships with [Joule](/en/blog/sap-joule-sales-cloud-v2-hands-on-guide/), SAP's AI assistant, embedded directly in the CRM. This is not a bolt-on — Joule runs inside the sales workspace:
- **Opportunity summaries** — Joule reads the full deal context (emails, notes, activities) and generates a brief before your next call
- **Email drafting** — write follow-ups based on the deal stage and last interaction, in the rep's tone
- **Lead scoring** — machine learning models trained on your own pipeline data, not generic benchmarks
- **Deal intelligence** — flags stalled deals, identifies at-risk revenue, and suggests next actions
- **Forecasting** — AI-driven predictions that use historical win rates and current pipeline velocity
### AI lead scoring in Sales Cloud V2
Lead scoring in SAP Sales Cloud V2 is built on a machine-learning model trained on **your own win/loss history**, not on generic industry benchmarks. Reps see scores that reflect how your team actually closes deals, and the model retrains continuously as new outcomes flow in.
With Joule Studio (GA since Q1 2026), you can build custom AI agents — for example, an agent that pulls product availability from S/4HANA and drafts a delivery timeline email, without the rep leaving Sales Cloud. For a hands-on walkthrough, see our [Joule in SAP Sales Cloud V2 guide](/en/blog/sap-joule-sales-cloud-v2-hands-on-guide/). For the broader picture of AI agents in SAP CX, read [what agentic AI means for sales teams](/en/blog/agentic-ai-sap-what-it-means-for-sales/).
## SAP Sales Cloud V2 mobile app — offline-first selling
The SAP Sales Cloud V2 mobile app runs full CRM functionality on iOS and Android with **true offline mode** — reps update opportunities, log activities, and capture signatures with no connection, and the app reconciles automatically when back online. Visit reports, route planning with [SAP Field Service Management](/en/solutions/field-service-management/), and barcode-driven asset scans all work without a network.
## Where most CRM projects fail
CRM projects fail when the system is configured for leadership reports, not for sales reps. We work the other way around. The first question we ask: what does a rep need to do in the first ten minutes of their day? Everything gets built backwards from there.
The second failure point is data. Dirty data imported from your old system just creates a faster way to make wrong decisions. We include data cleansing and validation as part of every migration — not an optional add-on. If you're migrating from spreadsheets, see our [Excel to SAP Sales Cloud V2 migration guide](/en/blog/excel-to-sap-sales-cloud-v2-migration-guide/).
## Why V2 matters — V1 vs V2 compared
SAP Sales Cloud V2 is a ground-up rebuild, not a feature update. V1 (formerly SAP C4C) entered maintenance mode in 2023. SAP's active investment — including all Joule AI capabilities — is in V2 only.
| Capability | V1 (C4C) | V2 |
|---|---|---|
| Architecture | Monolithic, customisation via SDK | Composable plug-in extensions — custom logic survives upgrades |
| AI & Joule | Not available | Native: lead scoring, deal intelligence, forecasting, Joule copilot |
| UX | Classic Fiori-style | Modern, mobile-first, responsive |
| Updates | Bi-annual, requires upgrade project | Quarterly, zero-downtime deployment |
| Extensibility | Key User Tools, limited | Plug-in framework, Joule Studio agents, SAP Build integration |
| Guided Selling | Basic | Configurable playbooks for complex B2B processes |
| CTI Integration | Third-party only | [Native CTI framework](/en/blog/cti-integration-sap-sales-cloud-v2/) with softphone embedding |
| Mobile | Companion app | Full CRM on any device, online and offline |
### Native CTI integration
V2 ships with a native CTI framework — softphone embedding, screen pops on inbound calls, and automatic activity logging — without the third-party middleware V1 required. Full walkthrough in our [CTI integration in SAP Sales Cloud V2](/en/blog/cti-integration-sap-sales-cloud-v2/) guide.
If you're still on V1, our [C4C to V2 migration strategy](/en/blog/sap-c4c-to-v2-migration-strategy/) lays out the timeline, risks, and data migration approach. For a deeper feature comparison, read [SAP Sales Cloud V2 vs. C4C: What Actually Changed](/en/blog/sap-sales-cloud-v2-vs-c4c/).
## Pricing and licensing
SAP integration can use supported APIs and preconfigured integration content. The actual data scope, latency and middleware requirements depend on the products, editions and configured scenario. Assess mapping, licences, error handling and monitoring before comparing total cost; SAP branding alone does not remove integration work or guarantee savings.
The total cost of ownership depends on your user count, integration scope (S/4HANA, ECC, third-party systems), and implementation complexity. Spadoom offers fixed-price implementation packages — including our [CRM in 10 Days](/sme) package for SMEs — so you know the full investment before signing. For a detailed comparison, see our [SAP Sales Cloud V2 vs Salesforce](/en/compare/sap-sales-cloud-v2-vs-salesforce/) and [vs Microsoft Dynamics 365](/en/compare/sap-sales-cloud-v2-vs-microsoft-dynamics-365/) pages.
## SAP Sales Cloud V2 vs Salesforce and Dynamics 365 — the short version
SAP Sales Cloud V2 is the lower-TCO choice for organisations already on SAP ERP or S/4HANA — native ERP integration removes the middleware stack that Salesforce and Dynamics both need. Salesforce wins on ecosystem breadth and AppExchange depth; Microsoft Dynamics 365 Sales wins on Power Platform integration. For SAP-centric stacks, V2 wins on governance, data residency under European regulations, and total cost. Deep dives: [Sales Cloud V2 vs Salesforce](/en/compare/sap-sales-cloud-v2-vs-salesforce/), [vs Microsoft Dynamics 365](/en/compare/sap-sales-cloud-v2-vs-microsoft-dynamics-365/), [vs HubSpot](/en/compare/sap-sales-cloud-v2-vs-hubspot/).
## Industry use cases
SAP Sales Cloud V2 is built for B2B complexity. Here's how we've deployed it across industries in Switzerland, Germany, Austria, and Italy:
**Manufacturing & industrial distribution** — The most common fit. Reps need real-time pricing and stock from S/4HANA, configurable product bundles, and multi-level approval workflows. We configure territory management to match regional sales structures common in DACH and Southern Europe.
**Medical devices & life sciences** — Compliance-heavy sales cycles with regulatory documentation requirements. We set up activity tracking and visit reports that satisfy audit trails, plus integration with quality management data from SAP.
**Automotive & high-tech** — Long deal cycles, multiple stakeholders, and large-value quotes. Guided selling playbooks walk reps through qualification stages. When paired with [SAP CPQ](/en/solutions/configure-price-quote-cpq/), Sales Cloud V2 handles complex quoting directly in the CRM.
**Professional services & consulting** — Opportunity-to-project handoffs. We integrate Sales Cloud V2 with project management and resource planning in S/4HANA. The transition from "deal won" to "project kicked off" happens without re-entry.
## Pairing with S/4HANA Public Cloud
When your ERP backbone is [SAP S/4HANA Public Cloud](/en/solutions/s4hana-cloud-public/), Sales Cloud V2 is the natural front-end: one vendor, one data model, and a pre-built integration that puts live pricing, stock levels, and order history inside the CRM without a middleware layer. Sales reps see accurate numbers because the numbers come directly from the ERP record — not from a nightly sync or a manually maintained price list. Joule agents can reach into S/4HANA to draft delivery timelines or check margin impact before a quote goes out, which closes the loop between the commercial conversation and the backend that fulfils it. And when pipeline data and ERP actuals need to land in one analytics foundation — pipeline-to-cash, forecast accuracy against shipped revenue — [SAP Business Data Cloud](/en/solutions/business-data-cloud/) is the layer that joins them.
Spadoom is one of the few partners in DACH that delivers both sides of this stack. We scope the S/4HANA Public Cloud integration as part of the Sales Cloud V2 implementation — not as a separate project that lands six months later. If you're evaluating the combined platform or planning a clean-core move, our [SAP S/4HANA Public Cloud and Sales Cloud V2 integrated-stack guide](/en/blog/sap-s4hana-public-cloud-sales-cloud-v2-integrated-stack/) walks through the architecture, the integration touchpoints, and what we've learned from running it in production.
## What good looks like
A well-implemented SAP Sales Cloud V2 means:
- Pipeline reviews that take 20 minutes because the data is trusted
- New reps productive in week two because the system guides them
- Forecasting that finance and sales agree on — because it comes from the same source
- Sales managers who can coach instead of chasing status updates
Six months after go-live, your adoption rate tells the story. We track it, and we're accountable for it.
Evaluating consultancies? Our roundup of the [best SAP CX consultancies in Switzerland](/en/blog/best-sap-cx-consultancies-switzerland/) shows where we stand in the Swiss market.
[SAP Integration Suite: supported integration capabilities](https://www.sap.com/products/technology-platform/integration-suite.html).
---
### Service
SAP Product: SAP Service Cloud V2
URL: https://www.spadoom.com/en/solutions/service-cloud/
Description: SAP Service Cloud V2 — customer service that doesn't require three escalations to get an answer. Spadoom configures SAP Service Cloud V2 from kickoff to hypercare across Switzerland, Germany, Austria and Italy, with omnichannel case management, Joule AI, and native SAP ERP + FSM integration.
## What is SAP Service Cloud V2?
SAP Service Cloud V2 is SAP's cloud-native customer service platform — a ground-up rebuild of SAP Service Cloud V1 and SAP CRM Service, not an upgrade. It runs on [SAP Business Technology Platform](https://www.sap.com/products/technology-platform.html), uses a plug-in extension architecture so custom logic survives upgrades, and ships with [Joule](https://www.sap.com/products/artificial-intelligence/ai-assistant.html) — SAP's native AI assistant — embedded directly in the agent workspace. V2 replaces V1's flat ticket model with structured case entities that move through configurable lifecycle states, and adds a unified agent desktop covering email, phone, chat, portal, and social in one console. Pre-built integration with [SAP S/4HANA](https://help.sap.com/docs/CX_NG_SVC) brings live order, asset, and warranty data into the case view. Quarterly zero-downtime releases replace V1's bi-annual upgrade cycles.
Spadoom is an SAP partner specialising in Service Cloud V2 implementation across Switzerland, Germany, Austria, and Italy. The rest of this page covers what we deliver, what it costs, how V2 compares to V1, and where we've put it into production.
Spadoom in numbers · SAP Service Cloud V2
35%
Faster case resolution (with Joule routing)
98%
SLA adherence at the customers we host
40%
Less manual case routing
6 weeks
Typical Spadoom Service Cloud V2 stabilisation
Based on Spadoom's SAP Service Cloud V2 implementations. SAP Value Stories 2025 and 2025 Gartner Magic Quadrant for CRM Customer Engagement Centers cited.
## Case study — Miltenyi Biotec sales + service
For [Miltenyi Biotec](/en/success-stories/miltenyi-biotec-sales-service/) (a German biotech with global sales and service operations), we deployed SAP Sales and Service Cloud V2 across multiple regions — connecting agents, sales reps, and field engineers around a single customer view. Read the [full Miltenyi sales + service rollout](/en/success-stories/miltenyi-biotec-sales-service/) for the architecture, integration scope, and outcomes.
## What Spadoom delivers
B2B service organisations have it harder than B2C. Contracts vary per customer. Products are complex. Technicians are expensive. Escalations carry real financial risk. We've implemented [SAP Service Cloud V2](/en/blog/discover-the-power-of-sap-service-cloud/) for manufacturers, pharmaceutical companies, and utilities across Switzerland, Germany, Austria, and Italy — where getting it wrong means broken SLAs and unhappy enterprise customers.
As an SAP Gold Partner based in the DACH region, we bring local presence and hands-on project delivery. No offshore handoffs. Our team has run Service Cloud V2 projects from first workshop to hypercare — omnichannel configuration, SLA rule engines, CTI integration, ERP connectivity, and end-user training that gets agents productive in week one.
Our implementations go deep on contract-based service, integration with ERP for warranty and asset data, and escalation workflows to [SAP Field Service Management](/en/solutions/field-service-management/). We don't do out-of-the-box deployments; every project is scoped to what your service model actually requires. Delivery follows [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hypercare — adapted for Service Cloud V2 projects. For a complete platform walkthrough, see our [SAP Service Cloud V2 guide](/en/blog/sap-service-cloud-v2-guide/).
We also run SAP Service Cloud V2 for our own service desk. The workflows we recommend are the ones we use ourselves every day.
## ROI you can measure
SAP reports that organisations using Service Cloud V2 see concrete operational improvements:
- **35% faster case resolution** — with AI-assisted routing and contextual knowledge suggestions, agents spend less time searching and more time solving (source: SAP Value Stories, 2025)
- **98% SLA compliance** — automated escalation rules and real-time SLA dashboards eliminate the manual tracking that causes breaches (source: SAP Value Stories, 2025)
- **40% reduction in manual case routing** — intelligent routing assigns cases to the right team based on product, contract tier, and agent skills, not round-robin guesswork (source: SAP Value Stories, 2025)
These are not theoretical gains. Our clients in manufacturing and utilities report first-call resolution rates improving within the first quarter, and service managers reclaiming hours previously spent on manual SLA reporting. [Calculate your projected ROI](/en/roi-calculator/) based on your team size and ticket volume.
## Joule AI — intelligent service automation
SAP Service Cloud V2 ships with [Joule](/en/blog/sap-joule-sales-cloud-v2-hands-on-guide/), SAP's AI assistant, embedded directly into the agent workspace. This is not a bolt-on — Joule runs inside the service console:
- **Sentiment analysis** — Joule reads incoming messages and flags frustrated or escalation-risk customers in real time, so supervisors can intervene before a situation deteriorates
- **Intelligent case routing** — machine learning models route cases based on product category, customer tier, agent expertise, and current workload — not static rules that break when your team changes
- **Suggested responses** — Joule drafts reply templates based on the case context, knowledge base matches, and resolution history for similar issues
- **Case summaries** — when an agent picks up a case with a long interaction history, Joule generates a concise summary so they don't have to read through 30 emails to understand the situation
- **Knowledge article recommendations** — as agents work a case, Joule surfaces the most relevant troubleshooting guides and product documentation from your knowledge base
With Joule Studio (GA since Q1 2026), you can build custom AI agents for service scenarios — for example, an agent that checks warranty status in S/4HANA and drafts a resolution proposal before a human even opens the case. For the broader picture of AI agents in SAP CX, read [what agentic AI means for service and sales teams](/en/blog/agentic-ai-sap-what-it-means-for-sales/).
## Why V2 matters — V1 vs V2 compared
SAP Service Cloud V2 is a ground-up rebuild, not a feature update. V1 entered maintenance mode alongside Sales Cloud V1. SAP's active investment — including all Joule AI capabilities — is in V2 only.
| Capability | V1 | V2 |
|---|---|---|
| Architecture | Monolithic, customisation via SDK | Composable plug-in extensions — custom logic survives upgrades |
| AI & Joule | Not available | Native: sentiment analysis, intelligent routing, suggested responses, case summaries |
| UX | Classic Fiori-style | Modern, unified agent desktop — all channels in one workspace |
| Updates | Bi-annual, requires upgrade project | Quarterly, zero-downtime deployment |
| Extensibility | Key User Tools, limited | Plug-in framework, Joule Studio agents, SAP Build integration |
| Omnichannel | Channels added via third-party connectors | Native email, phone, chat, portal, and social in one console |
| CTI Integration | Third-party only | Native CTI framework with softphone embedding and screen pop |
| Field Service | Separate integration project | Native escalation to [SAP FSM](/en/solutions/field-service-management/) with full case context |
If you're evaluating the migration from V1 or from on-premise SAP CRM Service, read our [C4C to V2 migration guide](/en/blog/sap-service-cloud-v2-guide/) for a step-by-step process. The architectural shift affects not just features but how you extend and maintain the platform long-term.
## Independent validation
The market is noticing the rebuild. In the **2025 Gartner Magic Quadrant for CRM Customer Engagement Centers**, SAP moved from Niche Player to **sole Challenger** — the only vendor to change quadrant position that year. That reflects the pace of V2 development: quarterly releases, native AI, and composable architecture that analysts can now evaluate against Salesforce and ServiceNow.
On **G2** (based on verified user reviews, 2025):
| Category | SAP Service Cloud | Salesforce Service Cloud |
|---|---|---|
| Ease of Use | **8.7** | 8.4 |
| Quality of Support | **8.8** | 8.3 |
| AI Text Generation | **9.3** | 8.0 |
| Meets Requirements | **8.8** | 8.6 |
SAP scores higher on every dimension except review volume (219 vs 6,640 reviews). For organisations already running SAP ERP, these scores matter — the integration advantage compounds the UX advantage. For head-to-head comparisons, see our [SAP Service Cloud V2 vs Salesforce](/en/compare/sap-service-cloud-v2-vs-salesforce-service-cloud/) and [vs Zendesk](/en/compare/sap-service-cloud-v2-vs-zendesk/) pages.
## Pricing and licensing
SAP Service Cloud V2 typically costs between **$60 and $80 per user per month**, depending on volume and contract terms. Compare that to the main alternatives:
- **Salesforce Service Cloud**: $25–$500 per user per month across five tiers. The entry-level Starter tier is limited; most B2B teams need Enterprise ($165) or Unlimited ($330) for omnichannel and AI features.
- **Zendesk Suite**: $55–$115 per agent per month. Competitive for B2C, but lacks native SAP ERP integration and the depth of SLA management that B2B service teams require.
SAP integration can use supported APIs and preconfigured integration content. The actual data scope, latency and middleware requirements depend on the products, editions and configured scenario. Assess mapping, licences, error handling and monitoring before comparing total cost; SAP branding alone does not remove integration work or guarantee savings.
Spadoom offers fixed-price implementation packages so you know the full investment before signing. For SMEs looking to get started quickly, see our [CRM in 10 Days](/sme) package — it covers both [Sales Cloud](/en/solutions/sales-cloud/) and Service Cloud V2 deployment.
## Industry use cases
SAP Service Cloud V2 is built for B2B complexity. Here's how we've deployed it across industries in Switzerland, Germany, Austria, and Italy:
**Pharmaceutical and medical devices** — Regulated service environments where every interaction must be traceable. We configure case documentation workflows that satisfy audit trail requirements, warranty tracking linked to serial numbers in SAP ERP, and compliance-aware escalation rules. Agents see device history, batch numbers, and recall status without leaving the service console.
**Utilities** — SLA enforcement is non-negotiable. We set up multi-tier SLA structures tied to customer contracts, automated escalation chains when response windows are at risk, and field dispatch integration for on-site technician scheduling via [SAP FSM](/en/solutions/field-service-management/). Real-time dashboards give operations managers visibility into SLA performance across regions.
**Manufacturing** — Spare parts ordering, warranty claims, and return authorisation workflows that connect directly to S/4HANA. Agents can check part availability, create service orders, and trigger logistics processes from the case — no switching to ERP. We configure product-based routing so cases land with the team that knows the equipment.
**Professional services** — Contract-based SLA management where service levels vary by client, engagement tier, and geography. We integrate Service Cloud V2 with project management in S/4HANA so that service cases linked to active engagements are visible to both the service desk and the project team.
## The integration advantage
SAP Service Cloud V2 becomes significantly more powerful when it's connected to the right systems. Agents need to see order history from ERP. They need to know if the product is under warranty. They need to dispatch technicians without re-entering information.
We handle these integrations as standard — not as an optional add-on. If you're on S/4HANA, SAP ECC, or SAP Commerce Cloud, the connectors are well-trodden ground. Pre-built integration covers:
- **Order and asset data** from S/4HANA — agents see what the customer bought, when, and whether it's under warranty
- **Field service escalation** to [SAP FSM](/en/solutions/field-service-management/) — dispatch technicians with full case context, no re-keying
- **Sales handoffs** to [SAP Sales Cloud V2](/en/solutions/sales-cloud/) — when a service interaction reveals an upsell opportunity, it flows directly to the sales team with context
- **Commerce integration** — customers who raise issues through your SAP Commerce storefront see their case status without logging into a separate portal
For non-SAP systems, we scope the integration as part of the project. Most B2B service teams also need CTI (computer-telephony integration) for screen pops and call logging — Service Cloud V2's native CTI framework handles this without third-party middleware.
## Pairing with S/4HANA Public Cloud
When [SAP S/4HANA Public Cloud](/en/solutions/s4hana-cloud-public/) is your ERP, Service Cloud V2 becomes the customer-facing layer of a single integrated system. Agents see what customers bought, when, and whether it's under warranty — pulled live from S/4HANA — without switching consoles. Spare-parts availability, service-order creation, and return authorisation all flow from the case view directly into the ERP, keeping the service team and the supply chain in sync without re-keying. When Joule checks warranty status in S/4HANA before a human opens the case, you're not patching two systems together — you're running one stack designed to work this way from the start. And for service profitability analytics — cases and SLAs against contract margins — [SAP Business Data Cloud](/en/solutions/business-data-cloud/) joins the service and ERP data in one governed foundation.
Spadoom handles both sides of this integration as a single delivery. We scope the S/4HANA Public Cloud connection alongside the omnichannel and SLA configuration — not as a post-go-live addition. If you're planning a clean-core ERP move alongside your CX transformation, our [SAP S/4HANA Public Cloud and Sales Cloud V2 integrated-stack guide](/en/blog/sap-s4hana-public-cloud-sales-cloud-v2-integrated-stack/) covers the architecture for the full CX layer, including the service-side integration touchpoints.
## Meet our team in Zurich — 29 June 2026
We're co-hosting **SAP CX für KMU – Summer Vibes** at AWS Zurich on Monday, 29 June 2026, with customer talks from intelligentfood, OPO Oeschger, STOBAG, and Nussbaum Matzingen. If you're evaluating Service Cloud V2, this is the room. [See the agenda and reserve a seat](/summer-vibes/).
## What good looks like
Six weeks after go-live, your service desk should:
- Have a single view of every customer across every channel
- Resolve first contacts faster because agents have full context — order history, warranty status, previous cases
- Escalate to field service without picking up the phone
- Run monthly SLA reporting in minutes, not days
- See Joule surfacing relevant knowledge articles before agents have to search
Six months after go-live, you should see measurable improvement in first-call resolution rates, SLA compliance, and agent satisfaction scores. We track these metrics post-go-live and hold ourselves accountable for the outcomes — not just the deployment.
[SAP Integration Suite: supported integration capabilities](https://www.sap.com/products/technology-platform/integration-suite.html).
---
### E-Commerce
SAP Product: SAP Commerce Cloud
URL: https://www.spadoom.com/en/solutions/sap-commerce-cloud/
Description: B2B and B2C commerce built to handle real catalogue complexity. We launched it in 90 days for Franke and scaled it to millions of SKUs for industrial distributors. We know what it takes.
## What is SAP Commerce Cloud?
SAP Commerce Cloud is SAP's enterprise e-commerce platform for B2B and B2C selling, hosted as a managed cloud service on Microsoft Azure. Formerly known as SAP Hybris, it ships a product catalogue engine built for millions of SKUs, customer-specific pricing from SAP condition records, multi-warehouse order management, and native real-time integration with [SAP S/4HANA](https://www.sap.com/products/erp/s4hana.html). Modern implementations use [SAP Composable Storefront](https://help.sap.com/docs/SAP_COMMERCE_COMPOSABLE_STOREFRONT) — an Angular-based headless PWA, formerly Spartacus — to decouple frontend and commerce engine. SAP's [official Commerce Cloud product page](https://www.sap.com/products/crm/commerce-cloud.html) is the canonical reference. SAP has been named a Leader in the Gartner Magic Quadrant for Digital Commerce 11 years running (2014–2025).
Spadoom is an SAP Gold Partner specialising in Commerce Cloud implementation across Switzerland, Germany, Austria, and Italy — with offices in the DACH region and Southern Europe. Our DACH CX practice is led by Dario Pedol, spokesperson of the DSAG (German-speaking SAP user group) CX working group Switzerland. The rest of this page covers which edition fits which buyer, what we deliver, how Cloud Edition compares to the new ERP Edition, what it costs, and where we have put it into production.
Spadoom in numbers · SAP Commerce Cloud
90 days
Franke: legacy to go-live
11
Consecutive years SAP a Gartner MQ Leader (2014–2025)
1×
SAP Quality Award (Franke, 2024)
4
Countries Spadoom delivers Commerce Cloud in (CH, DE, AT, IT)
Franke 90-day go-live: SAP Quality Award winner, 2024. Gartner MQ Leader citation: SAP press, November 2025.
## Case study — Franke: 90 days from legacy to SAP Quality Award
Our most-cited project. Franke had a stalled custom B2B e-commerce build. We replaced it with SAP Commerce Cloud in 90 days — composable storefront, B2B pricing, full SAP ERP integration. The result: an **SAP Quality Award** for implementation quality and a platform that now serves Franke's global distribution network. [Read the full Franke story](/en/success-stories/franke-legacy-to-award-winning/) for the timeline, migration approach, and lessons learned.
## SAP Commerce Cloud editions — Cloud Edition vs ERP Edition vs on-premise
In 2026 SAP ships three commerce products under similar names. Buyers regularly ask us which one they actually need. The short answer:
| Edition | Best for | Architecture | Go-live | Where it lives |
|---|---|---|---|---|
| **SAP Commerce Cloud (Cloud Edition)** | Enterprise B2B and B2C with complex catalogues (≥100k SKUs), multi-country, deep ERP integration | Standalone commerce engine, composable storefront, OCC REST APIs | 12–24 weeks (90 days for Franke-style scoped projects) | SAP-managed cloud on Azure |
| **SAP Commerce Cloud, ERP Edition** | SMEs and mid-market on S/4HANA Public Cloud who need B2B commerce without a separate platform | B2B storefront built into S/4HANA Public Cloud, master data via SAP Business Data Cloud, Joule included | ~90 days | Inside S/4HANA Public Cloud |
| **SAP Commerce (on-premise / Hybris)** | Existing customers on the legacy platform | Self-hosted, monolithic | — (in End-of-Mainstream-Maintenance transition) | Customer data centre |
**Cloud Edition** is the right answer for most enterprise scenarios — and the focus of this page. It is what we built for Franke and what we migrate hybris customers onto.
**ERP Edition** is the credible new SAP answer for the mid-market on S/4HANA Public Cloud, unveiled at SAP Sapphire Orlando in May 2026. Spadoom is one of the first pilot partners delivering it. See our [ERP Edition deep dive](/en/blog/sap-commerce-cloud-erp-edition-for-sme/) and the [Cloud Edition vs Shopify Plus](/en/compare/sap-commerce-cloud-vs-shopify-plus/) and [ERP Edition vs Shopify Plus](/en/compare/sap-commerce-cloud-erp-edition-vs-shopify-plus/) comparisons.
**On-premise hybris** is in transition. If you are still on it, our [Hybris end-of-life migration checklist](/en/blog/sap-hybris-end-of-life-migration-checklist-2026/) and [90-day migration playbook](/en/blog/sap-hybris-to-commerce-cloud-90-day-playbook/) lay out the path off it.
## New for SMEs: SAP Commerce Cloud, ERP Edition
At SAP Sapphire Orlando in May 2026, SAP unveiled the **SAP Commerce Cloud, ERP Edition** — a lightweight B2B commerce variant built into S/4HANA Public Cloud, with master data flowing through SAP Business Data Cloud and Customer Data Cloud, Joule included, and a 90-day implementation target. It is the first credible SAP commerce answer for the mid-market on cloud ERP, and **Spadoom is one of the first pilot partners** delivering it. For the full architectural and strategic breakdown, see our [DSAG-CX-spokesperson take on the ERP Edition](/en/blog/sap-commerce-cloud-erp-edition-for-sme/).
## What Spadoom delivers
Our track record in SAP Commerce Cloud is long and specific. We built Franke's award-winning B2B platform in 90 days — a project that replaced a stalled custom build and won an SAP Quality Award. We've migrated distributors off legacy hybris accelerators to SAP Commerce Cloud Composable Storefront. We've scaled catalogue management for companies with 3+ million SKUs across multiple countries and languages.
As an SAP Gold Partner with offices in Switzerland, Italy, Austria, and Estonia, we bring local presence across the DACH region and Southern Europe. No offshore handoffs. The architects who scope your project are the same people who configure your storefront and train your team. When something breaks at 8 AM on a Monday, you call someone in your time zone.
What we handle end to end:
- **Storefront build** — composable or accelerator, B2B or B2C, single-brand or multi-brand
- **Catalogue setup** — product modelling, variant management, classification, and localisation for millions of SKUs
- **Pricing and promotions** — customer-specific pricing, tiered discounts, and promotion rules that work with your existing SAP condition records
- **SAP ERP integration** — bidirectional sync with S/4HANA or ECC for pricing, stock, orders, and customer master data
- **B2B workflows** — punch-out, order approval chains, budget management, and customer-specific product visibility
- **Training and hyper-care** — we don't leave after go-live. Four weeks of active support, issue resolution, and adoption tracking
Our delivery follows [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hyper-care — adapted for SAP Commerce Cloud projects. Discovery takes two weeks. We map your catalogue structure, pricing rules, order workflows, and integration points before a single line of code is written.
For a full technical overview of the platform — from product content management to order orchestration — see our [SAP Commerce Cloud A-Z Handbook](/en/blog/the-complete-guide-to-sap-hybris-a-z-handbook-to-unleash-the-power-of-sap-commer/).
### Franke: 90 days from legacy to SAP Quality Award
Our most-cited project. Franke had a stalled custom B2B e-commerce build. We replaced it with SAP Commerce Cloud in 90 days — composable storefront, B2B pricing, full SAP ERP integration. The result: an **SAP Quality Award** for implementation quality and a platform that now serves Franke's global distribution network. [Read the full Franke story](/en/success-stories/franke-legacy-to-award-winning/) for the timeline, migration approach, and lessons learned.
## ROI you can measure
E-commerce projects live or die on numbers. Here's what SAP Commerce Cloud implementations deliver when done right:
- **15–30% higher conversion rates** — B2B buyers who can self-serve (check stock, see their contract prices, reorder) convert at significantly higher rates than those forced to call or email sales reps (source: SAP Customer Experience benchmarks, 2025)
- **20–25% increase in average order value** — cross-sell and up-sell recommendations based on purchase history and catalogue relationships. Customers buying one product see the accessories, spare parts, and bundles that go with it
- **60–70% reduction in time-to-market for new storefronts** — composable storefront plus the B2B accelerator templates mean launching a second country or a second brand takes weeks, not months
- **40% lower cost-to-serve** — self-service order tracking, returns, and reorder lists reduce call centre volume for routine B2B transactions
These are not theoretical. Our clients see order error rates drop by 80%+ after moving from phone/fax ordering to online self-service. The most immediate gain is cost-to-serve: every order that goes through self-service instead of a phone call saves your inside sales team 15–20 minutes. Multiply that by hundreds of orders per week.
The ROI case typically pays back the implementation cost within 12–18 months. [Calculate your projected return](/en/roi-calculator/) based on your order volume and average transaction size.
## Independent validation
The analyst community has consistently recognised SAP Commerce Cloud. In the **2025 Gartner Magic Quadrant for Digital Commerce**, SAP was named a **Leader for the 11th consecutive year** — the only vendor to hold the position unbroken since the report's inception in 2014. That is not momentum from a legacy install base — it reflects continued investment in composable architecture, B2B capabilities, and AI-driven personalisation.
SAP Commerce Cloud is also a **Leader** in both the **IDC MarketScape for Enterprise B2B Digital Commerce** (2023–2024) and the **IDC MarketScape for Enterprise B2C Digital Commerce** (2024).
On **G2** (based on verified user reviews, 2025):
| Category | SAP Commerce Cloud | Shopify Plus | Adobe Commerce |
|---|---|---|---|
| Overall Rating | **4.0** | 4.4 | 4.0 |
| Ease of Use | 8.4 | **8.9** | — |
| Quality of Support | **8.6** | 8.4 | — |
Shopify Plus leads on ease of use — expected for a platform designed for rapid setup and smaller catalogues. SAP Commerce Cloud scores higher on quality of support and matches Adobe Commerce overall despite serving a more complex B2B market. For organisations already running SAP ERP, the integration advantage compounds the platform advantage. For head-to-head comparisons, see our [SAP Commerce Cloud vs Shopify Plus](/en/compare/sap-commerce-cloud-vs-shopify-plus/) and [vs Adobe Commerce](/en/compare/sap-commerce-cloud-vs-adobe-commerce/) analysis pages.
**Platform reliability at scale:** During Cyber Week 2025, SAP Commerce Cloud processed **$17.8 billion in gross merchandise value** (up 40% year-over-year) with **100% platform uptime**. The previous year saw 18.2 million orders during the same peak period — again, zero downtime (source: SAP Commerce Cloud Year in Review, 2025).
## Composable Storefront — the modern architecture
If you're starting fresh or replacing an older hybris accelerator, composable storefront is the right direction. SAP Commerce Cloud Composable Storefront (formerly Spartacus) decouples the frontend from the commerce engine entirely — see the [official SAP Composable Storefront documentation](https://help.sap.com/docs/SAP_COMMERCE_COMPOSABLE_STOREFRONT) for the full architecture reference. The storefront is a Angular-based progressive web app (PWA) that talks to the commerce backend via OCC REST APIs.
**What that means in practice:**
- **Faster page loads.** The frontend is a static PWA served from a CDN. First contentful paint under 1.5 seconds. Product pages render client-side without round-trips to the commerce server.
- **Independent deployments.** Your frontend team ships UI changes without touching the backend. Your backend team updates pricing rules without a full storefront release. Two separate release cycles.
- **Full design control.** No Freemarker templates. No JSP. Standard Angular components with your own design system. Mobile-first by default.
- **Future-proof.** SAP's active investment is in the composable architecture. The classic accelerator still works, but new features ship for composable first.
**When to use the accelerator instead:** If you need an internal B2B portal where function matters more than UX, and you want to go live in 6–8 weeks, the accelerator approach still works. It's faster to configure, requires less frontend skill, and covers 80% of B2B self-service needs out of the box. We'll tell you which fits your situation — not the one that maximises project scope.
For a deeper dive on composable architecture, OCC APIs, and implementation patterns, see our [SAP Commerce Cloud A-Z Handbook](/en/blog/the-complete-guide-to-sap-hybris-a-z-handbook-to-unleash-the-power-of-sap-commer/).
## SAP Commerce Cloud on-premise to cloud migration
This is a question we get every week. If you're running SAP Hybris on-premise, the clock is ticking. SAP has been directing all new feature development to the cloud version since 2020. The on-premise version still gets security patches, but no new capabilities.
**Our migration methodology:**
We don't rip and replace. We've developed a phased approach based on what we learned migrating Franke — which won an SAP Quality Award:
1. **Assessment (weeks 1–2).** Map your current customisations, extensions, and integrations. Identify what transfers directly, what needs rebuilding, and what you can drop.
2. **Customer-facing layer first (weeks 3–8).** Launch the new composable storefront on top of your existing catalogue and pricing data. Customers see a modern frontend. Backend stays stable.
3. **Catalogue and order management (weeks 8–14).** Migrate product content, pricing rules, and order workflows to the cloud instance. Run both systems in parallel with order routing.
4. **Decommission (weeks 14–18).** Cut over remaining traffic. Shut down the on-premise instance.
Go-live happens at week 8 — before you've finished the migration. Customers get a better experience immediately. The backend migration happens behind the scenes.
**What trips people up:** Data migration is not a copy-paste job. Product classifications, price lists with thousands of condition records, and customer-specific catalogue views all need validation. We build automated migration scripts with data quality checks at every stage. If your legacy system has 50,000 products with incomplete attributes, we catch that in week one — not week twelve.
The other common mistake is trying to replicate every customisation from the old system. Most organisations discover that 30–40% of their legacy extensions are no longer needed. We help you separate what matters from what was built to work around old platform limitations.
We documented the full playbook — timelines, risk mitigation, and data migration patterns — in our [90-day migration playbook](/en/blog/sap-hybris-to-commerce-cloud-90-day-playbook/). It's based on real projects, not theory.
## Pricing and licensing
SAP Commerce Cloud licensing is based on gross merchandise volume (GMV) and traffic tiers, not a simple per-user price. That makes direct comparison tricky, but here's a realistic picture:
| | SAP Commerce Cloud | Shopify Plus | Adobe Commerce (Magento) |
|---|---|---|---|
| Pricing model | GMV + traffic tiers | Revenue-based (0.25% of GMV over $800K) | Licence + GMV tiers |
| Annual licence (mid-market) | EUR 150K–500K+ | EUR 24K–180K+ | EUR 40K–200K+ |
| B2B features | Native: punch-out, account pricing, approval workflows | Limited, requires apps | Available with B2B module |
| SAP ERP integration | Native, real-time | Third-party middleware | Third-party middleware |
| Multi-country / multi-brand | Built-in with shared catalogue | Separate stores (Plus only) | Multi-store with shared backend |
| Composable / headless | Yes (Composable Storefront) | Hydrogen (newer) | PWA Studio / Hyva |
| Hosting | SAP-managed cloud (Azure) | Shopify-managed | Self-hosted or Adobe-managed |
**The real cost question is total cost of ownership.** If you're already running SAP ERP, Commerce Cloud eliminates the middleware layer you'd need with Shopify Plus or Adobe Commerce. Real-time pricing, stock, and order sync come out of the box. For companies doing EUR 10M+ in online revenue with complex B2B requirements, SAP Commerce Cloud typically delivers lower TCO over a 3-year period despite higher licence costs.
Spadoom offers fixed-price implementation packages. You know the full investment — licence, implementation, training, and hyper-care — before signing. No surprise change requests at month four.
## Industry use cases
SAP Commerce Cloud is built for catalogue complexity and process depth. Here's where we've deployed it:
**Manufacturing and industrial distribution** — The core use case. Distributors with 500,000+ SKUs need customer-specific pricing, multi-warehouse stock visibility, and order approval workflows. We configure punch-out catalogues for procurement system integration (SAP Ariba, Coupa) and set up reorder lists that let buyers repeat last month's order in two clicks. Real-time stock and pricing from S/4HANA means no more "sorry, that price changed" emails after order submission. For companies with field sales teams, the same platform serves both the self-service portal and the sales rep's order entry — same prices, same stock, one system.
**Consumer goods and retail** — B2C brands with high SKU counts, seasonal catalogues, and multi-country storefronts. SAP Commerce Cloud handles localised content, currency, tax rules, and shipping per market — all from a single catalogue. The personalisation engine serves different promotions to different customer segments without custom code. One catalogue, one order management system, one integration layer — but each country gets its own storefront, pricing, and fulfilment logic.
**Automotive aftermarket** — Parts catalogues are a special kind of complex. Vehicle fitment data, supersession chains, and cross-reference lookups on top of standard e-commerce. We've built SAP Commerce Cloud storefronts that integrate with TecDoc and ETKA catalogues, serving the right parts for the right vehicle without forcing buyers to know part numbers.
**Food and beverage** — B2B ordering with minimum order quantities, case-pack logic, delivery window scheduling, and temperature-controlled logistics integration. SAP Commerce Cloud's order management handles split shipments across multiple warehouses and delivery routes. Route accounting integration with SAP ERP closes the loop from order to delivery to invoice. We've configured recurring order schedules that let restaurant and hospitality buyers set up weekly standing orders — reducing manual reordering to zero for their top 50 products.
## The integration advantage
SAP Commerce Cloud's strongest differentiator is how it connects to the rest of your SAP landscape. This is not an abstract benefit — it directly affects your order accuracy, pricing consistency, and operational efficiency.
**S/4HANA and ECC integration** — Real-time, bidirectional. When a customer checks product availability on your storefront, they see live stock from S/4HANA. When they place an order, it flows into SAP as a sales order — no CSV imports, no batch jobs, no reconciliation. Pricing comes from SAP's condition records, so the price online is always the price in ERP.
**[SAP CPQ](/en/solutions/configure-price-quote-cpq/)** — For complex B2B quoting (configurable products, tiered pricing, multi-step approvals), CPQ plugs directly into Commerce Cloud so buyers configure and price products inside the same storefront session. Essential for manufacturers selling configurable industrial equipment, automotive aftermarket bundles, or any catalogue where price depends on configuration.
**[SAP Engagement Cloud (formerly Emarsys)](/en/solutions/marketing-emarsys/) (marketing automation)** — Connect your commerce data to SAP Engagement Cloud for abandoned cart recovery, post-purchase campaigns, and personalised product recommendations based on browsing and purchase behaviour. The integration is pre-built. Campaign performance data flows back into commerce analytics.
**[SAP Customer Data Platform](/en/solutions/customer-data-platform/)** — Unify customer profiles across your storefront, service desk, and marketing channels. CDP collects behavioural data from Commerce Cloud (product views, searches, purchases) and combines it with CRM and service interactions. The result: a single customer view that powers personalisation across every touchpoint.
**[SAP Customer Identity (CIAM)](/en/solutions/customer-identity-ciam/)** — Enterprise-grade authentication and consent management for your storefront. Single sign-on across multiple brand sites, progressive profiling, and GDPR-compliant consent tracking. Essential for multi-brand or multi-country deployments where customers expect one login across all your properties.
When these systems work together, you get something that Shopify and Adobe cannot replicate: a commerce platform that knows your customer across sales, service, marketing, and ERP — with data flowing in real time, not via nightly syncs. A B2B buyer who called your service desk yesterday sees a follow-up banner when they log in today. A marketing campaign targeting high-value customers uses actual purchase data, not guesses. That's the difference between connected systems and a collection of tools.
## SAP Commerce Cloud implementation in Switzerland
Spadoom is headquartered in Zug, and Switzerland is our home market — not a flag on a coverage map. Our two most-cited Commerce Cloud references are Swiss companies. [Franke](/en/success-stories/franke-legacy-to-award-winning/), the Swiss kitchen and home solutions group, is the 90-day rebuild that won an SAP Quality Award and cut manual orders by 75% across 10+ global channels. [Distrelec](/en/success-stories/distrelec-b2b-commerce/), the B2B electronics distributor with Switzerland as its home market, is where our headless re-architecture reduced time-to-market by 70% and lifted conversion by 15%. And for [Meier Tobler](/en/success-stories/meier-tobler-field-service/), the Swiss building-technology supplier, we built the SAP Integration Suite backbone that keeps their online shop and S/4HANA in real-time sync — over 1 million messages a month.
Implementing commerce for the Swiss market comes with requirements that standard EU playbooks miss, and we build them in from day one:
- **Data protection**: dual compliance with the Swiss nDSG (nLPD) and GDPR — consent, privacy texts, and data-residency options covered for both regimes
- **Currency and tax**: CHF and EUR price lists side by side, with correct VAT determination per destination and cross-border customs handling for a non-EU country
- **Languages**: German, French, and Italian storefronts (plus English) with per-locale content, category structures, and legal texts
- **Swiss payments**: TWINT and PostFinance integrated via Datatrans or Saferpay alongside international card processing
- **Swiss ERP landscapes**: real-time integration with S/4HANA — on-premise or public cloud — the way we delivered it for Franke and Meier Tobler
We documented the full Swiss and DACH delivery approach — payments, VAT corridors, nDSG vs GDPR, logistics — in our [Commerce Cloud in Switzerland and DACH implementation guide](/en/blog/sap-commerce-cloud-partner-switzerland-dach/).
## Meet our team in Zurich — 29 June 2026
We're co-hosting **SAP CX für KMU – Summer Vibes** at AWS Zurich on Monday, 29 June 2026, with customer talks from intelligentfood, OPO Oeschger, STOBAG, and Nussbaum Matzingen. If you're evaluating SAP Commerce Cloud, this is the room. [See the agenda and reserve a seat](/summer-vibes/).
## What good looks like
A well-implemented SAP Commerce Cloud means:
- **Order error rate under 1%.** Self-service ordering with real-time pricing and stock eliminates the misquotes and out-of-stock surprises that plague phone/fax ordering
- **B2B buyer adoption above 70% within 6 months.** If your buyers are still calling instead of ordering online, something went wrong in the implementation. We track adoption and fix friction points during hyper-care
- **New country storefront live in 4–6 weeks.** Once the first storefront is running, rolling out to additional markets is a content and configuration exercise — not a development project
- **Page load times under 2 seconds.** Composable storefront with CDN delivery means fast pages everywhere, not just in your home market
- **Reorder rate up 30%+.** B2B buyers who can reorder their regular items in two clicks do it more often. That's revenue you weren't capturing before
Six months after go-live, these numbers tell the story. We track them, and we stay accountable through hyper-care and beyond.
Ready to discuss your SAP Commerce Cloud project? Whether you're building a new storefront, migrating from on-premise hybris, or replacing a platform that's holding you back — we'll give you an honest assessment. [Start the conversation](/en/contact/?topic=SAP%20Commerce%20Cloud&message=I'd%20like%20to%20discuss%20an%20SAP%20Commerce%20Cloud%20project.) or explore our [CRM in 10 Days](/sme) package if you're also looking at SAP Sales Cloud.
Evaluating providers? Our market roundup of the [best SAP Commerce Cloud implementation partners in Switzerland](/en/blog/best-sap-commerce-cloud-partners-switzerland/) shows how we compare, and who else deserves a look.
[SAP Integration Suite: supported integration capabilities](https://www.sap.com/products/technology-platform/integration-suite.html).
---
### Marketing
SAP Product: SAP Engagement Cloud
URL: https://www.spadoom.com/en/solutions/marketing-emarsys/
Description: Marketing automation that actually automates things. SAP Engagement Cloud (Emarsys) for email, SMS, push, and loyalty — with the segmentation and triggers your team will use every week, not just at launch.
## What is SAP Engagement Cloud?
SAP Engagement Cloud — formerly SAP Emarsys, renamed in early 2026 — is SAP's omnichannel marketing platform for B2C and e-commerce: email, SMS, push, and web personalisation orchestrated from one canvas, with AI-driven segmentation and 60+ pre-built tactics. The [official product page](https://www.sap.com/products/crm/emarsys.html) lists the [full capabilities](https://www.sap.com/products/crm/emarsys/features.html), and the [SAP Emarsys documentation](https://help.sap.com/docs/SAP_EMARSYS) covers setup and integration.
Spadoom has been implementing the platform since its Emarsys days, for retail and e-commerce brands across Switzerland, Germany, Austria, and Italy. This page walks through the automation programmes, AI capabilities, and data integrations we set up — and the revenue metrics we plan around.
## What Spadoom delivers
Emarsys is a powerful platform. Most teams use 20% of it. We close that gap. Our implementations cover the full channel mix — email, SMS, push notifications, web personalisation — and the automation flows that generate revenue without manual campaign management.
We have implemented Emarsys for retail brands, pet supply companies, pharmaceutical distributors, and luxury e-commerce businesses across Switzerland, Germany, Austria, and Italy. As an SAP Gold Partner based in the DACH region, we bring local presence and hands-on delivery — no offshore handoffs, no consultants who disappear after go-live.
The use cases differ but the approach is the same: start with what moves revenue (cart abandonment, re-engagement, loyalty), then expand as the team's confidence grows. We scope every project so the first automated campaigns are live within weeks, not months.
Our delivery follows [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hyper-care, adapted for SAP Engagement Cloud projects. We have mapped out [what each phase looks like in practice](/en/blog/sap-emarsys-setup-a-spadoom-guided-journey/). For a full overview of the platform and when it makes sense, read our [SAP Engagement Cloud guide](/en/blog/all-you-need-to-know-about-sap-emarsys/).
## ROI you can measure
Marketing automation only matters if it drives numbers your CFO cares about. SAP Engagement Cloud benchmark data shows concrete results from well-implemented deployments:
- **20% increase in email revenue** — triggered lifecycle campaigns consistently outperform batch-and-blast because they reach the right person at the right moment with the right offer
- **15% improvement in customer retention** — automated win-back, loyalty, and post-purchase flows keep customers active longer and reduce churn across cohorts
- **3x faster campaign deployment** — pre-built tactics and drag-and-drop automation mean your team launches campaigns in hours, not weeks of developer back-and-forth
These are not aspirational targets. They are the baseline we plan around. The gap between "installed Emarsys" and "Emarsys generating revenue" is execution — choosing the right automations, feeding them clean data, and iterating based on results. [Calculate your projected ROI](/en/roi-calculator/) based on your audience size and average order value.
## 60+ pre-built tactical programmes
This is the single biggest reason Emarsys wins against HubSpot, Mailchimp, and Klaviyo for e-commerce and retail. Instead of building every automation from scratch, Emarsys ships with 60+ pre-built tactical programmes — complete automation workflows based on industry best practices that your team activates, configures, and launches.
**Acquisition** — Welcome series for new subscribers, first-purchase nurture, referral programme triggers, and lead-to-customer conversion flows. Each tactic is designed to move contacts from anonymous to known to purchasing as efficiently as possible.
**Engagement** — Browse abandonment (the customer looked but did not buy), wishlist price-drop alerts, personalised product recommendations based on purchase and browse history, and category affinity campaigns. These are the campaigns that turn casual browsers into repeat buyers.
**Retention** — Lifecycle automations that detect when a customer is slipping away. Includes post-purchase follow-ups, replenishment reminders, loyalty tier upgrade nudges, win-back campaigns for lapsed customers, and churn prevention flows triggered by predictive scoring. For a deeper look at how loyalty and Emarsys work together, see our guide on [moving beyond points-based loyalty](/en/blog/beyond-points-sap-loyalty-emarsys-cdp/).
**Seasonal and event-driven** — Holiday campaigns, flash sale countdowns, birthday and anniversary messages, and back-in-stock notifications. Pre-built logic handles the timing and segmentation; your team focuses on creative and offers.
The value here is speed-to-revenue. A marketing team that would spend three months building automations from scratch in a generic tool can have the same programmes live in Emarsys within weeks. We cover the full campaign-building process in our [guide to effective marketing campaigns with SAP Engagement Cloud](/en/blog/all-you-need-to-know-for-developing-effective-marketing-campaigns-with-sap-emars/).
## AI-powered marketing
Emarsys does not just automate what you tell it to do — it learns from your data and makes your campaigns smarter over time. The AI and machine learning capabilities are built into the platform, not sold as add-ons:
- **Predictive segmentation** — machine learning models score every contact for purchase probability, churn risk, and product affinity. Segments update automatically as customer behaviour changes.
- **Send-time optimisation** — Emarsys calculates the optimal send time for each individual contact based on their engagement history. Not just "Tuesday at 10 am for everyone" — per-contact timing that lifts open rates.
- **Product affinity scoring** — the platform identifies which products each customer is most likely to buy next, based on purchase history, browse behaviour, and similar-customer patterns. Feed this into recommendations and you get relevance without manual merchandising rules.
- **Revenue attribution** — clear reporting on which campaigns, automations, and channels actually drive revenue. Not vanity metrics — attributed revenue per programme, so you know where to invest.
- **Churn prediction** — models flag customers likely to lapse before they do, giving your retention automations time to act.
The Joule AI copilot, SAP's cross-platform AI assistant, is now integrated into Emarsys for campaign insights, audience recommendations, and natural-language queries against your marketing data. For the broader picture of how AI agents are reshaping SAP CX, read [what agentic AI means for sales and marketing teams](/en/blog/agentic-ai-sap-what-it-means-for-sales/).
## Omnichannel execution
Emarsys is not an email marketing tool. It is an omnichannel customer engagement platform, and the distinction matters. Every automation and segment you build works across all channels from a single canvas:
- **Email** — the workhorse channel. Personalised content blocks, dynamic product recommendations, and A/B testing built in.
- **SMS** — transactional and promotional messages with the same segmentation and triggers as email. Ideal for time-sensitive offers and appointment reminders.
- **Push notifications** — mobile and web push for re-engagement when customers are not checking email.
- **Web personalisation** — on-site banners, product recommendations, and pop-ups that react to the same segments and lifecycle stages as your outbound campaigns.
- **Paid ad audience sync** — push Emarsys segments directly to Google Ads, Meta, and other paid channels for retargeting and lookalike audiences. No CSV exports, no stale lists.
- **In-app messaging** — reach customers inside your mobile app with contextual messages tied to their purchase journey.
The point is consistency. A customer who abandons a cart should not receive an email, an SMS, a push notification, and a retargeting ad all saying the same thing. Emarsys orchestrates across channels so each contact gets the right message on the right channel — and the others stay silent.
## Data integration is everything
Emarsys is only as good as the data you feed it. A campaign triggered by stale or incomplete customer data is worse than no campaign. We treat the data integration as the most critical part of every project.
If you are on SAP Commerce Cloud, the native connector gives you real-time order and browse events — product views, cart additions, purchases, and returns flow into Emarsys within seconds. For third-party shop systems (Shopify, Magento, custom storefronts), we build the integration as part of the project using Emarsys APIs and middleware where needed.
The real power unlocks when you connect Emarsys to the rest of the SAP CX stack. [SAP Customer Data Platform](/en/solutions/customer-data-platform/) unifies customer profiles from every touchpoint — web, app, in-store, service — and feeds them into Emarsys for segmentation. [SAP Loyalty Management](/en/solutions/loyalty/) syncs tier status, points balances, and reward eligibility so your campaigns reflect each customer's loyalty standing in real time.
This native data flow is a key reason why Emarsys outperforms [standalone marketing automation platforms](/en/blog/sap-emarsys-vs-standalone-marketing-automation/) that depend on batch syncs and fragile connectors. When your triggered campaign fires on a two-hour-old data sync instead of real-time events, you lose the moment — and the conversion. For more on how loyalty, Emarsys, and CDP work as an integrated stack, see [building lasting customer relationships with SAP Engagement Cloud](/en/blog/sap-emarsys-your-secret-to-building-lasting-customer-relationships/).
## Industry use cases
SAP Engagement Cloud is built for B2C and e-commerce, but the use cases extend well beyond online retail. Here is how we deploy it across industries:
**E-commerce and retail** — The core use case. Abandoned cart recovery, post-purchase follow-ups, replenishment reminders, personalised product recommendations, and loyalty programme integration. Emarsys's product catalogue and order data model means these automations work out of the box with minimal customisation.
**Luxury and fashion** — VIP loyalty programmes with tier-based communications, personalised styling recommendations, early access to collections, and event invitations. The segmentation engine handles high-value customer cohorts that need a different tone and cadence than mass-market campaigns.
**Travel and hospitality** — Booking abandonment flows, pre-arrival upsells, post-stay feedback and re-engagement, seasonal destination campaigns, and loyalty programme management. Send-time optimisation is especially valuable when your customers span multiple time zones.
**B2B with e-commerce** — Account-based nurture sequences, event marketing (webinar invites, trade show follow-ups), product launch announcements, and reorder reminders for consumables. While Emarsys is B2C-first, companies with B2B e-commerce storefronts get strong value from the product recommendation and lifecycle automation capabilities.
## What good looks like
Twelve weeks after go-live, your marketing team should be running:
- Automated lifecycle flows covering at least 60% of your customer base
- Personalised product recommendations in email and web driven by real purchase and browse data
- A loyalty programme that integrates with your transactional communications and reflects tier status in every touchpoint
- Weekly A/B tests that the team can run without developer support
- Clear revenue attribution showing which automations generate the most value
Six months in, the platform should be self-sustaining — your team launches new campaigns without Spadoom's help, iterates on what works, and retires what does not. We measure success by whether your marketing team can operate independently, not by how many consulting hours we bill after go-live.
---
### Customer Identity (CIAM)
SAP Product: SAP Customer Identity
URL: https://www.spadoom.com/en/solutions/customer-identity-ciam/
Description: Registration, login, and consent that works — and that your legal and security teams won't reject. SAP Customer Identity, configured for B2C and B2B use cases.
## What is SAP Customer Identity and Access Management (CIAM)?
SAP Customer Identity and Access Management (CIAM) is SAP's platform for customer registration, authentication, and consent — single sign-on, social login, MFA, progressive profiling, and auditable consent records for B2C and B2B. Built on the former Gigya platform, it is delivered as part of [SAP Customer Data Cloud](https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD); the [official SAP CIAM product page](https://www.sap.com/products/technology-platform/customer-identity.html) and SAP's [CIAM explainer](https://www.sap.com/resources/what-is-customer-identity-access-management) are the canonical references.
Spadoom implements SAP Customer Identity for clients across Switzerland, Germany, Austria, and Italy — with the GDPR and Swiss nDSG consent layer designed in from day one. The rest of this page covers what we deliver, how CIAM differs from a CDP, and the ROI a well-run identity project produces.
Spadoom in numbers · SAP Customer Identity (CIAM)
30–50%
Registration completion uplift (social login + progressive profiling)
60–75%
Marketing opt-in rate with structured consent flow
40–60%
Login-related support tickets cut within 3 months
8–12 weeks
Standalone CIAM go-live
Outcomes observed across Spadoom SAP Customer Identity rollouts. Specific results vary with prior baseline and traffic profile.
## What Spadoom delivers
Identity management is infrastructure. Getting it wrong costs you twice: lost conversions at registration and legal exposure when consent is not captured correctly.
Spadoom is an SAP Gold Partner with offices in Switzerland, Germany, Italy, Austria, and Estonia. We implement SAP Customer Identity for companies that need registration, login, and consent management integrated with their SAP CX stack. Our team delivers on-site across the DACH region and Northern Italy. No offshore handoffs.
Common scenarios we handle:
- A retailer deploying [SAP Commerce Cloud](/en/solutions/sap-commerce-cloud/) who needs a proper login and consent system from day one
- A B2B distributor replacing a custom-built registration flow that has become a maintenance burden
- A brand operating multiple regional web properties that need unified identity across countries
- A company preparing for Swiss nDSG or EU GDPR audits and discovering that their consent records are incomplete
Our delivery follows the [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hyper-care — adapted for identity projects. Every implementation includes screen-set configuration, consent flow design, integration setup, and end-user testing with your legal and marketing teams.
For a broader look at how SAP's identity and data tools fit together, our overview of [SAP Customer Data Cloud covers the full CDC landscape](/en/blog/all-you-need-to-know-about-sap-customer-data-cloud/) — including where CIAM sits within it.
## Customer Identity vs CDP — what's the difference?
Customer Identity (CIAM) and the [Customer Data Platform (CDP)](/en/solutions/customer-data-platform/) often get bundled in the same sentence, but they own very different jobs. Most enterprises end up needing both, and confusing them is the most common architectural mistake we see.
Customer Identity is the **front door**. It handles the moment a stranger becomes a known customer — registration, login, social sign-in, password reset, MFA — and the moment they tell you what they're comfortable with: marketing consent, data-processing consent, preference flags. It owns identity, authentication, and consent capture.
The Customer Data Platform is the **engine room**. It takes the identity and consent signals from CIAM, combines them with everything that person has ever done with you — orders, service tickets, browse behaviour, email engagement — and builds a unified, activate-ready profile. CDP owns unification, segmentation, and real-time activation.
Historically SAP grouped both capabilities under the SAP Customer Data Cloud (SAP CDC) umbrella. Since then SAP has split the offering into discrete products — Customer Identity for the CIAM job, Customer Data Platform for the unification and activation job — so you can buy, scope, and scale each one independently. In a typical SAP CX architecture, CIAM feeds registration and consent events into CDP in real time, and CDP feeds enriched, consent-compliant profiles back to Sales, Service, Commerce, and SAP Engagement Cloud (formerly Emarsys).
## ROI you can measure
Identity is not a cost centre. A well-implemented CIAM deployment produces measurable returns across three areas.
**Registration conversion.** Social login and progressive profiling reduce friction at the point of registration. Typical results: registration completion rates increase by 30–50% when you replace a 12-field form with social login plus two or three essential fields. Every percentage point of registration improvement feeds directly into your addressable customer base.
**Consent compliance rates.** With SAP Customer Identity, consent capture is part of the registration flow — not an afterthought pop-up. Clients who move from a generic cookie banner to a structured consent flow see opt-in rates for marketing communications reach 60–75%. Higher opt-in means a larger audience for [Emarsys campaigns](/en/solutions/marketing-emarsys/) and better data quality in your [Customer Data Platform](/en/solutions/customer-data-platform/).
**Support ticket reduction.** Self-service password reset, SSO, and clear account management screens eliminate the most common identity-related support requests. We typically see a 40–60% drop in "I can't log in" tickets within three months of go-live. That is real time returned to your support team.
## The compliance layer
Consent management is where legal and engineering intersect. You need consent records that are timestamped, versioned, and auditable. You need them synchronised to every system that uses them. And you need opt-out to propagate reliably — not on the next batch run, but immediately.
**The consent vault.** SAP Customer Identity stores every consent event with a timestamp, the exact wording shown to the customer, and the version of your privacy policy at the time. This is what auditors ask for. Without it, you are guessing.
**Granular consent types.** We configure separate consent categories: email marketing, SMS, data processing, third-party data sharing, profiling. Each consent is independent. A customer can opt into email but decline profiling. The system enforces this distinction downstream.
**Downstream propagation.** When we connect SAP Customer Identity to [SAP Customer Data Platform](/en/solutions/customer-data-platform/) and [Emarsys](/en/solutions/marketing-emarsys/), consent changes propagate in real time. A customer revokes marketing consent at 14:07. By 14:07, Emarsys stops sending. No batch delay. No manual suppression list. This is not optional for GDPR and nDSG compliance — it is the requirement.
**Swiss nDSG specifics.** The revised Swiss Federal Act on Data Protection (nDSG), in force since September 2023, requires documented consent for certain data processing activities. SAP Customer Identity's consent vault meets this standard. We configure it to capture and store the specific legal basis for each processing activity, which matters if your DPO is ever asked to produce records.
The consented profile data that flows into CDP then powers segmentation and personalisation. Our deep dive into [SAP Customer Data Platform explains how that works in practice](/en/blog/sap-customer-data-platform-a-deep-dive-into-its-core-features-and-benefits/).
## Progressive profiling in practice
Asking for 15 fields on a registration form is a conversion killer. Progressive profiling is the alternative: collect data gradually, across multiple sessions, based on what you actually need at each stage.
**How it works.** On the first visit, you capture email and a password (or social login — no password at all). On the second login, you ask for company name and role. After the third purchase, you ask for communication preferences. SAP Customer Identity manages this logic through configurable screen sets. Each screen set defines which fields to show, when to show them, and what triggers the next step.
**The impact on conversion.** Reducing registration fields from 10+ to 3 typically lifts completion rates by 30–50%. That is not a theoretical number. We measure it on every project by comparing pre- and post-implementation registration funnels.
**Data quality improves too.** When you ask for information at the right moment, customers give you accurate answers. A job title provided during a product demo request is more reliable than one filled in during a rushed checkout. Progressive profiling gives you better data, not just more data.
**Configuration, not code.** SAP Customer Identity's screen-set editor lets you adjust profiling flows without developer involvement. Marketing can add a field. Legal can require a new consent checkbox. Neither needs a release cycle to make it happen.
## B2B identity specifics
B2B identity is more complex than B2C. You have company accounts with multiple users, varying permission levels, and approval workflows that differ by customer.
**Delegated administration.** SAP Customer Identity supports a hierarchy: organisation, then groups, then individual users. A company admin can invite new users, assign roles, and deactivate former employees — without contacting your support team. This is table stakes for B2B portals with more than 50 buyer accounts.
**Role-based access.** Different users within the same company need different access. A procurement manager sees pricing and can place orders. A technical user sees documentation and support tickets. An executive sees reporting dashboards. We configure these roles in SAP Customer Identity and enforce them across your commerce and service portals.
**Account approval workflows.** Not every self-registered user should get immediate access. For B2B, we configure approval workflows where a new registration triggers a review by the account owner or your internal sales team. The user gets notified when access is granted. No manual email chains.
**Integration with B2B Commerce.** When paired with [SAP Commerce Cloud](/en/solutions/sap-commerce-cloud/), delegated admin maps directly to the commerce organisation model. Buyers see their company's negotiated pricing, order history, and credit limits. Identity and commerce stay in sync without custom middleware.
If your B2B portal currently requires a support ticket to add a new buyer, this is worth looking at.
## SSO and passwordless authentication
Passwords are the weakest link in customer identity. They get forgotten, reused, and stolen. SAP Customer Identity gives you alternatives.
**Single sign-on (SSO).** One authentication event covers every connected property — web store, mobile app, support portal, partner portal. Customers authenticate once. Your systems share the session. You stop managing multiple identity stores, and customers stop resetting passwords across five different sites.
**Social login.** Google, Apple, LinkedIn, and Microsoft login integrations ship out of the box. Adding a social login provider takes hours, not weeks. The benefit: verified email addresses from day one and registration completion rates that are 2–3x higher than traditional email-and-password forms.
**FIDO2 and WebAuthn.** Passwordless authentication using device biometrics (fingerprint, face recognition) or hardware security keys. SAP Customer Identity supports FIDO2/WebAuthn for customers who want the highest security without the friction of typing passwords. Adoption is growing fast — especially on mobile devices where biometric authentication is already the default.
**Risk-based MFA.** Not every login needs a second factor. SAP Customer Identity evaluates login context — device, location, time of day, IP reputation — and triggers step-up authentication only when risk indicators appear. A returning customer on their usual laptop gets straight in. The same account logging in from a new country at 3 AM gets prompted for a verification code. Security that adapts to the situation, not a blanket policy that frustrates everyone.
## The integration advantage
SAP Customer Identity is most valuable when it connects to the rest of your stack. Identity data in isolation is a directory. Identity data connected to commerce, marketing, and service becomes a growth driver.
**SAP Commerce Cloud.** CIAM provides the registration, login, and consent layer for your storefront. Customer identity flows into Commerce Cloud's customer model. One account, one login, one set of preferences — whether the customer is on your B2C webshop or your B2B ordering portal. [Read more about SAP Commerce Cloud](/en/solutions/sap-commerce-cloud/).
**Emarsys.** Consent captured in CIAM determines what Emarsys can send and to whom. Profile data collected through progressive profiling enriches Emarsys segments. When a customer updates their preferences in CIAM, Emarsys reflects the change in real time. This connection is what makes compliant personalisation possible. [Read more about Emarsys](/en/solutions/marketing-emarsys/).
**SAP Customer Data Platform.** CIAM feeds first-party identity data into CDP. CDP stitches it with behavioural data from web, app, and offline sources to build a unified profile. Without CIAM as the identity source, CDP is working with anonymous fragments. [Read more about SAP CDP](/en/solutions/customer-data-platform/).
**SAP Sales Cloud V2.** For B2B use cases, customer identity data from CIAM can inform the CRM. When a buyer registers on your portal, that event can create or update a contact in Sales Cloud. Your sales team sees portal activity alongside pipeline data.
**Non-SAP systems.** SAP Customer Identity exposes REST APIs, JavaScript SDKs, and webhook events. We have connected it to Salesforce, Shopify, custom-built portals, and third-party analytics platforms. If your system accepts HTTP calls, it can receive identity events.
## What good looks like
A well-implemented SAP Customer Identity deployment produces results you can track in the first 90 days:
- Registration completion rates up 30–50% from reduced form friction
- Marketing consent opt-in rates at 60–75% through structured, in-flow capture
- Identity-related support tickets (password resets, login issues) down 40–60%
- Consent audit readiness: every record timestamped, versioned, and retrievable on demand
- SSO adoption above 80% across connected properties within 60 days
Six months after go-live, we review these numbers with you. If your B2B delegated admin is not reducing support load, we adjust the configuration. If progressive profiling is not lifting data completeness, we rework the screen sets. The implementation is not done at go-live. It is done when the metrics prove it works.
Got an identity project to discuss? [Talk to us about your requirements](/en/contact/?topic=SAP%20Customer%20Identity&message=I%27d%20like%20to%20discuss%20an%20SAP%20Customer%20Identity%20(CIAM)%20implementation.) — no pitch deck, just a conversation.
---
### Customer Data Platform (CDP)
SAP Product: SAP CDP
URL: https://www.spadoom.com/en/solutions/customer-data-platform/
Description: One customer profile across every touchpoint — commerce, service, marketing, and ERP. We build the data model and the ingestion pipelines so you actually trust what you see.
## What is SAP Customer Data Platform?
SAP Customer Data Platform is SAP's real-time customer data platform: it ingests data from commerce, service, marketing, and ERP sources, resolves identities across anonymous and known touchpoints, and activates unified, consent-compliant profiles across every connected channel. The [official product page](https://www.sap.com/products/data-cloud/customer-data-platform.html) and the [SAP Help Portal documentation](https://help.sap.com/docs/SAP_CUSTOMER_DATA_PLATFORM) are the canonical references.
Spadoom designs the data models, ingestion pipelines, and activation flows behind SAP CDP for clients in Switzerland, Germany, Austria, and Italy. Below: what we deliver, how CDP differs from Customer Identity (CIAM), and the ROI ranges we observe in production.
Spadoom in numbers · SAP CDP
15–30%
Campaign waste reduction observed at clients
2–3×
Personalisation lift versus pre-CDP baseline
8–12 weeks
Focused CDP go-live (2–3 sources)
20–40%
Duplicate customer record reduction (identity resolution)
Ranges observed across Spadoom CDP implementations. Outcomes scale with source data quality.
## What Spadoom delivers
A Customer Data Platform is only valuable if the data inside it is trustworthy. Most CDP projects fail at the data layer — poor source mapping, inconsistent identifiers, incomplete consent capture. We have seen the wreckage across DACH and Southern Europe. We have fixed it.
Every Spadoom CDP project starts with a data audit. We sit with your engineering and marketing teams and map every customer touchpoint: what data it generates, how it is structured, where identifiers exist, and what needs transforming before ingestion. We document gaps. We flag consent blind spots. Only then do we configure the platform.
This approach is slower up front and significantly faster overall. It eliminates the rework cycles that plague CDP rollouts where teams skip the audit and start connecting sources on day one.
As an [SAP Gold Partner](/en/blog/all-you-need-to-know-about-sap-gold-partners/) with offices in Zurich, Bolzano, Vienna, and Tallinn, we deliver CDP projects across the DACH region, Italy, and broader Europe. Our delivery follows the [SAP Activate methodology](/en/how-we-work/) across five phases — discovery, preparation, exploration, realisation, and deployment — adapted specifically for CDP scope and complexity.
We are not a platform reseller. We build the data model, the ingestion pipelines, the identity rules, and the activation flows. Then we train your team to run it.
## CDP vs Customer Data Cloud — which is which?
CDP and Customer Identity (CIAM, formerly part of SAP Customer Data Cloud) sound similar and are often confused. They solve different problems and most enterprises end up needing both.
Think of **[Customer Identity (CIAM)](/en/solutions/customer-identity-ciam/)** as the front door. It answers "who is this person, how do they prove it, and what did they consent to?" — registration, login, social sign-in, password reset, consent capture, preference management. It owns the moment a stranger becomes a known customer.
Think of **Customer Data Platform (CDP)** as the engine room. It answers "what has this person ever done with us, what do they look like as a unified profile, and which audiences should we activate?" — ingest from commerce, service, marketing, ERP and third parties; resolve identities across anonymous and known touchpoints; build segments; push to channels in real time.
Historically SAP grouped both capabilities under the SAP Customer Data Cloud (SAP CDC) umbrella. Since then SAP has split the offering into discrete products — Customer Identity for the CIAM job, Customer Data Platform for the unification and activation job — so you can buy, scope, and scale each one on its own terms. In a typical SAP CX architecture, CIAM feeds registration and consent events into CDP, and CDP feeds enriched profiles back to Sales, Service, Commerce, and SAP Engagement Cloud (formerly Emarsys).
## ROI you can measure
CDP projects should pay for themselves. If yours does not, something went wrong in scoping or execution. Here is what we see across our client base:
- **15–30% reduction in campaign waste.** When you suppress recently converted customers and deduplicate audiences, you stop paying to advertise to people who already bought. That saving is measurable from month one.
- **2–3x higher personalisation rates.** Unified profiles mean SAP Engagement Cloud and your commerce engine see real behaviour, not partial snapshots. Personalised content rates double or triple because the data behind them is complete.
- **Segment activation in minutes, not days.** Marketers build and push segments from the CDP interface without filing a ticket. The time from business idea to live campaign drops from days to under an hour.
- **20–40% reduction in duplicate customer records.** Identity resolution merges fragmented profiles. Your CRM, service desk, and marketing platform stop treating one customer as three separate people.
Want to model the numbers for your business? Use our [ROI calculator](/en/roi-calculator/) to estimate the impact before the project starts.
## SAP CDP in the SAP CX context
SAP Customer Data Platform is the connective tissue of the SAP CX suite. When it is properly implemented, every connected product gets better.
[SAP Engagement Cloud](/en/solutions/marketing-emarsys/) receives richer segmentation data. Campaigns target audiences built from unified profiles, not siloed email lists. Suppression works because SAP Engagement Cloud knows what happened in commerce and service, not just in past email sends. Read more in our [deep dive on Engagement Cloud and CDP integration](/en/blog/beyond-points-sap-loyalty-emarsys-cdp/).
[SAP Sales Cloud V2](/en/solutions/sales-cloud/) agents see customer lifetime value, recent support tickets, and marketing engagement alongside pipeline opportunities. They walk into calls with context instead of guessing.
[SAP Service Cloud V2](/en/solutions/service-cloud/) agents see a customer's full purchase history, loyalty tier, open marketing offers, and past interactions — in one screen. Resolution times drop because agents stop asking customers to repeat themselves.
[SAP Commerce Cloud](/en/solutions/sap-commerce-cloud/) uses CDP segments for on-site personalisation. Product recommendations, pricing rules, and content blocks respond to the unified profile, not just the current session cookie.
[SAP Customer Identity (CIAM)](/en/solutions/customer-identity-ciam/) provides the authentication and consent layer that feeds CDP. Registration events, consent updates, and preference changes flow into CDP in real time. For detail on how these two systems divide responsibility, read our [CDP vs CDC comparison](/en/blog/sap-cdp-vs-cdc-unraveling-the-functionalities-and-benefits-of-each-platform/).
[SAP Loyalty Management](/en/solutions/loyalty/) shares points balances, tier status, and reward redemptions with CDP. This data enriches profiles and enables loyalty-aware segmentation across all channels.
If you are running multiple SAP CX products, a CDP implementation multiplies the value of each one. If you are only on one product today, CDP is the foundation that makes the next one fast to deploy.
## Identity resolution
Identity resolution is the hardest part of a CDP implementation. It is also the part that delivers the most value. Get it wrong and your unified profiles are fiction. Get it right and every downstream system benefits.
SAP CDP supports two approaches:
**Deterministic matching** links records that share an exact identifier — email address, phone number, loyalty ID, CRM account number. This produces high-confidence merges. It is the backbone of identity resolution and handles 60–80% of matches in most deployments.
**Probabilistic matching** fills the gaps. It uses behavioural signals, device fingerprints, and fuzzy attribute matching to link records that likely belong to the same person. Confidence scores determine whether a merge happens automatically or gets flagged for review.
Spadoom configures **merge policies** that define which source wins when two records conflict. Your CRM says the customer is in Zurich; your commerce platform says Basel. Merge policies resolve this based on source trustworthiness and recency, not random chance.
The practical impact: clients typically see a 20–40% reduction in duplicate profiles after identity resolution is live. That means fewer wasted marketing impressions, more accurate lifetime value calculations, and service agents who see the real history.
## Real-time activation
Batch data loads are necessary but not sufficient. The highest-value CDP use cases depend on real-time event processing.
SAP CDP ingests streaming events — page views, cart additions, form submissions, service interactions, app events — and updates the unified profile within seconds. This powers three categories of use case:
**Cart abandonment and browse recovery.** A customer adds a product to their cart on your commerce site and leaves. Within seconds, CDP updates the profile and pushes the event to SAP Engagement Cloud. The abandonment email fires while the intent is still warm — not 24 hours later from a batch sync.
**Real-time lead scoring.** A prospect visits your pricing page, downloads a whitepaper, and opens a recent email. Each event updates the lead score in CDP. When the score crosses a threshold, CDP pushes the enriched profile to [Sales Cloud V2](/en/solutions/sales-cloud/) as a hot lead. The sales rep sees it in their queue within minutes.
**Service context enrichment.** A customer contacts support after placing an order and browsing the returns page. The CDP profile — updated in real time — tells the [Service Cloud V2](/en/solutions/service-cloud/) agent what happened before the customer explains. Resolution is faster. The customer feels understood.
Spadoom configures the event pipeline architecture during the discovery phase. We define which events matter, how they map to the data model, and what activation rules trigger downstream actions.
## What non-SAP data looks like
Many of our clients have customer data spread across non-SAP systems. SAP CDP handles these through standard API ingestion, pre-built connectors, and streaming integrations.
**Salesforce CRM.** Accounts, contacts, opportunities, and activities sync into CDP via API connectors. We map Salesforce fields to the CDP data model and configure bidirectional sync where needed.
**Shopify and other commerce platforms.** Orders, customer records, and browsing events flow into CDP. This is common for clients running SAP for B2B and Shopify for B2C — CDP unifies the customer across both.
**Custom APIs and mobile apps.** Any system with a REST or webhook endpoint can push events to CDP. Mobile app SDKs capture in-app behaviour — screen views, feature usage, in-app purchases — and stream it to the unified profile.
**Data lakes and warehouses.** BigQuery, Snowflake, Azure Synapse, Amazon Redshift — CDP ingests batch exports from any of these. This handles historical data loads and periodic enrichment from analytics systems.
We scope every non-SAP integration as part of the project plan. Data format mapping, authentication, rate limits, error handling, and monitoring are all defined before development starts. There are no surprises at go-live about what can and cannot be connected.
Connecting non-SAP sources raises a follow-up question: does this data belong in CDP or CDC? Our [guide to SAP CDP vs CDC](/en/blog/sap-cdp-vs-cdc-unraveling-the-functionalities-and-benefits-of-each-platform/) helps you draw that line before the project starts.
## The integration advantage
A CDP is not a standalone product. Its value compounds with every system connected to it.
One data source in CDP gives you a clean profile store. Two sources give you identity resolution. Three sources give you segments that actually reflect customer behaviour. Four or more sources give you a single customer view that no individual system can produce on its own.
This compounding effect is why we treat CDP as infrastructure, not as an application. It sits between your operational systems and your activation channels. It does not replace your CRM, your marketing platform, or your commerce engine. It makes all of them better by feeding them unified, consent-compliant, real-time customer data.
The practical implication for project planning: CDP value scales with the number of connected sources. Start with your two or three highest-value sources — typically CRM, commerce, and marketing. Prove the ROI. Then expand. Each additional source is faster to connect because the data model and identity rules already exist.
For a detailed look at how CDP fits into the broader SAP CX architecture, read our [SAP CDP deep dive](/en/blog/sap-customer-data-platform-a-deep-dive-into-its-core-features-and-benefits/).
## What good looks like
At six months post-go-live, a well-implemented CDP deployment shows measurable results across four dimensions:
**Data quality.** Duplicate profiles are down 20–40%. Consent coverage is above 90% for active customers. Data freshness SLAs are met — real-time events land in under 10 seconds, batch sources sync within their defined windows.
**Marketing efficiency.** Campaign audience overlap drops because segments are built from unified profiles, not siloed lists. Suppression rules work across channels. Cost-per-acquisition falls because you stop spending on already-converted customers.
**Sales and service context.** CRM users in [Sales Cloud V2](/en/solutions/sales-cloud/) and [Service Cloud V2](/en/solutions/service-cloud/) see the unified profile without switching systems. Agents reference purchase history, marketing engagement, and loyalty status from one screen. Customers stop hearing "Can you tell me your order number again?"
**Operational independence.** Marketing teams build and activate segments without filing engineering tickets. The time from "we need this audience" to "it's live in SAP Engagement Cloud" is under an hour. New data source onboarding follows a documented, repeatable process — not a custom project every time.
If your current setup does not deliver these outcomes, the gap is either in your data architecture or your implementation approach. Wondering whether a CDP belongs in your roadmap now or later? [Our planning guide](/en/blog/sap-cdp-when-you-need-it/) lays out the decision framework we use with clients. Or [estimate the financial impact](/en/roi-calculator/) before the project starts.
---
### Loyalty
SAP Product: SAP Customer Loyalty Management
URL: https://www.spadoom.com/en/solutions/loyalty/
Description: Loyalty programmes that earn their keep — not just points that collect dust. SAP Customer Loyalty Management for retailers and brands that want repeatable revenue, not vanity metrics.
## What is SAP Customer Loyalty Management?
SAP Customer Loyalty Management is SAP's cloud-native SaaS solution for designing and running loyalty programmes — points, tiers, cashback, and multi-brand coalition models — with real-time basket analysis during checkout. It runs on [SAP Business Technology Platform](https://www.sap.com/products/technology-platform.html) and integrates natively with SAP Commerce Cloud and SAP Engagement Cloud. See the [official product page](https://www.sap.com/products/crm/customer-loyalty-management.html) and the [SAP Help Portal documentation](https://help.sap.com/docs/Customer_Loyalty_Management).
Spadoom pairs programme strategy with hands-on implementation, as an SAP partner working across Switzerland, Germany, Austria, and Italy. This page walks through the programme models, the Engagement Cloud and Commerce Cloud integrations, and what a healthy programme looks like after go-live.
Spadoom in numbers · SAP Customer Loyalty Management
2×
Repeat purchase rate vs control cohort
15–25%
Incremental revenue from loyalty members
12–16 weeks
Typical SAP Loyalty go-live with Engagement Cloud integration
4
Spadoom loyalty case studies in market
Conservative ranges based on Spadoom client outcomes. Loyalty results highly dependent on programme design and customer mix.
## What Spadoom delivers
SAP Customer Loyalty Management launched in Q4 2025 as a standalone cloud product. It runs natively on SAP BTP and integrates directly with Commerce Cloud, SAP Engagement Cloud (formerly Emarsys), and CDP. It is SAP's answer to standalone loyalty platforms — built for organisations that already run SAP CX and want loyalty as part of the stack, not another silo.
We were early. Spadoom started working with SAP Loyalty Management during its ramp-up phase, before general availability. As an SAP Gold Partner with offices across Switzerland, Germany, Austria, Italy, and Estonia, we bring local DACH presence and direct access to SAP product teams. No offshore handoffs. No guessing about product roadmaps.
We implement the full programme lifecycle: member onboarding flows, earning and burning rules, tier structures with re-qualification logic, redemption mechanics across channels, basket-level promotions, SAP Engagement Cloud communication triggers, and Commerce Cloud storefront integration. Every project starts with programme strategy — not technology configuration. The worst loyalty programmes are built by developers who never asked the business what behaviour they want to incentivise.
Our team includes loyalty programme strategists alongside SAP consultants. We help you model the programme economics (cost per point, breakage rates, liability forecasting) before writing a single line of configuration. This means your CFO signs off on the business case before your IT team starts the implementation.
Our delivery follows [SAP Activate methodology](/en/how-we-work/) — five phases from discovery through hyper-care — adapted for loyalty projects where business rules matter as much as technical setup.
## ROI you can measure
Loyalty programmes justify their existence with numbers. Here is what well-run SAP Loyalty implementations produce:
- **15–25% higher repeat purchase rates** — members buy more often because they have a reason to come back. Points balances, tier thresholds, and expiring rewards create urgency that generic newsletters cannot match.
- **10–20% lift in average order value** — real-time basket offers during checkout prompt members to add one more item or hit a spending threshold. This is not a post-purchase email. It happens while the customer is still deciding.
- **2–3x higher spend from loyalty members vs non-members** — members spend more per visit and visit more frequently. The gap compounds over time as tier status and reward history deepen the relationship.
- **30–40% lower cost-per-acquisition on returning customers** — retaining an existing member through targeted rewards costs a fraction of acquiring a new customer through paid ads.
These are industry benchmarks from SAP and loyalty programme studies. Your actual results depend on programme design, reward economics, and execution quality. We help you set realistic targets during the discovery phase and measure against them post-go-live.
## Who this is for
SAP Loyalty Management fits organisations with significant repeat-purchase behaviour and a customer base large enough to justify programme investment. Specifically:
**Grocery and pharmacy chains** — High transaction frequency, tight margins, and fierce competition for wallet share. Loyalty here is about basket penetration and visit frequency, not luxury rewards.
**Fashion and apparel retailers** — Seasonal purchase cycles with long gaps between visits. Tier programmes and personalised offers bring customers back between seasons instead of losing them to competitors.
**Electronics and specialty retail** — Higher basket values with lower purchase frequency. Points programmes and cashback incentives encourage trade-ins, accessories, and upgrades.
**B2B distributors and dealer networks** — Purchase volume tracking, certification rewards, and sales performance incentives. Different mechanics than B2C, but the same platform handles both.
**Multi-brand consumer groups** — Companies operating several brands that want coalition earning across the portfolio while keeping programme governance separate per brand.
The common thread: you already run SAP Commerce Cloud or [SAP Engagement Cloud](/en/solutions/marketing-emarsys/), or you plan to. Native integration is the biggest advantage of SAP Loyalty over standalone platforms.
## What makes it different
Most loyalty platforms issue points and send a monthly statement. SAP Loyalty Management makes those points active during the transaction — not just after it.
### Real-time basket analysis
This is the core differentiator. During checkout, the platform reads the current basket contents, the customer's purchase history, their tier status, and active promotions. It then surfaces a targeted offer in real time. Examples:
- Customer is 50 points from Gold tier — "Add one more item and reach Gold status today"
- Basket contains a coffee machine — "Add 500g of our premium beans and earn 3x points"
- Member has not purchased in 60 days — "Welcome back — here's 200 bonus points on today's order"
This happens during the live shopping session. The customer sees the offer before they pay. It affects the current transaction, not the next one.
### Contextual rewards at checkout
The basket analysis engine connects to SAP Commerce Cloud's promotion framework. Rewards are not generic coupons. They are calculated based on who the customer is, what they are buying, and what behaviour you want to encourage. You configure the rules. The platform executes them in milliseconds.
No standalone loyalty platform can do this without custom middleware between the loyalty engine and the commerce platform. With SAP, it is one system. The latency between "customer adds item to basket" and "loyalty offer appears" is measured in milliseconds, not API round-trips.
## Programme design
SAP Loyalty Management supports five programme models. Most implementations combine two or more.
**Points programmes** — Earn points on every purchase. Redeem for discounts, products, or experiences. The most common model and the fastest to implement. Earning rates and redemption thresholds are configurable per product category, customer segment, or channel.
**Tier programmes** — Bronze, Silver, Gold (or whatever names fit your brand). Tier qualification is based on spend, visit frequency, or a combination. Each tier unlocks different earning rates, exclusive offers, and member benefits. Tier re-qualification rules prevent status inflation.
**Cashback schemes** — A percentage of spend returned as store credit. Simple for the customer to understand, straightforward to model financially. Works well in grocery and electronics where margins support it.
**Coalition programmes** — Multiple brands share a single loyalty currency. A customer earns at Brand A and redeems at Brand B. Financial settlement between brands happens automatically through S/4HANA integration. This model requires careful programme governance — SAP Loyalty Management handles it with dedicated workspaces per brand.
**Hybrid models** — The most common real-world setup. Points accumulation plus tier status. Or cashback plus exclusive member pricing. The rule engine supports layered mechanics without custom development.
We design the programme model during the discovery phase. The technology supports all of them. The real question is which combination drives the behaviour you want from your customers — and which one your finance team can model with confidence. A programme that looks great in marketing but destroys margin is worse than no programme at all.
## Integration with SAP Engagement Cloud
A loyalty programme that does not communicate with its members is a database. Connecting SAP Loyalty Management to [SAP Engagement Cloud](/en/solutions/marketing-emarsys/) turns member data into marketing actions.
### Trigger-based loyalty communications
Once connected, SAP Engagement Cloud can fire campaigns based on loyalty events:
- **Welcome to programme** — onboarding flow with programme benefits and first-purchase bonus
- **Tier upgrade** — congratulations, here is what your new status unlocks
- **Points expiry warning** — "You have 2,000 points expiring in 14 days. Here's how to use them"
- **Milestone reached** — birthday rewards, anniversary bonuses, spend milestones
- **Win-back for lapsed members** — personalised re-engagement based on past purchase patterns
These triggers fire automatically. Your marketing team sets up the automation once. The loyalty platform feeds the events.
### Loyalty data in segmentation
SAP Engagement Cloud receives tier status, points balance, last redemption date, and programme tenure as contact attributes. Your marketing team can use them in any segmentation:
- Send different content to Gold members versus Bronze members
- Exclude members close to tier downgrade from generic promotions (send them a targeted earn offer instead)
- Create lookalike audiences of your highest-value loyalty members for acquisition campaigns
This is not a one-way sync. SAP Engagement Cloud engagement data (email opens, click patterns) flows back to inform loyalty programme optimisation. Members who ignore email but respond to app notifications get different treatment.
For the full integration architecture, see our guide on [how SAP Loyalty, Engagement Cloud, and CDP work together](/en/blog/beyond-points-sap-loyalty-emarsys-cdp/). For what SAP Engagement Cloud can do on its own, read [how SAP Engagement Cloud drives customer loyalty through personalised engagement](/en/blog/sap-emarsys-your-secret-to-building-lasting-customer-relationships/).
## Integration with Commerce Cloud and CDP
SAP Loyalty Management connects to two other SAP CX products that make the programme operational at scale.
### SAP Commerce Cloud — storefront redemption
When Loyalty Management is connected to [SAP Commerce Cloud](/en/solutions/sap-commerce-cloud/), your online store becomes a full loyalty touchpoint:
- Members see their points balance and tier status on their account page
- Reward redemption happens at checkout — apply points as a payment method, select a reward, or activate a personalised offer
- Real-time basket analysis runs during the shopping session, not after it
- Promotions configured in Loyalty Management appear in the storefront without separate development
This integration also covers POS systems for physical retail. Members earn and redeem across online and in-store channels with a single loyalty profile.
### SAP Customer Data Platform — unified loyalty profiles
[SAP CDP](/en/solutions/customer-data-platform/) resolves a single customer identity across all touchpoints — web, mobile, in-store, call centre. When connected to Loyalty Management:
- Anonymous web behaviour links to the known loyalty profile once the member identifies themselves
- Purchase data from all channels feeds into one loyalty record
- Segmentation in CDP includes loyalty attributes (tier, points, programme tenure)
- Personalisation engines use loyalty data to adjust web experiences in real time
The result: a member who browses running shoes on your website at lunch and visits your store after work sees their loyalty status and a relevant offer in both places. No data lag, no duplicate profiles. The same customer is recognised whether they log in on desktop, tap their loyalty card in-store, or open the mobile app.
## Industry use cases
### Grocery and pharmacy
High frequency, low margin. Every basket matters. SAP Loyalty Management handles the volume — thousands of transactions per hour — with real-time basket offers that push basket size upward. A customer buying pasta and canned tomatoes gets a bonus-point offer on olive oil. The offer is calculated on the fly based on their purchase history and current promotions. Pharmacy chains use it for health programme incentives: purchase tracking for supplements, prescription reminders tied to member profiles, and personalised product recommendations based on purchase history. The multi-brand capability supports pharmacy groups operating different store brands under one programme.
### Fashion and apparel
Seasonal buying patterns mean long gaps between purchases. Tier programmes keep members engaged between seasons. A Gold member receives early access to new collections. A Silver member gets a "Double Points Week" to push them toward the next tier. The SAP Engagement Cloud integration handles the communication. The basket analysis engine suggests accessories during checkout.
### Electronics and specialty retail
Larger basket values, lower frequency. Points programmes incentivise trade-ins and upgrades. A customer who bought a laptop 18 months ago receives a targeted offer for peripherals or an extended warranty. The loyalty programme tracks product lifecycle and triggers relevant offers at the right time — through SAP Engagement Cloud email, app push notifications, or in-store at the next visit. Cashback schemes work well here because the basket value supports the return. Members who feel they are getting something back spend more confidently on higher-priced items.
### B2B dealer networks
Distributors and manufacturers use SAP Loyalty Management to incentivise their dealer and partner networks. Instead of points on consumer purchases, the programme tracks purchase volumes, certifications completed, training participation, and sales targets met. A dealer who hits quarterly volume targets earns rebates, marketing co-op funds, or priority access to new product lines. The S/4HANA integration handles financial settlement automatically — no spreadsheets, no quarterly reconciliation delays. Spadoom has built B2B loyalty structures for industrial and technology clients across the DACH region.
## What good looks like
A well-implemented SAP Loyalty programme shows results within the first quarter after launch:
- Member sign-up rates that exceed your initial projection because the value proposition is clear at the point of sale
- Repeat purchase frequency rising within 90 days as members engage with points and tier mechanics
- Average order values climbing as real-time basket offers influence checkout behaviour
- Marketing campaign performance improving because SAP Engagement Cloud segments by loyalty status instead of guessing
- Redemption rates above 20% — meaning members actually use their rewards, which drives visits
- Finance teams satisfied because the programme economics are modelled accurately and settlement with S/4HANA is automated
Six months after go-live, your member-to-non-member spend ratio tells the story. A healthy programme shows members spending 2–3x more than non-members. If that gap is not growing, something is wrong with the programme design, the communication cadence, or the reward economics. We track these metrics during hyper-care and adjust programme rules based on what the data shows — not assumptions from the initial business case.
The goal is a loyalty programme that pays for itself within the first year through measurable lift in repeat purchases, basket size, and customer retention. We help you get there.
[SAP Integration Suite: supported integration capabilities](https://www.sap.com/products/technology-platform/integration-suite.html).
---
### Configure, Price, Quote (CPQ)
SAP Product: SAP CPQ
URL: https://www.spadoom.com/en/solutions/configure-price-quote-cpq/
Description: Complex products, accurate quotes, no spreadsheets. SAP CPQ for manufacturers and equipment companies who've outgrown manual quoting — or never want to start.
## What is SAP CPQ?
SAP CPQ is SAP's [configure, price, quote](https://www.sap.com/resources/what-is-cpq) platform for complex B2B products: sales reps configure valid product combinations step by step, pricing rules and discount approvals fire automatically, and branded quotes generate in minutes instead of hours. The [official product page](https://www.sap.com/products/financial-management/cpq.html) and the [SAP CPQ documentation](https://help.sap.com/docs/SAP_CPQ) cover the full capability set; the platform connects natively to SAP Sales Cloud V2 and SAP ERP.
Spadoom implements SAP CPQ as an SAP Gold Partner for manufacturers and technology companies across Switzerland, Germany, Austria, and Italy. The rest of this page covers what we deliver, the ROI we track, and how we model product rules before the first quote goes out.
## What Spadoom delivers
We implement SAP CPQ for manufacturers and technology companies across DACH and Southern Europe. Our clients sell complex products — industrial equipment, medical devices, configurable machinery, multi-component systems. Their product catalogues have hundreds or thousands of valid combinations. Pricing depends on volume, customer tier, region, and contract terms.
As an SAP Gold Partner, we bring certified consultants who have configured CPQ for real product lines — not demo environments. Every project follows [SAP Activate methodology](/en/how-we-work/): five phases from discovery through hyper-care. We adapt the framework for CPQ-specific challenges like rule modelling, pricing migration, and quote template design.
The typical client has sales reps spending 30–40% of their time on quoting. They pull data from multiple systems. They check configurations manually. They chase approvals via email. CPQ brings that down to under 10 minutes per quote and removes human error entirely.
## ROI you can measure
CPQ projects produce hard numbers. We track three metrics across every deployment.
**65% faster quote generation.** What took 2–4 hours drops to under 10 minutes. Guided configuration eliminates the back-and-forth between sales and engineering. Pricing rules fire automatically. The quote generates itself.
**95% quote accuracy.** Manual quoting averages 80% accuracy in complex product environments. Wrong configurations, outdated pricing, missed discounts — all common. CPQ enforces valid combinations and current prices at the point of entry. The 15-point accuracy gain means fewer order corrections, fewer credit notes, and fewer angry calls from production.
**30% shorter sales cycles.** Faster quotes mean faster customer decisions. When a buyer asks "Can you do this configuration at this price?" the rep answers in the meeting, not three days later. Approval workflows run in parallel instead of sequential email chains. Deals close before competitors finish their spreadsheets.
Want to model these numbers for your team? Run the scenarios in our [ROI calculator](/en/roi-calculator/).
## The product configuration challenge
Getting product rules right is the hardest part of any CPQ implementation. Rules that are too rigid frustrate sales reps. Rules that are too loose create orders for impossible configurations. Both cost money.
We run structured workshops before a single rule is coded. Our process:
1. **Catalogue mapping.** We document every product family, option set, and dependency. We identify which combinations are valid, which require engineering review, and which are impossible.
2. **Rule modelling.** We translate business logic into CPQ configuration rules. This includes constraint rules (what can combine with what), recommendation rules (what should combine), and exclusion rules (what must never combine).
3. **Edge case testing.** We pull 50–100 historical quotes — including the messy ones. We run them through the new configuration engine. If the system produces a different result than what was sold, we investigate. Sometimes the old quote was wrong. Sometimes our rules need adjustment.
4. **Sales team validation.** Reps test the configuration flow before go-live. They try to break it. They flag scenarios we missed. This front-loaded investment pays back immediately — you don't spend the first six months of production fixing rules.
Multi-level BOMs get special attention. A parent product with three levels of dependent sub-assemblies requires careful dependency mapping. We model these as hierarchical configuration trees where each level inherits constraints from the level above. The result: a rep selects a base unit, and the system narrows available options at every subsequent level automatically.
## Dynamic pricing and discount management
Pricing in CPQ goes far beyond a price list. Most B2B companies we work with have at least four pricing dimensions running simultaneously.
**Volume tiers.** Buy 10, pay list price. Buy 100, get 12% off. Buy 1,000, trigger a custom pricing request. CPQ applies the right tier automatically based on line quantities and total order value.
**Customer-specific pricing.** Key accounts have negotiated rates. Distributor tiers carry different margins. Regional pricing reflects local market conditions. CPQ pulls customer-specific price books and applies them without the rep needing to look anything up.
**Approval workflows with teeth.** Discounts above 15%? Routed to the regional sales director. Above 25%? VP of Sales. Above 35%? CFO sign-off required. These thresholds are configurable per product line, per region, per customer segment. The system enforces them — no exceptions, no workarounds.
**Margin protection.** CPQ calculates margin in real time as the rep builds the quote. Floor prices prevent reps from going below cost. Warning thresholds flag deals that are technically valid but commercially questionable. Finance sees the margin impact before the quote leaves the building.
Currency conversion, tax calculation, and Incoterms handling run automatically based on the ship-to location. For companies selling across Switzerland, the EU, and beyond, this eliminates an entire category of quoting errors.
## Quote-to-order automation
The quote itself is the output that customers see. It needs to look right and contain the right information.
**Branded PDF generation.** CPQ produces professional quote documents from templates. Product images, line item details, terms and conditions, pricing breakdowns — all assembled automatically. No more copying data into Word or PowerPoint. Templates are configurable per product line, per region, per language.
**E-signature integration.** DocuSign, Adobe Sign, and other providers connect directly to the CPQ workflow. The customer receives the quote, reviews it, signs digitally, and the acceptance flows back into the system. No printed paper. No scanned PDFs. No "I'll send it Monday."
**ERP order creation.** This is where CPQ pays for itself. When a quote is accepted, CPQ creates the sales order in SAP ERP or S/4HANA automatically. Bill of materials, pricing, delivery dates, payment terms — all transferred without manual re-entry. The order is correct because it was correct in CPQ. No one types it again.
For companies running [SAP Commerce](/en/solutions/sap-commerce-cloud/) alongside CPQ, the same configuration engine can power self-service quoting on the B2B storefront. Customers configure products, see pricing, and request quotes — all through the same rules engine that sales reps use internally.
## Integration with SAP Sales Cloud V2
CPQ works best when it's embedded in the sales workflow, not bolted on as a separate tool. In [SAP Sales Cloud V2](/en/solutions/sales-cloud/), the integration is native.
**Embedded launch.** Reps open CPQ directly from the opportunity in Sales Cloud V2. No separate login. No context switching. The customer data, opportunity details, and account pricing carry over automatically.
**Bidirectional sync.** Quotes created in CPQ appear as quote records in Sales Cloud V2. Status changes flow both ways — when a quote is approved, accepted, or rejected, the opportunity reflects it immediately. Activity history stays unified.
**Pipeline accuracy.** Because quotes carry real configuration and pricing data, pipeline values become trustworthy. Forecast calls stop being guessing games. Managers see what was actually quoted, not what a rep estimated.
**Single source of truth.** No more version conflicts between the CRM and the quoting tool. The quote in CPQ is the quote in Sales Cloud V2 is the order in ERP. One data lineage from opportunity to invoice.
We configure this end-to-end integration as standard on every project. The quote-to-order flow should require zero manual steps from the rep.
## Industry use cases
SAP CPQ serves any business that sells configurable products. Four industries make up the majority of our project portfolio.
**Manufacturing.** Industrial equipment with modular assemblies, optional accessories, and region-specific compliance requirements. Configuration rules prevent invalid combinations. Pricing reflects volume commitments and framework agreements. Quote-to-order automation eliminates the 2–3 day gap between "deal won" and "order in ERP."
**High-tech.** Software and hardware bundles with subscription pricing, perpetual licenses, maintenance add-ons, and upgrade paths. CPQ handles mixed billing models (one-time + recurring) in a single quote. Renewal quoting pulls current contract terms automatically.
**Medical devices.** Regulated products with strict configuration constraints. Certain components require specific certifications in certain markets. CPQ enforces regulatory rules alongside commercial rules. Audit trails document every configuration decision for compliance reviews.
**Automotive (aftermarket and fleet).** Vehicle configuration, parts kitting, and fleet pricing with dealer-tier discounts. Multi-currency, multi-country pricing for European distribution networks. CPQ replaces the 47-tab Excel file that no one trusts but everyone uses.
## Pricing and licensing
SAP CPQ is licensed per user per month. Exact pricing depends on volume, contract length, and bundling with other SAP CX products. Most mid-market deployments fall between $50 and $90 per user per month.
For comparison: Salesforce CPQ (now Revenue Cloud) starts at $75 per user per month for the basic tier, with advanced features at $150+. Oracle CPQ Cloud starts at similar price points but adds integration costs for non-Oracle back-end systems.
The real cost difference is in integration. SAP CPQ connects to SAP ERP and S/4HANA through pre-built connectors. Salesforce CPQ and Oracle CPQ require middleware (MuleSoft, Boomi, or custom) to reach SAP back-end data — pricing, inventory, credit checks. That middleware layer adds $30,000–$80,000 in annual platform costs plus ongoing maintenance.
Total cost of ownership over three years favours SAP CPQ for companies already running SAP ERP. The licensing delta is small. The integration savings are significant.
Spadoom provides a detailed cost estimate after the two-week discovery phase. No surprises. No scope creep.
## What good looks like
A successful CPQ deployment produces outcomes you can point to in a board meeting.
- **Quote volume per rep doubles.** Same team, twice the output. No additional headcount.
- **Order errors drop below 2%.** Configuration rules and automated pricing eliminate the manual mistakes that cost 3–5% of revenue in rework and credit notes.
- **Sales cycle compresses by 4–6 weeks.** Faster quotes, parallel approvals, and instant ERP order creation remove dead time from the process.
- **Rep satisfaction improves.** Sales people want to sell, not administer spreadsheets. CPQ gives them back 8–12 hours per week.
- **Finance gets visibility.** Real-time margin data, discount tracking, and approval audit trails replace the quarterly "what happened?" analysis.
These are the numbers we track at 30, 90, and 180 days post-go-live. If they're not moving in the right direction, we adjust. That's what the hyper-care phase in [our methodology](/en/how-we-work/) is for.
[SAP Integration Suite: supported integration capabilities](https://www.sap.com/products/technology-platform/integration-suite.html).
---
### Field Service Management (FSM)
SAP Product: SAP FSM
URL: https://www.spadoom.com/en/solutions/field-service-management/
Description: Technician dispatching that doesn't rely on calls and whiteboards. SAP FSM for manufacturers and utilities — we're an SAP-authorised FSM partner and we've been running these projects since the platform launched.
## What is SAP Field Service Management?
SAP Field Service Management (FSM) is SAP's platform for planning, dispatching, and executing field service work — AI-assisted scheduling, an offline-capable mobile app for technicians, and spare-parts visibility in one system. The [official product page](https://www.sap.com/products/scm/field-service-management.html) outlines the [full feature set](https://www.sap.com/products/scm/field-service-management/features.html), and the [SAP FSM documentation](https://help.sap.com/docs/SAP_FIELD_SERVICE_MANAGEMENT) covers configuration and integration with SAP Service Cloud V2 and SAP ERP.
Spadoom is an SAP-authorised FSM partner delivering rollouts for manufacturers, utilities, and medical device companies in Switzerland, Germany, Austria, and Italy. The sections below explain our delivery approach, the three ROI metrics we track on every project, and where the platform fits your operation.
## What Spadoom delivers
Spadoom is an SAP-authorised Field Service Management partner. We hold the certification, but more importantly, we've run FSM projects since the platform launched. We know where it excels and where it needs configuration work to fit real operations.
Our FSM clients are manufacturers with 50–500 field technicians, utilities managing complex asset hierarchies, and medical device companies operating under strict regulatory requirements. These are organisations where a missed appointment costs money, where SLA penalties are real, and where "we'll fix the scheduling later" is not acceptable.
We deliver across Switzerland, Germany, Austria, and Italy — on-site when needed, remote when it makes sense. No offshore handoffs. Every project follows [SAP Activate methodology](/en/how-we-work/) with five phases from discovery through hyper-care. The discovery phase is where most FSM projects are won or lost: we map your current dispatching logic, technician workflows, and integration requirements before writing a single line of configuration.
If your field service team still runs on spreadsheets, phone calls, and tribal knowledge, we've seen your situation before. The fix is not just software — it's structured implementation with people who understand field operations.
Getting the right partner matters more in FSM than in most SAP projects. The platform touches dispatchers, technicians, warehouse staff, and customers — every group has different needs. A partner who's only configured CRM will miss the operational realities. We don't.
## ROI you can measure
FSM projects pay for themselves when three numbers move:
- **25% improvement in first-time fix rate** — the right technician with the right parts arrives the first time. Repeat visits are the most expensive line item in field service. Intelligent scheduling and van stock visibility eliminate the most common causes: wrong skills, missing parts, incomplete job context.
- **30% reduction in travel time** — route-optimised scheduling clusters jobs geographically and accounts for traffic patterns. Technicians spend more hours on-site and fewer behind the wheel. For a 100-technician workforce, that's thousands of recovered productive hours per year.
- **40% fewer emergency dispatches** — preventive maintenance catches failures before they happen. Calendar-based, usage-based, and IoT-triggered maintenance plans replace reactive break-fix cycles. Emergency calls drop because equipment gets serviced before it breaks.
These are not aspirational targets. They come from SAP's published FSM value benchmarks and align with what we've measured on our own projects.
The compounding effect matters. Higher first-time fix rates mean fewer return visits. Fewer return visits mean more capacity for new jobs. More capacity means revenue growth without hiring. The maths works in your favour once the first metric moves.
[Calculate your projected ROI](/en/roi-calculator/) based on your team size and service volume.
## Intelligent scheduling and dispatch
Manual dispatching works until it doesn't. A dispatcher who knows every technician by name can handle 20 people. At 50, the complexity outpaces human memory. At 100+, you're guessing. And when that one dispatcher goes on holiday, the whole operation slows down.
SAP FSM's scheduling engine replaces guesswork with rules. Every job assignment considers:
- **Technician skills and certifications** — a gas boiler repair goes to someone certified for gas, not the nearest available body
- **Geographic proximity and travel time** — real-time traffic data, not straight-line distance
- **Parts availability** — the system checks van stock before assigning. No point sending someone who doesn't have the part
- **SLA urgency** — contractual response windows get priority. A 4-hour SLA job bumps a next-day routine inspection
- **Customer preferences** — some customers request specific technicians. The system respects that
The engine learns over time. It tracks which technicians complete which job types fastest, which routes are consistently slow, and which parts are consumed most often. After six months of data, scheduling suggestions improve measurably.
Dispatchers don't lose control. They review suggestions, override when their experience says otherwise, and approve the final schedule. The system handles the maths; humans handle the exceptions.
We configure the scheduling rules during implementation. This is not a generic setup — every client has different skill taxonomies, territory boundaries, and SLA structures. A utility company's scheduling rules look nothing like a medical device company's. We model your specific constraints, test them with real historical data, and tune before go-live.
## The mobile technician experience
The FSM mobile app is where the platform lives or dies. If technicians don't use it, you have an expensive scheduling tool that feeds nobody.
SAP FSM's app runs on iOS and Android. It works offline — fully. Technicians in basements, rural sites, or underground utility corridors complete their work without connectivity. Everything syncs when signal returns.
What the app provides in the field:
- **Daily schedule** with job details, customer history, and equipment records
- **Step-by-step checklists** — configurable per job type, enforced by the system
- **Parts consumption** — scan barcodes, log parts used, trigger replenishment
- **Time tracking** — start and stop per activity, feeding directly into billing
- **Digital signatures** — customer sign-off on the device, attached to the work order
- **Photo and video capture** — document conditions before and after, attached to the service report
- **Knowledge base access** — manuals, troubleshooting guides, and past repair notes for the same equipment
The app is not a stripped-down version of the desktop. It's purpose-built for field conditions: large touch targets, high-contrast display for outdoor use, and minimal typing. Technicians who resisted the old system tend to adopt this one because it actually saves them time instead of adding paperwork.
Adoption is the make-or-break metric for any mobile rollout. We run hands-on training with technicians during the pilot phase — not classroom sessions, but ride-alongs where we configure the app to match their actual daily workflow. If the app adds friction, we fix it before scaling to the full team.
## Preventive maintenance and IoT
Reactive maintenance is the most expensive way to run field service. An emergency dispatch costs 3–5x more than a planned visit. Equipment that fails unexpectedly damages customer relationships and triggers SLA penalties.
SAP FSM supports three levels of preventive maintenance:
**Calendar-based** — the simplest model. Service every 90 days, inspect every 6 months. The system generates work orders automatically based on the schedule. No dispatcher intervention required.
**Usage-based** — triggered by runtime counters, cycle counts, or operational hours. A printing press that hits 500,000 impressions gets a maintenance visit regardless of calendar date. This requires meter readings — either manual entry or automated from equipment.
**IoT sensor-triggered** — the most advanced model. Connected equipment sends real-time data: temperature, vibration, pressure, humidity. You define threshold rules in FSM. When a compressor's vibration exceeds the normal range, FSM creates a work order, assigns a qualified technician, and dispatches them — before the machine fails.
IoT-triggered maintenance converts unplanned downtime into planned visits. A utility company monitoring transformer temperatures can schedule a replacement during off-peak hours instead of responding to an outage at 2 AM. A manufacturer watching CNC machine vibration patterns replaces bearings on a Saturday instead of losing a production shift on Tuesday.
The IoT integration requires connected equipment and a data pipeline (SAP IoT, Azure IoT Hub, or similar). Spadoom handles the FSM side: threshold configuration, work order templates, and technician assignment rules. We partner with IoT specialists for the sensor and connectivity layer.
Not every client starts with IoT. Most begin with calendar-based maintenance and graduate to usage-based as they collect data. IoT comes third, once the infrastructure and business case are in place. We build the FSM configuration to support all three levels from day one, so you can progress without re-implementation.
## Integration with SAP Service Cloud V2 and ERP
FSM on its own is a scheduling and mobile tool. The real value appears when it connects to the rest of your SAP landscape.
**SAP Service Cloud V2** — when a service ticket in [Service Cloud](/en/solutions/service-cloud/) requires on-site intervention, it escalates to FSM with full context. The technician sees the customer's complaint, previous interactions, equipment details, and warranty status on their mobile app. When the work is done, completion data flows back to Service Cloud. The service agent sees the resolution without calling the technician. SLA clocks stop automatically.
**SAP ERP / S/4HANA** — parts consumed on-site post directly to materials management. Time recorded by the technician feeds into billing. Equipment master data in ERP stays current with maintenance history from FSM. No manual reconciliation, no duplicate entry, no month-end surprises in inventory counts.
**Customer portals** — end customers book service appointments, track technician location in real time, and access their full service history. This reduces inbound calls to your service desk by 30–40% based on typical FSM deployments.
**[SAP Sales Cloud V2](/en/solutions/sales-cloud/)** — when a technician identifies an upsell opportunity during a service visit (aging equipment, expansion needs), they log it in the mobile app. It surfaces as a lead in Sales Cloud for the account manager to follow up. Field technicians are your most credible salespeople — they're already on-site and trusted.
We implement these integrations as standard. A standalone FSM deployment is a half-measure. The full value requires the connected workflow from ticket to dispatch to completion to billing.
Getting the connected workflow right requires a partner who's done it before. The integration between FSM and S/4HANA alone involves mapping equipment master data, material numbers, cost centres, and billing documents. Get it wrong and you spend months reconciling data. Get it right and field service becomes a profit centre with full financial visibility.
## Industry use cases
SAP FSM fits any organisation with field technicians, SLA commitments, and equipment to maintain. Here's where we've deployed it:
**Manufacturing** — warranty service, break-fix repairs, and preventive maintenance for industrial equipment. Technicians need access to equipment history, spare parts catalogues, and installation drawings. We configure FSM to pull asset data from S/4HANA and push completed work back to plant maintenance. Common scope: 50–300 technicians, multi-country operations, integration with SAP PM and MM modules.
**Utilities** — infrastructure inspection, meter installation, and emergency repair. Asset hierarchies are deep — a substation contains transformers, switches, and meters, each with independent maintenance schedules. FSM handles multi-level asset structures and compliance-driven inspection workflows. We configure geo-fencing for restricted sites and safety checklists that must be completed before work begins.
**Medical devices** — regulated servicing with audit trail requirements. Every service action, part replacement, and calibration must be documented and traceable. FSM's checklist system enforces step-by-step procedures. Digital signatures and timestamped photos provide the evidence trail. We configure compliance-specific workflows and integrate with quality management systems. For medical device companies, a missed compliance step is not just a process failure — it's a regulatory risk. FSM enforces the process so technicians can't skip steps.
**Telecommunications** — installation, activation, and repair across distributed infrastructure. High job volumes, tight SLA windows, and customer self-service booking. FSM handles the scheduling complexity — route optimisation matters when a technician visits 8–12 sites per day. We configure customer portal integration for appointment booking and real-time technician tracking.
The common thread across all four industries: technicians in the field, equipment that needs maintaining, and service data that must flow back to ERP. If that describes your operation, FSM fits.
## Pricing and licensing
SAP FSM pricing depends on user count and contract terms. Typical ranges:
| Platform | Per user / month | Notes |
|---|---|---|
| **SAP FSM** | $40–$70 | Native SAP integration included |
| **ServiceMax** | $50–$80 | Requires middleware for SAP ERP |
| **IFS** | $70–$100+ | Broader ERP scope, higher base cost |
The per-user cost tells only part of the story. For organisations running SAP ERP or S/4HANA, FSM eliminates the middleware layer that ServiceMax and IFS require. That's one less vendor, one less integration to maintain, and one less system to troubleshoot when data doesn't sync.
ServiceMax offers strong asset management features and a mature Salesforce integration — a good fit if your CRM is Salesforce. IFS targets large-scale operations with complex resource planning. SAP FSM wins on total cost of ownership for SAP shops and on the depth of the mobile technician experience.
Spadoom provides fixed-price implementation quotes. We scope the project, define deliverables, and agree on cost before work begins. No open-ended time-and-materials surprises. Contact us for a tailored estimate based on your technician count and integration requirements.
## What good looks like
A well-implemented SAP FSM means:
- First-time fix rates above 85% because technicians arrive with the right skills, parts, and context
- Dispatchers managing 100+ technicians without heroic effort because the system handles assignment logic
- Preventive maintenance plans that run on autopilot — calendar, usage, or IoT-triggered — reducing emergency calls by 40%
- Service data flowing to ERP without manual entry, so billing is accurate and inventory counts match reality
- Technicians who actually use the mobile app because it saves them time instead of adding admin work
- Customers who book appointments and track progress themselves, reducing inbound service desk calls
Six months after go-live, the numbers tell the story. We track them, and we hold ourselves accountable for them. That's the standard we set for every FSM project — measurable outcomes, not just a successful go-live.
---
### Supply Chain Collaboration
SAP Product: SAP Business Network for Supply Chain Collaboration
URL: https://www.spadoom.com/en/solutions/supply-chain-collaboration/
Description: Collaborate with suppliers, contract manufacturers, and logistics partners on a single network. Replace email and spreadsheets with structured purchase order, forecast, and inventory data flowing both ways.
## What is SAP Business Network for Supply Chain Collaboration?
[SAP Business Network for Supply Chain Collaboration](https://www.sap.com/products/business-network/supply-chain-collaboration.html) is the multi-tier supply chain capability of [SAP Business Network](https://www.sap.com/products/business-network.html) — the platform that absorbed the Ariba Network. Buyers exchange structured purchase orders, forecasts, inventory data, quality records, and shipping notifications with suppliers, contract manufacturers, and logistics partners, with pre-built integration into SAP S/4HANA and ECC. SAP's [network overview](https://www.sap.com/products/business-network/what-is-sap-business-network.html) explains the platform in depth.
Spadoom delivers supplier collaboration projects for European manufacturers and retailers across Switzerland, Germany, Austria, and Italy. The rest of this page covers where collaboration breaks down over email, how the network fixes it, and how we implement it.
## What Spadoom delivers
We connect buyers, suppliers, contract manufacturers, and 3PLs onto SAP Business Network for Supply Chain Collaboration. The starting point is almost always purchase order collaboration — getting confirmations, changes, and rejections off email and into structured data your planners can actually trust. From there we layer on rolling forecast sharing so tier-1 suppliers see your demand signal weeks before a firm order lands, supplier-managed inventory for high-volume parts where the supplier replenishes under agreed thresholds, and quality records — inspection results, non-conformance reports, corrective actions — written once and visible to both sides.
Logistics partners join the same network. Advance shipping notifications, packaging data, and delivery confirmations land in your system without re-keying or PDF parsing. ERP integration is the part most clients underestimate: SAP ships pre-built integration content for S/4HANA and ECC covering POs, goods receipts, invoices, ASNs, and supplier master data. We configure and test that integration end to end. No custom middleware. No bespoke iDocs that break at the next upgrade.
We are based in the DACH region and deliver hands-on. No offshore handoff after kickoff. Our consultants run the discovery workshops, design the integration, sit with your planners during user testing, and stay through the first weeks of live traffic. The goal is a network you operate, not a network we operate for you.
## Why supplier collaboration breaks down
If you run procurement or supply chain operations today, this list will sound familiar.
Purchase orders go out as PDFs. Suppliers reply by email — sometimes confirming, sometimes counter-proposing, sometimes silently changing the dock date and hoping nobody notices. Your planner copy-pastes confirmations into the ERP. When a delivery is late, you find out from the goods-in dock, not from the supplier. Finger-pointing follows.
Forecasts, when they exist, are sent as Excel attachments once a quarter. Suppliers either ignore them or treat them as firm orders — both wrong answers. Capacity at your tier-1 supplier is opaque, and capacity at your tier-2 supplier might as well be on another planet.
Quality is its own domain of pain. A non-conformance hits the receiving inspection. Someone fills in a form, scans it, emails it to the supplier's quality contact, and waits. The corrective action arrives weeks later as another PDF. The audit trail lives across three inboxes and a shared drive.
Master data is the quiet disaster. Supplier identities are duplicated across business units. The same supplier shows up under three different vendor IDs — one for the German plant, one for the Italian one, one inherited from an acquisition. Spend reports do not roll up cleanly. Negotiating leverage gets diluted.
None of these failures are exotic. They are the default state of supply chain collaboration when the only integration layer is email.
## How SAP Business Network changes that
The shift is structural, not cosmetic. Once buyer and supplier are on the same network, every transaction has a single canonical state, visible to both sides, with an audit trail.
Purchase orders move into the network. The supplier confirms, partially confirms, proposes a change, or rejects — and your planner sees the response inside the ERP, in a status field, not as a PDF in someone's inbox. Confirmation rates and on-time delivery become measurable in real time, not reconstructed from a spreadsheet at month-end.
Forecasts flow on a rolling cadence. Suppliers see firm orders, planned orders, and forecast horizon in one view. They can flag capacity issues before a firm order lands. For high-volume parts, supplier-managed inventory replaces the reorder point: the supplier sees your stock and replenishes under the rules you agreed. Safety stock comes down because the lag between "we need more" and "more is on the way" collapses.
Quality records sit on the same shared object. Non-conformance, root cause, corrective action — one record, both sides edit, the timeline is the timeline. Audit-ready by default.
Logistics joins the same network. The 3PL posts the ASN, the goods-in team scans against it, the supplier sees the goods receipt. Three parties, one set of facts.
Multi-tier visibility is the layer most procurement teams have never had. With suppliers and their suppliers on the same network, you can see capacity exposure two levels deep — useful well before a chip shortage, a port closure, or a flood at a tier-2 supplier turns into a tier-1 production stop.
The data model matters. Every transaction on the network is a typed object with a clear state machine: ordered, confirmed, shipped, received, invoiced, paid. Both sides see the same state. There is no "what does the supplier think the status is" conversation, because the network is the answer.
## A Fleurop note
Spadoom defined the SAP Business Network roadmap for Fleurop covering supplier collaboration and procurement. The work spanned both sides of the network — moving purchase order traffic onto the network and starting the consolidation of a fragmented supplier base. The detail is in the [Fleurop case study](/en/success-stories/fleurop-digital-flower-delivery/).
## Implementation in practice
We deliver via [SAP Activate methodology](/en/how-we-work/) — discovery, prepare, explore, realize, deploy, run. A focused tier-1 supplier collaboration go-live typically runs 8–14 weeks. Multi-tier scope, non-SAP ERP integration, or a large supplier population pushes that out.
The discovery phase scopes which transactions belong on the network on day one (POs and ASNs are usually the right starting point) and which come later (quality, supplier-managed inventory, multi-tier). Prepare locks the integration architecture with S/4HANA or ECC. Explore is where supplier onboarding becomes the critical path — and where most projects underestimate the work.
Supplier onboarding is its own workstream. Identifying the right contacts at each supplier, communicating the change, walking them through standard-account registration, training their planners on confirmations and ASNs, and tracking adoption all take longer than the technical configuration. We staff a dedicated onboarding lead from day one and treat supplier readiness as a hard go-live criterion. A network with 30% of your tier-1 spend live is not a useful network.
Realize covers configuration, integration build, and end-to-end testing. Deploy is the cutover, with a hyper-care window where we shadow the first weeks of live traffic. Run is steady-state — we hand over to your team with documented playbooks for the operations they will run forever.
Two practical notes on scope. First, do not try to onboard every supplier at once. Pick the tier-1 cohort that covers the bulk of inbound volume and get them live cleanly. The long tail follows in waves. Second, agree the cutover criteria up front. "Goes live when 80% of in-scope spend is transacting on the network for two consecutive weeks" is the kind of criterion that prevents a soft launch from drifting forever.
## What good looks like
Six months in, what changed shows up in steady-state behaviour, not in a launch press release.
- Every PO has a confirmation status that came from the supplier, not a planner guess. Email-driven status checks are gone.
- Quality records live on the network. Non-conformance, root cause, and corrective action share one timeline both sides can read.
- Tier-1 supplier capacity is visible four-plus weeks ahead. Surprises become rare.
- Supplier-managed inventory is running on your top-volume SKUs. Safety stock is lower, stockouts are lower, and the planner is no longer the bottleneck.
- Supplier identities are consolidated. One vendor, one master record, one spend report.
- ASN coverage from your 3PLs is high enough that goods-in works against expected receipts, not against truck-by-truck surprise.
That is the steady state. It is not glamorous. It is operational and durable.
If your priority is procure-to-pay automation rather than multi-tier supplier collaboration, see [Procurement (Ariba)](/en/solutions/business-network-procurement/).
---
### Procurement (Ariba)
SAP Product: SAP Business Network for Procurement (formerly SAP Ariba)
URL: https://www.spadoom.com/en/solutions/business-network-procurement/
Description: Procure-to-pay on the SAP Business Network — formerly the Ariba Network. Connect buyers to a global supplier base, automate invoice processing, and consolidate supplier master data with SAP-native procurement.
## What is SAP Business Network for Procurement?
[SAP Business Network for Procurement](https://www.sap.com/products/business-network/procurement.html) is SAP's procure-to-pay network — formerly SAP Ariba, built on the [Ariba Network](https://www.sap.com/products/spend-management/ariba-network.html) — connecting buyers with a global base of millions of suppliers for catalog buying, electronic purchase orders, structured e-invoicing, and supplier onboarding. It runs on the wider [SAP Business Network](https://www.sap.com/products/business-network.html) platform and integrates out of the box with SAP S/4HANA and ECC.
Spadoom implements it for European buyers — manufacturers and retailers across Switzerland, Germany, Austria, and Italy — with supplier data cleansing and country e-invoicing mandates scoped into the project from day one. Below: what we deliver, where procurement projects fail, and what the Ariba rename actually changed.
## What Spadoom delivers
We implement SAP Business Network for Procurement — what most teams still call SAP Ariba — for European buyers who want their procure-to-pay on a network rather than glued together with email and PDF invoices.
The work usually starts with the catalog. Pre-negotiated supplier catalogs surface to requisitioners through guided buying. The default path becomes the compliant path. Off-contract spend drops, and procurement no longer plays whack-a-mole with rogue purchases. Around the catalog we configure approval workflows that match how the company actually buys — by cost centre, by category, by amount — instead of forcing the company to match a default workflow.
E-invoicing is the second pillar. Suppliers submit structured electronic invoices straight to the network. The network checks the invoice against the PO and the goods receipt automatically. Three-way matching, which used to be a person opening three screens and squinting, becomes a status flag. Exceptions go to a human; matches go straight to payment.
Supplier onboarding and master data sit underneath. Onboarding flows capture qualifications, certifications, tax and bank details once. The same supplier record is then maintained centrally, with change-control. Duplicate supplier IDs are not somebody else's problem.
Spend visibility falls out for free once the data is structured. Category, supplier, cost centre, plant — pulled from live PO and invoice data, not from a quarterly retrospective dashboard built in Excel. Country-specific compliance — Italy's SDI, France's Chorus Pro, Germany's ZUGFeRD/XRechnung — is handled inside the network. SAP keeps the compliance profiles current as mandates evolve.
ERP integration is pre-built. SAP ships connectors for S/4HANA Cloud and SAP ECC covering POs, goods receipts, invoices, and supplier master data. We configure and test that integration as a standard part of the project. Non-SAP ERPs are supported via SAP Integration Suite.
## Where procurement projects fail
Procurement projects fail in predictable places.
Invoice processing is the loudest one. A finance team is opening thousands of PDF invoices a month, keying them into the ERP, hunting down POs, chasing approvers, and discovering errors at month-end. The headcount cost is real. The bigger cost is invisible: late payments, missed early-payment discounts, duplicate payments, audit findings. Throwing OCR at the problem helps a little. Moving the invoice itself onto a structured network is the actual fix.
Master data is the second predictable failure. The same supplier exists three times in your vendor master under three different IDs. Spend reports double-count. Negotiating leverage is diluted because nobody can produce a single view of total spend with that supplier. Onboarding has no controls, so anyone who emailed a quote ends up as a vendor record. Cleanup projects come and go without sticking, because the underlying flow keeps creating new duplicates.
Off-contract spend is the third. Pre-negotiated agreements exist, but requisitioners do not see them, do not understand them, or find it faster to raise a free-text PO. Compliance metrics live in a slide deck nobody enforces.
Supplier onboarding becomes a scramble at the worst moment — when a new country mandate lands, when a major supplier needs replacing, when an audit asks for proof of due diligence on the 200 suppliers you onboarded last year. The information was never captured systematically.
Country-specific e-invoicing mandates are the fourth. Italy's SDI was the first wave. France, Germany, Spain, Belgium, Poland — all mandated structured e-invoicing on different timelines, with different formats. Teams without a network are doing each one as a side project.
## What changed when Ariba became SAP Business Network
SAP is consolidating its procurement and supply-chain solutions under one umbrella: SAP Business Network. Ariba — Procurement, Sourcing, Contracts — sits inside that brand as SAP Business Network for Procurement. The Ariba name is being de-emphasised in marketing, but it remains the search term most procurement leaders still type into Google, and the term most consultants still use in conversation. Both names point to the same product.
The supplier base is the same. The supplier accounts are the same. The integration content for S/4HANA and ECC is the same. The network APIs are the same. What improves is the unification: SAP Business Network for Procurement and SAP Business Network for Supply Chain Collaboration sit on one platform, share supplier identities, and share core network services. A buyer running both gets one supplier onboarding flow, one supplier directory, one set of network credentials per supplier — instead of two parallel onboardings.
The strategic point is simple. SAP wants procurement, supply-chain collaboration, asset collaboration, and the green network on one platform. The Ariba rebrand is the front-end of that consolidation. The product underneath is the same battle-tested procure-to-pay engine.
## Country-specific e-invoicing mandates
European e-invoicing mandates are a moving target. The network handles them centrally so each country's compliance is configuration, not a side project.
**Italy — SDI (Sistema di Interscambio).** Italy's e-invoicing mandate has been in force for B2B since 2019 and is the most mature in Europe. The network sends invoices through SDI, manages the XML format, and handles the receipt confirmations and rejections.
**France — Chorus Pro and Factur-X.** France's public-sector mandate runs through Chorus Pro. The B2B mandate is rolling out in phases under the Factur-X (hybrid PDF + XML) format. The network handles both routing and format, including the upcoming PDP (Plateforme de Dématérialisation Partenaire) requirements.
**Germany — ZUGFeRD and XRechnung.** Germany requires XRechnung for B2G and is moving toward mandatory B2B e-invoicing with ZUGFeRD as the hybrid standard. The network supports both formats and the Peppol routing layer that German public sector buyers expect.
**Other EU mandates.** Spain (Verifactu and B2B mandate), Poland (KSeF), Belgium (Peppol), the Netherlands, and the Nordics all have active or upcoming mandates. SAP keeps the compliance profiles current centrally — your team configures the profile per legal entity rather than building each mandate from scratch.
## A Fleurop note
Spadoom defined the SAP Business Network roadmap for Fleurop covering procure-to-pay automation and supplier base consolidation. The work addressed both the volume of manual invoice processing and the duplication in the supplier master, on the same procurement platform that backs the supply-chain collaboration side. The detail is in the [Fleurop case study](/en/success-stories/fleurop-digital-flower-delivery/).
## Implementation phases
We deliver via [SAP Activate methodology](/en/how-we-work/) — discovery, prepare, explore, realize, deploy, run. A focused e-invoicing and PO automation rollout typically runs 12–20 weeks. Adding sourcing and contracts pushes the overall programme out by another 2–4 months.
Discovery scopes the procure-to-pay slice that goes live first — usually e-invoicing and PO collaboration for the top suppliers by volume. Prepare locks the integration to S/4HANA or ECC, decides the master-data consolidation approach, and identifies the country mandates in scope. Explore designs the catalog structure, the guided buying flows, the approval workflows, and the supplier-onboarding plan.
Realize is the build: integration content, catalog setup, workflow configuration, e-invoicing compliance profiles, supplier onboarding tooling. We bake explicit data-cleansing and supplier-onboarding workstreams into this phase from day one — they are not optional. Deploy is the cutover with hyper-care. Run is steady-state operations with documented playbooks.
## What good looks like
A year into steady state, the operational picture should look like this.
- E-invoicing covers more than 90% of supplier invoice volume. Manual PDF processing is the exception, not the default.
- Three-way matching is automated. Exception handling is the only invoice work the AP team does.
- The supplier master is single-instance. One supplier, one record, one spend view.
- On-contract spend is trending up, measurably, because requisitioners default to the catalog and approval workflows enforce the contracted route.
- Country-specific e-invoicing mandates are handled inside the network's compliance profiles, not as discrete projects every time a new mandate goes live.
- Supplier onboarding is a workflow, not an inbox. Qualifications, certifications, and bank details are captured once and maintained with change-control.
- Spend visibility — by category, supplier, cost centre, plant — comes from live data and is reconciled with finance because both sides are reading the same network.
That is the operational endpoint. Procurement stops being a backlog of exceptions and becomes a managed pipeline.
If your priority is multi-tier supplier collaboration (forecasts, ASNs, quality records) rather than procure-to-pay, see [Supply Chain Collaboration](/en/solutions/supply-chain-collaboration/).
---
### Sustainability Control Tower
SAP Product: SAP Sustainability Control Tower
URL: https://www.spadoom.com/en/solutions/sustainability-control-tower/
Description: Steer ESG performance from a single SAP-native platform. Pull energy, emissions, social, and governance data from across your business — and report on CSRD, ESRS, and the SEC climate rules with audit-grade traceability.
## What is SAP Sustainability Control Tower?
[SAP Sustainability Control Tower](https://www.sap.com/products/scm/sustainability-control-tower.html) is SAP's central platform for ESG reporting and steering. It consolidates emissions, social, and governance data from SAP and third-party systems into audit-ready dashboards, with [pre-built data models](https://www.sap.com/products/scm/sustainability-control-tower/features.html) aligned to CSRD, ESRS, and the EU Taxonomy. The [SAP Help Portal documentation](https://help.sap.com/docs/SAP_SUS_SCT) covers the data model, metrics catalog, and integration scope.
For European companies facing their first CSRD reporting cycles, Spadoom configures Control Tower on the SAP S/4HANA backbone — for manufacturers and retailers across Switzerland, Germany, Austria, and Italy. The rest of this page covers what we deliver, why bolted-on ESG reporting fails, and what audit-ready looks like a year in.
## What Spadoom delivers
We connect the sustainability data already sitting inside your SAP landscape to a single steering and reporting platform. The starting point is almost always carbon accounting — Scope 1, 2, and the relevant slices of Scope 3 — calculated from primary data: energy meters, fleet records, asset management, procurement spend, and travel data inside SAP ERP. From there we configure the CSRD and ESRS disclosure scope that applies to your sector and reporting boundary, build the ESG KPI dashboards that sit alongside your finance KPIs, and stand up the audit trail that turns "trust us" into "here is the source record".
ERP integration is the part most ESG projects underestimate. SAP ships native data flows between Sustainability Control Tower and S/4HANA, SAP Asset Management, and SAP Ariba. We configure those flows end to end. No custom middleware. No quarterly extracts that go stale within a week.
We are based in the DACH region and deliver hands-on. Our consultants run discovery, design the data model, sit with your sustainability and finance teams during validation, and stay through the first reporting cycle. The goal is a control tower your team operates, not one we operate for you.
## Why ESG reporting fails when bolted on
If you sit anywhere near sustainability reporting today, this list will sound familiar.
Carbon data lives in spreadsheets. The energy team owns one workbook, facilities owns another, the fleet sits in a third, and Scope 3 is a quarterly email exchange with procurement. Every reporting cycle is a scramble: numbers reconciled at month-end, assumptions re-explained, and a finance reviewer who has no way to tie any of it back to a primary source.
There are multiple sources of truth for the same emissions number. Group sustainability has one figure for a German plant, the plant has another, and the energy supplier reports a third. Nobody can say definitively which is right, because none of them flow from the same underlying record.
Audit requests take weeks. The auditor asks for the calculation behind a single Scope 2 figure and the team spends ten days reassembling it from emails, PDFs, and a spreadsheet history. By the time the answer comes back, the auditor has moved on.
CSRD changes the rules. Disclosure is no longer voluntary, the data points are specified, and the audit standard is the same one your finance numbers face. ESG reporting that worked as a year-end exercise on top of Excel does not survive contact with that regime.
## How Control Tower fixes that
The shift is structural, not cosmetic. Once sustainability data flows from the same ERP records that finance trusts, every disclosure has a single canonical source, visible to both sides, with an audit trail.
Scope 1 and 2 emissions calculate from primary ERP data. Energy consumption posts from meter readings or supplier invoices, fuel from fleet records, refrigerant losses from asset maintenance. The number on the dashboard ties back to a transaction you can open. Scope 3 categories — purchased goods, business travel, upstream transport — pull from procurement and travel data already inside the SAP backbone.
CSRD-aligned data models ship with the platform. The ESRS data points are pre-built. We configure which apply to your sector and your reporting boundary, and the disclosure structure is set. No bespoke spreadsheet templates that need rebuilding when the standard updates.
ESG metrics sit alongside finance KPIs in the same workspace. Governance and social indicators — board diversity, lost-time injury rate, supplier audit coverage — are visible to the executive team next to revenue and EBITDA, not in a separate appendix the board sees once a year.
Audit-grade traceability is the layer most teams have never had. Every figure on the dashboard is linked to its source records. When the auditor asks why Scope 2 is what it is, the answer is two clicks away.
## Implementation in practice
We deliver via [SAP Activate methodology](/en/how-we-work/) — discovery, prepare, explore, realize, deploy, run. An initial CSRD-aligned reporting scope on top of SAP S/4HANA typically runs 8–16 weeks. Broader Scope 3 modelling, supplier data integration, and a wider set of ESRS topics extend that.
Discovery scopes the disclosure boundary: which entities, which ESRS topics are material, which Scope 3 categories matter, and which CSRD timeline applies to your group. Prepare locks the data model and the integration architecture with S/4HANA, Asset Management, and Ariba. Explore is where the data sources become the critical path — most projects underestimate the cleanup effort for emissions factor libraries and supplier mappings.
Realize covers configuration of the dashboards, integration build, and end-to-end testing against a known reporting period. Deploy is the cutover, with a hyper-care window through the first quarterly cycle. Run is steady-state — your team owns the operations.
There is a CX angle that is easy to miss. Customers increasingly ask for product-level carbon footprints, and a sales rep who answers "we'll get back to you" loses to one who answers "here it is". Where customer-facing sustainability claims need ESG backing — product passports, supplier-level emissions in a tender response, scope-3 commitments in a master agreement — Control Tower is the system of record that backs the claim. We connect that record to the SAP CX layer where the conversation happens.
## What good looks like
A year in, what changed shows up in steady-state behaviour, not in a launch press release.
- Scope 1 and 2 emissions report monthly from primary ERP data. The figure on the executive dashboard ties back to transactions, not to a workbook.
- The CSRD report is ready before year-end, not in March. The disclosures pull from the same data the finance team is closing the books on.
- Governance and social metrics are visible to the executive team alongside revenue and EBITDA. ESG stops being a separate conversation.
- Audit requests for emissions calculations are answered in hours. The lineage is in the system.
- Procurement, sales, and product teams pull supplier and product-level emissions on demand — the data is no longer a quarterly favour from the sustainability team.
That is the steady state. It is operational, durable, and audit-ready by default.
---
### Business Data Cloud
SAP Product: SAP Business Data Cloud
URL: https://www.spadoom.com/en/solutions/business-data-cloud/
Description: SAP Business Data Cloud (BDC) — the data foundation that makes your CX and ERP data actually usable. Spadoom connects BDC to SAP Sales Cloud V2, Service Cloud V2, and S/4HANA Public Cloud for Swiss mid-market companies.
## What is SAP Business Data Cloud?
[SAP Business Data Cloud](https://www.sap.com/products/data-cloud.html) (BDC) is SAP's managed data platform, announced in February 2025. It brings together SAP Datasphere, SAP Analytics Cloud, and a natively embedded [Databricks](https://www.databricks.com/company/partners/sap) engine in a single SaaS offering. The core idea: instead of every customer extracting, cleaning, and modelling SAP data themselves, SAP ships **data products** — curated, zero-copy, semantically consistent datasets from S/4HANA, SAP Sales and Service Cloud V2, SuccessFactors, and other SAP applications — and keeps them current through every release.
That solves the problem most companies actually have. Not "we need another BI tool" — but "our CRM says one number, our ERP says another, and nobody trusts either."
## Why this matters for the Swiss mid-market
Large enterprises have data engineering teams. Swiss mid-market companies — the manufacturers, distributors, and industrial firms we work with every day — usually don't. They have an ERP, a CRM, a warehouse of spreadsheets, and a management team that wants answers without a two-year data programme.
BDC changes the economics: the extraction and modelling work that used to require a dedicated team now ships as a maintained SAP product. What remains is the part that actually differentiates — deciding which questions matter, connecting the right domains, and putting the answers where people work. That part is consulting, not plumbing, and it is measured in weeks.
## BDC and Datasphere: what changes, what stays
If you already run SAP Datasphere, nothing you built is lost — Datasphere becomes a component of Business Data Cloud, and existing spaces and models carry over. What changes is the packaging and the ceiling: one contract covers Datasphere, SAP Analytics Cloud, and Databricks; SAP-managed data products replace hand-maintained replication flows; and machine-learning workloads run inside SAP governance instead of in a parallel shadow platform. We wrote up the details in [BDC and Datasphere: what changes, what stays](/en/blog/bdc-and-datasphere-what-changes-what-stays/).
## The data foundation under your CX and ERP
This is our angle, and it is different from the classic BI house. Spadoom's core business is [SAP Sales Cloud V2](/en/solutions/sales-cloud/), [Service Cloud V2](/en/solutions/service-cloud/), and [S/4HANA Public Cloud](/en/solutions/s4hana-cloud-public/). We implement the systems that *produce* the data — pipeline, orders, cases, margins. BDC is where that data becomes usable:
- **Pipeline-to-cash in one view.** Opportunities from Sales Cloud V2 joined with orders and invoices from S/4HANA — the report every CFO asks for and almost nobody has.
- **Service profitability.** Cases and SLAs from Service Cloud V2 against contract margins from the ERP.
- **Forecast you can defend.** CRM forecast quality measured against what actually shipped.
A data platform team can model these domains; we have implemented them. That is the difference between a BDC project that produces dashboards and one that produces decisions.
## What Spadoom delivers
We deliver BDC the same way we deliver CX: fixed scope, Swiss directness, and adoption over shelfware. A typical first engagement: activate BDC, connect the S/4HANA and Sales Cloud V2 data products, model one business domain end to end, and ship the first insight app to the people who need it. From there you extend domain by domain — each one paying for the next.
Start with the fundamentals if you want the full picture: [SAP Business Data Cloud explained](/en/blog/sap-business-data-cloud-explained/).
## BDC and SAP Business AI
Every AI conversation ends at the same place: the data. Joule agents, AI forecasting in Sales Cloud V2, automated service resolution — all of it runs on the data underneath, and AI on messy data is expensive noise. BDC is the foundation layer of [our SAP Business AI practice](/en/solutions/business-ai/): clean, governed, connected data first, then AI that actually holds up in production.
## What good looks like
A BDC implementation is working when management stops debating whose number is right and starts debating what to do about it. One semantic model, maintained by SAP, consumed by dashboards, Databricks notebooks, and Joule agents alike — and a mid-market data foundation that one team can own without a data engineering department.
---
### Business AI
SAP Product: SAP Business AI
URL: https://www.spadoom.com/en/solutions/business-ai/
Description: AI where it helps the work: data quality, service triage and planning. Spadoom connects the process, SAP systems and human approval.
## Start with a task you can measure.
We use AI in our delivery: analysis, code, tests and documentation, with our team responsible for the result. For your business, we begin with a concrete workflow and an agreed baseline. A demo shows an idea; a pilot tests it on authorised data; production requires acceptance, monitoring and a named owner.
## Data quality before migration
Suggest duplicates and missing fields. Data owners approve changes before migration.
## Service triage
Evaluate classification and response drafts against real service categories. Agents approve customer-facing answers.
## Field-service planning
Test scheduling proposals against skills, availability and travel constraints. Dispatchers retain the decision.
## Joule and SAP Business AI
Check the release, region, licences and available functions for your SAP tenant before agreeing scope.
## AI-assisted delivery
Use AI for analysis, implementation and testing. Engineers review code and own the integration.
## A measured pilot
Agree a baseline, a representative test set and acceptance thresholds. Measure time saved, errors and human corrections.
## Connected data, explicit permissions
AI does not remove integration work. ERP and CX must expose the required data through supported interfaces and permissions. SAP BTP and, where justified, Business Data Cloud can provide the foundation. A shared data platform is an architecture choice, not a prerequisite for every AI use case.
## Make the first step small
Bring one process that costs your team time. We define the decision, the data, the human review and the measurement. Product roadmap items stay separate from available features. We do not present illustrative workflows as productive customer references.
[Discuss an AI use case](/en/contact/?topic=SAP%20Business%20AI)
---
### SAP BTP
SAP Product: SAP Business Technology Platform
URL: https://www.spadoom.com/en/solutions/sap-btp/
Description: The foundation for the extensions we build. Connect Cloud ERP and CX, automate handoffs and add the processes your business needs.
## Connect. Extend. Automate.
SAP BTP is the base for our extensions. We connect SAP S/4HANA Cloud Public Edition with Sales Cloud, Service Cloud, Commerce, CPQ and FSM. We start with the business process, agree who owns each record and build the interfaces, applications and monitoring around it.
## From a quote to a job in the field
A salesperson prepares an offer in Sales Cloud and CPQ. The accepted order reaches Cloud ERP. A service requirement creates work for the field team in FSM. BTP connects the handoffs and any extensions the process needs. This is an example architecture: the exact interfaces, product scope and licences are checked during assessment.
## Start with one flow. Build it properly.
Bring a workflow that still depends on copying data or chasing an email. In a fixed-price assessment, we map its systems, data owners and exceptions. You receive a proposed architecture, delivery scope and cost basis. We agree acceptance tests before implementation and include monitoring and handover in the scope.
[SAP product documentation](https://help.sap.com/docs/btp)
## Comparison Pages (SAP vs Competitors)
### SAP Sales Cloud V2 vs Salesforce
URL: https://www.spadoom.com/en/compare/sap-sales-cloud-v2-vs-salesforce/
Verdict: If your ERP is SAP S/4HANA, SAP Sales Cloud V2 wins on integration, architecture, and implementation speed. If you live in the Salesforce ecosystem, Salesforce's breadth is hard to beat. The tipping point is almost always your ERP.
### SAP Sales Cloud V2 vs Microsoft Dynamics 365
URL: https://www.spadoom.com/en/compare/sap-sales-cloud-v2-vs-microsoft-dynamics-365/
Verdict: If your ERP is SAP, SAP Sales Cloud V2 is the logical choice — native integration eliminates middleware cost and complexity. If your business runs on Microsoft 365 and Azure, Dynamics 365 fits naturally into that ecosystem. Both are capable platforms; the winner is whichever connects to your ERP without a middleware layer.
### SAP Sales Cloud V1 vs V2: What Actually Changes
URL: https://www.spadoom.com/en/compare/sap-sales-cloud-v1-vs-v2-migration/
Verdict: SAP Sales Cloud V2 is architecturally superior in every measurable way. The question is not whether to migrate — SAP has signalled V1's end of innovation — but when and how. Migrations with experienced partners run 4–8 weeks. Those who try to go it alone typically spend 3–4× longer.
### SAP Sales Cloud V2 vs HubSpot CRM
URL: https://www.spadoom.com/en/compare/sap-sales-cloud-v2-vs-hubspot/
Verdict: For SMBs with no SAP ERP and a marketing-first culture, HubSpot CRM is excellent — fast to deploy, generous free tier, and tightly integrated with HubSpot Marketing. For companies running SAP ERP or planning B2B growth at enterprise scale, SAP Sales Cloud V2 is the better long-term bet. The gap closes as HubSpot's enterprise pricing rises and SAP's implementation speed improves.
### SAP Service Cloud V2 vs Salesforce Service Cloud
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-salesforce-service-cloud/
Verdict: For SAP ERP shops that need service-to-field-service workflows and live ERP data in the agent console: SAP Service Cloud V2. For organisations deep in the Salesforce ecosystem with AppExchange dependencies: Salesforce Service Cloud. The tipping point is your ERP and whether you need native field service dispatch.
### SAP Service Cloud V2 vs Zendesk
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-zendesk/
Verdict: Zendesk wins on speed-to-deploy and ease of use for straightforward support operations. SAP Service Cloud V2 wins for B2B organisations with complex SLAs, SAP ERP integration needs, and field service escalation workflows. If your service desk needs to see warranty data from S/4HANA, Zendesk cannot do that without custom middleware.
### SAP Commerce Cloud vs Shopify Plus
URL: https://www.spadoom.com/en/compare/sap-commerce-cloud-vs-shopify-plus/
Verdict: For D2C and B2C brands that want to launch fast with minimal infrastructure: Shopify Plus. For B2B enterprises with complex catalogues, customer-specific pricing, punch-out requirements, and SAP ERP integration: SAP Commerce Cloud. The deciding factors are almost always B2B requirements and ERP connectivity.
### SAP Commerce Cloud, ERP Edition vs Shopify Plus
URL: https://www.spadoom.com/en/compare/sap-commerce-cloud-erp-edition-vs-shopify-plus/
Verdict: For B2B SMEs already running or moving to S/4HANA Public Cloud: SAP Commerce Cloud, ERP Edition wins on integration depth, AI inclusion, and the absence of a separate frontend project. For brands needing a polished branded storefront, an app ecosystem, or operating outside SAP: Shopify Plus remains the right answer. The tipping point is your ERP.
### SAP Engagement Cloud (Emarsys) vs HubSpot Marketing Hub
URL: https://www.spadoom.com/en/compare/sap-emarsys-vs-hubspot-marketing/
Verdict: HubSpot Marketing Hub is the better platform for B2B lead generation, inbound marketing, and CRM-driven nurturing. SAP Engagement Cloud (Emarsys) is the better platform for B2C/e-commerce lifecycle automation, omnichannel orchestration, and organisations already running SAP CX. The overlap is smaller than you think.
### SAP Engagement Cloud (Emarsys) vs Klaviyo
URL: https://www.spadoom.com/en/compare/sap-emarsys-vs-klaviyo/
Verdict: Klaviyo is the better choice for Shopify-native e-commerce businesses with straightforward marketing needs. SAP Engagement Cloud (Emarsys) is the better choice for enterprises running SAP Commerce Cloud, companies needing loyalty programme integration, or organisations that require true omnichannel beyond email and SMS.
### SAP CPQ vs Salesforce CPQ
URL: https://www.spadoom.com/en/compare/sap-cpq-vs-salesforce-cpq/
Verdict: For SAP ERP shops with complex BOMs and multi-level product configuration: SAP CPQ. For Salesforce-native organisations with simpler product bundles: Salesforce CPQ (Revenue Cloud). The ERP integration question is decisive — pulling live pricing from SAP into Salesforce CPQ requires middleware that SAP CPQ eliminates.
### SAP Commerce Cloud vs Adobe Commerce
URL: https://www.spadoom.com/en/compare/sap-commerce-cloud-vs-adobe-commerce/
Verdict: If your back office runs on SAP S/4HANA, SAP Commerce Cloud wins on integration depth, B2B capabilities, and total cost of ownership. If you need maximum customisation flexibility and have strong in-house PHP/Magento developers, Adobe Commerce gives you more control over the codebase. The tipping point is almost always your ERP and your team's skillset.
### SAP Service Cloud V2 vs ServiceNow
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-servicenow/
Verdict: If your service operations are tightly connected to SAP ERP (warranties, spare parts, service contracts), SAP Service Cloud V2 wins on integration depth. If you need unified IT + customer service on one platform with sophisticated workflow automation, ServiceNow is stronger.
### SAP Service Cloud V2 vs Dynamics 365 Customer Service
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-dynamics-365-customer-service/
Verdict: If your ERP is SAP S/4HANA, SAP Service Cloud V2 wins on integration depth — warranties, service contracts, and spare parts flow natively. If your organisation lives in Microsoft 365 and Teams, Dynamics 365 Customer Service fits naturally into your agents' daily workflow.
### SAP Service Cloud V2 vs Freshdesk
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-freshdesk/
Verdict: If you're an SAP ERP company with complex service processes (warranties, SLAs, spare parts, installed base), SAP Service Cloud V2 is the right tool. If you need a simple, affordable helpdesk for straightforward ticket management, Freshdesk delivers excellent value at a fraction of the cost.
### SAP Service Cloud V2 vs HubSpot Service Hub
URL: https://www.spadoom.com/en/compare/sap-service-cloud-v2-vs-hubspot-service-hub/
Verdict: If your service operations require deep ERP integration (warranties, service contracts, spare parts) and complex B2B processes, SAP Service Cloud V2 is the right platform. If your priority is a unified marketing-sales-service CRM with an easy-to-use interface, HubSpot Service Hub is compelling — especially if you already use HubSpot CRM.
### SAP S/4HANA Public Cloud + Sales Cloud V2 vs Salesforce on SAP ERP
URL: https://www.spadoom.com/en/compare/sap-s4hana-public-cloud-sales-cloud-v2-vs-salesforce/
Verdict: For companies running SAP S/4HANA Public Cloud, the integrated stack wins on total cost of ownership, data quality, and implementation speed. Salesforce is a powerful platform — but running it alongside SAP means maintaining two systems of truth, a middleware layer, and two release cadences. The integration tax adds up fast. If your organisation is deeply invested in the Salesforce ecosystem (AppExchange, Salesforce Marketing Cloud, large internal SF team), those switching costs are real and must be weighed honestly.
## Events (listing: https://www.spadoom.com/en/events/)
### Spadoom SME Christmas @ Google — Save the Date
Date: 2026-12-10
Location: Google Zürich, Europaallee, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/spadoom-sme-google-fondue-2026/
Description: A festive afternoon for Swiss SMEs at Google Zürich this December — honest SAP CX conversations and the Zurich Christmas spirit. Save the date; exact date to be confirmed.
### SAP Connect Day for KMU – Zürich 2026
Date: 2026-12-03
Location: Zürich, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/sap-connect-day-kmu-zurich-2026/
Description: Meet Spadoom at the year-end SAP Connect Day for KMU in Zürich. Booth and a stage talk on SAP CX for Swiss SMEs — real Sales & Service Cloud V2 projects.
### LEAD 2026
Date: 2026-11-19
Location: Kongresshaus Zürich, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/lead-2026/
Description: Dario Pedol — DSAG Customer Experience Switzerland spokesperson — attends LEAD 2026, one of Switzerland's leading marketing and digital business conferences.
### SAP NOW AI Tour Switzerland 2026
Date: 2026-11-05
Location: Halle 550, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/sap-now-switzerland-2026/
Description: Meet Spadoom at SAP NOW AI Tour Switzerland 2026. Booth, a joint stage session with Felchlin, and live SAP Sales & Service Cloud V2 demos.
### SAP Partner Summit Series Amsterdam 2026
Date: 2026-10-19
Location: RAI Amsterdam, Amsterdam, Netherlands
URL: https://www.spadoom.com/en/events/sap-partner-summit-amsterdam-2026/
Description: SAP's Partner Summit Series at RAI Amsterdam, 19–21 October 2026. Spadoom's leadership is on site to deepen the SAP partnership and bring the latest SAP CX direction back to Swiss and European customers.
### DSAG Jahreskongress 2026
Date: 2026-10-14
Location: Congress Center Leipzig, Leipzig, Germany
URL: https://www.spadoom.com/en/events/dsag-congress-2026/
Description: Spadoom at DSAG's flagship annual congress — the largest SAP user group event in Europe.
### DSAG CX Switzerland — Service Cloud Focus 2026
Date: 2026-09-23
Location: Google Zürich, Europaallee, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/dsag-cx-service-cloud-2026/
Description: Dario Pedol — DSAG Customer Experience Switzerland spokesperson and CEO of Spadoom — hosts the September 2026 working group session at Google Zürich, focused on SAP Service Cloud V2.
### SAP Connect Day for KMU – Bern 2026
Date: 2026-08-27
Location: Bern, Bern, Switzerland
URL: https://www.spadoom.com/en/events/sap-connect-day-kmu-bern-2026/
Description: Meet Spadoom at the SAP Connect Day for KMU in Bern. Booth plus a stage talk on SAP CX for Swiss SMEs — real Sales & Service Cloud V2 implementations.
### SAP Connect Day for KMU – Bodensee 2026
Date: 2026-08-12
Location: Romanshorn, Romanshorn, Switzerland
URL: https://www.spadoom.com/en/events/sap-connect-day-kmu-bodensee-2026/
Description: Meet Spadoom at SAP's Connect Day for SMEs at Lake Constance. Pascal Strnad is on site to talk SAP CX for SMEs.
### SAP CX for SMEs – Summer Vibes @ AWS Zurich
Date: 2026-06-29
Location: Amazon Web Services Zurich (ZRH15), Zurich, Switzerland
URL: https://www.spadoom.com/en/events/summer-vibes/
Description: A summer afternoon with Swiss SME leaders — how to sell more, make service better, and understand what SAP actually offers. Real stories from the field, no slide decks, plus an Apéro Riche on Lake Zurich.
### Swiss Customer Relations Forum 2026
Date: 2026-05-21
Location: Kongresshaus Zürich, Zürich, Switzerland
URL: https://www.spadoom.com/en/events/swiss-crm-forum-zurich-2026/
Description: Dario Pedol — DSAG Customer Experience Switzerland spokesperson — at the Swiss CRM Forum 2026. The Swiss meeting point for CX, CRM, and AI-driven customer engagement.
### SAP Sapphire Madrid 2026
Date: 2026-05-19
Location: IFEMA Madrid, Av. del Partenón 5, Barajas, 28042 Madrid, Madrid, Spain
URL: https://www.spadoom.com/en/events/sap-sapphire-madrid-2026/
Description: The European chapter of SAP's flagship customer event. Pascal Strnad, Spadoom's CRO, will be on site for one-to-one conversations on SAP Commerce Cloud, ERP Edition and the broader SAP CX roadmap.
### OMR Festival 2026
Date: 2026-05-05
Location: Hamburg Messe, Hamburg, Germany
URL: https://www.spadoom.com/en/events/omr-2026/
Description: Spadoom at OMR 2026 — find us at the SAP booth for a proper chat about CX, digital commerce, and what's next.
### Webinar: SAP Sales Cloud V2 Migration Masterclass
Date: 2026-04-10
Location: Online
URL: https://www.spadoom.com/en/events/v2-migration-webinar/
Description: A 45-minute deep-dive into migrating from SAP C4C/V1 to Sales Cloud V2 — architecture, data migration, and lessons from 10+ projects.
### SAP Connect Day for Customer Experience 2026
Date: 2026-04-09
Location: Aeschbachhalle (AHA!), Aarau, Switzerland
URL: https://www.spadoom.com/en/events/sap-connect-day-cx-2026/
Description: Spadoom at the SAP Connect Day for Customer Experience in Aarau — the dedicated CX track of the SAP Connect Days Switzerland 2026.
### DSAG Customer Experience Event 2026
Date: 2026-02-26
Location: AWS Zurich Office, Zurich, Switzerland
URL: https://www.spadoom.com/en/events/dsag-cx-2026/
Description: Spadoom presents at the DSAG Customer Experience working group meeting — real stories, real systems, real results with SAP Sales & Service Cloud V2.
## Recent Blog Posts (listing: https://www.spadoom.com/en/blog/)
### SAP Commerce Cloud: What Matters in September 2026
URL: https://www.spadoom.com/en/blog/sap-commerce-cloud-september-2026-practical-updates/
Description: Vercel storefronts, conversational commerce and the tests that matter before adopting new SAP Commerce Cloud capabilities.
### An Agent That Watches Our Blog and Drafts the Social Posts
URL: https://www.spadoom.com/en/blog/blog-watcher-agent-social-drafts/
Description: How Spadoom uses an AI agent that watches the blog and drafts platform-specific social posts, and why the human keeps the publish button.
### Four Languages, One CRM: Making SSCV2 Truly Multilingual
URL: https://www.spadoom.com/en/blog/sscv2-four-languages-multilingual-crm/
Description: Lessons from running SAP Sales and Service Cloud V2 in German, French, Italian and English: the logon language rules, translation is two jobs, and test after a fresh login.
### Native Screen Pop in the SSCV2 Agent Desktop: What the PDF Does Not Tell You
URL: https://www.spadoom.com/en/blog/sscv2-native-screen-pop-agent-desktop/
Description: Lessons from wiring a telephony widget into the native SAP Sales and Service Cloud V2 Agent Desktop screen pop: silent contracts, ID discipline, and timing races.
### Connecting SAP Sales Cloud V2 with Business Data Cloud: Integration Patterns That Work
URL: https://www.spadoom.com/en/blog/sales-cloud-v2-business-data-cloud-integration-patterns/
Description: How SAP Sales Cloud V2 data lands in Business Data Cloud: data products vs custom extraction, pipeline-to-cash modelling, and the patterns that survive production.
### SAP Engagement Cloud: Emarsys Edition vs Enterprise Edition, Compared Properly
URL: https://www.spadoom.com/en/blog/sap-engagement-cloud-emarsys-vs-enterprise-edition/
Description: Emarsys edition or Enterprise edition? Feature scope, modules, licensing mechanics, and the real price gap based on current SAP list prices.
### SAP Commerce On-Prem Support Ended Yesterday. Now What?
URL: https://www.spadoom.com/en/blog/sap-commerce-onprem-support-ended-now-what/
Description: SAP Commerce on-premise mainstream maintenance ended July 31, 2026. The 4 realistic paths now: risk it, extended maintenance, Commerce Cloud, or replatform.
### Quoting Configurable Products in the Field: Sales Cloud V2 + AVC in S/4HANA Public Cloud
URL: https://www.spadoom.com/en/blog/avc-quoting-sales-cloud-v2-s4hana-public-cloud/
Description: SAP Sales Cloud V2 has no AVC engine and doesn't need one. Lean quote in the CRM, configuration in the S/4HANA order: architecture, ground rules.
### ABAP Lives: Getting Embedded Steampunk Right in S/4HANA Public Cloud
URL: https://www.spadoom.com/en/blog/embedded-steampunk-abap-cloud-s4hana-public-cloud/
Description: ABAP isn't dead in S/4HANA Public Cloud, it has become disciplined. Key user vs Embedded Steampunk vs BTP: terminology, rules, decision ladder.
### Side-by-Side: Extending S/4HANA Public Cloud with Small Cloud Foundry Apps, Without Sacrificing the Clean Core
URL: https://www.spadoom.com/en/blog/extend-s4hana-public-cloud-btp-cloud-foundry/
Description: Key-user extensibility at its limit? Small CAP apps on SAP BTP Cloud Foundry extend S/4HANA Public Cloud via released APIs. With a checklist.
## Contact
https://www.spadoom.com/en/contact/
support@spadoom.com
+41 44 577 76 75