How-toOdoo (Manufacturing / MRP)Manufacturing / External API

Odoo Manufacturing API: Working with mrp.production and mrp.bom

Question

odoo manufacturing api

Also searched as

odoo mrp.production api
odoo create manufacturing order xmlrpc
odoo bom api

Short answer

Odoo exposes manufacturing through its normal external API: the models mrp.bom (bills of materials), mrp.production (manufacturing orders) and mrp.workorder, called via XML-RPC or JSON-RPC with execute_kw. Authenticate, search and read the BOM, create a manufacturing order, then call its action methods such as action_confirm to move it through states. There is no separate manufacturing API.

Applies to: Odoo Manufacturing (MRP) in recent versions, Community and Enterprise. Field names and behaviour change between versions, so check your model definitions through the Technical menu or fields_get.

Create and confirm a manufacturing order over the API

1Authenticate to the common endpoint with database, login and password or API key, and keep the returned user id.
2Look up the product with search_read on product.product, and read the BOM with search_read on mrp.bom filtered by product_tmpl_id.
3Read the BOM lines from mrp.bom.line using the BOM id, to see components and quantities.
4Create the manufacturing order with create on mrp.production, giving product_id, product_qty, product_uom_id and bom_id.
5Call action_confirm on the new order to confirm it, which creates the stock moves for components and finished product.
6Check availability and state by reading state, reservation_state and move_raw_ids.
7To finish, set the produced quantity and call button_mark_done. Be ready for it to return a wizard action instead of finishing, if confirmation is needed.

A worked example in Python

This uses the standard xmlrpc.client library. Replace the connection values with your own. Test on a copy of the database, since creating and confirming orders reserves stock.

import xmlrpc.client
url, db, user, key = 'https://odoo.example.com', 'mydb', 'api@example.com', 'API_KEY'
common = xmlrpc.client.ServerProxy(url + '/xmlrpc/2/common')
uid = common.authenticate(db, user, key, {})
m = xmlrpc.client.ServerProxy(url + '/xmlrpc/2/object')

def call(model, method, *args, **kw):
    return m.execute_kw(db, uid, key, model, method, list(args), kw)

prod = call('product.product', 'search_read', [['default_code', '=', 'FG-100']], fields=['id', 'uom_id'], limit=1)[0]
bom = call('mrp.bom', 'search_read', [['product_tmpl_id.default_code', '=', 'FG-100']], fields=['id'], limit=1)[0]
mo_id = call('mrp.production', 'create', [{'product_id': prod['id'], 'product_qty': 10, 'product_uom_id': prod['uom_id'][0], 'bom_id': bom['id']}])
call('mrp.production', 'action_confirm', [mo_id])
print(call('mrp.production', 'read', [mo_id], fields=['name', 'state', 'reservation_state']))

States and methods to know

A manufacturing order moves through draft, confirmed, in progress, to do, done and cancel states, although labels vary by version. The action methods are what the buttons on the form call, for example action_confirm, button_plan for work orders, button_mark_done, and action_cancel.

Some of those methods return a dictionary describing a wizard, for example a warning about consumption or an immediate production prompt. An integration must check the return value, and either handle the wizard model or set quantities first so the wizard is not needed.

Practical advice for integrations

Use fields_get on mrp.production to see what fields your version supports, and read only the fields you need. Avoid reading every field on large orders.

For many records, batch calls rather than one request per record. Use an API key for a dedicated integration user with only manufacturing rights, so you can revoke it without affecting people.

Odoo's external API is documented by Odoo, and JSON-RPC and XML-RPC are both supported. Check which one your version recommends, since newer releases have been evolving the external API.

Try it here, free

Odoo XML-RPC BOM Export Python Script Generator

Open full tool

Fill in your Odoo URL, database and filters to get a ready Python script that exports BOMs and component lines to a CSV file.

Fill in

Odoo URL

Database name

BOM type

Max BOMs to export

Output file

Generated code

Download:

Python script

import csv
import getpass
import xmlrpc.client

URL = 'https://mycompany.odoo.com'
DB = 'mycompany'
USER = 'api.user@example.com'
API_KEY = getpass.getpass('Odoo API key: ')

common = xmlrpc.client.ServerProxy(URL + '/xmlrpc/2/common')
uid = common.authenticate(DB, USER, API_KEY, {})
if not uid:
    raise SystemExit('Authentication failed: check database, login and API key')

models = xmlrpc.client.ServerProxy(URL + '/xmlrpc/2/object')

boms = models.execute_kw(
    DB, uid, API_KEY, 'mrp.bom', 'search_read',
    [[['type', '=', 'normal']]],
    {'fields': ['id', 'product_tmpl_id', 'product_qty', 'type', 'bom_line_ids'], 'limit': 500}
)

line_ids = [lid for b in boms for lid in b['bom_line_ids']]
lines = models.execute_kw(
    DB, uid, API_KEY, 'mrp.bom.line', 'read',
    [line_ids],
    {'fields': ['bom_id', 'product_id', 'product_qty', 'product_uom_id']}
)
lines_by_bom = {}
for ln in lines:
    lines_by_bom.setdefault(ln['bom_id'][0], []).append(ln)

