Omnichannel platform architecture: the complete guide

Most businesses did not plan to become omnichannel. They added an online store, then a marketplace listing, then a B2B ordering portal, then click and collect, each with its own system and its own integrations. The result is familiar: stock that shows as available online but is not on the shelf, prices that differ between channels, orders re-keyed by hand and customers who are recognised in one channel and strangers in the next.

Omnichannel platform architecture is the design of systems and integrations that lets every channel share the same products, prices, stock, orders and customer information. This guide covers how to map what you have, choose the centre of the architecture, connect each channel and plan a rollout that does not disrupt trading.

Map your channels and flows

Start by drawing the current picture. List every channel, the system behind it and how products, prices, stock, orders, customers and payments move between systems. Note where data is re-keyed, where it is copied overnight and where it is maintained separately. This map nearly always reveals more manual work and more duplicate data than leaders expect.

• Which system is the master for products, prices, stock, orders and customers?
• How often is stock updated in each channel, and how is it reserved when an order is placed?
• Where are orders re-keyed or exported manually?
• How are returns handled when a customer buys in one channel and returns in another?
• Which integrations are custom, undocumented or reliant on one person’s knowledge?

Add the pain points from the people who live with them: store staff, customer service, warehouse teams and finance. Their examples, such as the number of cancelled online orders for out-of-stock items, help set priorities and build the business case.

Use the map to agree the target picture: which system will be the master for each type of data, which integrations will be replaced and which channels will be added in the next two years. Keep the target simple enough that a non-technical leader can understand it on one page. That page becomes the reference for every platform and integration decision that follows.

Design the architecture around one back office

For most mid-sized businesses, one back office, usually the enterprise resource planning (ERP) or commerce management system, is the right centre. It holds the master records for products, prices, stock and financial transactions. Each channel connects to it rather than to every other channel, which keeps the number of integrations manageable and gives one source of truth.

Larger or faster-moving businesses may add an order management layer that routes orders across warehouses and stores, or a product information system for rich content. Add these when the volume or complexity justifies them, not by default. Each extra system brings integration, licence and support costs.

Choose the platform

Platform choice should follow the architecture, not drive it. Shortlist options that support your must-have processes, such as customer-specific pricing, click and collect or multiple currencies, and that have proven connectors to your back office. Ask for references from businesses of similar size and complexity, and speak to them about integration effort and support after go-live, not only about features.

One stock number: the heart of omnichannel

If customers cannot trust the availability you show them, nothing else matters. One stock number means keeping stock in one place, updating it quickly when goods are received, sold, moved or returned, and showing availability honestly in every channel.

1. Keep stock in one place: the back office holds the definitive figure for each location.
2. Update quickly: sales, receipts and transfers flow through within minutes, not overnight.
3. Reserve stock when an order is placed, so two channels cannot sell the last unit.
4. Hold a small buffer for fast-moving items where accuracy is uncertain.
5. Show availability honestly: ‘low stock’ or a realistic delivery date beats a cancelled order.

Real-time stock needs discipline as well as integration. If store teams do not record transfers, damages and returns promptly, the fastest integration in the world will still show the wrong number. Train teams, make recording easy and measure stock accuracy regularly.

Connect your channels

Ecommerce platform

When choosing an ecommerce platform, list the must-haves for your customers and operations, check that proven integrations with your back office exist and estimate total cost over five years, including licences, hosting, apps, development and support. A cheaper platform that needs heavy custom integration often costs more in the end.

Marketplaces

Marketplaces offer reach and established customer traffic but add fees, strict service rules and limited access to customer data. Your own store gives control and the customer relationship but requires you to attract visitors. Many businesses use both: marketplaces for reach and certain products, their own store for the full range and repeat customers. Connect marketplaces to the same stock and order flows, and price with fees in mind.

B2B portals

Trade customers want to order the way they choose: online, at any hour, with their own prices and terms. A good B2B portal shows customer-specific prices, makes reordering easy with saved lists and order history, and integrates fully with the back office so orders arrive without re-keying.

Point of sale

Linking point of sale with online gives one customer view. Identify customers at the till with their consent, share purchase history across channels so staff can help with online orders and returns, and respect marketing preferences wherever the customer appears.

Plan the rollout

Change the architecture in stages, protecting trading at every step. A typical sequence is to clean product and stock data first, connect the back office and main online store, then add marketplaces, B2B and point of sale integration. Avoid major cut-overs during peak trading periods, run old and new systems side by side where risk is high and test with real orders, returns and edge cases before each go-live.

Plan the people side as carefully as the technology. Store teams, customer service and warehouse staff need training on new processes, such as reserving stock for online orders or handling cross-channel returns. Give them clear guidance before go-live and a simple way to report problems in the first weeks.

Build integrations to be reused. Standard interfaces for products, stock, orders and customers mean each new channel connects to the same services rather than requiring new custom work. Over time this is what makes launching a new channel a matter of weeks rather than months.

What you will achieve

A well-designed omnichannel architecture gives you one stock number customers can trust, far fewer manual orders and re-keying errors, faster launch of new channels and a better customer experience, with consistent prices and service wherever people choose to buy. It also gives leaders a single view of sales and stock across the business, which improves buying, replenishment and planning.

A sensible first step is the channel and flow map described above. It takes a few weeks, costs little and usually makes the priorities obvious.

Source: Intelliversal analysis, drawing on the briefings in this series.

Frequently asked questions

Do we need a new ERP to become omnichannel?

Not always. Many existing back-office systems can serve as the centre with better integration and data discipline. Replace them only if they cannot support the volumes, speed or processes you need.

How real-time does stock need to be?

For most businesses, updates within a few minutes are enough, with reservation at the point of order. Fast-moving or limited-stock items may need near-instant updates.

Should we sell on marketplaces?

If your customers shop there and the margins work after fees, marketplaces can add valuable reach. Start with a focused range and connect them to your main stock and order flows.

Explore Omnichannel platform architecture