Odoo for Retail & POS
Odoo rollouts for retail chains
Multi-store chains, cash offices and online. How the rollout is sequenced store by store, and what has to be true about your stock data first.
Retail chains rarely stall on features. They stall on the gap between what the till reports and what the stockroom holds, and on a month-end that waits for store managers to email cash sheets. An Odoo rollout in retail is mostly a data and sequencing exercise: get one store right, make stock trustworthy, then repeat.
Where it hurts today
Stock numbers nobody trusts
Counts happen quarterly, shrinkage surfaces at the annual audit, and buyers reorder against figures they already know are wrong. Every downstream decision inherits the error.
Promotions run per store
Each branch keeps its own spreadsheet of offers and staff discounts. Margin per product cannot be compared across the chain because no two stores price the same way.
The till is cut off from the back office
Sales export overnight, returns and exchanges get keyed twice, and cash variance is argued rather than traced to a session and a cashier.
Online and in-store are two businesses
Two catalogues, two stock pools, two price lists. Click-and-collect breaks both, so it never launches properly.
Close takes as long as the month
Finance rebuilds store performance by hand. By the time the numbers land, the trading decision they were meant to inform has already been made.
The modules that carry the load
Each one is here for a reason specific to retail, not because it appears on a standard module list.
- ๐งพ Odoo POS (Point of Sale)
The till itself: sessions, cashiers, cash control, and offline operation so a dropped line does not stop trade.
- ๐ฆ Odoo Inventory
One stock pool per store with barcodes, transfers and reorder rules, so buying stops being guesswork.
- ๐ Odoo Purchase
Supplier ordering against real reorder points, with cost changes visible before they hit the shelf price.
- ๐ผ Odoo Accounting
Cash sessions, card settlement and stock valuation post automatically instead of arriving as a spreadsheet.
- ๐๏ธ Odoo eCommerce
The online shop reads the same catalogue and the same stock as the stores, which is what makes collect-in-store work.
- ๐ฃ Marketing Automation
Loyalty and win-back campaigns driven by what customers actually bought, not by a separate mailing list.
How the rollout runs
- 1 Reference store
One branch is configured end to end: products, prices, hardware, cashier flow, opening and closing. Everything later is a copy of this, so it is worth over-investing here.
- 2 Make stock true
Barcodes, opening counts, transfer rules and reorder points. Stock accuracy is the gate for every other phase, and skipping it is the single most common reason a retail rollout drags.
- 3 Chain rollout
Stores go live in batches on a fixed weekly cadence: hardware in, count done, staff trained, session opened. Batches beat a big-bang weekend.
- 4 Finance and online
Bank feeds, the close cycle and store reporting first. The online shop comes last, on the stock pool that is already trustworthy.
What to have ready before kickoff
Projects that slip usually slip here, not in the build. Bring these to the first workshop.
- โ A clean product master: one row per sellable variant, with barcode and supplier code.
- โ A decision on who owns pricing: head office, region, or the store manager.
- โ A hardware list per till: printer, scanner, cash drawer, and how each one connects.
- โ Counting weekends booked, store by store, before the cutover date is announced.
- โ The promotions actually running today, not the ones on the marketing plan.
- โ Named cashier supervisors per store who will own the till after go-live.
Where it connects
Systems we most often connect on retail projects. The full list is on the integrations page.
Retail & Multi-Store
For the feature-by-feature view of retail POS, loyalty and multi-store, read the solution page.
Open the Retail & Multi-Store solutionRelated work
Questions we get asked
Can Odoo POS run in stores with unreliable internet? +
Yes. Odoo POS is offline-first: a session keeps selling while the connection is down and syncs when it returns. We deliberately test the offline path during the pilot store rather than discovering it on a busy Saturday.
Do all our stores have to go live at the same time? +
No, and they should not. One reference store is configured and traded for a few weeks, then the rest go in batches. A batched rollout costs slightly more calendar time and dramatically less risk.
Can head office set prices while stores keep some local control? +
Yes. Pricelists can be layered by chain, region and store, with discount limits by user role, so a store manager can act within a boundary you set rather than inventing offers in a spreadsheet.
We already have a Shopify or WooCommerce shop. Do we have to replace it? +
No. We either keep the existing storefront and sync products, stock and orders both ways, or move the shop onto Odoo eCommerce if you want one system. The deciding factor is usually how much custom front-end work is already invested in the current shop.
How long does a multi-store rollout take? +
Typical multi-module retail projects run in the 8 to 12 week band for the pilot store and core finance, with additional stores added in batches after that. Chains with dirty product data spend most of the extra time on the product master, not on the software.