A plant on Odoo keeps Odoo as its record. Morsa, the AI that operates the factory for you, reads the manufacturing orders, work orders, purchase orders, receipts, transfers and sales orders that Odoo exposes through its documented External API, or through automation-rule webhooks, or through a database read on a self-hosted install, connects them to what people say in the plant’s group chats and email, and handles what happens when reality moves off the plan. Which of those paths is open depends on the plant’s Odoo plan and edition. This page quotes Odoo’s own documentation on each, because the answer is not the same for every Odoo plant. Odoo is one of the systems shown on Morsa’s integration flow, alongside SAP Business One, Business Central, Zoho, QuickBooks and spreadsheets.
In this guide
What does Odoo Manufacturing do well, and where is the gap?
Which Odoo plan and edition does the integration need?
Which Odoo interfaces does Morsa use?
Which Odoo records does Morsa read, and what does it do with each?
What does a caught shortage look like on an Odoo plant?
Does Morsa write to Odoo?
Do Odoo 19’s AI agents cover this?
Where does Morsa run alongside Odoo?
What should a plant check before starting?
What changed at plants running Morsa above their ERP?
Sources, Changelog
What does Odoo Manufacturing do well, and where is the gap?
Odoo’s manufacturing app is broad for its price. Odoo’s own page: “MRP + MES + PLM + Quality + Shop Floor + Maintenance. All you need on one single platform,” with “finite capacity planning,” a master production schedule that “is perfect for your S&OP meeting,” lot and serial traceability, and a Shop Floor app on tablets (Odoo Manufacturing). The user documentation covers bills of materials, one- to three-step manufacturing, work centers, work order dependencies, the master production schedule, scrap, backorders, subcontracting and OEE (Odoo 19 documentation, Manufacturing). Odoo 19, released September 2025, added a Gantt view for manufacturing orders and an editable MO deadline (Odoo 19 release notes).
The gap is the same as on every ERP. Odoo records that a manufacturing order’s deadline moved; it does not tell the dispatch planner that Friday’s customer order moved with it, does not read the supplier’s email that caused it, and does not chase the purchasing head at 9:15 p.m. in the group where the purchasing head actually reads messages. The practitioner rule quoted on manufacturing ERP software is “very little customization, just config”. Morsa follows it: nothing is built inside Odoo.
Which Odoo plan and edition does the integration need?
This is the part most Odoo pages skip, and it decides how Morsa connects. Three of Odoo’s own statements matter.
Question | Odoo’s own answer | What it means |
|---|---|---|
Which plans have the External API? | “Access to data via the external API is only available on Custom Odoo pricing plans. Access to the external API is not available on One App Free or Standard plans.” (Odoo 19 External API docs) | An Odoo Online plant on the Standard plan has no API for Morsa to call. Custom is $61.00 per user per month on a yearly term, list $76.20 (Odoo pricing) |
Which edition has Shop Floor, Quality and Studio? | Odoo’s editions page marks Manufacturing (MRP) as available in Community, and Shop Floor, Control Panel, Scheduling, Quality, PLM and Studio as Enterprise only (Odoo, Compare Editions) | A Community plant has BoMs and manufacturing orders but no Shop Floor record and no Studio, which is where automation-rule webhooks are built |
Can a plant host Odoo itself? | The Custom plan lists “Odoo Online / Odoo.sh / On-premise” and lets a plant “Download Odoo Enterprise and host it yourself”; Community is open source under LGPLv3 (Odoo pricing; Odoo LICENSE, 19.0 branch) | A self-hosted plant, Community or Enterprise, can also give Morsa a direct database read, which needs no API plan at all |
So the map is: Odoo Online Standard, no API, Morsa reads exports and the group chats until the plant moves to Custom; Odoo Online Custom or Odoo.sh, the External API and Studio webhooks; self-hosted, the API, webhooks where Studio exists, or a database read. Morsa works in all three cases; what it can read on day one differs.
Which Odoo interfaces does Morsa use?
Three, all documented by Odoo.
The External API. In Odoo 19 this is the JSON-2 API: “Part of the Models API is easily available over HTTP via the /json/2 endpoint,” called by posting “a JSON object at the /json/2/<model>/<method> URL” with “An API key must be set in the Authorization request header, as a bearer token” (Odoo 19 External API docs). Odoo’s key rules shape how Morsa is set up: “it is not possible to create keys that last for more than three months. This means that long lasting keys must be rotated at least once every three months,” and “All calls to the JSON-2 endpoint run in their own SQL transaction.” For plants on Odoo 18 or earlier, the older XML-RPC and JSON-RPC endpoints still work, but Odoo states they “are scheduled for removal in Odoo 22 (fall 2028)” and that “All three services are deprecated.” Morsa reads through whichever the plant’s version supports.
Automation-rule webhooks. Odoo’s Studio documentation describes an action that “is used to send a POST API request with the values of the selected Fields to the webhook URL specified in the URL field,” and an “External” trigger to “Trigger automated actions based on a specific event in an external system or application using a webhook” (Odoo 19 documentation, Automation rules). This lets Odoo push a changed manufacturing order to Morsa the moment it changes, instead of Morsa polling. Odoo’s own caution applies: “It is highly recommended to consult with a developer, solution architect, or another technical role when deciding to use webhooks.”
A database read. On a self-hosted install, a read-only database role on the Odoo PostgreSQL database. Not an Odoo API, so no plan requirement, and read-only by construction.
Which Odoo records does Morsa read, and what does it do with each?
Odoo’s names for the records, in the plain terms its documentation uses, and what Morsa does with each.
Odoo record | What it holds | What Morsa does with it |
|---|---|---|
Manufacturing order | The order to make: product, quantity, deadline, components, work orders | Watches the deadline and component availability against the sales orders behind it; when a component is short or the “Late Availability” condition Odoo 19 filters on appears, works out which customer orders move |
Work order | One operation at one work center, with its status and dates | Reads the status Odoo 19 lets users edit; a work order that has not started by its planned time is a signal |
Purchase order | What was ordered from a supplier, with the expected date | Compares the expected date with what the supplier actually said in email or a group, and chases purchasing before the date |
Receipt (incoming transfer) | What actually arrived | Closes a material job on the receipt, not on a “done” message |
Internal transfer | Material moved between locations | Confirms staged material reached the line the plan assumed |
Sales order | The customer commitment and its delivery date | The consequence side: which customer order a shortage or a late MO puts at risk |
Bill of materials | Components per product, and Odoo 19’s default batch size | Names the parts a shortage affects |
Master production schedule | Planned demand and replenishment by period | The plan Morsa compares reality against |
Odoo’s documentation names each of these as a feature of the manufacturing, inventory and purchase apps (Odoo 19 documentation, Manufacturing; Odoo 19 release notes). Odoo 19’s “Late Availability filter on transfers and manufacturing orders to view sales orders with products expected to arrive after the delivery date” is, in one filter, the exact condition Morsa watches for, and then acts on.
What does a caught shortage look like on an Odoo plant?
The pattern from the J4S customer story, with Odoo as the ERP.
9:10 p.m., Stores group. The stores in-charge posts that 6 mm clear stock is enough until Wednesday. Nobody replies.
9:10 p.m., Morsa. Reads the message, reads the open sales orders and manufacturing orders in Odoo that consume that component, finds three on Line 2 dispatching Thursday and Friday.
9:11 p.m., Purchase group. Morsa creates “Cover 6 mm clear for Line 2 orders”, owner the purchasing head, due Tuesday noon, and posts it with the three orders and their delivery dates.
Tuesday 3:20 p.m. Purchasing posts the supplier’s confirmation for Wednesday morning. Morsa moves the due date and notes who moved it and why. Within the plant’s rules, the purchase order’s expected date in Odoo is updated; otherwise Morsa asks the owner to do it.
Wednesday. The receipt is validated in Odoo. The job closes on the receipt.
Does Morsa write to Odoo?
Only within the rules the plant approves, and Odoo stays the record. Reading is the default. Typical allowed writes are an expected-date change on a purchase order once the supplier has confirmed in writing, a note in the chatter of a manufacturing order, and an activity assigned to the owner. Consequential actions, such as rescheduling manufacturing orders or committing to a supplier, follow the customer’s approval rules and go to a named person. Odoo’s own transaction model helps here: each JSON-2 call “is committed in case of success and is discarded in case of error,” so a refused write leaves nothing behind. Every write is attributed and reversible.
Do Odoo 19’s AI agents cover this?
Not this job, by Odoo’s own description. Odoo 19 added “Agents: Chat with AI agents that can learn from your documents and perform actions,” “AI agent database queries: Internal users can now chat with an AI agent to query their own database records,” AI fields, an “Ask AI” search that “transforms it into an Odoo domain,” and the option to “Use your own Gemini account as your Odoo AI provider” (Odoo 19 release notes). These act on Odoo’s own records for internal users who are logged in.
Morsa’s job starts where those stop: with the supplier’s email, the stores message at 9:10 p.m. and the people who will never have an Odoo login. The two are complementary. A plant on Odoo 19 Enterprise can use Odoo’s agents for questions inside Odoo and Morsa for the coordination across Odoo, the floor and the group chats. The wider set of agents is compared on best AI agents for factory operations.
Where does Morsa run alongside Odoo?
Wherever Odoo does. Odoo Online is Odoo’s own cloud; Odoo.sh is its hosting for custom developments, with hosting “not included” in the Custom plan price; on-premise is a download of Odoo Enterprise or the open-source Community edition (Odoo pricing). Morsa runs in its own cloud, in the plant’s private cloud, or fully on-premise with the AI models and databases inside the plant. An on-premise Odoo and an on-premise Morsa can share a network with no plant data leaving the perimeter, which is the configuration for ITAR, CMMC and defense suppliers.
What should a plant check before starting?
Five questions, each answerable in a day.
Which Odoo version? 19 uses the JSON-2 API; 18 and earlier use XML-RPC or JSON-RPC, which Odoo has deprecated with removal planned for Odoo 22 in fall 2028.
Which plan? On Odoo Online, the External API needs the Custom plan. Odoo’s pricing FAQ: “The custom plan is for companies that want to manage multiple companies on a single database and that need to customize Odoo through Odoo Studio, custom developments or through the API.”
Which edition? Community has Manufacturing (MRP) but not Shop Floor, Quality or Studio. Morsa reads what exists.
Who owns the API key? Odoo keys expire within three months at most, so someone owns rotation. Odoo notes that “By default, programmatic API key management is restricted to users with the Settings administration access right.”
Where do the supplier emails and the group chats live? Odoo holds the expected date; the supplier’s real date is usually in an inbox. Morsa needs both.
Odoo publishes its prices: Standard $24.90 and Custom $49.00 per user per month billed yearly, or $31.10 and $61.10 billed monthly, against list prices of $31.10 and $61.00 yearly ($38.90 and $76.20 monthly), with the discount “valid for 12 months, for initial users ordered” (Odoo pricing; prices as served in US dollars on 21 September 2026). Morsa is priced per plant, not per user, with a guarantee; see how Morsa is priced.
What changed at plants running Morsa above their ERP?
J4S, a 120-person glass plant, was onboarded in two days: Morsa joined the Production, Stores, Purchase and Dispatch groups and connected to the ERP on day one. On-time completion of operational commitments rose from about 30% to about 75% in the first four weeks, across about 900 commitments, with no new software. Production Head Anil Kohli: “Our people don’t have to learn any new software. The chasing happens in the group chats they already use.” At JRG Automotive, Morsa identified 5 of 8 production-stopping material shortages early enough to act and saved the plant $2 million.
Bring one problem from your plant. We’ll show you how Morsa would have caught it, against your Odoo. Book the call with Vedant.
Sources
Odoo, External JSON-2 API, Odoo 19.0 developer documentation, https://www.odoo.com/documentation/19.0/developer/reference/external_api.html (fetched 20 September 2026)
Odoo, Automation rules, Odoo 19.0 documentation, Studio, https://www.odoo.com/documentation/19.0/applications/studio/automated_actions.html (fetched 20 September 2026)
Odoo, Manufacturing, Odoo 19.0 documentation, https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/manufacturing.html (fetched 20 September 2026)
Odoo, Open-source Manufacturing (MRP) software, https://www.odoo.com/app/manufacturing (fetched 20 September 2026)
Odoo, Odoo 19 Release Notes, September 2025, https://www.odoo.com/odoo-19-release-notes (fetched 20 September 2026)
Odoo, pricing, https://www.odoo.com/pricing (fetched 20 September 2026; prices are localized and were served in US dollars)
Odoo, Compare Editions, https://www.odoo.com/page/editions (fetched 20 September 2026)
Odoo, LICENSE file, 19.0 branch, https://raw.githubusercontent.com/odoo/odoo/19.0/LICENSE (fetched 20 September 2026)
Morsa, J4S customer story, /customers/j4s; manufacturing ERP software, /guides/manufacturing-erp-software
Changelog
24 September 2026: Odoo prices re-read. Billed yearly, Standard is $24.90 and Custom $49.00 per user per month for the first 12 months (lists $31.10 and $61.00); billed monthly they are $31.10 and $61.10 (lists $38.90 and $76.20). Every current Odoo price on this page now names its billing term.
21 September 2026: Odoo’s published prices corrected to the ladder read on 21 September 2026, Standard $31.10 and Custom $61.00 per user per month on a yearly term against $38.90 and $76.20 list. The draft carried $24.90 and $49.00, the rates before Odoo moved both tiers up one step.
21 September 2026: first draft. Every Odoo fact quoted from Odoo’s documentation, pricing and editions pages fetched on 20 September 2026; the plan-and-edition table added because it decides the integration path.
