Retail turnover grew by 4.7% in 2024 (INE). That growth is not evenly distributed — it is concentrated among those who have already unified their channels. The retailer still managing stock across three separate systems is growing despite its operation, not because of it.

This guide is not a survey of omnichannel features. It is a priority matrix with the mistakes that cost the most — to use in tomorrow's meeting with management.

The premise most people ignore

The omnichannel problem in Portugal is not technological. It is one of product data.

Across INFOS projects, we systematically see retailers with modern POS, a functional online shop and a loyalty app — and stock out of date across channels because the ERP does not hold a single shared product record. The customer buys online, goes to collect in-store, and the item does not exist. Not because the sales system failed, but because the item master file has three versions: one in the ERP, another in the e-commerce, another in the POS.

The priority for 2026 is not to add channels. It is to ensure that those already in place share the same data from the same source.

Those who fail to resolve this first will spend budget on integrations that synchronise wrong data faster.

What you need before you start

Before configuring any omnichannel feature, there are six baseline conditions. Without them, each subsequent step will amplify existing problems rather than resolve them.

A single item master file — code, description, EAN, price and stock — accessible to all systems in real time. Stock by physical location (store, central warehouse, supplier) visible in the back office before any promise to the customer. Documented business rules: which channel has reservation priority in a stockout? A POS-ERP integration tested with real load, not merely in a staging environment — the difference between the two is where projects die.

Compliance with DL 28/2019 and SAF-T communication (Portaria 195/2020) at all points of sale, including online shops with AT-certified invoicing. And an omnichannel returns policy, written and communicated to store teams — "bought online, return in-store" requires a procedure, not just goodwill.

  • ☐ Single item master file shared in real time?
  • ☐ Stock by location visible in the back office?
  • ☐ Reservation priority rules documented?
  • ☐ POS-ERP integration tested with real load?
  • ☐ AT-certified invoicing across all channels?
  • ☐ Omnichannel returns policy written and displayed?

Step 1 — Audit the integrity of your product data

Export the item catalogue from the ERP, the e-commerce and the POS to three separate files. Compare the number of records. If the three numbers differ — and in most of the projects we see, they do — you have a synchronisation problem that no omnichannel feature will resolve on top.

Identify the items with positive stock in the ERP and zero stock in the e-commerce, or the reverse. That difference is the real cost of poorly configured omnichannel: sales lost to "phantom" stock, or overselling with a consequent service failure. The detail the manuals don't mention: items on temporary promotion are the ones that most often become desynchronised, because a price update in the ERP does not automatically propagate to the POS if the integration is not configured for promotional prices — only for base prices.

  • ☐ Does the number of SKUs match across the three systems?
  • ☐ Is the EAN/barcode the same across all channels?
  • ☐ Do promotional prices propagate automatically from the ERP to the POS and e-commerce?
  • ☐ Do product photos and descriptions have a single source (PIM or ERP)?

Step 2 — Define the fulfilment architecture

There are three possible models. The decision is not technical — it is operational. Choose one, document it, get it approved by management, and only then configure the systems.

Model How it works When it makes sense Main risk
Central warehouse All online orders ship from a single warehouse Small store network, centralised stock High transport cost for remote areas
Ship-from-Store The store nearest the customer prepares and dispatches the order Dense store network with distributed stock In-store picking interrupts face-to-face service
Click & Collect (BOPIS) Customer buys online and collects at the chosen store Low store footfall, customer wants speed Stock reservation not confirmed in real time

Most regional Portuguese retailers start with Click & Collect because it requires no additional logistics. The classic — and costly — mistake is not reserving the stock at the moment of the order. The item is sold in-store before the customer arrives. The customer arrives, there is no item, and they don't come back. It is not a system problem: it is a business rule that no one wrote before switching the feature on.

  • ☐ Is the fulfilment model documented and approved by management?
  • ☐ Is stock reservation automatic and immediate at the moment of the order?
  • ☐ Is the collection/delivery deadline promised to the customer achievable with current resources?

