| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Sales (sale_management) • Invoicing (account) |
| Lines of code | 4396 |
| Technical Name |
nex_huengsberg_edi |
| License | See License tab |
| Website | https://nexigo.io/docs/huengsberg-edi |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Sales (sale_management) • Invoicing (account) |
| Lines of code | 4396 |
| Technical Name |
nex_huengsberg_edi |
| License | See License tab |
| Website | https://nexigo.io/docs/huengsberg-edi |
Hüngsberg EDI Connector
Connect the power of the Hüngsberg EDI-platform to Odoo with a structured, traceable workflow designed for daily operations, guided correction, and clean API visibility.
Built by Nexigo GmbH for teams that need reliable EDI processing without losing operational clarity.
CONTACT
To connect your EDI processes to Odoo contact us
If your EDI requirements extend beyond the current module scope, Nexigo can support implementation, process alignment, and customer-specific extensions.
IMPLEMENTATION PARTNER
Nexigo GmbH
WEBSITE LINK TO COPY
https://nexigo.io
Phone: +49 7243 / 35 88 5 35
Email: info@nexigo.io
Use the QR codes below for fast access on mobile devices.
Website QR
Scan to open the Nexigo website.
Contact Card QR
Scan to save the Nexigo contact card.
EDI PLATFORM PARTNER
Hüngsberg GmbH
WEBSITE LINK TO COPY
https://huengsberg.com
Phone: +49 811 9592 0
Email: info@huengsberg.com
Use the QR codes below for fast access on mobile devices.
Website QR
Scan to open the Hüngsberg website.
Contact Card QR
Scan to save the Hüngsberg contact card.
OPERATIONAL POSITIONING
More than XML exchange: a controlled sales workflow inside Odoo
The module is built around the actual operational path from incoming customer order data to validated sale order creation and confirmed ORDRSP feedback. Instead of pushing EDI processing outside the ERP, it keeps imports, decisions, errors, and communication status in one place.
Inbound endpoint for receiving Hüngsberg ORDERS XML directly in Odoo.
Structured validation for partners, GLNs, payment terms, products, quantities, and prices.
Guided correction flow before the sale order is created.
Full traceability across imports, sale orders, callbacks, and API traffic logs.
CORE CAPABILITIES
What the module delivers
Inbound ORDERS Processing
Hüngsberg sends XML to a dedicated Odoo endpoint. Each request creates a dedicated import record with the original payload and the business data extracted from it.
Validation in Odoo
The module checks buyer and delivery references, GLN assignments, payment terms, customer product codes, quantities, and price deviations before any order is generated.
Guided Correction
Missing master data can be resolved from the import flow itself, reducing disconnected manual work and preserving the original context.
Sale Order Creation
Valid imports can create sale orders automatically or manually, depending on the operating mode selected in configuration.
Outbound ORDRSP
Order responses can be sent back to the configured Hüngsberg endpoint when the linked sales workflow reaches the required state.
Technical Traceability
Inbound and outbound API calls are logged with payload and response visibility so operations and support can diagnose failures quickly and with context.
PROCESS FLOW
How the daily workflow runs
Receive the inbound order
Hüngsberg submits an ORDERS XML message to /huengsberg/edi/orders using the configured API key.
Create and analyze the import record
Odoo stores the incoming payload, extracts relevant data, and presents the import as a working document for review.
Validate and correct master data issues
Operators resolve missing partners, product mappings, payment terms, or pricing mismatches before proceeding.
Generate the sale order
Once validation succeeds, the sale order is created according to the selected automation behavior.
Send ORDRSP and retain full auditability
Odoo can return order response information to Hüngsberg and keep the communication trail available for later review.
CONFIGURATION
Implementation areas that matter before go-live
| Area | What you configure | Why it matters |
|---|---|---|
| Inbound Authentication | Generate and distribute the API key used by Hüngsberg to post ORDERS XML into Odoo. | Protects the endpoint and ensures only authorized inbound traffic is accepted. |
| Outbound Callback | Set the Hüngsberg callback URL plus the username and password used for HTTP basic authentication. | Required for successful ORDRSP transmission and controlled external communication. |
| Automation Behavior | Decide whether sale orders and ORDRSP messages are created automatically or remain user-controlled. | Lets the business align the EDI process with its own approval and exception-handling model. |
| Validation Rules | Configure duplicate handling and optional price deviation tolerance. | Prevents unstable imports and makes exception handling predictable. |
| Master Data Readiness | Maintain GLNs, partner roles, and customer product mappings before production traffic starts. | Clean master data reduces manual correction and improves straight-through processing. |
Implementation note: Stable EDI operations depend on business readiness as much as technical setup. The module supports guided correction, but high-quality partner and product data remain critical for reliable live usage.
OPERATIONS
Designed for the teams who run the process after go-live
Dashboard and Imports
- Central visibility into import volume, status, and current workload.
- Operational lists for filtering imports that require action.
- Persistent linkage between the EDI import and the resulting sale order.
Monitoring and Error Analysis
- Request and response visibility for inbound and outbound API traffic.
- Stored payload context for support and root-cause analysis.
- Clear status information for callback failures and communication problems.
Retry and Follow-Up
- Failed outbound callbacks can be retried through the configured background job behavior.
- Operators retain the import context even after the order is created.
- Process transparency supports support teams, consultants, and internal operations alike.
REQUIREMENTS
What should be in place
Platform
Odoo 19 with the required sales and communication modules available.
Dependencies
The module requires an active agreement with Hüngsberg in order to function. It serves as an extension to the standard Odoo functionality, providing additional features and integrations specific to the Hüngsberg EDI system.
Master Data
Partner GLNs, partner roles, and external product references should be prepared before production use.
External Coordination
The customer must align endpoint access, credentials, and return-channel expectations with Hüngsberg.
TECHNICAL SCOPE
Key implementation details
| Topic | Details |
|---|---|
| Inbound Endpoint | ORDERS XML is received on /huengsberg/edi/orders with the API key provided in the X-Api-Key header. |
| Outbound Communication | ORDRSP messages are sent to the configured Hüngsberg endpoint using HTTP basic authentication. |
| Data Retention in Process | Payload data, validation information, import status, linked order, and callback status remain available for review. |
| Multi-Company Awareness | Settings, imports, and traffic logs are designed around company-aware operation inside Odoo. |
| Supportability | API logs and import records provide the operational evidence needed for support and troubleshooting. |
LICENSE
Module license
This module is distributed under proprietary license terms. It should only be used according to the licensing terms shipped with the addon.
License & Terms of Use Hüngsberg Odoo EDI Connector 1. Subject of Use This license and terms of use govern the use of the software application “Hüngsberg Odoo EDI Connector” (hereinafter “App”). The App serves exclusively for the technical connection of an Odoo ERP system to the Hüngsberg EDI platform and does not itself provide any independent EDI functions. 2. Scope of License The App is provided for use free of charge. A simple, non-exclusive, non-transferable, and non-sublicensable license to use the App is granted. Use is permitted exclusively for the licensee’s own business purposes. 3. Purpose-Limited Use The App may only be used: - for connecting Odoo to the Hüngsberg EDI platform - in conjunction with an active and valid usage agreement for the Hüngsberg EDI Services In particular, the following is prohibited: - use of the App for connection to third-party EDI systems or EDI providers - bypassing or replicating the Hüngsberg EDI platform - use of the App as a general or standalone EDI connector 4. Distinction Between App vs. EDI Service The App does not contain any EDI engine, format logic (e.g. EDIFACT, XML), partner profiles, or communication protocols. All EDI functions, in particular: - transformation - validation - transmission - monitoring - archiving are provided exclusively via the Hüngsberg EDI platform. Use of the Hüngsberg EDI platform is subject to a fee and is not part of this App license. 5. Availability and Operation The App is provided “as is”. There is no entitlement to availability, further development, or adaptation of the App. Support, maintenance, and operation are provided exclusively within the framework of the agreed EDI platform services. 6. Warranty and Liability No warranty is provided for the App made available free of charge. Hüngsberg shall only be liable for damages resulting from intentional or grossly negligent conduct. Liability for indirect damages, consequential damages, or loss of profit is excluded to the extent permitted by law. 7. Changes and Further Development Hüngsberg reserves the right to: - further develop the App technically - adjust the scope of functions - discontinue providing the App in whole or in part 8. Termination of Use Hüngsberg is entitled to prohibit use of the App if: - it is used contrary to the agreed terms of use - there is no valid contract for the use of the Hüngsberg EDI platform - misuse is identified 9. Final Provisions The law of the Federal Republic of Germany shall apply. Place of jurisdiction shall – where permissible – be the registered office of Hüngsberg. Should individual provisions be ineffective, the validity of the remaining provisions shall remain unaffected.
Please log in to comment on this module