A business may have four sales channels, each serving a different product group, customer and vocabulary. The difficulty begins when the work behind those channels is also repeated four times.
That was the starting point here. Product information, technical documents and orders were managed channel by channel. A product change had to be repeated, and the current version of a document could become unclear.
The real need was not another website
What looked like four separate web projects was a data and operations problem. Separate management panels might have been easy in the short term, but they would have required the same product information and documents to be entered repeatedly for years. More channels would have meant more repeated work.
We focused on the shared operation behind the visible sites.
The system decision
We built a central backbone for product, category, technical-document and order information. Each channel drew from this source while retaining its own product presentation and language for its audience.
- Product information prepared centrally was distributed to the relevant channels.
- One current version of each technical document was maintained.
- Orders from the channels came into a common operational view.
- Adding a channel did not require rebuilding the entire system.
What changed over 22 years?
Interfaces, screen sizes, user habits and publishing technologies changed. Product groups expanded. The underlying need stayed the same: show the right product with the right technical information in the right channel, then bring the order reliably to the center.
The system lasted because the parts that could change were separated from the operational core. The four channels have used this shared structure for more than 22 years, with periodic renewals.
The client and channel names are withheld. The case study draws on the original project record, the four-channel scope, its use period and later renewals; it makes no revenue or customer-list claim.
Who may need a similar structure?
- Manufacturers running several brand or product sites
- Wholesalers serving different customer groups with separate catalogues
- Companies with technical-document-heavy products
- Businesses opening new sales channels without rebuilding product data
Engin Sistem starts by identifying which data is shared and which rules are channel-specific. We then build a system that works today and can be adapted to another channel later. Product-data ownership, order stages, document updates and future renewal all matter alongside publication.
Common questions
Must every sales channel look the same? No. Product data and operations can be shared while each channel keeps its own language, design, pricing structure and audience.
Does this require replacing every existing site? Not always. We first review the current data sources and channels. Where appropriate, a shared layer can be added behind them and connected in stages.
Why can the structure last? It separates interfaces from operational rules. Design and technology can change while the product, order and document flows are maintained and improved.