Omnichannel retail: how the MAXIRETAIL backoffice manages franchisees

Retail grew by 4.7% in turnover in 2024 (INE), but the franchisor trying to manage a network of 15 shops with spreadsheets shared by email knows that this growth reaches the back office as chaos: margins per shop that nobody can compare, promotions that the franchisee applies whenever they feel like it, and a month-end close that depends on the person in charge of each point of sale remembering to send the SAF-T on time.

The thesis this article defends is this: the biggest risk in a franchise network is not price inconsistency. It is stock opacity. A franchisor who does not know, in real time, what each shop has on the shelf cannot manage centralised replenishment, cannot make lateral transfers between shops, and cannot honour the omnichannel promise of BOPIS or ship-from-store without phoning the franchisee. And by the time they phone, it is already too late.

The real problem for the Portuguese franchisor

Most franchising networks in Portugal with fewer than 30 shops operate with a POS chosen by the franchisee — often different from shop to shop — and a central ERP that receives data via FTP file or manual integration. The result: the franchisor sees what happened yesterday, not what is happening now.

There are three failure patterns we see repeatedly. The first is the heterogeneous POS: each franchisee chose their own system, integration is done by file export when it is done at all, and the franchisor has no intraday visibility. The second is inconsistently applied promotions: head office sends the promotional price list by email, the franchisee uploads it manually, and typing errors and delays are the norm, not the exception. The third is the fragmented month-end close: each shop closes its SAF-T independently, head office's finance department consolidates manually, and compliance with DL 28/2019 and Portaria 195/2020 depends on the discipline of each franchisee — not on a process.

By the time the franchisor discovers that a shop sold below the recommended minimum price, the week is already over. The margin damage is done and the customer has already compared it with the shop next door.

MAXIRETAIL back-office architecture for franchise networks

MAXIRETAIL operates on a hub-and-spoke architecture: the central back office manages catalogue, prices, promotions, stock and reports; each shop runs the MAXIRETAIL POS with automatic synchronisation. Communication is not by file — it is by REST API with replication configurable by interval, typically 5 to 15 minutes for stock and immediate for sales transactions.

The functional layers of the central back office cover five domains. In the catalogue, the franchisor defines the item, the reference, the recommended selling price and the minimum price — the POS blocks any transaction below that minimum without human intervention. In the promotions engine, activation is automatic by date, target shop and discount type: the franchisee uploads nothing manually. In stock, the franchisor sees each point of sale's inventory in real time and can initiate lateral transfers directly from the back office. In invoicing, MAXIRETAIL generates each shop's SAF-T autonomously and makes it available in the central back office — head office's finance department accesses each shop's file without depending on anyone. In dashboards, the integration with Qlik Sense delivers KPIs for sales, margin, average ticket and stock rotation that are comparable across shops and against network benchmarks.

What the franchisee controls — and what they do not

This is the operational detail that software manuals rarely explain: the granularity of permissions is the real battleground between franchisor and franchisee. MAXIRETAIL resolves this with a permissions model by role and by entity.

Offline synchronisation: the detail that decides the network's stability

A franchising network has a risk that a chain of own shops does not: the franchisee has no contractual obligation to maintain the network infrastructure to the same standard as head office. Shops in second-tier shopping centres or in areas with limited fibre coverage lose their connection. The MAXIRETAIL POS operates in offline mode with deferred synchronisation — transactions are recorded locally and synchronised when the connection is re-established. The central back office automatically flags the disconnection periods for auditing. This is not a technical detail: it is what separates a network that works from a network that phones head office at 10:30 on a Saturday because the POS will not open.

Regulatory compliance in a franchise network

The franchisor is, in practice, responsible for the network's tax compliance — even if each shop is an independent legal entity. When the Tax Authority requests a shop's SAF-T, it is the franchisor who has to deliver it if the franchisee does not. This risk is rarely made explicit in Portuguese franchising contracts. It is a silent liability that only appears when the audit arrives.

DL 28/2019 and ATCUD in a multi-entity environment

DL 28/2019 requires invoicing software to be certified by the AT and each tax document to include the ATCUD. In a franchise network with distinct legal entities, each shop has its own tax number and its own document series. MAXIRETAIL manages document series by entity — the central back office does not mix the series of different shops, but has visibility over all of them. AT certification applies to the software, not to the shop: a single certified software covers the entire network.

Portaria 195/2020: monthly SAF-T communication

