Omnichannel – how to combine online and offline sales?

Omnichannel is an approach in which a customer can start a purchase in one channel and complete it in another without unnecessary barriers, for example reserve a product online, try it on in store and pay in the app. In practice, the biggest challenge is not a “lack of channels”, but a lack of consistency: separate baskets, inconsistent pricing, different return policies and invisible stock levels. A well-designed omnichannel setup connects online and offline sales into one coherent experience, so customer convenience increases and the number of drop-offs at channel touchpoints decreases. To achieve this, you need a clear strategy (what and where you sell, and how you fulfil orders) as well as a map of real customer paths. In this section, we discuss the foundations: the definition and scope of omnichannel and the way of mapping the customer journey, which suggests what to implement first. This makes it easier to start with MVP-type actions and only then scale the solutions.

Omnichannel strategy and design: how to integrate sales channels?

Integrating sales channels in omnichannel comes down to designing a process in which the customer moves smoothly between online and offline without losing the basket, purchase history or consistent rules. Omnichannel is not just a presence in multiple channels (multichannel), but an answer to the question of whether a purchase can be started in one place and completed in another without unnecessary barriers. That is why the strategy should cover not only e-commerce and the physical store, but also customer service, availability and order fulfilment rules. An example of omnichannel is reserving online, trying on in store and paying in the app.

Consistency starts with the rules that the customer checks immediately: prices, promotions and availability. If the question arises “why is it more expensive in store than online?”, the solution is often a single pricing policy or clearly described exceptions (for example, coupons only in the app or differences resulting from service costs). Equally important is managing the assortment by channel, because not every product has to be available everywhere, but the customer should be able to quickly check whether a given variant is in their store. In practice, a channel matrix helps (SKU only online, only in stores and shared) as well as clear information in the store search and on labels (for example QR codes to online variants).

On the operational side, omnichannel combines fulfilment models such as click&collect, endless aisle and ship-from-store, which answer questions like “can I collect it today?” or “there is no size in store”. A physical store can simultaneously sell, fulfil online orders and accept returns, so store KPIs should cover not only turnover, but also online order fulfilment, service quality and retention (for example NPS). To avoid “burning through the budget”, a sensible starting point is MVP: a unified product catalogue, stock visibility, click&collect and cross-channel returns, and only then CDP personalisation, advanced OMS and automation. The whole thing is worth supporting with change management, including short training sessions (30–45 min) and checklists for reservation, collection, return and endless aisle sales.

1. 01Start online, smooth transitionKeeping the basket, history and context.
2. 02Consistent experience, no barriersUniform prices, promotions, availability.
3. 03Finish in any channel, integrated rulesService, reservation, order fulfilment.

A smooth process, consistent rules, no loss of context between online and offline.

Mapping customer journeys: the key to effective online and offline integration

Mapping customer journeys is crucial, because it shows exactly where the experience breaks down at the online-offline touchpoint and which parts of the process need joining up. The best place to start is by outlining 5–8 of the most common purchase scenarios, for example “checks availability online → collects in store” or “browses in store → buys in the e-store with delivery”. Such a map answers the question “where do customers most often abandon the purchase?” and turns the general idea of “omnichannel” into a set of concrete tasks. This makes it easier to set implementation priorities and the scope of changes across the channels.

A well-mapped customer journey should immediately identify the required integration points: stock visibility, reservations, payments and cross-channel returns. If the customer is to check availability in store, they need clear information on “is it definitely available?” as well as the rules for reservation or collection. If they are to collect or return in store a product bought online, the process must be easy to understand and consistent both in communication and in the terms and conditions. Mapping also helps capture the moments when the customer expects unambiguous answers (for example, online vs offline returns policies) and points to places where communication should be clarified.

On the basis of customer journeys, you design specific solutions that shorten the path to purchase and reduce uncertainty. For the “I want to collect today” scenario, a natural element is click&collect with a defined SLA per store, and for “there is no size in store” — endless aisle, where the salesperson orders from the central warehouse to the customer’s home. If the journey includes “I am comparing online and in store”, a consistent pricing and promotions policy becomes critical, so that the customer does not encounter conflicting conditions. Only after such analysis can you sensibly decide what to implement first and what to leave for the scaling stage.

Consistent pricing and promotions policy: how to avoid misunderstandings?

You avoid pricing misunderstandings when the customer encounters the same rules in every channel or has exceptions clearly described. The most common dilemma (“why is it more expensive in store than online?”) is solved by a single pricing policy or clearly shown differences, for example coupons available only in the app. It is important that promotion terms are unambiguous and can be checked both in e-commerce and in store. This way, comparing offers between online and offline does not end in a loss of trust.

