"Omnichannel" has become a word people use to mean different things. For this site, the working definition is simple: every channel you sell through draws on the same stock, feeds the same order flow and writes to the same customer record, so the business behaves as one operation regardless of where the sale happened. The definition matters because the destination shapes the journey. If you know what connected means, you can measure how far away you are.

What connected actually means

Connected is not the same as integrated. A retailer with hourly syncs between five systems is integrated and still fragmented, because the systems disagree for part of every hour and reconcile forever. Connected means the channel never holds its own version of the truth. The shop till, the website, the marketplace listing and the warehouse all read from and write to the same records, and the word "sync" disappears from the vocabulary because there is nothing to synchronise. The integration silo article prices the alternative, which is why the connected target is worth the effort.

One stock record

The first record is stock. One sellable quantity per SKU, held centrally, allocated across channels by rule, with reservations applied before anything is published. When a shop sells a unit, the website and the marketplace see it immediately because they never had their own copy of the number. This single change eliminates the overselling and stockout patterns covered in the oversell and stockout guide and the margin improvement article, and it is the foundation everything else stands on. If you only ever do one thing from this site, do this one.

One order flow

The second record is the order. Every sale, from any channel, becomes an order in one flow with the same lifecycle: captured, allocated, fulfilled, shipped, delivered, returned. The channel matters for reporting and for the customer experience, but the order does not live in the channel. This is what makes shop fulfilment of web orders, marketplace dropshipping and split shipments possible without a coordinator in the middle, and it is the difference between the architectures compared in the ERP and WMS comparison.

One order flow also means one set of numbers. The finance team stops reconciling channel sales against the ledger because the ledger is where the sales were posted in the first place. The marketplace mechanics article shows the payout side of the same flow, where marketplace fees and refunds land in the same accounts as everything else.

One customer view

The third record is the customer. The same person who bought in the shop, returned online and complained on a marketplace is one record, not three. That record holds their order history, their returns behaviour, their marketing preferences and the contact data they have given you. It is also the record that creates your data protection obligations, because a unified customer record concentrates the personal data your business holds. The Information Commissioner's Office guidance applies to whatever you hold, wherever you hold it, and a connected business should know exactly where its customer data lives, which is the point of the exercise.

The governance that holds it together

Connected systems fail without connected governance. Three rules keep the operating model honest:

  • One owner per record. A named person owns the stock record, a named person owns the order flow, a named person owns the customer record. Ownership means accountability for accuracy, not access.
  • Weekly reconciliation, forever. Even connected systems drift, so the weekly check of channel sales against the central records stays on the calendar permanently. The number of exceptions is the health metric.
  • Whole business channel decisions. The marketplace team does not decide marketplace stock policy alone, and the web team does not decide web stock policy alone. Channel decisions get made against the total picture, which is the seasonal stock guide approach applied all year.

Tax and compliance are part of the governance too. Selling through more channels changes where and how transactions are recorded, and the GOV.UK guidance on VAT rates is a reminder that the connected business still has to report per transaction correctly even when the records are unified. The systems make that easier, not automatic.

Starting from where you are

If you are on fragmented systems, do not wait for the perfect ERP to start being connected. Choose the highest cost seam, usually the stock record or the marketplace order flow, and connect it properly first. Measure the change, then move to the next seam. Readiness for an omnichannel ERP helps you judge when the seam fixing has run its course and a proper platform change is due, and the buying questions make sure that when you do change, the new platform actually delivers the three connected records this article describes.

The honest summary from client work: the connected business is not a project with an end date. It is a way of making decisions, with systems that support it. Start with the stock record, keep the governance simple, and let every other improvement follow from there.