| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Purchase (purchase) • Invoicing (account) |
| Lines of code | 518 |
| Technical Name |
neurona_purchase_order_xml |
| License | OPL-1 |
| Website | https://neurona.cloud |
Neurona Purchase Order XML
Publish purchase orders as structured XML without pretending to become a full EDI stack.
Built for teams that already work with standard Odoo purchase orders and need a machine-readable supplier output, a controlled download path and a clean XML attachment inside the native send flow.
Standard purchase orders are readable for people, not always for supplier systems.
Many companies still send PDFs or free-form emails and leave suppliers to re-enter the data manually. That creates avoidable friction, poor traceability and repeated custom work when a supplier needs structured purchase input.
Neurona Purchase Order XML adds a narrow, reusable export layer on top of native Odoo purchase flow.
The module generates a versioned XML document from the confirmed purchase order, keeps that output under control when the order changes, and injects the current XML into the standard send wizard.
Structured supplier output with minimal operational disruption
Versioned XML publication
Generates a current XML when the purchase order is confirmed and keeps publication history instead of overwriting traceability.
Safe standard send flow
Reuses the native purchase email wizard and adds the XML attachment there instead of inventing a parallel outbound process.
Controlled narrow scope
Keeps v1 focused on one-way export, one public XML dialect and one clear purchase use case that is actually validated.
A disciplined export flow inside standard purchasing
This module extends Odoo Purchase. It does not replace the standard purchasing workflow or claim network-level EDI behavior.
Enable the vendor
Activate purchase XML on the supplier and select the public adapter used for export.
Confirm the order
The module creates a current XML document from a canonical snapshot of the purchase order.
Review or download
Users can inspect the XML history from the purchase order and download the current attachment directly from Odoo.
Send with the native wizard
If the order changed, the XML is regenerated and injected into the standard purchase email wizard as an application/xml attachment.
What v1 includes
- vendor-level activation for purchase XML export
- canonical snapshot plus adapter-based XML rendering
- generation on confirmation, stale detection and controlled regeneration
- manual download and XML injection into the standard purchase send flow
What this module does not claim
- full EDI network integration or PEPPOL behavior
- supplier portal URLs or arbitrary XML designers per supplier
- bidirectional acknowledgements, ASN or invoice exchange
Built for Odoo 18 purchase flows
Standard module install
Install it as a normal backend addon on top of Odoo Purchase with Mail available.
Narrow vendor setup
Enable the vendor, assign the supported adapter and keep product and order data clean before operational rollout.
Best fit
Businesses that need a structured supplier-facing purchase export without opening a broader EDI project.
Clear scope before broader automation
This product solves one supplier-output pattern well. It should not be sold as a universal XML engine or a complete B2B integration platform.
Only one public adapter is supported in v1: neurona_po_xml_v1.
Output quality still depends on coherent vendor, product and purchase order data in Odoo.
This first commercial release does not include portal URLs, inbound confirmations, ASN flows, invoice exchange or exhaustive multi-company validation.
A tighter supplier export layer for native purchasing
Neurona Purchase Order XML turns a repeated B2B requirement into a narrow, sellable module with verified behavior inside standard Odoo Purchase and a public scope that stays honest about its limits.
Built by Neurona · Odoo Lab
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module