The monthly communication of the SAF-T to the AT is an obligation of each entity. MAXIRETAIL automates file generation per shop and makes it available in the central back office. The franchisor can verify whether all shops have generated and submitted the month's SAF-T — without depending on emails or phone calls. The process moves from reactive to auditable.

The franchisor who has no visibility over the SAF-T of their shops is not only managing a tax risk. They are managing a reputational risk: if a shop is audited and the file is incomplete, the network's name appears in the news, not the franchisee's tax number.

GDPR and loyalty programme customer data

The centralised loyalty programme means that the franchisor is the controller of the personal data of the customers of all shops. The franchisee is a processor. This distinction, required by the GDPR (EU Regulation 2016/679) and by Law 58/2019, has concrete implications: the franchising contract must include a Data Processing Agreement (DPA), and the back office must record each customer's consent in an auditable way. MAXIRETAIL records consent at the moment of joining the programme and maintains the change log. Without this record, any customer complaint to the CNPD could expose head office — not the shop.

Technical integration options: comparison of approaches

Not all franchising networks start from scratch. Many have franchisees with a POS already installed and active maintenance contracts. The integration decision is not binary — there are at least three approaches with distinct trade-offs.

The file integration trap

File integration is the most common choice in the early stages of a franchising network because it is the cheapest. It is also the one that most frequently becomes permanent through inertia. The problem is not technical — it is operational: when the file does not arrive, the back office does not know whether the shop sold nothing or the export process failed. The difference between "day with no sales" and "shop offline" is not visible until someone phones. And by then, the stock data is already wrong throughout the entire decision chain that depended on it.

What works in practice

Pattern 1: phased rollout by geographic cluster

A specialist retail network with shops scattered across the North and Centre of Portugal reduces the rollout risk by starting with the shops in Greater Porto — where geographic proximity facilitates on-site support and training. The inland shops enter in a second phase, with the support team already having accumulated experience from the first implementations. This pattern is not merely logistical: it allows the permissions configuration to be fine-tuned before scaling it to franchisees with less tolerance for operational disruption. A franchisee in Bragança who loses their POS on a Friday afternoon does not have the same level of support available as a franchisee in Porto.

Pattern 2: the loyalty programme as leverage for franchisee buy-in

The franchisee resists changing POS for legitimate reasons: staff training, risk of downtime, cost. Buy-in increases when the franchisor offers, in return, access to the centralised loyalty programme — which the franchisee could not implement or fund alone. The loyal network customer is a commercial argument the franchisee understands better than any technical argument. The conversation shifts from "you'll have to change your POS" to "you'll get access to the whole network's customer base".

Pattern 3: benchmarking dashboards as a network management tool

The franchisor who shares with each franchisee their ranking within the network — average ticket, conversion rate, stock rotation — creates a performance incentive at no additional cost. Qlik Sense integrated with MAXIRETAIL makes it possible to configure a dashboard per franchisee with their own KPIs and their relative position in the network, without exposing the individual data of other franchisees. This mechanism of controlled transparency is, in practice, more effective than contractual performance clauses.

The franchisee who knows they are in the network's bottom quartile for average ticket does not need an appraisal meeting. They need a dashboard that shows it to them every day.

Post-implementation success metrics

Implementing a centralised back office for franchisees is not measured in uptime alone. The metrics that matter are operational and financial, and they should be defined before go-live — not after the system is in production.

• Month-end close time: number of days between the last day of the month and the availability of consolidated data in the back office. Target: fewer than 2 working days.
• SAF-T compliance rate: percentage of shops that submitted the SAF-T within the legal deadline. Target: 100% — any value below that is an active tax risk.
• Price deviation: number of transactions in which the selling price fell outside the range defined by head office. Target: zero — if it is not zero, the permissions configuration has a fault that needs to be corrected, not monitored.
• Stock latency: the difference between a shop's actual stock and the stock visible in the central back office. For lateral transfer decisions, the acceptable latency is under 15 minutes.
• Loyalty programme adoption: percentage of transactions associated with an identified customer. This indicator indirectly measures the quality of the franchisee's POS operation — a franchisee who does not register customers is sabotaging the programme, consciously or unconsciously.

Decision matrix: when to migrate to a centralised back office

Not all franchising networks need to migrate at the same time. The decision depends on the size of the network, the maturity of the franchisees and the current level of regulatory risk.

Integration with the rest of the INFOS operation

