Industry · Retail
Retail: one platform, every location.
A five-store retailer's nightly close fell from two hours to 11 minutes once every register ran on Odoo POS.
Register to ledger
- Sale rung upPOS
Store 3 · 0412 - Stock drops at that storeInventory
WH3/POS/00318 - Points added to the cardLoyalty
+120 pts - Low stock triggers a transferReplenishment
WH1/INT/00077 - Session closed and countedPOS
0 differences - Takings posted to store P&LAccounting
Reconciled
The build
What we configure in Odoo
These are the settings that decide whether the nightly close runs itself.
- Point of SaleOne catalog for every store, offline selling, session close posting cash and card totals.
- InventoryA stock location per store, transfers from one screen, replenishment rules per SKU.
- AccountingAutomated daily reconciliation with exception flags, cash and card differences posted, P&L by store.
- eCommerceA web store on the same stock, Shopify or WooCommerce sync, in-store pickup.
- LoyaltyPoints earned and spent at any store, gift cards and eWallet across channels.
- PricelistsOne central pricelist for every store, store-level overrides, promotions with start and end dates.
- PurchaseOrders drafted from reorder rules, vendor prices and lead times on file, supplier EDI.
- BarcodeScanned receipts, transfers and counts, cycle counts without closing, shelf labels from the product.
- SellPoint of Sale
Every store on one POS, which keeps selling if the internet drops.
- RewardLoyalty
Points and promotions shared across stores and the web store.
- DepleteInventory
Each sale reduces stock at the store that made it.
- TransferInventory
Store-to-store transfers before anything is reordered.
- ReorderPurchase
Reorder rules raise purchase orders from what sold.
- CloseAccounting
Closing the session posts sales, cash and card to the books.
The problem
What breaks first in a multi-store retailer
The typical stack: a separate Square or Shopify POS in each store, no shared inventory, and a spreadsheet in the middle.
- A two-hour close every nightRegisters, drawers and card batches reconciled by hand at each store.
- Stock nobody can findOne store runs out while another has it on the shelf.
- Online and in-store splitSeparate inventories mean the site oversells and staff stop trusting counts.
- Loyalty stuck in one storePoints earned at one location can't be spent at another.
- Prices keyed in by handOne client needed 45 minutes per price change, terminal by terminal.
- Reports stitched from exportsThe weekly report means exporting and merging spreadsheets first.
The change
Before and after
What changes at the register and in the back office once every store runs on one record.
| Area | Before | With Odoo, configured by us |
|---|---|---|
| Nightly close | Two hours across five stores | 11 minutes, exceptions flagged automatically |
| Stock visibility | Shared sheet, always out of date | Every store's stock live at every register |
| Price changes | 45 minutes, one terminal at a time | One pricelist update reaches every store |
| Loyalty | Points locked to one store | Earned and redeemed at any location |
| Reporting | Five exports merged by hand | One dashboard by store, daily to monthly |
The plan
The plan for a multi-store retailer
Every proposal carries its own dated plan.
- Phase 1
Audit and scope
Registers, catalog and close process mapped store by store.
- Phase 2
Catalog and pilot
One deduplicated catalog with central pricing; the busiest store goes live first.
- Phase 3
Roll out and train
Remaining stores live in waves, each supported on its first trading day.
- Go-live
Automate and stabilize
Reconciliation and loyalty switched on, 30-day hypercare, then our Rajkot support desk.
Results
What changed for our clients
One client, measured at day 90 against the close it ran before go-live.
Case study · Retail
Five locations, one platform: reconciliation cut from 2 hours to 11 minutes
A fashion retailer with five stores and 45 staff replaced five separate Square POS setups with one Odoo POS and inventory layer in 12 weeks.
FAQ
Common questions
The questions store owners and finance leads ask before scoping.
Does Odoo POS work offline?
Yes. If the connection drops, Odoo POS keeps taking sales and queues the orders on the device. They sync to the server when the connection returns, so an outage does not close the register.
Can Odoo run POS and inventory across multiple store locations?
Yes. Each store gets its own POS and its own stock location, all in one database. Staff can check stock at other stores from the register, and transfers between stores are tracked with a full history.
Can Odoo POS replace Square across several stores?
Yes. Our five-store client replaced five separate Square POS setups with one Odoo POS and inventory layer. We merged 2,400 SKUs into one catalog and ran the pilot store alongside Square for two weeks before switching.
Can Odoo integrate with Shopify or WooCommerce?
Yes, through a connector we configure or build. Products, stock levels, orders and customers sync both ways, so online and in-store channels sell from one inventory pool. Odoo's own eCommerce app is an option if you would rather run one system.
Can Odoo run one loyalty program across all our stores?
Yes. The Loyalty app handles points, gift cards and eWallet balances across every store, not just the one that issued them. Our retail client processed 340 cross-store redemptions in its first 90 days, something its old setup could not do.
How long does an Odoo retail implementation take?
Our five-store client went live in 12 weeks: catalog first, then a pilot store, then the other four stores in two waves. Your proposal states your date. We use AI across configuration, development and testing to shorten delivery.
Start with a 30-minute call.
Bring your store count, your POS setup and last week's close times.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751