Integrations
STRYKE and Odoo
Odoo has an external API, and STRYKE uses it with an API key your shop makes for one of its users. A customer PO becomes a confirmed sales order with its customer; vendor invoices go to your books.
How the connection works
By Odoo's external JSON-2 API, with an API key made for one of your users.
- Self-hosted Odoo, Odoo.sh, and Odoo Online on a plan that allows the external API
- Nothing is saved until Odoo accepts the key, names the company you typed and lets STRYKE read its partners
- Before each order is written, STRYKE asks Odoo whether that PO is already on a sales order
- One Odoo company connects to one STRYKE shop
What a PO becomes in Odoo
A confirmed sales order, the way your team would enter it.
- A sales order with the customer PO as its Customer Reference, lines by your products' internal references, quantity, price and date, confirmed
- A customer Odoo does not have yet is created as a partner and marked as STRYKE's, so it is easy to find and check
- The order's Source Document names STRYKE and the document, and the original PO is attached
- A change order changes the confirmed order's lines in one write
- Bills, invoices and payments go to your books, not to Odoo
What to have ready
Four things, entered once in Settings › Connections.
- Your Odoo server's address: https://your-company.odoo.com, or where you host it
- The database name, only when one server holds several
- An API key from Preferences › Account Security, for a user who can read and write sales and purchases
- The company name, exactly as Odoo shows it
Read the vendor's own pages
Odoo S.A. publishes these; they are its pages, not ours.
Starting at $500 a month*
Every document, every system you connect. No seats, no per-system fees, month to month. *Plans scale with your document volume. How pricing works.
