Yamaha was moving the business onto SAP S/4HANA. The UK direct-to-consumer channel was running on a legacy ecommerce platform that was not ready to move with it. Working with Yamaha’s leadership, we settled how the two should work together, then built the middleware that makes it run. Without losing a day of trading.
Yamaha was moving the business forward onto SAP S/4HANA, aligned to the global directive.
The UK direct-to-consumer channel sat outside it. Ecommerce ran on a legacy platform, and it was not ready to migrate on the same timetable. Replacing it was a separate decision on a separate schedule, and the D2C operation had to keep trading in the meantime. The two systems had no way of talking to each other in anything close to real time.
That is a common position. When a group standardises its ERP, the local ecommerce estate may not move at the same speed. The new system and the older storefront end up having to work together for longer than planned.
Stock on the website updated once a day, in the early hours of the morning. By the evening, the peak online shopping window, the inventory shown to customers could be up to 24 hours out of date. Customers were regularly ordering products that had already sold out, triggering the cancellations and back-order emails that erode a brand.
Orders ran on the same 24-hour file, and that was the lesser problem. The order file could be pushed manually when something needed to move sooner, so the team had a way to work around it. Stock had no such workaround. A product page showing yesterday’s availability at eight in the evening is simply wrong, and the customer would only find this out after they have paid.
This is what we call the operational middle: the layer where the ERP and the storefront meet. Stock, orders, returns, customer data: all of it has to move cleanly across that layer, in something close to real time, or the customer feels it.
The middle is where ERP programmes and ecommerce platforms come apart. The ERP moves on the group’s timetable. The storefront moves on the channel’s. When those two timetables differ, and they usually do, something has to hold the systems together in the gap. It is not a problem you can market your way out of: more demand arrives on the same unreliable plumbing. It is not usually solved by forcing the storefront to migrate before the business is ready either. It is making the systems you already run talk to each other properly, for as long as you need them to. That is where Voodoo came in.
We began in a consultancy capacity, working closely with senior stakeholders across ecommerce, IT, operations and finance. The first job was to map the entire ecommerce estate: order-lifecycle processes, product information management, customer data flows, payment and fulfilment integrations, reporting and compliance requirements, and every dependency between SAP and the ecommerce platform.
That discovery work surfaced the technical risks, operational bottlenecks and edge cases up front. So the integration would do more than hold the business together structurally. It would improve how the D2C operation ran day to day.
The most important outputs were not technical. They were operating decisions, made with Yamaha’s leadership before anything was built: how a part-stocked order should be handled, which stock belongs to trade partners and can never be sold to consumers, who owns a return as it moves between systems. Once those were settled, the build had something solid to implement.
With discovery complete, the project moved into delivery. Our development team worked alongside Yamaha’s existing development partners and their enterprise SAP partner, who owned the wider enterprise SAP workstreams. Together we documented and rationalised the existing processes, defined future-state workflows aligned to the European operating model, established data governance and validation rules, and scoped the custom APIs needed to move data cleanly between systems.
The build centred on a middleware layer, the Voodoo Connector, which sits between SAP and the ecommerce platform rather than forcing one system to conform to the other, or forcing the legacy platform to migrate before the business was ready. It interfaces with both through their APIs and applies a customised set of business rules before any data moves. Those rules carry the operating decisions from discovery, the edge cases off-the-shelf connectors would miss:
For a D2C brand, where customer trust depends on accurate stock and fast fulfilment, that customisation layer is the difference between an integration that works and one that costs money.
The final phase was execution without disruption. We remapped and cleansed product data to fit SAP’s structured format, aligned stock locations, storage locations, logistics and order-status workflows, deployed the Connector, and ran end-to-end transactional testing from browse to order to fulfilment. Security validation, compliance checks and peak-load performance testing all happened before go-live.
We delivered on the planned go-live date. Order and stock workflows were monitored closely for the first three days, and from day four the operation ran on a fully automated workflow, with no fall-out and no roll-back required. Downtime was minimal, the customer experience was uninterrupted, and the trading team carried on as normal throughout: go-live changed the systems, not the jobs.
The programme ran as a strategic partnership first and an integration second: de-risking decisions as they were made, and keeping business objectives and technology execution aligned throughout. Working with internal and external teams across the UK and Germany, that is what delivered:
The work here is the combination: strategic consultancy that settles how the operation should run, then deep technical delivery that makes it run that way. The integration layer itself has since been developed into a flexible tool we offer as Legacy Logic Integration: connecting the systems a business already runs, whichever side of the estate is moving, without forcing either one to be replaced.
If you are planning a D2C launch, re-platforming ecommerce, or trying to keep a direct channel trading through an ERP programme, the transformation has to deliver commercial value, not technical change alone.
Yamaha
Ecommerce & Technology
England
Author bio:
Peter Nicholls is the founder of Voodoo, the D2C implementation partner for FMCG and manufacturing brands. Over 25 years he has helped established businesses sell direct alongside the trade relationships that grew their business, working with global names including Yamaha, JDE and Pladis. For Yamaha, Voodoo took Yamaha Europe’s home audio channel to the most followed in the entire global group. For JDE, they untangled a social presence spread across thirty countries into a single coherent global framework. Peter and Voodoo work in what he calls the messy middle: the gap between boardroom strategy and the warehouse floor, where many D2C projects stall.
