E-commerce engineering, beyond the off-the-shelf ceiling
Zulbera builds custom e-commerce platforms for brands that have hit the wall on Shopify, Magento or WooCommerce — and for B2B and marketplace operators where off-the-shelf was never the answer. Headless storefronts, custom checkout, subscription billing, multi-vendor commerce — built on flexible commerce backends and integrated with the ERP/OMS/PIM you already run.
Six commerce capabilities. One coherent stack.
Shopify Hydrogen, Commerce Layer, Saleor, Medusa — storefront decoupled from the commerce backend so you control UX, performance, and SEO end-to-end.
Quote-to-cash, contract pricing, multi-account hierarchy, PunchOut/cXML integrations with enterprise buyer procurement systems.
Stripe, Adyen, Mollie, Checkout.com. SCA-compliant flows, multi-currency, tax (Stripe Tax, Avalara), local payment methods (iDEAL, SOFORT, Klarna, PayPal).
Recurring billing, dunning, churn-aware retention flows, subscription pause/skip UX, customer portals with self-service plan changes.
Multi-vendor onboarding, split payments (Stripe Connect, Adyen for Platforms), commission engines, KYC for sellers, dispute resolution.
Akeneo, Pimcore for product data. NetSuite, SAP, Dynamics for ERP. Multi-warehouse OMS for omnichannel fulfilment.
E-commerce product shapes we ship
Headless DTC storefronts
Next.js/Astro storefronts on Shopify Hydrogen, Saleor or Medusa with edge-rendered product pages, sub-second navigation, and SEO that ranks at the level your brand actually deserves.
B2B and B2B2C commerce platforms
Quote workflows, contract pricing, approval chains, PunchOut/OCI integration, account-level catalogs. Built for the buyer who logs in, not the visitor who lands.
Subscription products
Recurring billing on Stripe Billing or Recharge, retention-grade dunning, churn-aware customer portals, plan migration, gift-and-share flows.
Multi-vendor marketplaces
Seller onboarding, KYC, payouts via Stripe Connect or Adyen for Platforms, commission engines, dispute resolution, search and discovery that scales to thousands of SKUs per vendor.
Common founder questions
Do you replace Shopify or work on top of it?
Both, depending on what the brand is trying to do. For brands whose storefront is the bottleneck — performance, SEO, brand expression — we build a headless Hydrogen or Next.js storefront on top of Shopify, keeping their fulfilment and admin intact. For brands whose commerce backend is the bottleneck — B2B pricing, complex catalogs, marketplace dynamics — we move them to a flexible backend (Saleor, Medusa, Commerce Layer) and integrate the rest of the stack.
What does a custom e-commerce build cost vs an off-the-shelf SaaS?
Custom builds make sense when off-the-shelf platforms create more friction than they remove. A Shopify Plus store with custom checkout, headless storefront and 5–10 integrations sits in the €60K–€180K range for the engineering layer. A B2B portal on top of a custom commerce backend with PunchOut, contract pricing and ERP integration is €120K–€350K. Marketplaces with multi-vendor onboarding and split payments are €150K–€400K. Off-the-shelf Shopify costs €30K–€80K for a strong launch — go that route unless something specific forces you off it.
How do you handle SCA and 3DS2 in custom checkout?
Default architecture uses Stripe Payment Elements, Adyen Drop-in or Checkout Frames so the SCA challenge is hosted by the PSP, not your application. 3DS2 frictionless flows trigger when the issuer accepts the risk signals; challenges fall back to in-flow modals. We do not build SCA UX from scratch — the PSP teams have shipped through every issuer regression, and recreating it is a poor use of build budget.
How do you handle multi-currency and tax?
For consumer storefronts: Stripe Tax or Avalara for global tax calculation, multi-currency on PSP-native rails (not roll-your-own FX), country-specific payment methods presented based on geolocation. For B2B: tax engines wired into the quote line item layer so quotes are tax-correct from generation, and tax-exempt customers are handled at the account level. Cross-border DDP vs DAP is configured per shipping lane.
How long does an e-commerce build take?
Headless storefront on existing Shopify: 6–12 weeks. Custom B2B portal with 3–5 integrations: 14–22 weeks. Multi-vendor marketplace MVP: 18–28 weeks. Commerce replatforms (off Magento, off WooCommerce) are usually 24–40 weeks depending on data migration scope and number of legacy integrations to preserve.
Can you integrate with our existing ERP / PIM / OMS?
Yes — we have shipped against NetSuite, SAP, Microsoft Dynamics, Akeneo, Pimcore, and a range of warehouse and OMS systems. The integration architecture matters more than the brand: we abstract the integration behind contracts so the e-commerce layer is not coupled to ERP-specific assumptions, which makes future ERP migrations a 3-month project instead of an 18-month one.
Hitting the ceiling on your current commerce stack?
Tell us where the current stack is breaking — performance, B2B workflows, marketplace dynamics, ERP integration — and we will respond within 2 business hours with a technical read.
Request an e-commerce architecture call