4.9
One commercetools partner for your architecture and the storefront your customers use. Building composable and headless commerce since 2019, when we open-sourced ScandiPWA.
scandiweb is a composable commerce agency and an official commercetools partner, covering solution architecture, headless storefront development, integrations, replatforming, and the support that follows.
commercetools gives you APIs and a data model rather than a finished store, so your project is really the front end your customers see plus the integration layer joining it to the systems that already hold your product and order data. That layer is where composable budgets overrun, and it is the part we scope first.
scandiweb is listed as a commercetools partner, and the same architects who hold that relationship are the ones assigned to your build. No part of the delivery is passed to a subcontractor.
Composable architecture spreads card and customer data across far more services than a monolith does, so procurement asks harder questions of you. scandiweb holds PCI DSS, ISO 27001, and ISO 27017.
Your architecture is sized by a team that has already built at this scale, with $4B+ processed through client stores every year. The trade-offs in your design review are familiar ones here.
Enterprise projects where the storefront and the commerce services behind it were built and deployed as separate pieces.
A commercetools partner builds everything the platform deliberately leaves to you. commercetools supplies the commerce APIs and the data model, nothing more. A commercetools implementation therefore covers the service architecture, the storefront that calls those APIs, and the connections into the systems already holding your product and order data. The vendor licenses software. The partner delivers the store your customers use.
Headless separates your storefront from one commerce backend. Composable goes further and assembles the backend itself from separate services chosen per capability, so search and pricing can each come from a different vendor. commercetools is built for the composable model. Every composable build is also headless, though many headless commerce projects keep a single monolithic backend underneath.
Most commercetools projects connect an ERP, a PIM, an OMS or WMS, a CDP, payment providers, tax engines, and a search and merchandising service, among others. We have built connectors across systems including SAP, NetSuite, Akeneo, Manhattan, and Stripe. The pattern matters more than the vendor name: we map the data owner for every field before writing any connector code.
You do. Every service, connector, and storefront component we write on commercetools is delivered into your repository under your ownership, with no proprietary layer you have to keep licensing from us. That is the point of composable architecture, and an agency that hands back something you cannot maintain elsewhere has undone the reason you left a monolith.
Yes. scandiweb appears in the commercetools partner listing. Our composable track record predates it: ScandiPWA, our open-source React storefront for Adobe Commerce, has been in production since 2019 and is used by more than 500 brands. The architects covered by the partner listing are the same ones assigned to your project.
Two checks matter more than the capability deck. First, find out who designs your integration layer and whether those people stay through delivery, because composable overruns start there rather than in storefront code. Second, ask which of their published projects were genuinely composable, since headless experience on a monolithic backend is a different discipline.
Yes, and a fair share of our composable projects begin that way. We open with a readiness audit covering your service boundaries and how much custom logic lives outside version control. The output is a written assessment naming what to keep and what to retire, with an estimate against each. You own that assessment whether or not we go on to build.
The number follows how many services you compose rather than how large your storefront is. A single-market build on standard connectors costs far less than a multi-market program with custom pricing and promotion services. We quote after the readiness audit, never before it. commercetools licenses its platform to you directly, and that cost is separate from what we invoice.