E-commerce when your systems have to keep up with the market
Migration, headless, API-first: 15+ years in e-commerce projects. Our teams work in delivery—when you scale or modernize—not just on architecture slides.
Where we start
Where we start
-
01
Bottlenecks first
What's slowing growth now—not a technology laundry list.
-
02
Parallel running
Migrate without downtime. The shop keeps running.
-
03
Bring the team along
Together we set the direction—and scale with your team, not around it.
-
04
Scale & integration
Headless, API-first, cloud—so infrastructure and the market aren't fighting each other.
Architectures we build in commerce projects
Modern architecture is the goal—often with commercetools at the core when it fits. The logo matters less than flexibility you can grow on.
Scalable
The architecture stays movable when business and traffic climb.
Faster to change
If the old stack was slow to touch, a modern base shortens the path from request to release—and makes market response realistic again.
Integration
Open APIs: connect partners and systems without ripping open the platform every time.
Room to evolve
Stay free of outdated lock-in—and adopt new tech where it actually helps.
Principles in client projects
- MACH architecture
- Headless commerce
- API-first
- Cloud native
- Modularity and microservices
- Built for internationalisation
- Buy before build
Partners and technologies
Long-standing partner
Open-source systems we use
Which system fits when?
| Criterion | Oscar (open source) | Saleor (headless) | commercetools (API-first) |
|---|---|---|---|
| Logo | |
|
|
| Technology stack | Python, Django | Django, GraphQL | API-first, cloud-native |
| Cost model | Open source, low entry, ongoing engineering | Free community edition, optional enterprise support | Premium licence, higher entry, broad enterprise features |
| Scalability | Strong fit for mid-sized work | High via microservices | Enterprise scale |
| Headless | Optional via APIs | Native via GraphQL | Fully API-first |
| Revenue | From ~€500k/year | From ~€1m/year | From ~€15m/year |
| Traffic | Up to ~100k visits/month | Up to ~500k+ visits/month | From ~500k visits/month |
| Catalogue size | From ~100 SKUs | From ~500 SKUs | 1,000+ SKUs with complex variants |
| Best fit for | Specialised B2B or highly custom needs | Growing brands with omnichannel | Large international setups with high traffic and complexity |
Not sure which setup will hold?
More from the field
See references for a cross-section of what we’ve shipped—APIs, marketplaces, B2B portals, and more. For new products and SaaS/cloud work: From idea to product and On-premise to SaaS & cloud.
What usually gets in the way when e-commerce needs to scale
When growth depends on the system landscape, every week counts. These patterns show up again and again.
Systems can’t keep up with growth
Outdated and inflexible—and that’s exactly when the stack blocks the next level.
Migration without shutting down
Moving a live shop without taking it offline takes experience, not just a target architecture.
Infrastructure falls behind
Demand and traffic grow. The platform has to carry that—or tech becomes the brake.
New architecture, old constraints
Headless and API-first often matter most once scale and channels get serious.
Manual processes eat capacity
What can be automated should be—otherwise there’s little room left for real product work.
What changes in practice
15+ years modernizing and scaling digital commerce—focused on what actually moves delivery and the market.
| Starting point | Direction | |
|---|---|---|
| Rigid e-commerce platform | Architecture that can keep up with channels and growth | |
| Accumulated legacy systems | Cloud- and API-ready foundation instead of constant firefighting | |
| Slow time-to-market | Shorter path from request to release | |
| Hard-to-connect systems | Open integration for partners and services | |
| Manual, error-prone workflows | Automation where it takes load off operations |