Step 3 — Unify the customer view

A customer who buys in the physical store and online should not be two different records. In Portugal, with the GDPR (Lei 58/2019 and Regulation EU 2016/679) requiring explicit consent and the right to erasure, having the same customer duplicated across three databases is not only inefficient — it is a compliance risk with real consequences: the CNPD has the power to impose fines of up to 4% of global annual turnover.

Unify by NIF or verified email. Not by name. There are too many "João Silva" in the north of the country, and an incorrect merge of records is worse than two separate records — because it contaminates the purchase history and the loyalty programme of two distinct customers.

  • ☐ Is there a single customer identifier shared across POS, e-commerce and CRM?
  • ☐ Is the purchase history (all channels) visible to the store employee in real time?
  • ☐ Does the loyalty programme accrue points regardless of the purchase channel?
  • ☐ Are GDPR consents recorded by channel and date?

Step 4 — Instrument the channels with operational data

You cannot manage what you do not measure. In omnichannel, what you do not measure is costing you money in idle stock or in customers who do not return.

Define a weekly dashboard with four metrics broken down by channel: conversion rate (visit → purchase) online versus store; average order value by channel; return rate by channel and reason; on-time fulfilment rate against the promised deadline. These four metrics together reveal where the model is failing — and which of the three fulfilment models is being penalised.

Dynamic pricing tools are gaining ground in European retail, but in Portugal most independent retailers still do not have data clean enough to use them safely. Instrument first, automate later. The reverse sequence is the origin of promotions applied to the wrong channel or during the wrong period.

Qlik Sense integrated with the POS and the ERP allows you to build this dashboard without manual exports to Excel — which, in practice, is the difference between data used every week and data that sits in a shared folder no one opens.

  • ☐ Is there a sales-by-channel dashboard updated daily?
  • ☐ Are returns categorised by reason and channel of origin?
  • ☐ Does the store team have access to performance data in real time?

Step 5 — Prepare the store operation for omnichannel

This is the step that software projects systematically ignore — and that kills adoption. A regional retail store with eight employees does not have an "e-commerce manager". The same employee who serves at the counter will prepare Click & Collect, process the online order return and issue the credit note on the POS. If the procedure is not written down, each employee will improvise differently. The result is poorly recorded returns, stock that never returns to the system, and customers who wait ten minutes while the employee phones the back office to ask what to do.

Define who does what, at what moment, with what tool. In writing. Displayed in the back office — not in a PDF manual no one will open.

  • ☐ Is there a written procedure for Click & Collect preparation (maximum time, picking location, customer notification)?
  • ☐ Does the team know how to process online channel returns on the POS without phoning the back office?
  • ☐ Does the POS issue an invoice or credit note in line with DL 28/2019 without manual intervention?
  • ☐ Is there a contingency plan for when the synchronisation system fails?

MAXIRETAIL was designed for this scenario — a POS with native synchronisation to e-commerce, BOPIS and ship-from-store, without requiring a permanent IT technician in the store to manage exceptions.

The five mistakes that cost the most

Launching omnichannel without real-time stock. Promising "available for collection in 2 hours" without automatic stock reservation is the recipe for the customer arriving at the store and leaving without the item. Block the Click & Collect feature until the stock integration is tested with real load — not with ten test items on a Saturday morning.

Treating omnichannel returns as an exception. In a mature operation, a significant share of online orders is returned. If the in-store returns process requires back-office approval, it will create queues and frustration. Delegate returns authority up to a defined amount directly to the store employee, with automatic recording on the POS — no phone call, no wait.

Measuring the online channel separately from the physical channel. A customer who researches online and buys in-store shows up as a "physical sale" in the metrics. This leads to underinvestment in the digital channel, which is precisely the channel that influenced the purchase decision. Implement session-based attribution — UTM plus a store coupon code — to capture cross-channel influence before cutting digital marketing budget.

