FAQ

We work technology-agnostic and combine the right building blocks for each project. In the Composable space we use backends like commercetools or VTEX, headless CMS like Hygraph, search solutions like Algolia and payment providers like Adyen. We build the frontend in Next.js, Frontastic or Vue Storefront, depending on the requirement. In the classic space we are Shopware-certified and have been in production on many projects since Shopware 6, occasionally still with OXID. For merch and D2C projects of manageable complexity we rely on Shopify, which we offer turnkey as a Merch-as-a-Service package. In B2B, options include Akeneo, Algolia or centric as a PIM, because product data is the decisive lever there, often in combination with Xentral as an ERP. Which combination fits your project we decide based on your starting point, your KPIs and your time and budget frame.

→ All partners

That depends heavily on the setup. We launched an MVP shop for Bravobike on commercetools in eight weeks, from kick-off to go-live. A full replatform case with complex ERP integration and multiple language and country shops takes more like 6 to 18 months, depending on how clean the data foundation is and how many stakeholders are involved in decisions. Our experience shows: don't start with the perfect end product, start with a lean MVP that gets measured in the real world and then expand in iterations. That lowers risk, lets you learn faster and avoids the typical big-bang project ruins.

→ Bravobike Case Study · All case studies

Both. Our portfolio ranges from prominent B2C brands like BVB Fanshop, Bergfreunde or gamescom to specialized B2B mid-sized companies like Paul Wiegand, ter Hürne or 1A Medizintechnik. What matters is not corporate status, but how honestly we look at the existing processes together, because that is where many projects fail, and how much change the company allows. We often work particularly intensively with mid-sized companies, because decisions get made faster through shorter hierarchies and the leverage per iteration is usually greater.

→ All case studies

Yes, we do that regularly. For strategic platform decisions, tech stack audits, replatforming assessments or as a second opinion on major investments, we advise even without an implementation contract. At Leifheit we did exactly that, laying the foundation for scalable D2C commerce without writing a single line of code ourselves. For this we developed the Platform Audit, a compact format that specifically clears up individual risks or open questions before you make a roadmap decision worth several hundred thousand euros.

Yes, operations and continuous development are often the more important part. After go-live, most clients continue in a retainer model: a dedicated team, a clearly prioritized backlog and regular reviews. Instead of tackling a big relaunch every few years, we keep developing the shop in step with your business needs. Engbers we have supported this way since 2009 and have delivered three major expansion stages in that time without any rushed migrations.

→ Operations

Composable Commerce and MACH are often used synonymously in the market, but they are technically different. MACH architecture originally stands for Microservices, API-first, Cloud-native and Headless and is the broader approach, defined by the MACH Alliance, of which we are a member. Composable Commerce is one of the core principles of this architecture and specifically describes building from independent, interchangeable services for frontend, backend, search, payment, CMS and order management. Instead of a monolithic shop system, you assemble the best-of-breed building blocks that fit your requirements and can swap or scale them individually. The advantage is maximum flexibility, faster time-to-market for new features and no lock-ins. The downside is higher architectural complexity, more interfaces and a different skill profile in the team. Which architecture we recommend always depends on the specific requirements of your project.

→ Composable Commerce / MACH at Shopmacher

Rarely. For most replatforming projects, the switch can be thought of in stages. Often we first replace the frontend and set it up headless on a modern architecture, while the backend stays in place for now and keeps delivering its data via APIs. At Hirmer we did exactly that: a headless frontend on the existing OXID, with minimal transition risk and immediately noticeable value for the customer. In a second stage, the backend is then modernized or replaced, for example with commercetools. In most cases this step-by-step migration is cheaper, more predictable and lower-risk than a big-bang replatform. Which cuts make sense depends on the state of the existing systems, the data structure and the business priorities.

→ Shop tech decision tree

Three things. First: a direct line instead of several layers of account management. You talk to the developers, architects and project leads who actually build your project, not to intermediaries. Second: KPI discipline. We decide based on your business goals and metrics, not on our current favorite framework or a methodology trend. Third: pragmatism instead of buzzword consulting. We tell you when something is not the right way, even if it costs us a project. Our compact team size allows flat structures and short decision paths, without losing the experience that comes from large projects.

→ About · The people

30 to 45 minutes, free and non-binding, without a PowerPoint battle. You tell us where you stand today, what you want to achieve and which constraints you currently face, whether technical, organizational or budget-related. We assess which platform and which approach best fits your situation, which typical pitfalls we see and whether we are the right partner for your specific task. If we are not, we tell you and, where possible, point you to a sensible alternative. The conversation leads either to a concrete next step with an effort estimate or to the honest realization that this step might still be too early.

→ Get in touch