.svg)
Why do new channels stall in manufacturing?
A manufacturer's ERP is built around the plant. It holds production orders, bills of materials, stock, and the trade price lists used to invoice distributors. The MES (manufacturing execution system) runs the shop floor against it, and the PLM (product lifecycle management) system feeds it product definitions.
Selling direct, or into a new country, asks for things that ERP was never configured to handle. Consumers expect their own prices, single-unit orders, card payments, and delivery in days. New markets add their own currency, VAT rules, language, and often a local carrier or 3PL (third-party logistics provider).
So a request for e-commerce for manufacturers arrives at IT as a request to change the ERP. It joins a queue behind everything the ERP already does for the plant, and nobody wants to risk the system that keeps production running.
Does selling direct mean changing the ERP that runs production?
A direct to consumer (D2C) channel needs data the ERP already holds: products, stock, and prices, plus somewhere to send orders. Only the shape of that data changes, and that difference can be handled between the ERP and the channel rather than inside it.
Many manufacturers take one of two familiar routes. They extend the ERP with consumer customer types, web order types, and extra fields, or they have a developer build a direct connection from the ERP to the webshop. Both work for the first channel, and the people building them usually know the ERP well. But each customisation sits in the ERP's upgrade path, and each direct connection has to be built again for the next channel.
Some manufacturers plan to sort it out in the ERP project instead. Integrations are often what slips in an ERP project, because they get scoped last. Keeping them in their own layer means the new channel does not wait for the ERP project, and the ERP project does not have to carry the channel.
The challenges of adding a marketplace or new country without an integration layer
The first channel takes the most work, and the next one should not mean starting again. But each marketplace or new country brings its own rules. Marketplaces score sellers on accurate stock and on-time dispatch confirmation. Cross-border selling adds currencies, tax rules, translated product content, and local delivery partners.
When every channel has its own direct connection to the ERP, each of those rules ends up in another piece of custom code, maintained by whoever built it. International expansion then becomes a series of projects, each with its own developer time and its own risk to the ERP. The same pattern slows international e-commerce expansion in any business.
E-commerce for manufacturers adds one more problem, which is the plant. Orders arrive from every channel in a different format, so production planning works from several order feeds instead of a single order book. An omnichannel sales operation then turns into a planning problem, unless the channels share one integration layer.
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
