Retail and D2C teams
Storefronts where speed is revenue and campaigns do not require a developer on standby.
E-Commerce & PIM
Headless Commerce That Converts
We build high-performance online stores, implement PIM systems, and orchestrate payments, all on modern headless architecture designed to scale your webshop.
Oronts is a Vendure developer and Pimcore agency based in Munich, Germany. We specialize in headless commerce architecture, building decoupled storefronts with React and Next.js that connect to Vendure, Shopify, or custom commerce backends via GraphQL APIs. As an experienced Pimcore partner, we implement Product Information Management systems that centralize product data across all sales channels, from web shops to marketplaces to print catalogs. Our Vendure commerce expertise includes custom plugin development, multi-channel commerce, B2B and B2C storefronts, and complex product configuration. Vendure commerce gives merchants full ownership of their storefront logic with a TypeScript-native, open-source framework. We build and maintain Vendure plugins including the Vendure Data Hub Plugin for data synchronization. On the PIM side, we deploy Pimcore for enterprise product data management, digital asset management, and master data management. We also work with Akeneo PIM for mid-market implementations. Our payment integration covers Stripe, Adyen, Mollie, and PayPal with 3D Secure, subscriptions, and multi-currency support. We integrate search solutions like Algolia and Meilisearch for fast, typo-tolerant product discovery. Every e-commerce project includes performance optimization for Core Web Vitals, SEO-ready server-side rendering, and mobile-first responsive design.
Min $Max $
Rating
Platforms We Work With
Vendure
Shopify
Pimcore
Akeneo
Stripe
Adyen
Mollie
Algolia
Meilisearch
Payload CMS
Contentful
Build engineered commerce when the shop is the smallest part of the problem
A hosted shop is the right call when you sell a catalog of standard products, your pricing is the same for everyone, and a theme plus a few apps covers what you need. Build engineered, headless commerce when the hard part lives around the shop: customer-specific B2B pricing, ERP-driven ordering, one product truth feeding web, marketplace and catalog, a checkout that has to match how your business actually sells. Headless splits the storefront from the commerce engine, so the frontend stays fast and the logic stays yours. The reason most teams move is ownership: you hold the code, the data and the integration depth, instead of renting them inside a platform you cannot leave.
- B2B reality first: customer groups, contract pricing, quotes and ERP-driven ordering, not a consumer cart bent into shape
- One product truth: PIM-backed data feeding web, marketplace and catalog, so the storefront, ERP and listing finally agree
- Headless by design: a decoupled React storefront over your commerce engine, fast to load and free to evolve
- You own the stack: the source code, the plugins and the data stay with you, with a defined exit on day one
The call we usually get
The shop is live but the product data is not: the ERP says one thing, the storefront another, the marketplace listing a third. Or the replatforming has been postponed twice because nobody can say what the checkout customizations actually do. Commerce problems are rarely about the shop; they are about the systems around it.
Built for the desks that run commerce
B2B manufacturers and wholesalers
Price lists, customer-specific catalogs and ERP-driven ordering, engineered for the way B2B actually buys.
Marketplace and multi-channel sellers
One product truth feeding shop, Amazon, Google and the next channel, without triple maintenance.
Which commerce platform fits
We work across four platforms and pick the one that fits your catalog, channels and team. An honest read of where each is strong.
Scroll sideways to see every platform.
| Vendure | Shopify / Hydrogen | Pimcore | commercetools | |
|---|---|---|---|---|
| Open source / self-hostable | ||||
| Hosted SaaS, no infra to run | ||||
| Deep custom business logic | ||||
| Built-in PIM / DAM | ||||
| Fast path to a first D2C launch | ||||
| Enterprise B2B price and order logic | ||||
| Typical fit | Custom B2B and D2C | Fast-launch D2C | Complex catalogs and PIM | Large enterprise scale |
Yes, partial or no describe platform capability as we assess it, not a ranking. The right choice depends on your catalog, channels and team.
Headless Commerce Architecture
A modern, composable stack where each layer can be independently scaled and replaced.
Layer 1
Presentation Layer
Next.jsReactTypeScriptTailwind CSSVercel Edge
Layer 2
Commerce Engine
VendureShopify Storefront APIcommercetoolsGraphQL
Layer 3
Data & Services
PimcoreAkeneoAlgoliaStripeRedisPostgreSQL
Request flow
What Integrations Do We Support?
We connect your commerce platform with the tools your business already uses.
Interactive Demos
See our commerce capabilities in action with live, interactive demonstrations.
Payment Orchestration Demo
Payments Orchestration
USD
Capture delayms
IP
Email
Device
Request
{
"provider": "Stripe",
"flow": "authorize",
"currency": "USD",
"amount": 199,
"idempotencyKey": "demo-authorize-Stripe",
"threeDS": false,
"captureDelayMs": 0,
"signals": {
"ip": "",
"email": "",
"deviceId": ""
}
}Response
Run a flow to see the response…
Product Information Management Demo
PIM Browser
Bulk edit:
| SKU | Name | Category | Attributes | Actions | |
|---|---|---|---|---|---|
| SKU-A1 | Running Shoes | Footwear | brand:Oronts color:Black size:42 material:Mesh | ||
| SKU-B7 | Explorer Backpack | Bags | brand:Oronts color:Olive capacity:25L! material:Nylon | ||
| SKU-C3 | Trail Jacket | Apparel | brand:Oronts color:Cobalt size:M material:Shell |
Demo only. no data persisted.
What headless commerce delivers
The advantages a composable, headless architecture brings to a commerce platform.
Faster storefronts
Faster page loads
99.9%
Uptime SLA target
Edge-fast loads
Page load time
Integration-ready
Integrations ready
Migration & Replatforming
Moving from a legacy monolith to headless commerce with zero downtime and full data integrity.
1
Audit & Discovery
We analyze your current platform, data models, integrations, and traffic patterns.
2
Architecture Design
We design the target headless architecture with a phased migration roadmap.
3
Parallel Build
New headless frontend runs alongside old backend. Traffic shifts progressively.
4
Cutover & Optimize
Full switchover with rollback safety net. Post-launch performance optimization.
Where teams put engineered commerce to work
Concrete situations a headless, owned commerce build is made for, across B2B, B2C and the systems behind the shop.
B2B distributors
A legacy shop holds the catalog hostage, every price change is manual, and the replatforming has been postponed twice because nobody can say what the old checkout actually does.
We replatform onto a headless Vendure build with the business logic written down and owned, so the catalog stays fast and the team ships changes without fearing the cart.
Manufacturers and wholesalers
Every customer sees the same list price, but the real business runs on customer-specific contract pricing and ERP-driven ordering that the shop cannot model.
We implement customer groups, contract prices and quote flows wired to the ERP, so each buyer logs in to their own pricing and ordering rules instead of a consumer cart.
Marketplace and B2B procurement sellers
You need to sell through a marketplace and accept PunchOut and OCI orders from enterprise procurement systems, and the hosted shop has no real answer.
We engineer multi-vendor or PunchOut and OCI flows on the commerce engine, so external procurement systems order straight from your catalog and the data stays in sync.
D2C brands
The brand lives inside a hosted theme and an app stack, and every growth idea hits a platform limit or another monthly fee.
We move the storefront to a headless frontend on a commerce engine you own, so the brand controls its experience, its data and its roadmap instead of renting them.
Multi-channel catalog teams
The ERP says one thing, the storefront another, and the marketplace listing a third, so product data is maintained three times and still disagrees.
We stand up a PIM-driven catalog in Pimcore as the one source of truth, feeding web, marketplace and print from a single governed dataset.
Teams with non-standard checkout
The way you actually sell, configurators, deposits, split shipments, approval steps, does not fit any off-the-shelf checkout.
We build the checkout your business needs on a headless engine, with the custom steps and rules as owned code, tested and yours to extend.
Published on GitHub
Vendure Data Hub
Enterprise ETL and data integration plugin for Vendure. Visual pipeline builder, 9 extractors, 61 transform operators, 24 entity loaders, and feed generators for Google Merchant and Amazon.
TypeScriptNestJSVendureDocker
GitHubPimcore Asset Pilot Bundle
Rule-based digital asset organization for Pimcore: configurable rules, priority ordering and audit logging for libraries that grow faster than teams can sort them.
PHPSymfonyPimcoreGitHub Actions
GitHubBuilt to clear your procurement and security review
The questions your buying committee, legal and data-protection teams ask before a commerce platform decision, answered in advance.
- Code ownership
- You own the storefront and platform source code, the plugins and the integration logic. No proprietary runtime holds your business rules where you cannot reach them.
- Your cloud
- The platform runs in your cloud or on-premises environment. Hosting and data residency follow your tenancy, with EU hosting available.
- Data and AVV
- Auftragsverarbeitungsvertrag in place where required, with GDPR-aligned handling of customer and order data, deletion paths and documented processing.
- Owned plugins
- Custom commerce plugins and connectors are delivered as your source, on open-source foundations like Vendure and Pimcore, not licensed black boxes you rent per month.
- Support
- Maintenance, updates and an SLA target are agreed in writing. We are the engineering partner behind the platform, not a reseller of someone else's product.
- Exit
- Defined handover: code, infrastructure-as-code, documentation and runbooks transfer to your team, so you can operate the commerce platform or move it without us.
When we are not the right choice
- Template-shop setups a freelancer serves better; we engineer platforms around commerce, not theme installs
- Pure media buying or shop marketing; we are the engineering side of revenue
- Replatforming for its own sake; if your current stack carries the roadmap, we say so
Engagement levels
Oronts works with serious teams that need senior delivery, not low-cost outsourcing.
- Production Pilot
- from 25k EUR
- Custom software and AI projects
- from 50k EUR
- Ongoing technical retainers
- from 15k EUR/month
Exact pricing depends on scope, responsibility, delivery speed, team size, integrations, support expectations and production risk.
Frequently Asked Questions
Headless commerce separates the frontend (what customers see) from the backend (commerce logic, inventory, orders). This architecture gives you complete design freedom, faster page loads, and the ability to sell across any channel from a single backend. In a traditional monolith like Magento or WooCommerce, the frontend and backend are tightly coupled, meaning design changes often require backend work and vice versa. With headless, your React or Next.js storefront communicates with the commerce engine through APIs, so your frontend team and backend team can ship independently. For instance, you can redesign your entire checkout experience without touching inventory logic. This also means you can serve the same product catalog to a website, mobile application, in-store kiosk, or IoT device without duplicating commerce logic. The trade-off is higher upfront complexity, but for businesses planning to scale across channels, the long-term flexibility pays for itself within the first year.
The right platform depends on your catalog complexity, team size, and growth trajectory. We recommend Vendure for custom B2B or B2C stores where you need full control over business logic, because it is open-source, TypeScript-native, and gives you complete ownership of the codebase. Shopify with Hydrogen works well for direct-to-consumer brands that want to launch quickly with a proven ecosystem of apps and payment processing. Pimcore is the right choice when complex product data management is your primary challenge, for instance if you have thousands of SKUs with detailed specifications across multiple sales channels. For large enterprises processing high transaction volumes across multiple regions, commercetools offers the scalability and composability needed at that level. During our discovery phase, we evaluate your catalog size, expected traffic, integration requirements, and team capabilities before making a recommendation, and we tell you honestly which one fits.
A focused MVP storefront with core product listing, cart, and checkout can launch in 8-12 weeks. This gives you a working store that you can start testing with real customers while we build out the rest. Full platform migrations that include PIM integration, ERP connections, multi-currency support, and multiple sales channels typically run 3-6 months. The timeline depends heavily on the number of integrations and how much product data migration is involved. For instance, connecting a Pimcore PIM with 10,000 products to a new Vendure storefront takes more data mapping work than a fresh catalog with 500 items. We use phased rollouts in every project, so you see working software in production within the first month. This approach also reduces risk, because each phase is validated with real traffic before the next phase begins.
Yes, zero-downtime migration is our standard approach. We run the new headless frontend alongside your existing platform, progressively shifting traffic using feature flags or DNS-based routing. During the transition, both systems share the same product data and order pipeline, so customers experience no disruption regardless of which system serves their request. The old platform stays live as a fallback until the new system is fully validated with real production traffic. We typically start by routing 5-10% of traffic to the new storefront, monitor conversion rates and error logs closely, then increase gradually over 2-4 weeks. If any issues surface, we can instantly route all traffic back to the original system. Product data, customer accounts, and order history are synchronized continuously during the migration window. This parallel approach does require running both systems temporarily, but it eliminates the risk of a 'big bang' cutover where you discover problems only after the switch.
PIM (Product Information Management) is a system that centralizes all your product data, including descriptions, images, technical specs, pricing, and translations, in one place. Instead of maintaining product information in spreadsheets, your webshop backend, and your marketplace listings separately, PIM becomes the single source of truth that feeds all channels automatically. You likely need PIM if you sell across multiple channels (webshop, Amazon, retail partners), manage more than 1,000 SKUs, or maintain product data in multiple languages. For instance, a company selling industrial equipment with detailed technical specifications across five European markets spends hours updating each channel manually without PIM. With Pimcore or Akeneo, changes made once propagate everywhere within minutes. If you have a small catalog sold through a single channel, PIM adds unnecessary complexity. We help you evaluate whether PIM fits your situation during our discovery process.
Yes, we offer SLA-backed support packages tailored to your needs. Every package includes infrastructure monitoring with automated alerting, performance optimization reviews, security patches for dependencies and frameworks, and continued feature development. Most engagements start with a 3-month stabilization period immediately after launch, during which we monitor error rates, page speed, and conversion metrics more closely and resolve issues with priority response times. After stabilization, support transitions to a monthly retainer model that covers a set number of development hours, on-call incident response, and regular check-ins. For instance, a typical e-commerce build uses its monthly retainer hours for seasonal promotions, A/B test implementations, and payment provider updates. We also provide thorough documentation and knowledge transfer sessions, so if your team prefers to handle maintenance in-house after launch, they have everything they need to do so confidently.
We are Pimcore developers and Vendure specialists based in Munich, Germany, working across both platforms and contributing open-source plugins and bundles. On the Pimcore side, we build custom bundles for asset management, data import workflows, and integration with external systems, including our open-source Pimcore Asset Pilot Bundle. For Vendure, we develop custom plugins covering ETL data pipelines, inventory synchronization, and multi-channel product feeds, including our open-source Vendure Data Hub Plugin. We participate actively in both communities, contribute bug fixes and documentation, and stay current with each platform's release cycle. This hands-on involvement means we understand not just the APIs, but the architectural decisions and trade-offs behind each framework.
Yes, custom plugin and bundle development is one of our core strengths. We build Pimcore bundles using Symfony and Vendure plugins in TypeScript, both following the official extension patterns of their respective platforms. Our Pimcore Asset Pilot Bundle handles rule-based asset organization with configurable rules, priority ordering, and audit logging. Our Vendure Data Hub Plugin provides enterprise ETL pipelines for product imports, inventory sync, and feed generation. Beyond our own plugins, we regularly extend existing community plugins and integrate them with third-party systems like ERPs, payment gateways, and marketing platforms. For instance, we have built Vendure plugins that connect order data to warehouse management systems via webhooks, and Pimcore bundles that synchronize product data with marketplace APIs. Every plugin we build includes automated tests, documentation, and versioned releases so your team can maintain it independently.
Vendure commerce is built on TypeScript and Node.js, which makes it a natural fit for teams already working with modern JavaScript tooling. Your frontend and backend engineers share the same language, reducing context switching and speeding up development. The plugin system is genuinely flexible, allowing you to override or extend any part of the order flow, product catalog, or payment processing without forking the core. The GraphQL API is well-designed with strong typing, making frontend integration straightforward. Unlike hosted SaaS platforms like Shopify, Vendure gives you full source code access and the freedom to self-host on any infrastructure. There is no per-transaction fee, no vendor lock-in, and no feature gating behind enterprise tiers. The trade-off is that you need engineering capacity to run and maintain it, but for teams that already manage their own infrastructure, Vendure offers more control at a lower total cost of ownership over time.
Ready to Build Your Commerce Platform?
Let's discuss your commerce goals and find the right architecture for your business.