with open('odoo_bom_export.csv', 'w', newline='', encoding='utf-8') as f:
    w = csv.writer(f)
    w.writerow(['bom_id', 'parent_item', 'parent_qty', 'component', 'component_qty', 'uom'])
    for b in boms:
        for ln in lines_by_bom.get(b['id'], []):
            w.writerow([b['id'], b['product_tmpl_id'][1], b['product_qty'], ln['product_id'][1], ln['product_qty'], ln['product_uom_id'][1]])

print('Exported', len(boms), 'BOMs and', len(lines), 'lines to odoo_bom_export.csv')

Create an API key in your Odoo user preferences under Account Security and use it in place of the password. Field names such as product_uom_id are correct for current Odoo versions; verify them with fields_get on older releases. Odoo Online and Odoo.sh allow the external API, but limits may apply to bulk calls.

Want this export scheduled and reconciled?

Optional: ask an expert to review your BOM data and automate the export.

Optional. The tool and every export work without this. No spam.

Common pitfalls

!Writing stock moves directly instead of using the order methods.
!Ignoring the wizard dictionary returned by button_mark_done.
!Using an admin account for the integration.
!Testing on production, so reservations pile up.
!Assuming field names are the same across versions.
!Creating orders without a BOM and wondering why components are missing.

How an ERP-grounded AI assistant handles this

Read access to mrp.production and mrp.bom is a good fit for a grounded assistant that answers which manufacturing orders are late or blocked on components. Writes such as confirming an order should go through a human approval step. Hosting the model on-prem keeps BOMs and production data inside your network.

See ERPray

Frequently asked questions

Does Odoo have a manufacturing API?

It uses the general external API (XML-RPC and JSON-RPC) with manufacturing models such as mrp.production and mrp.bom, rather than a separate API.

How do I create a manufacturing order via API?

Call create on mrp.production with product, quantity, unit of measure and BOM, then call action_confirm.

How do I read a BOM?

Search mrp.bom for the product, then read mrp.bom.line records for the BOM id to get components and quantities.

Why does button_mark_done not finish the order?

It may return a wizard action, such as an immediate production or consumption warning. Handle that wizard or set quantities first.

How-to

Odoo External API: Authenticate and search_read with XML-RPC and JSON-RPC

Call the Odoo external API by authenticating against /xmlrpc/2/common to get a user id, then calling execute_kw on /xmlrpc/2/object with the database, uid, password or API key, model name, method and arguments. If authenticate returns False, the database name, login, or API key is wrong, or two-factor is enforced for that user.

Error fix

Odoo Manufacturing Order: Components Not Available or Will Not Reserve

An Odoo manufacturing order stays in Confirmed with components marked Not Available when stock.move lines for the raw materials cannot be reserved from the quantity actually sitting in the MO's source location. The usual causes are stock in the wrong location, stock already reserved by another document, lot or tracking mismatches, and a unit of measure difference between the BoM and the product.

How-to

Odoo Reordering Rule Not Creating Manufacturing Orders: Causes and Fixes

Odoo creates a manufacturing order from a reordering rule only when the rule's forecast quantity falls below its minimum, the product has the Manufacture route with an active BoM, and the replenishment scheduler actually runs. Check the rule's route and warehouse, the product's forecast, the BoM, and the scheduler cron, in that order.

How-to

How to Create a Generic Inquiry in Acumatica

Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.

Error fix

Fix Odoo AccessError: You Are Not Allowed to Access Records

Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.

How-to

How to Void a Check in Sage 100

Sage 100 voids checks through Accounts Payable > Main > Check and Payment Voiding. Select the bank code, choose the check number, and Sage reverses the Cash Disbursements Journal entry and reopens the invoice it paid. A check that already cleared in Bank Reconciliation or falls in a closed period needs an extra step before it can be voided cleanly.

AI for ERP

AI for Odoo Manufacturing That Reads Your Own Database, Not a Vendor's Cloud

Add grounded, natural-language AI to Odoo Manufacturing without sending MRP, BoM, or work order data to a public model. On-prem or private cloud, ORM-native.

AI for ERP

AI Agents for ERP, Running On-Prem

A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.

Stuck on Odoo (Manufacturing / MRP)?

Talk to engineers who work inside Odoo (Manufacturing / MRP) every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineer Browse ERP Help

All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software

OdooWhat Odoo is, how its open-source Community and Enterprise editions differ, how the manufacturing apps and XML-RPC API work, and which alternatives to compare.

Odoo Manufacturing API: Working with mrp.production and mrp.bom

Create and confirm a manufacturing order over the API

A worked example in Python

States and methods to know

Practical advice for integrations

Fill in

Python script

Want this export scheduled and reconciled?

Common pitfalls

How an ERP-grounded AI assistant handles this

Frequently asked questions

Related

Odoo External API: Authenticate and search_read with XML-RPC and JSON-RPC

Odoo Manufacturing Order: Components Not Available or Will Not Reserve

Odoo Reordering Rule Not Creating Manufacturing Orders: Causes and Fixes

How to Create a Generic Inquiry in Acumatica

Fix Odoo AccessError: You Are Not Allowed to Access Records

How to Void a Check in Sage 100

AI for Odoo Manufacturing That Reads Your Own Database, Not a Vendor's Cloud

AI Agents for ERP, Running On-Prem

Stuck on Odoo (Manufacturing / MRP)?

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software

Fill in

Python script

Want this export scheduled and reconciled?