You decide when
Reviewed in the discovery session and turned on when you authorize it, not before.
Odoo
Your counter answers, your Odoo finds out.
Your customers write by email, call the counter or send a text. Peaking answers with your Odoo catalog, your price lists and your real availability, and leaves the quote and the order created in your Odoo, with their own numbers.
With your Odoo
Your Odoo current, with no extra work.
Every answer goes out with that customer price list and with what is on the shelf today, exactly as it stands in Odoo.
When the customer confirms, the sale is already in your Odoo. Nobody types it again.
Your customer gets a quote at midnight off your Odoo data, and in the morning your team has the sale.
Your specialists stop searching and keying, and spend the day closing.
The walkthrough
From the customer message to the order written.
What happens at each step, with your system.
Understood
Your customer is recognized with their history, without repeating who they are.
Found
The option you actually have, not the one that ran out.
Quoted
On that customer price list, with no keying errors.
Written
The sale written into your Odoo without anyone typing it.
Ready
Your customer knows when their order arrives.
How it connects
It turns on when you say so.
Nothing gets connected without your sign off, and Peaking is already operating on its own catalog before that.
Connected in stages
Read first, write second. Each stage turns on once the previous one is producing a result.
Isolated environment
Every customer runs in its own environment, and your data is yours.
Running from day one
Peaking answers and quotes from the first day, before touching Odoo.
See it run on your own catalog.Peaking shows up to the session already working with your products, so you see the result before you decide.
The Odoo fact sheet
What your systems team will ask.
Verified against Odoo documentation.
The official Odoo external API over XML-RPC and JSON-RPC, reaching the same models the interface itself uses: product.template, product.pricelist, stock.quant, res.partner, sale.order and sale.order.line.
An Odoo user with an API key, scoped by the access rights and record rules you define for that user.
Odoo Online, Odoo.sh or your own server. Peaking works the same either way, and the connection route is decided in the discovery session.
An integration user with an API key and a scoped role. Access rights over products, pricelists, stock, partners and sales orders. HTTPS access to your instance, or a connector on your server if it runs on your network.
Start today. Connect when you decide.
Peaking answers, quotes and writes from day one. Once you authorize it, the quote and the order are written into your Odoo.
Proof
Four operations running on Odoo.
Preguntas
What people with Odoo ask first.
Does it work with our Odoo version?
The external API has been stable across versions for a long time, and in the discovery session we check your version, your installation and which modules you have, then tell you what is connected on day one and what is not.
Odoo Online, Odoo.sh or self hosted?
All three. On Odoo Online and Odoo.sh it connects over HTTPS to your instance. On your own server, a local connector talks to Odoo and goes out encrypted, without exposing your database.
What permissions does it need?
An integration user with an API key and a scoped role, with access to products, pricelists, stock, partners and sales orders. Not an administrator credential.
Do we have to change how we work in Odoo?
No. Odoo stays exactly as it is, with your price lists, your warehouses and your terms. Peaking works with that, not on top of it.
Can we start before connecting Odoo?
Yes, and that is the recommended way. Peaking answers and quotes on its own catalog from day one, so you see the result before your systems team is asked for anything.
You've got this.
Peaking shows up to the session already running on your catalog, so you watch one of your own requests land in your Odoo.