Skip to main content

Integration guideSeal API and Scripts

Odoo

Exchange inventory, purchase orders and supplier information.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

Odoo and SealSeal API and Scripts

Seal reads
Inventory, purchase-order and supplier records
Writes back
The inventory and purchase records you agree
Source of truth
Agreed when scoped
Set up
Scoped with your team
Neil › Material reconciliation
draft

Reconcile the material records with our batch evidence.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Inventory, purchase-order and supplier records
Returns
  • Quantities, identifiers and unmatched records
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Odoo: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Exchange inventory, purchase order and supplier information between Odoo and Seal through a connection set up with Seal’s API or Scripts, for receiving inspection and material qualification. Agree which system owns each record before scoping the transfer.

Connection setup and permissions

Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.

Related blueprints

2Exchange inventory and purchase records with Odoo’s JSON-2 API.

Route

Odoo’s current external API, JSON-2, posts to a model and method URL with a bearer API key. It replaces XML-RPC and JSON-RPC, whose services are scheduled for removal in Odoo 22.⁠¹² External API access is only on Custom Odoo plans, and the models and fields available differ by database, listed on its /doc page.⁠¹

Record identity

search and create return database record IDs. A lot identifies a batch of products; lot tracking is set per product, and lots can be assigned on receipt.⁠²³

Units

A product has an inventory unit and a purchase unit in the same category, and Odoo converts the purchase unit to the inventory unit on receipt.⁠⁴

Revisions

Records keep a last-updated time in write_date. Each JSON-2 call is its own transaction, so another user’s change can land between two calls.⁠⁵¹²

When it fails

A call fails
A JSON-2 call commits on success and is discarded on error, returning a 4xx or 5xx status with a JSON error body.⁠¹ Retry the whole call, and read the record back before the next one.
A quantity is out by a factor
The purchase unit is converted to the inventory unit on receipt.⁠⁴ Map a unit with every quantity, and compare receipts in Seal against the inventory unit.

Check one record

Receive one lot of a raw material in a test database. Seal should hold the Odoo record ID, the lot and the quantity in the inventory unit. Change the receipt in Odoo and confirm write_date moved and Seal shows the change on its next read.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →

References

  1. 1Odoo 20: external JSON-2 API.
  2. 2Odoo 20: external RPC API.
  3. 3Odoo 20: lot numbers.
  4. 4Odoo 20: units of measure.
  5. 5Odoo 20: ORM reference.