MAXIRETAIL does not operate in isolation. In a franchising network with a central warehouse — shop replenishment, returns management, cross-docking — integration with the KORA Inventory Suite makes it possible to manage the flow of stock between the central warehouse and each franchised shop with full traceability. The debate between centralised and fragmented stock has a different answer depending on the franchising model: if the franchisee buys their stock from head office, centralisation is natural; if they buy directly from the supplier, visibility is harder to guarantee and requires data-sharing agreements that should be in the franchising contract, not in the IT manual.

For networks with a sales force that visits franchisees — collecting orders, presenting new collections — the KORA Sales Suite integrates with the MAXIRETAIL back office and allows the head office salesperson to see each shop's stock and sales at the moment of the visit. No paper, no phone calls before leaving the office.

Managing promotions and seasonality in a franchise network has an added complexity that the software does not resolve on its own: the franchisee has incentives not to take part in promotions that reduce their margin, even if they benefit the network. The MAXIRETAIL centralised promotions engine resolves this technically — but the franchisor has to resolve the question of margin compensation contractually before activating mandatory promotions. Technology without a contract is a source of conflict, not of efficiency.

The mistake the manuals do not mention

There is a failure pattern we see in franchising networks that migrate to a centralised back office: the permissions configuration is done once, at go-live, and is never reviewed. After 18 months, there are franchisees with administrator permissions that were granted "temporarily" during implementation and were never revoked. At a point of sale where staff turnover is high — and in retail it is always high — that means former employees may have active credentials. Audit each shop's user permissions every six months. This is not a generic good security practice: it is a specific operational necessity for franchising networks, and it is the kind of task that nobody does because it is not on anybody's calendar.

For networks already thinking about the omnichannel retail trends for 2026, the centralised back-office architecture is the prerequisite for any personalisation initiative or integration with digital channels. Without real-time stock visibility per shop, there is no ship-from-store. Without consolidated transaction data, there is no customer segmentation. The back office is not support infrastructure — it is the condition that makes the omnichannel strategy possible. Whoever treats it as an operational cost will pay double when they try to build the strategy on top of data that arrives 24 hours late.

Sources

• INE — National Statistics Institute. Turnover Index in Retail Trade, 2024. Available at: ine.pt
• Tax and Customs Authority. Decree-Law No. 28/2019, of 15 February — Rules applicable to the processing of invoices and other tax-relevant documents. Available at: dre.pt
• Tax and Customs Authority. Portaria No. 195/2020, of 13 August — Monthly communication of the SAF-T(PT). Available at: dre.pt
• European Parliament and Council of the EU. Regulation (EU) 2016/679 (GDPR). Available at: eur-lex.europa.eu
• Assembly of the Republic. Law No. 58/2019, of 8 August — National implementation of the GDPR. Available at: dre.pt

Frequently asked questions

What is the MAXIRETAIL hub-and-spoke model?

It is an architecture where the central back office manages catalogue, prices, promotions, stock and reports, while each shop runs the MAXIRETAIL POS with automatic synchronisation. Communication occurs via REST API with configurable replication, typically every 5-15 minutes for stock and immediate for sales transactions.

How does synchronisation work when the internet connection drops?

The MAXIRETAIL POS operates in offline mode, recording transactions locally. When the connection is re-established, the data synchronises automatically with the central back office. The system flags the disconnection periods for auditing, preventing the network from depending on phone calls to head office to resolve technical problems.

Who can change the selling prices in a MAXIRETAIL network?

The franchisor defines the base selling price and the minimum price. The franchisee can adjust the price within the permitted range. The POS automatically blocks any transaction below the minimum price without human intervention, protecting the network's margins.

How are national promotions applied?

The franchisor activates promotions automatically in the promotions engine, specifying date, target shop and discount type. The franchisee uploads nothing manually. Activation is automatic and synchronised across all shops, eliminating typing errors and delays.

What is the franchisor's responsibility in tax compliance?

The franchisor is responsible for the network's tax compliance, even if each shop is an independent legal entity. When the Tax Authority requests a shop's SAF-T, the franchisor has to deliver it if the franchisee does not. It is a silent liability that is rarely made explicit in contracts.

How does MAXIRETAIL resolve the stock opacity problem?

The franchisor sees each point of sale's inventory in real time and can initiate lateral transfers directly from the back office. This intraday visibility makes it possible to manage centralised replenishment and honour omnichannel promises such as BOPIS or ship-from-store without depending on phone calls.

Can the franchisee access data from other shops?

No. The permissions model by role and by entity ensures that the franchisee only accesses their own shop's data. They can export the SAF-T for their shop only, while the franchisor has full visibility of all shops and access to data that is comparable across points of sale.