Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
A quote leaves Odoo and becomes a Pandadoc document somebody signs, so the version carrying a signature has to be the version the ledger will actually will actually bill from once the work is done.
Pandadoc documents are built from templates, and a template is a set of fields waiting for values. Send a quote from Odoo and the document is right. Change the quote afterwards and the document is not, because a signed document is a version of something rather than a live view of it. So a customer signs, the price moves, and nobody can say afterwards which figure they agreed to without opening two systems and comparing them line by line. Connecting Odoo and Pandadoc keeps the signed version and the billed version the same one, so nobody has to prove which was which.
DATA THAT FLOWS BETWEEN THEM
Quotations
Quote lines
Customer records
Document templates
Signature status
Signed documents
The Odoo quote a Pandadoc document was built from is recorded against it, so the figure a customer signed can be identified without comparing two systems by hand.
Changing a quote after a document has gone out supersedes it rather than editing it, so nobody ends up holding a signature against a price the business has since moved on from.
Templates carry the fields once, so a change to how a quote presents itself is made in one place instead of in each document somebody has built from an older copy.
Signature status travels back to the Odoo quote, so a salesperson knows whether a document has been signed without opening the document tool to go and look for themselves.
When an Odoo quote is ready, Alumio builds the Pandadoc document from the template you nominate with the quote lines already in place, so nobody assembles a document by copying figures across by hand from another screen.
If the Odoo quote changes after the document was sent, the previous version is superseded rather than quietly edited, so a customer cannot sign a figure the business has already moved on from, and both versions stay identifiable.
A completed signature updates the Odoo quote, so the order can be raised from a document that is known to have been signed rather than from somebody's recollection of a phone call that happened some time last week.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
What the document commits you to is the question that opens the next connection, and a signed quote is only the first of several. A contract repository is the common addition, because Pandadoc handles the signing and Odoo handles the billing, and neither is where somebody looks a year later for what was actually agreed. Alumio holds both connections, so the signed document reaches the place it will be needed from.
The template and its fields are settled first, because they are the integration. Alumio takes the Odoo quote lines and populates the Pandadoc template you nominate, then writes the signature status back when it completes. A quote that changes after sending supersedes the document rather than editing it, so versions stay distinguishable.
No, and the template is the integration rather than a presentation choice. Which Odoo fields land in which Pandadoc template positions is configured in Alumio, which is why a change to how a quote reads does not involve a developer. Where a document has to include a value Odoo derives rather than stores, the Code Transformer produces it at that step.
The one the document was built from, which is only knowable if it was recorded at the time. A Pandadoc document is a version rather than a live view, so a quote edited in Odoo afterwards leaves a signature attached to figures that no longer exist anywhere. Keeping the quote reference on the document, and superseding rather than editing, is what makes the question answerable at all.
The document version is what this turns on. Alumio records which Odoo quote each Pandadoc document was built from, so a signature arriving against a superseded version is flagged rather than accepted, alerts fire at once with the quote and the reason, retries run where configured, and unresolved documents stay listed, so nothing is billed quietly from a version nobody can identify.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
