Case Study · Modernisation
A global B2B marketplace moved to a new e-commerce and ERP platform without stopping trade
A global wellness and personal care marketplace sells to distributors and business buyers from warehouses in Germany, Singapore and New Zealand. AMT built its new multilingual B2B e-commerce and ERP platform and migrated the live business onto it in phases over about six months. Fulfilment got 28% faster and customer retention rose 34%.
Schedule Technical DiscoveryYour first conversation will be with a senior technical partner, not a salesperson.
Published
At a glance
- Client
- Globally recognised wellness and personal care platform connecting manufacturers, suppliers and brands with distributors and business buyers
- Warehouses
- Germany, Singapore, New Zealand
- What AMT built
- Multilingual, multi-currency B2B e-commerce platform with ERP modules and custom ERP middleware
- Migration
- Phased, about six months, business kept trading throughout
- Scale
- 200,000+ SKUs across 12 wellness categories
- Results
- 28% shorter average fulfilment time, 34% higher customer retention, 8 languages and 30+ countries within 12 months of launch
- Stack
- React, Node.js, Express, MongoDB, Redis, Elasticsearch, Docker, Kubernetes, Jenkins, AWS
The short version
As the client's buyer and supplier network grew, the old setup could not keep up: no single multilingual storefront, poor stock visibility across three warehouses, and manual order handling for complex B2B deals. AMT built a new platform with tiered B2B pricing, drop shipment, multi-warehouse inventory sync and ERP modules for content, orders, products and stock. Then AMT moved the business across one stage at a time, warehouse by warehouse and market by market, instead of one risky cutover.
The challenge
- No central multilingual platform with localised content and currency
- Limited stock visibility across warehouses in Germany, Singapore and New Zealand, causing delays and stockouts
- Complex B2B needs: bulk orders, minimum order quantities, tiered pricing, drop shipments
- Manual order processing slowing fulfilment
- Weak links between product, inventory, content and order systems
- Growing complexity as product volume and reach expanded
And one hard constraint: the business could not stop serving customers while the platform changed.
What AMT built
Multilingual, multi-currency commerce
Localised content and currency by region, so buyers in each market purchase in a familiar environment.
Global inventory and fulfilment
Inventory integrated across the three fulfilment centres, with central stock visibility and regional order allocation.
B2B commerce
Business buyers get the purchasing models they expect:
- Tiered pricing
- Minimum order quantities
- Volume discounts
- Customer-specific access
- Bulk ordering
- Account-based purchasing with approval workflows
Drop shipment
Selected suppliers ship directly to customers. Automated routing, supplier API integrations and notifications reduce manual work.
ERP-enabled modules
- Content management: product pages, articles, regulatory information and regional content
- Order management: tracking, bulk orders, approval workflows, fulfilment status
- Product management: hierarchical categories, variants, attributes, catalogue
- Stock management: sync across warehouses, stock levels, replenishment triggers
- Drop shipment management: supplier routing and notifications through APIs
Search
Elasticsearch powers faceted product discovery across 200,000+ SKUs.
The phased migration
AMT did not do a single big-bang cutover. Over about six months, the move happened in six stages:
- Platform and data preparation. Catalogue, customer, pricing and operational data structures were prepared and mapped to the new platform.
- Catalogue and content migration. Product information and multilingual content moved across progressively and were validated as they went.
- ERP and inventory integration. Stock and fulfilment integrations went live warehouse by warehouse: Germany, Singapore, New Zealand.
- Order and B2B workflow migration. Orders, pricing, accounts and drop shipment moved in controlled phases.
- Regional rollout. Markets and customer groups switched over incrementally.
- Final transition. After operational and data validation, the remaining workload moved to the new platform.
Throughout, existing ordering and fulfilment stayed available. Each stage was validated before the next one started.
Results
| Measure | Result |
|---|---|
| Catalogue size | 200,000+ SKUs across 12 wellness categories |
| Average order fulfilment time | Down 28%, through multi-warehouse sync |
| Customer retention | Up 34%, supported by B2B personalisation |
| Reach within 12 months of launch | 8 languages, 30+ countries |
| Inventory | Real-time visibility across global fulfilment locations |
| Migration | Completed in phases while the business kept trading |
Technology stack
| Layer | Technology |
|---|---|
| Front end | ReactJS, HTML5, Tailwind |
| Back end | Node.js, Express |
| Database | MongoDB |
| Caching | Redis |
| Search | Elasticsearch |
| DevOps | Docker, Kubernetes, Jenkins |
| Cloud | AWS Elastic Beanstalk, S3, CloudFront |
| ERP integration | Custom middleware for order, stock and content sync |
Before you plan a migration like this
- What can never go offline? List it. That list sets the order of your phases.
- Can you split by warehouse or region? Natural boundaries let you move one piece, check it, then move the next.
- How will you prove each stage worked? Agree validation checks before you move anything.
- Where does data live during the overlap? Running old and new side by side needs a clear source of truth for each record.