SAP Commerce Cloud Implementation: What Actually Happens in a Project
Cyrill Pedol
SAP Commerce Lead, Spadoom AG
Most content about SAP Commerce Cloud implementations reads like a vendor brochure. This post is different. It covers what actually happens in a project — the decisions that matter, the phases that take longer than expected, and the patterns that separate smooth implementations from painful ones.
SAP has been a Leader in the Gartner Magic Quadrant for Digital Commerce for 11 consecutive years (SAP News Center, 2025). But being a market leader doesn’t make implementations easy. 83% of data migration projects exceed their budgets or schedules (Bloor Group, 2023). The difference between the 17% that succeed and the rest comes down to preparation, architecture decisions, and execution discipline.
TL;DR: SAP Commerce Cloud implementations typically take 3–9 months depending on scope. The four phases that matter: discovery (architecture decisions), build (iterative delivery in 2–4 week sprints), integration (ERP, PIM, payment, shipping), and go-live (data migration, performance testing, cutover). Agile delivery has a 42% success rate vs 13% for waterfall (Standish Group, 2020). Start with a discovery workshop and customisation audit — they save multiples of their cost during build.
What Happens During Discovery?
The discovery phase is where projects are won or lost. 47% of IT leaders cite technical debt as a major driver of overspending (IDC, 2024). Discovery is where you find that debt before it derails the build.
A good discovery phase (2–4 weeks) covers:
Architecture decisions. Composable Storefront or custom frontend? How many environments? What CI/CD pipeline? These choices are hard to change later.
Customisation audit. If you’re migrating from on-prem, classify every customisation: still needed, replaceable by platform capability, or obsolete. We typically find 25–35% are removable.
Data assessment. Profile your product catalogue, customer records, order history, and content. Identify quality issues before they become migration blockers.
Integration mapping. Document every inbound and outbound connection — ERP, PIM, CRM, payment, shipping, tax, analytics. For each: protocol, data format, frequency, error handling.
Team structure and governance. Who owns what? How do decisions get made? Weekly demos or monthly reviews? Get this right upfront.
How Should the Build Phase Work?
Agile projects succeed 42% of the time compared to just 13% for waterfall (Standish Group, 2020). Commerce Cloud implementations should follow iterative delivery — 2–4 week sprints, each producing a working increment.
Sprint 1: Data models and core configuration. Custom types, product catalogue structure, pricing rules, promotion engine setup. The goal is a working catalogue on staging by the end of week 2–3.
Sprint 2–3: Storefront and checkout. Deploy Composable Storefront with your product data. Build the checkout flow, cart logic, and account management. Each sprint delivers a demo-able increment.
Sprint 4+: Business logic and edge cases. Complex pricing (customer-specific, volume-based), multi-warehouse inventory, B2B features (approval workflows, purchase limits, buyer hierarchies).
The key discipline: every sprint ends with a working system that stakeholders can test. No “we’ll show you something in month 4.”
What Makes Integration the Hardest Part?
Integration work typically accounts for 30–40% of total project effort. The connections that matter most:
ERP (SAP S/4HANA, ECC). Order export, inventory sync, pricing updates, customer master data. This is usually the most complex integration — and the one you can’t get wrong.
PIM. Product data feeds, media assets, classification hierarchies. If your PIM is the master for product data, the integration needs to be real-time or near-real-time.
Payment. Payment gateway connection, tokenisation, 3D Secure, refund processing. Commerce Cloud supports multiple payment extensions — choosing and configuring the right one matters.
Shipping and logistics. Rate calculation, label generation, tracking updates. Often involves multiple carriers with different APIs.
The pattern that works: start integration development in parallel with the later build sprints. Don’t wait until the platform is “finished” — that’s how you end up with a 3-month integration phase after an already-long build.
What Does Go-Live Actually Involve?
90% of businesses that migrated platforms reported revenue improvements (commercetools, 2024). But getting to go-live requires disciplined execution:
User acceptance testing (2–3 weeks). Business users test every critical flow with real data. Not developers — business users. They find issues that developers miss.
Performance testing. Load test with realistic traffic (including peak-day simulation). Validate auto-scaling. Benchmark page load times against targets. Commerce Cloud handles scaling, but your custom code and data queries still need to perform.
Data migration dress rehearsal. Run the full migration pipeline end-to-end. Measure elapsed time — this defines your cutover window. Test delta migration for data created during the transition period.
Cutover. Execute the go-live runbook: freeze the old system, run delta migration, switch DNS, validate key flows, monitor for 48 hours with the full team on standby.
What Separates Good Implementations from Bad Ones?
Three patterns consistently separate smooth implementations from painful ones:
Discovery investment. Projects that spend 2–4 weeks on proper discovery save multiples of that cost during build. Projects that skip discovery spend the build phase discovering what they should have planned.
Scope discipline. The biggest risk isn’t technical — it’s scope creep. “While we’re at it, let’s also add…” is how 4-month projects become 9-month projects. Define the MVP. Ship it. Iterate.
Integration-first mindset. Don’t treat integration as an afterthought. Start integration architecture in discovery. Start integration development in Sprint 2 or 3. The platform isn’t useful until it connects to your ERP.
Planning an SAP Commerce Cloud implementation? We start with a discovery workshop that defines your architecture, maps your integrations, and produces a realistic timeline. Talk to us.
Frequently Asked Questions
How long does a typical SAP Commerce Cloud implementation take?
It depends on scope. A migration from on-prem with a moderate customisation footprint takes 3–6 months — we completed Franke’s in 90 days. A greenfield implementation for a complex B2B scenario with multiple storefronts, extensive integrations, and custom business logic can take 6–9 months. The biggest variable is integration complexity, not platform configuration.
How much does an SAP Commerce Cloud implementation cost?
Costs range from CHF 250,000 for a streamlined migration to CHF 800,000+ for a complex greenfield implementation. The main cost drivers are: number of integrations, customisation complexity, data volume, number of storefronts/markets, and whether you’re migrating from an existing SAP system or building from scratch.
What team do we need for an SAP Commerce Cloud project?
A typical mid-size project needs 3–5 implementation consultants (SAP Commerce, frontend, integration) plus 2–3 client-side resources (product owner, business analyst, IT liaison). The client-side product owner is critical — they make scope decisions and provide business context. Projects without a dedicated product owner consistently take longer.
Should we use Composable Storefront or a custom frontend?
Start with Composable Storefront for most projects. It’s well-integrated, actively maintained, and handles standard B2B and B2C scenarios out of the box. Consider a custom frontend (React, Next.js) only if you need a fundamentally different UX or run multiple distinct storefronts. The custom route adds 4–8 weeks and requires dedicated frontend developers for ongoing maintenance.
What’s the most common reason Commerce Cloud implementations go over budget?
Integration complexity that wasn’t properly scoped during discovery. The second most common reason is scope creep during build. Both are preventable with a disciplined discovery phase and clear MVP definition. Our discovery workshops explicitly map every integration and classify all customisations before a single line of implementation code is written.
Solutions for E-Commerce
See how SAP Commerce Cloud can work for your business.
Related Articles
From SAP Hybris to Commerce Cloud in 90 Days: A Migration Playbook
Based on the Franke migration and SAP Quality Award. Step-by-step playbook covering pre-migration audit, three delivery sprints, and go-live — with the actual timeline that made 90 days possible.
Composable Commerce After EoMM: Is It Right for Your Business?
EoMM forces a platform decision by July 2026. Composable commerce is tempting — but Commerce Cloud migration takes 3-6 months while composable takes 9-15. Here's an honest decision framework.
5 Mistakes Companies Make When Migrating Off SAP Commerce On-Prem
83% of data migrations fail or exceed their budgets. Based on real project experience with ANWR, Franke, and Distrelec: the five most common SAP Commerce migration mistakes and how to avoid each one.