Ignoring certified invoicing in e-commerce. The AT requires online invoicing software to be certified (DL 28/2019). Shops using international e-commerce platforms without a certified invoicing module for Portugal are non-compliant — and the AT has data cross-checking mechanisms that identify this situation. Check the AT's list of certified software and confirm that your online shop's invoicing module appears on that list.

Copying the omnichannel model of a large-scale retailer. What works for a chain with 200 stores and an automated warehouse does not work for a regional chain with 12 stores and an 800 m² warehouse in Braga. Start with the simplest fulfilment model that resolves 80% of orders — and only then add complexity. Premature complexity is the leading cause of omnichannel project abandonment in Portuguese SMEs.

What separates those who grow from those who stagnated

The 4.7% growth in retail in 2024 (INE) is not a rising tide that lifts all boats. It is a reward for those with clean data and simple processes. Technological complexity is inversely proportional to adoption by the store team — and it is the store team that executes omnichannel every day, not the software.

Those who will win in 2026 are not those with the most channels. It is those who can get the store employee with three years on the job to process a Click & Collect, an online return and a face-to-face sale in the same shift, without hesitating, without phoning anyone and without getting the POS record wrong.

To go deeper into the operational management of stock and fulfilment, the article on MES and OEE in the Portuguese factory offers a complementary perspective on real-time operational visibility that applies directly to omnichannel stock management. For the security dimension of the systems that support this infrastructure — customer data, online transactions, POS-ERP integrations — the guide to NIS2 cybersecurity for Portuguese industrial SMEs covers the requirements that also apply to retailers with a digital presence.

Frequently asked questions

What is omnichannel commerce and why does it matter in 2026?

Omnichannel commerce integrates all sales channels (physical store, online, app) into a unified experience. In 2026 it is essential because retail growth is concentrated among those who have already unified their channels. Retailers with separate systems grow despite their operation, not because of it. Integration enables shared stock, a single customer view and flexible fulfilment.

What is the biggest mistake Portuguese retailers make in omnichannel?

Having multiple item master files (ERP, e-commerce, POS) instead of a single shared record. This causes out-of-date stock, sales lost to "phantom" stock and overselling. The customer buys online, goes to collect in-store and the item does not exist. The problem is not technological — it is poorly structured product data.

Do I need complex technical integration to start omnichannel?

No. Before any integration, resolve six baseline conditions: a single master file, stock by location visible, documented reservation rules, a POS-ERP integration tested with real load, AT-certified invoicing and a written returns policy. Without these, integrations merely synchronise wrong data faster.

How do I avoid stock desynchronised across channels?

Export the catalogue from the ERP, e-commerce and POS to three files. If the numbers differ, you have a synchronisation problem. Identify items with positive stock in one system and zero in another. Pay particular attention to promotions: temporary prices frequently do not propagate automatically if the integration is not configured for this.

What is the best fulfilment model for Portuguese stores?

Most regional retailers start with Click & Collect (buy online, collect in-store) because it requires no additional logistics. The classic mistake is not reserving stock at the moment of the order — the item is sold in-store before the customer arrives. Reserve automatically and immediately when the order is placed.

How do I manage the same customer across multiple channels without breaching GDPR?

Unify by NIF or verified email, never by name. A customer duplicated across three databases is a compliance risk — the CNPD can impose fines of up to 4% of annual turnover. Incorrect merges contaminate purchase history and loyalty. A single identifier shared across POS, e-commerce and CRM resolves this.

Sources

  • INE — Statistics Portugal. Turnover Index in Retail Trade, 2024. Available at: www.ine.pt
  • Tax and Customs Authority (AT). Decree-Law No. 28/2019, of 15 February — Electronic invoicing obligations and software certification. Available at: www.at.gov.pt
  • Tax and Customs Authority (AT). Portaria No. 195/2020, of 13 August — Monthly communication of SAF-T files. Available at: www.at.gov.pt
  • National Data Protection Commission (CNPD). Lei No. 58/2019, of 8 August — National implementation of Regulation (EU) 2016/679 (GDPR). Available at: www.cnpd.pt