From an operational perspective, consistency in pricing and promotions requires central control, rather than manual adjustments at individual touchpoints. A good practice is to manage promotions in OMS/ERP and adopt rules in which base prices remain identical, with differences arising solely from clearly defined programmes (e.g. loyalty benefits). If different conditions apply, they should stem from simple rules, for example discounts assigned to a loyalty programme, such as -5% in the app. This reduces situations in which the customer only finds out about exclusions at the till or in the basket.

A consistent policy should also work “at the interface” between systems, so that the till sees the same prices and promotion mechanics as the online store. In practice, this is achieved by integrating the POS with a central price list and promotion engine, rather than using local, fragmented settings. This approach also makes it easier to standardise vouchers and discount codes so they are honoured in POS and e-commerce with identical restrictions. The result is fewer disputes at checkout and fewer customer service queries about a “non-working code”.

1. 01One pricing policyConsistent rules in every channel.
2. 02Clear differencesClearly described exceptions (e.g. in the app).
3. 03Unambiguous termsEasy to check online and in-store.
4. 04Central controlManagement in OMS/ERP, without manual adjustments.

Key to success: Transparency and central management build customer trust.

The role of physical stores in an omnichannel strategy

In omnichannel, physical stores act as a customer experience hub, combining sales with fulfilment and the handling of cross-channel processes. In practice, this means a space where the customer can conveniently collect an order, resolve an order issue and get support, regardless of where the purchase was made. This role addresses the expectation “can I sort this out at the nearest location?”, which often decides which brand is chosen. At the same time, it requires defining which processes the store handles as standard and which remain with head office.

An effective strategy assigns stores KPIs that go beyond turnover alone, so they are not judged solely on actions supporting e-commerce. It is worth measuring not only sales, but also online order fulfilment, service quality and retention, for example through NPS. This gives the store an incentive to handle scenarios such as collections, returns or shopping support, instead of redirecting the customer to another channel. This model also helps to organise operational priorities when the store becomes part of order fulfilment.

For the store’s role to be a genuine convenience for the customer, in-store processes must be designed with speed and clarity in mind. A good example is BOPIS/click&collect handled via a dedicated collection point and clear signage, which reduces queues and shortens service time. The store should also support scenarios in which the customer expects to have the matter dealt with “straight away”, for example a return or complaint at any location, which requires a single RMA system and case number. This setup reduces friction at the channel interface and makes it easier to use the store network as part of the overall omnichannel experience.

A unified customer profile: how do you create a single source of truth?

A single source of truth about the customer is created by building a unified profile (Single Customer View) that brings together data from e-commerce, POS and customer service in one place. This is most often achieved in a CRM/CDP (e.g. Salesforce, Microsoft Dynamics 365, HubSpot, Segment, Bloomreach), as well as by consistently using one customer identifier across every channel. Such a profile answers the practical question: “can the salesperson and consultant see my online and offline purchase history?”. This makes it easier to maintain a consistent experience, for example in loyalty, returns or order statuses.

In a physical store, customer identification should minimise friction, which is why a phone number, e-mail, QR code in the app or a loyalty card are used. In practice, a scenario where the salesperson scans the QR code and the system automatically suggests coupons and order statuses works well. For till purchases to count towards online thresholds and benefits, the POS should pass transactional data to the CRM/loyalty system in near-real-time. The standard is integrations via API or connectors to POS systems (e.g. LS Retail, Oracle Retail, Comarch POS) and a data warehouse.

Customer profile consistency also requires order in data and consents, because otherwise duplicate accounts and inconsistent marketing messages appear. Put in place deduplication rules (e-mail/phone + fuzzy matching of surnames) and MDM for key entities: customer, product, store and order, to avoid situations like “why do I have two point balances?”. Move marketing consents to a central consent register (e.g. OneTrust, Usercentrics) and synchronise them across e-mail, SMS, push and phone. At the same time, stick to data minimisation (for example, limit questions like “why do you need my PESEL?”) and secure integrations with tokens, encryption and access control (RBAC).

1. 01Source integrationE-commerce, POS, customer service
2. 02CRM / CDP & identifierConsistent data key
3. 03One source of truthFull purchase history
4. 04Consistent experienceLoyalty, returns, status

Building a consistent view of the customer enables personalisation and streamlines service in every channel.

Integration of POS with e-commerce: ensuring consistency of prices and promotions

Consistency of prices and promotions between POS and e-commerce can be achieved by integrating the till with a central price list and promotion engine, rather than making manual adjustments at individual tills. As a result, the same discount calculation rules and offer terms apply in the physical store and online. In practice, this answers the operational question: “does the till see the same prices and promotions as the online store?”. This approach reduces tension at the till and cuts the number of situations in which the customer questions the promotion rules.

