Newsletter · September 2026

September 2026: retail deep-dive, mobile integration guide, and an Odoo 20 update

Notes from the field on Q4 retail readiness, multi-location retail in Odoo 19, where the mobile app fits, an Odoo 20 update, and a plain guide to replenishment rules.

By Octagotech Team7 min readUpdated

In this issue

  1. From the field. Q4 retail readiness and inventory forecasting.
  2. Article spotlight. Multi-location retail operations in Odoo 19.
  3. Tech corner. Where the Odoo mobile app fits, and where it doesn't.
  4. Odoo 20. An update now that it has shipped.
  5. Tip of the month. Odoo's three replenishment strategies, explained.

From the field: September note

September always brings a shift in the conversation. The strategic planning calls that dominated Q2 and Q3 give way to something more urgent: "We need to be ready for Q4." This month, many of our incoming retail inquiries have the same subtext: the holiday season is close and inventory control is not where it needs to be.

The most common ask we're hearing is inventory forecasting. Specifically: how do we use what Odoo already knows about our sales history to set smarter reorder points before the November rush hits? Most retailers who've been on Odoo for a year or more already have the data. They're just not using the forecasting and replenishment tools that surface it.

If that sounds familiar, the tip of the month at the bottom of this issue is written for you. We walk through the three replenishment strategies in Odoo's inventory module and explain when each one makes sense. It's one of those configuration decisions that looks simple on the surface but has a real impact on stockout rates and carrying costs.

Billing is a good example of the same point. In our healthcare billing case study, a clinic group cut billing lag from 14 days to 2 and recovered lost revenue in its first year.


Article spotlight: retail multi-location operations

This month we published a detailed piece on running multi-location retail operations in Odoo 19. The focus was on the specific configuration decisions that separate a clean implementation from one that creates reporting headaches three months in.

The usual problem with multi-location retail is the assumption that each location can be treated as its own island until end-of-day reconciliation forces them together. Odoo's inter-company and multi-warehouse features work well when you drop that assumption from day one.

Key points from the article:

  • Warehouse vs. location hierarchy. Most retailers with 3–8 locations are better served by a single-warehouse, multi-location model rather than separate warehouses per store. Separate warehouses simplify some reporting but complicate stock transfers and demand aggregation in ways that usually aren't worth it at that scale.
  • POS session reconciliation. Session close is where cash differences surface, so decide upfront how you want them handled: automatic journal entry vs. manual review. Get this wrong and your accountant will be unhappy within a week of go-live.
  • Centralized vs. distributed replenishment. In most multi-store retail setups, a centralized buying function ordering to a main warehouse and replenishing stores via internal transfers produces better margin outcomes than letting each store manager trigger their own purchase orders.

Read the full post, Odoo for retail: multi-location POS and inventory sync, or learn more about our retail industry work.


Tech corner: mobile app integration

Our mobile integration guide went live earlier this month. The piece covers how to connect a custom mobile app to Odoo: choosing between REST and JSON-RPC, API-key authentication, when to put middleware in between, real-time updates with webhooks, and four data gotchas from real projects.

The point we keep making in client conversations: the Odoo mobile app is good for consumption and simple actions, but it's not designed for high-throughput scanning workflows. If your warehouse team confirms a high volume of picks per shift, you'll want dedicated barcode scanner hardware rather than relying on phone cameras.

Key takeaway: Before scoping a mobile integration, classify your users' workflows by frequency and input method. Low-frequency, approval-type actions (manager sign-offs, expense approvals, leave requests) work well in the native app. High-frequency, data-entry-heavy workflows (warehouse picking, delivery POD capture at scale) need purpose-built hardware or a custom mobile view.

The full post is on our blog: how to integrate a mobile app with Odoo.


Odoo 20: an update

Update, October 2026: Odoo 20 shipped in September, soon after this issue went out. The predictions we made here about AI, Studio and the external API were guesses made before the release, and we have removed them. See our Odoo 20 release overview for what actually shipped.

One correction matters for integration projects. Odoo is not improving its JSON-RPC API. It is deprecating the older XML-RPC and JSON-RPC endpoints in favour of the JSON-2 API that arrived in Odoo 19, so new integrations with external eCommerce platforms, logistics providers or industry-specific tools should be built on JSON-2.

If you're mid-implementation on Odoo 19, don't pause. For most databases we recommend landing on 19 first and moving to 20 once it matures, and our Odoo upgrade and migration page covers the path to 20 when you are ready.


Tip of the month: Odoo replenishment rules explained

Odoo's inventory module gives you three replenishment strategies, and picking the wrong one for a given product is one of the most common configuration mistakes we see in post-go-live audits.

Make to order (MTO)

With MTO, a purchase order or manufacturing order is created automatically when a confirmed sales order comes in, and only then. There's no stock held in advance. Use this for high-value, low-volume products where the carrying cost of holding inventory outweighs the risk of lead time delays, or for highly configured products where you can't predict exact demand. The downside is obvious: your lead time becomes your customer's wait time.

Make to stock (MTS)

MTS means you produce or purchase in anticipation of demand, building a buffer you draw down as orders arrive. It's the right choice for high-velocity, predictable SKUs where stockouts have an immediate revenue impact. The risk is overstock if your demand forecast is off. Odoo's forecasted inventory report helps here; if you're not checking it regularly for your top-selling products, you should be.

Reorder point (min/max)

The reorder point rule is the most practical choice for most mid-market retailers and distributors. You set a minimum quantity (the trigger) and a maximum quantity (the target). When forecasted stock (on hand plus incoming, minus outgoing) drops below the minimum, Odoo automatically creates a replenishment order to bring stock back up to the maximum. It's reactive rather than predictive, but it's transparent and easy to adjust seasonally.

Q4 recommendation: For retail clients heading into the holiday season, review your reorder points now, not in October. If your sales velocity in November and December is 3× your average, your min/max quantities need to reflect that. Reordering rules have no date range, so for seasonal SKUs raise the minimum before the peak and put a reminder in the calendar to lower it again in January, rather than raising the global minimum and forgetting about it.

If you're unsure which strategy fits which product category in your catalog, this is a quick consulting conversation, usually resolved in an hour with someone who knows the module well. Book a discovery call with our team and we'll walk through it with you.


That's September. As always, email us at sales@octagotech.com or reach us through the contact page if something here sparked a question. The retail Q4 readiness window is short. If you're thinking about getting inventory and POS configuration tightened up before November, now is the right time to start that conversation.

The Octagotech team, San Francisco · New York · Ahmedabad · Rajkot

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

The Octagotech team writes this newsletter from live Odoo engagements, with 20+ implementations over 5+ years. About Octagotech.

Getting ready for Q4?

30 minutes on your reorder rules, your POS setup, and what to tighten before November.

Book a discovery call

Tighten inventory and POS before November

The first call takes 30 minutes.

Or email sales@octagotech.com