System assessments and risk audits
Fixed scope, fixed price. Findings with file-level evidence: the extension, the cronjob, the config flag - not a maturity heatmap. Every finding comes with a remediation plan. Read access to the repo, no production credentials needed.
- Architecture - how the platform is put together, where it fights the standard, what that costs at upgrade time.
- Performance and scale readiness - what slows down or breaks first as catalog, order volume, or traffic grows.
- Integration resilience - what happens when a connected system is slow, down, or returns garbage.
- Upgrade path - where you are versus where SAP is going, and what blocks the move.
- Security posture - configuration and code-level exposure, not a checkbox scan.
Platform improvements
Slow checkout, fragile cronjobs, integration timeouts, upgrade debt: the problems an assessment names, fixed. Prioritized remediation delivered with your team, at architecture level or in the code.
- Performance work - checkout, search, catalog jobs, caching.
- Integration hardening - retries with backoff, idempotency on money-adjacent calls, divergence checks between systems.
- Upgrade debt - reducing the custom code that stands between you and the next platform version.
Migration architecture
Accelerator storefronts to SAP composable storefront (formerly Spartacus) over OCC APIs: the Accelerator UIs are deprecated since release 2205. On-premise SAP Commerce to Commerce Cloud: mainstream maintenance ends July 31, 2026. Teams treating either move as lift-and-shift find out mid-project why it is not.
- Storefront migration - fork-depth inventory, OCC coverage gaps, what rebuilds and what maps.
- Cloud migration - customization triage, deployment model, what on-premise habits do not survive the move.
- Phasing - a cutover plan that keeps the business selling while the platform moves.
Extensibility on SAP BTP
SAP's stated direction for Commerce Cloud: keep the core clean, extend side-by-side. Event-driven microservices on SAP BTP and Kyma instead of another in-core customization. Architecture for what moves out of the platform, what stays, and how the two stay consistent.
- Decision framework - which customizations belong in core, which move to side-by-side services.
- Event-driven design - extensions that subscribe to commerce events instead of patching the platform.
- Consistency - data ownership and failure behavior between core and extensions, decided up front.
Marketplace integration
Mirakl on SAP Commerce at production scale. Connector strategy, sync resilience, rate-limit design, what breaks when seller count doubles.
- Connector strategy - the connector is a fork you own; inventory the overrides before an upgrade forces it.
- Sync resilience - retry, idempotency, and reconciliation for the jobs that move offers, orders, and refunds.
- Checkout dependencies - what your buy flow does when the marketplace API is slow or down.
Platform architecture, fractional
Senior architecture capacity for delivery teams that have developers but no one owning architecture and risk.
- Architecture ownership - decisions carried across sprints, not re-litigated every quarter.
- Risk judgment - integrations, upgrades, and scale calls made by someone who has carried them in production.
- Part-time by design - senior capacity without a full-time architect on payroll.