SAP Commerce
On-Prem?
We keep it running. Past 2026 and beyond.
SAP ended mainstream maintenance on 31 July 2026. Your shop still works. It should stay that way, without a forced cloud migration and with a maintenance model that fits your risk and your budget.
Discuss your optionsWhat's happening
End of Mainstream Maintenance
SAP ended mainstream maintenance for SAP Commerce on-premise (release 2205, the final on-premise release) on 31 July 2026. Since 1 August 2026 the product is in Customer Specific Maintenance: no regular patches or new fixes. Source: SAP Help Portal
SapMachine 17 End of Life
SAP's support for SapMachine 17, the Java runtime of SAP Commerce 2205, ends in September 2026. After that, no more security patches for it. Running an unpatched JDK in production is a compliance risk. Source: SapMachine
SAP's option: Customer Specific Maintenance
SAP offers Customer Specific Maintenance for 2205. It keeps the platform supported but adds no new features. For many shops that run stable, targeted hardening by us covers the same risk at lower cost. We compare both with you.
A forced migration to SAP Commerce Cloud isn't always the right move. Not now, not for everyone. There is a pragmatic path in between.
Pragmatic, modular, transparent
Technical hardening and proactive maintenance by Spadoom, as an alternative or a complement to SAP's Customer Specific Maintenance. You choose what you need. Nothing more.
Security & Upgrade
- Security & health audit
- JDK migration: SapMachine 17 → Amazon Corretto 17 (LTS support until Oct 2029)
- Regression testing of all core processes
- Disable unnecessary endpoints (HAC, Backoffice)
Extended Maintenance
- Continuous vulnerability monitoring (CVE scanning)
- Patch management for Spring & 3rd-party libraries
- 2nd/3rd level incident management
- Next business day response time
AWS Migration
- AWS landing zone setup
- 1:1 lift & shift of application + database
- VPN connectivity to your network
- Full infrastructure control
Development & Support
- Frontend changes & feature extensions
- Non-critical bug fixes
- Monthly billing by actual effort
- Our own development team, no offshore handoff
Transparent. Modular. No lock-in.
You pick what you need. Every module has a clear scope and a fixed or time-based pricing model. No hidden costs, no multi-year commitments.
Security & Upgrade
Fixed scope, one-off
Extended Maintenance
Monthly retainer
AWS Migration
Project-based, optional
Development
Time & materials
Pricing depends on your setup and scope. We'll give you a detailed quote after the initial assessment.
Your Benefits
A clear cost comparison
We compare our maintenance with SAP's Customer Specific Maintenance for your setup, so you decide on numbers.
Hosting flexibility
Stay on-prem or move to AWS. Your infrastructure, your decision.
Custom SLAs
Tailored to your actual needs. Not a one-size-fits-all contract.
Ready for the cloud when you are
Ready for SAP Commerce Cloud (CCv2) when you are. We prepare the migration path.
Expert team
Consultants who have delivered SAP Commerce projects across Europe, including Franke's SAP Commerce Cloud platform (SAP Quality Award).
We know the platform
Down to bytecode level. SAP Commerce, Spring, Solr, OOTB processes: no black boxes.
From 2026 to 2029
Security audit & hardening
JDK migration to Corretto 17
SAP mainstream maintenance has ended
Spadoom maintenance begins
Ongoing patching, monitoring & support
AWS migration (optional)
Corretto 17 LTS ends
Plan next steps
Your shop runs today.
We make sure it still runs tomorrow.
No drama, no forced migration. Just a solid plan from people who know SAP Commerce inside out.
Let's talk about your Commerce platform