- Agency · white label
- Magento 2
- Headless
- TYPO3
- B2B
- ERP integration
Headless B2B commerce on Magento 2 inside an existing TYPO3 website
An industrial manufacturer's buyers researched products on the website but ordered by email and phone. We added customer-specific pricing, cart, checkout and quote requests with headless Magento 2, without rebuilding the TYPO3 site or touching its SEO.

Project
- Delivered for
- German digital agency, white label
- Client
- US division of a German industrial manufacturer of precision connectors
- Platform
- Magento 2 (headless) inside TYPO3
- Systems
- ERP and PIM via XML over FTP, ~5,000 SKUs
- Timeline
- 5 months
- Markets
- US · EN / ES / FR
Results
- less manual work on orders
- 40–80%
- fewer order errors
- 20–40%
- more large orders
- 20–50%
- SEO impact on the existing site
- Zero
About the client
The client is the US division of a family-owned industrial manufacturer, founded in 1960 and headquartered in Germany, with around 2,000 employees and 45 sales representatives on five continents. It makes high-precision connectors and electrical components for automation, robotics, medical technology and electronics, built to industrial standards such as IP67 and certified to ISO 9001 and ISO 14001.
Its buyers are engineers, procurement specialists, OEMs and distributors who need detailed technical data, configuration options and often custom solutions. The website is the main digital channel, with 108,000+ monthly visitors, and years of SEO and content work made its stability and URL structure a business asset.
The challenge
The TYPO3 website worked well for content and product discovery, but it had no B2B commerce: no customer pricing, stock, cart, checkout or quotes. Customers found products online and then ordered by email or phone. A full rebuild was ruled out: too costly, too slow and too risky for SEO, and the ERP and PIM only exchanged files, not APIs.
01
B2B commerce without a rebuild
- Checkout and cart
- Account management
- Quote requests
Goal: Add full B2B commerce without breaking the existing website.
02
Customer pricing without a new UX
- Customer-specific and tier pricing
- A cart embedded in the current pages
Goal: Prove Magento can work as a commerce layer behind the existing CMS.
03
Manual data that didn't scale
- Catalog updated by hand
- Stock availability out of date
Goal: A reliable, automated catalog, stock and checkout.
04
Large orders left the funnel
- Buyers abandoned the cart and sent an email
- Sales answered manually
Goal: Keep large orders online with a quote-based flow.
05
English only
- Lower usability and conversion for non-English buyers
Goal: English, Spanish and French without changing the architecture.
How it fits together
TYPO3 stays the website; Magento 2 runs as the commerce engine behind it. Customers stay on one site with one login, while each system does what it does best.
TYPO3 keeps
- Pages and content
- SEO and URL structure
- Design and UX
Magento 2 adds
- Customer pricing
- Cart, checkout and accounts
- Stock and quotes
ERP and PIM feed
- Daily catalog sync, ~5,000 SKUs
- Stock updates every 30 minutes
- XML files over FTP
What we did
01
Headless Magento next to TYPO3
- TYPO3 kept as the main site, Magento on a subdomain
- Shared login through cookies and one consistent UI
- Magento pages kept out of search indexing
Result: Commerce added with no risk to SEO.
02
Proof of concept first
- Magento with sample products and tier pricing
- A script in TYPO3 pages calls the Magento API
- Personalized price and add-to-cart on existing product pages
Result: The approach was validated before any full build.
03
Data sync and B2B checkout
- Daily catalog sync, stock every 30 minutes, real-time API for prices
- UPS and FedEx shipping; card, PayPal and purchase-order payments
- Search with weighting, synonyms and typo tolerance
04
Cart to quote
- Orders above 249 units turn the cart into a quote request
Result: Large orders stay online instead of moving to email.
05
Three languages
- English, Spanish and French with the same flows
Team, timeline and stack
Delivered in 5 months by
- Full-stack engineer
- 1
- QA engineer
- 0.5
- Project manager / analyst
- 0.5
Technology
- Magento 2
- TYPO3
- Elasticsearch
- AWS
- Docker
- Cloudflare
- New Relic
- Sentry
- XML importers (FTP)
- ShipperHQ
Commerce without a rebuild
The client gained B2B e-commerce while the website, its content and its search rankings stayed as they were, with 4,500+ daily users and no downtime at launch. And the design keeps the site safe: even if the commerce layer is down, the website still works.
Need something similar? Let's discuss.
Tell us what you want to build, and for whom. If we're a fit, you get a clear next step. If not, we'll tell you.
- Reply within one business day
- Fixed estimate before we start
- No commitment