Odoo automation

Runtara automates the operations work around Odoo: customer orders, supplier invoices and product data move into Odoo automatically, and your team handles only the exceptions. Our team has integrated Odoo for distributors.

01 / Workflows

What you can automate.

Customer orders into Odoo

Customer orders that arrive by email, PDF, EDI or API become Odoo sales orders, with exceptions held for a person.

How it runs: customer orders into odoo

Supplier invoice processing

Supplier invoices matched against purchase orders and receipts in Odoo, with variances held for approval before they are posted.

How it runs: supplier invoice processing

Product data and pricing

Supplier price changes from letters, spreadsheets or files go into Odoo price lists and items, with unclear changes held for review.

How it runs: product data and pricing

EDI with trading partners

Orders, invoices and ship notices exchanged with customers and suppliers over EDI or SFTP, connected to Odoo by our team.

How it runs: edi with trading partners

02 / Connection

How the connection works.

Runtara connects to Odoo through its API, over EDI, or by file exchange, whichever fits your setup and your trading partners. Our team scopes the connection with your Odoo administrator during implementation.

If Odoo runs on your own servers, Runtara needs network access to it, for example through a VPN. That is part of the access checklist that starts the two-week clock.

Each workflow step declares the connection it uses, and the runtime denies anything else. There is no custom code for your team to own or maintain.

03 / Approval

Exceptions wait for a person.

In the illustrative order PO-58213, five lines match the customer, items and contract prices. Line 04 is priced $26 above contract and is held. Inside sales approves the contract price, and the workflow creates the sales order in Odoo.

Everything else posts automatically. One query against the instance database returns the order, the match, the approval, and the ERP response.

04 / Availability

In every edition.

Odoo is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

05 / Questions

Common questions.

Has your team integrated Odoo before?

Yes. Our team has integrated Odoo for distributors, so the connection behind the workflow is work we have done before.

How long until it is live?

Live in two weeks once access is in place: API keys, system URLs and endpoints, credentials, the specs for your files and EDI documents, and network access for Runtara.

Is Odoo included in my plan?

Yes. Odoo is a standard integration, included in Cloud, Enterprise and the open-source engine. The connection and field mappings for your setup are scoped and quoted as part of implementing each process. EDI, SFTP, FTPS and SSH connections to it are premium.

Can a person approve before anything is written to the ERP?

Yes. A workflow holds an exception for approval and writes to Odoo only after the person decides. The run keeps the source, the decision, who made it, and the ERP response together.

Which other ERPs do you work with?

Our team has integrated QuickBooks, Business Central, Infor CSD/SX.e, Epicor Prophet 21, Epicor Eclipse. Other ERPs that expose an API, EDI or file exchange are scoped during implementation.

Bring your Odoo process.

Start with a paid pilot of one real process, such as order intake. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.