Online store development —
connected to your ERP.

The platform matters less than people tend to assume. What matters is what happens behind the store: where the products come from, where the orders go, and which system holds the customer records.

Shopware fits when the store is the central sales tool and needs logic of its own — different prices per customer group, particular ordering workflows, product presentations built for the range.

Shopify fits when the business needs to start quickly and the effort of running the platform should stay small. ERP integration is possible here too; we built it for Juwelier Bockholt.

WooCommerce fits when the store is part of an existing WordPress website and should not sit beside it.

Ecwid fits small ranges that are embedded into a page that already exists.

Which one is right can be settled in a conversation. We will recommend a platform even when we do not run it ourselves.

Swiss stores have requirements that a standard installation does not anticipate: price display under Swiss law, VAT rates, shipping zones, payment methods such as TWINT, and customs handling where goods cross the border.

Then there is working in more than one language. German and French in one store means more than translated text: separate maintenance of the range, its own addresses per language, and clean markup so that search engines can tell the versions apart.

We settle these points before the platform decision, not after it.

Every store project we have delivered had a leading system behind it. That is the part we have specialised in.

In business-to-business trade there is more to it, and it is what separates a B2B store from a consumer one: customer-specific prices and discounts, ordering on account, approval steps inside the customer’s own organisation, reordering from the order history, and minimum quantities or pack sizes.

Almost none of this lives in the store. It lives in the ERP — and that is where it is decided whether a B2B store works.

What we connect: SAP, Odoo, Business Central, Abacus, Clarity and Avista. Through n8n, Alumio or an interface of our own. How that looks in detail is on the page interfaces between store and ERP. What such a connection costs, you can work out for yourself with the integration check.

One more thing applies in business-to-business: most of the companies that visit your store do not order on the first visit. Which companies they are can be identified — how that works, and what data protection law requires, is on the page visitor identification.

Online store with SAP integration for Held AG · Shopify connected to the ERP at Juwelier Bockholt · Shopware connected to Avista for Spyk Bänder AG

Three tasks come up in almost every store project, and for all three the standard is not enough:

Pricing logic of your own. Volume tiers, customer groups, promotional periods, prices that come from the ERP and should stay maintained there.

Particular ordering processes. Configurable products, orders that need approval, call-off orders over a longer period.

Inventory integration. Stock levels, delivery times and availability at the pace the business needs — not at the pace the interface happens to allow.

Part of our work begins before the product range: a first web presence for a new business, a digital presence from a single source, from the domain to the brand, the replacement of an existing corporate website. Sometimes the goal is narrower — a landing page for a specialist webinar, with exactly one purpose. And sometimes the best solution is that we make ourselves unnecessary: an SEO workshop that enables a team rather than binding it. (These case studies are in German.)