Apps › Compliance and e-invoicing

EDIFACT EDI: ORDERS, INVOIC and DESADV

Each ORDERS file your retail customers send becomes a sales order, each posted invoice and validated delivery can go back as INVOIC and DESADV, and every file is kept as it came in or went out.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

Sales > EDI > Messages on the demo: inbound and outbound EDIFACT files, each with its direction, message type, document reference, the document it made or came from, and its status
Sales > EDI > Messages on the demo: inbound and outbound EDIFACT files, each with its direction, message type, document reference, the document it made or came from, and its status
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsInventory, Invoicing, Salesno Enterprise module
Price249 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.1.3bambooforge_edifact

61 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

How you use it

Three things you do with it

Flow 01

Set up a trading partner

Once per retail chain and company.

  1. Open Sales > EDI > Trading Partners and press New.
  2. Choose the customer, and enter their interchange ID and yours: usually the two GLNs, with qualifier 14.
  3. Choose the product field their codes are matched against, a warehouse, and whether to check prices and to confirm their orders automatically.
  4. Save: their ORDERS files can be read, and their invoices and deliveries sent.
Trading partner profiles on the demo, each with the customer, our interchange ID, theirs, the test flag and automatic confirmation
Flow 02

Receive an order

From your EDI gateway, through Odoo's external API.

  1. Your gateway hands the ORDERS file to the module (the method receive).
  2. The file is kept as an inbound message and read at once: a draft sales order for the buyer, one line per LIN, the buyer's order number as Customer Reference.
  3. Open the message and press Open Document to check the order.
  4. A file that fails goes to Error with the reason: fix the data and press Process Again.
An inbound ORDERS message on the demo: the buyer's order number, the sales order it became, the segment count, the file download and the interchange as received
Flow 03

Send an invoice or a despatch advice

Built in Odoo, handed to your gateway.

  1. Create a server action once that calls build_invoic on the selected invoices, and one that calls build_desadv on transfers.
  2. Run it on a posted customer invoice, or a validated delivery.
  3. The INVOIC or DESADV is kept as an outbound message, linked to its document.
  4. Download the.edi file from the message and hand it to your gateway.
An outbound INVOIC message on the demo: the invoice it was built from, the segment count, the file download and the interchange as written

Price and where to buy

249 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.