Grocery retail breaks a lot of assumptions baked into a general ERP. You sell bananas by the kilogram but stock them by the case; a carton of yoghurt has a real expiry date that must drive what the picker grabs and what the cashier is allowed to sell; margins are razor-thin so a mis-keyed weighed-item price or an untracked shrink write-off is money gone. Out of the box, Odoo can hold products, run a POS, and track lots — but it does not natively know that a barcode beginning 20 encodes an embedded weight and price, that a supplier ships in cases while you sell in units with an automatic UoM conversion, or that expiring stock should be surfaced and marked down before it is thrown away. Teams end up bridging those gaps with spreadsheets, manual price overrides at the till, and end-of-day guesswork.

This is a made-to-order module we build for your business — not an existing download from apps.odoo.com. It layers grocery-specific behaviour onto standard Odoo (product.template, stock.move, stock.lot, pos.order) rather than forking it, so you keep native accounting, reporting, and upgrade paths. Concretely, we extend the models with the fields grocery operations need — weighed-item flags, embedded-barcode (EAN-13 price/weight) parsing, per-lot expiration_date with computed @api.depends shelf-life indicators, purchase-UoM vs sales-UoM conversion, and department/aisle categorisation — plus the ir.model.access.csv rules and record rules so shelf staff, cashiers, and buyers each see only what their role needs. Views (XML and OWL for the POS side) put the right controls where the work happens: an expiry dashboard for the shift lead, a weighed-goods flow at the counter, and a reorder view for the buyer. Automated actions and scheduled jobs handle the repetitive parts — near-expiry markdown proposals, low-stock reorder triggers on perishables, and daily shrink reconciliation. Where you run a scale, EDI feed, or loyalty system, we integrate it through Odoo's XML-RPC/JSON-RPC API rather than manual re-keying.

We build against your target Odoo version (17.0, 18.0, or 19.0) and are explicit about the Community vs Enterprise line: everything above works on Community, while features that lean on Enterprise-only apps (for example advanced barcode scanning flows or certain accounting localisations) are scoped to what your edition actually includes, and we tell you before we quote if a capability needs Enterprise.

Delivery is build-to-order. After a short scoping call we confirm the exact model changes, views, roles, and integrations in writing, then build and test on a staging copy of your database, run UAT with your team, and deploy behind a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, depending on integration count and data migration. Pricing starts from $349 (indicative, single-company base scope); multi-company or multi-store rollouts, scale/EDI/loyalty integrations, deeper localisation, and larger product/stock data migrations increase the quoted scope. You get a fixed quote after the scoping call — never a surprise on the invoice.