SAP Commerce Cloud · SAP BTP · B2B Commerce
InvertLogic is the independent SAP Commerce practice of Borislav Angelov. He has spent 15+ years consulting and building on the platform, and the last three as platform architect of a live multi-country B2B marketplace on SAP Commerce Cloud and Mirakl, serving tens of thousands of business customers.
Services
Fixed scope, fixed price. Architecture, performance, upgrade path, integration resilience, scale readiness, security posture. Findings with file-level evidence and a remediation plan. Read access to the repo, no production credentials needed.
More ->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.
More ->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.
More ->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.
More ->Mirakl on SAP Commerce at production scale. Connector strategy, sync resilience, rate-limit design, what breaks when seller count doubles.
More ->Senior architecture capacity for delivery teams that have developers but no one owning architecture and risk.
More ->If it can't handle real load with real data and real users across multiple markets, it's not architecture. It's a slide deck.
Why independent matters
Most SAP Commerce advice comes from people who sell you more of it. An SI sells hours. A platform partner sells the platform. InvertLogic keeps a production platform running and carries no vendor quota.
Every recommendation comes with its evidence and with the test that would prove it wrong. If a finding cannot be tested, it does not go in the report. Risk is bounded by measurement, not by argument. More on the practice and its track record on the About page.
Writing
Retry that does not amplify, idempotency on the money paths, reconciliation as a component, alerts on absence. The failure-path architecture that keeps marketplace sync alive - and the translation that gets it funded.
Read the article ->