Coupons and discount codes should be honoured in POS and e-commerce with the same restrictions, which requires a central promotion engine and coupon validation via API. This means the rules do not result from interpretation in the store or from local configurations, but from one shared source of rules. This is particularly important when promotions are linked to customer identification and a loyalty programme, because the system must recognise the customer and apply the correct terms in every channel. As a result, the customer benefits in a predictable way, without “surprises” at the payment stage.

Integration of POS with e-commerce also supports consistent settlement of purchases and benefits, provided that POS transactions are transferred to CRM/loyalty in near-real-time. This makes it possible to maintain one points currency, consistent benefit thresholds and an immediate display of the balance in the app and on the receipt/invoice. From a data management perspective, data quality remains key (MDM and deduplication), so that purchases are not assigned to two different accounts. At the same time, you need to ensure security, i.e. access control (RBAC) and data minimisation, so that the integration does not require collecting information that is unnecessary for customer service.

Click&collect and ship-from-store: optimising deliveries and collections

Click&collect and ship-from-store streamline deliveries and collections because they shorten fulfilment time and give the customer a choice between collection in store and delivery from the nearest location. In click&collect, the key is to provide a real “ready for collection” time, based on the picking process in a given store (SLA per location), because delays immediately reduce trust. For this to work smoothly operationally, the process should be supported by alerts in the OMS that signal the risk of missing the SLA. This means the collection promise is not just a marketing slogan, but becomes part of a predictable shopping experience.

Ship-from-store shortens delivery time because an order can be dispatched from the nearest store rather than only from the central warehouse. In day-to-day operations, routing selects the location by looking for the optimal compromise between lead time (e.g. D+1), courier cost and the risk of stock-outs on the shelf. At the same time, it is worth designing the “last mile” with integrated carriers and collection points so that the customer can choose between a parcel locker, a collection point and a courier. If you plan to allow the delivery method to be changed after purchase, limit it to a short window (e.g. 30 minutes) and only to available integrations.

Real “frictionless” shopping only appears when systems and processes maintain consistent statuses, reservations and status communication. In practice, this means reserving the goods and blocking stock at the moment click&collect is selected, as well as consistent order statuses in e-mail/SMS and the customer account (typically 6–10 statuses) with a link to the carrier tracking. To avoid damaging in-store display during picking, store picking rules are used: priority from the back room, daily limits, picking outside peak hours and a minimum display stock level (e.g. 1 item on the shelf). This fulfilment model reduces the number of cancellations and limits customer frustration caused by inconsistent availability.

• Set a click&collect SLA for each store and support it with alerts in OMS.
• Introduce reservation and stock blocking at collection to avoid double-selling.
• Configure ship-from-store routing in terms of time, cost and the risk of shelf stock-outs.
• Ensure consistent order statuses (6–10) in every channel and carrier tracking.
• Set store picking rules so that picking does not reduce the quality of the display.

Personalising offers based on cross-channel behaviour

Cross-channel personalisation involves tailoring recommendations and communication to customer behaviour online and offline, so that they remain relevant even when the shopping journey moves between channels. The most important rule is: personalise with exclusions, so that you do not recommend to the customer what they have already bought, only what genuinely complements their needs. For this purpose, CDP and marketing automation are used (e.g. Klaviyo, Braze, Salesforce Marketing Cloud) as well as recommendation rules: complementary products, accessories, servicing or size exchange. The result is communication that supports the purchase decision rather than creating information noise.

In omnichannel, personalisation often starts with RFM segmentation (Recency, Frequency, Monetary) taking offline purchases into account. This split answers business questions such as “who is worth inviting into the store?” or “who should be made to first buy in the app?”. For example, the “VIP offline, dormant online” segment may receive a click&collect offer with a +10% bonus on the first order in the app. The condition for effectiveness is that transaction data from POS and e-commerce feeds segmentation in a consistent way.

Personalisation delivers the best results when it goes hand in hand with useful touchpoints across the entire shopping journey. A tried-and-tested online-offline bridge is often a mobile app, which can include QR identification, coupons, order status and a store map, as well as on-site barcode scanning to check reviews and size availability. In post-purchase communication, it is worth guiding the customer along the simplest possible support path, e.g. through a returns guide in the email and in the account, supplemented with an exchange option (“change size in 2 clicks” or “return it at the nearest store without a label”). This means personalisation does not end with a “nice-looking mailing”, but genuinely reduces friction and improves the customer experience.