OdooWiki OCA HUB

Voxel sale order

edi_voxel_sale_order_import folder_open OCA/edi open_in_new
Sale License: AGPL-3

This module allows you to import sales orders from Voxel. Imports are queued in jobs running in the background.

auto_awesome What this module does

AI-generated from the code · Odoo 13.0

Automatically imports sales orders from Voxel into Odoo. Orders are fetched in the background every 10 minutes and created as quotations with customer, delivery address, products, quantities, discounts and taxes.

This module connects Odoo Sales with the Voxel EDI platform so that sales orders received in Voxel appear in Odoo without manual entry.

  • A scheduled job runs every 10 minutes and, for each company that has Voxel enabled and a sale order login configured, queues the import of new Voxel orders in the background.
  • Each imported order is created as a sales order/quotation, with the customer, delivery address, order reference, order date, commitment date and validity date taken from the Voxel document.
  • Products are matched by supplier SKU, customer product code or product name; quantities and units of measure are read from the document, and discounts and taxes are applied to each line.
  • Comments from the Voxel document are added to the order's internal notes, and a message is posted on the order showing the source file and any problems found during import.
  • If a customer, delivery address, product, unit of measure or tax cannot be matched, the order is still created and the errors are listed in the order's chatter.

Where it appears: a Voxel tab on the sales order form (visible to Voxel managers) shows the original XML file; a 'Voxel Quotations' filter is added to the sales search; and a 'Voxel order Jobs' menu under Sales > Reporting lists the background import jobs. The Voxel sale order login is configured on the company form and in Settings.

Depends on

edi_voxelonchange_helpersale

Required by other modules

edi_voxel_sale_secondary_unit

Menus it adds

menu_voxel_queue_job
Models and fields (3)
  • sale.order · new modelvoxel_enabled, voxel_job_ids (Jobs)
  • res.company · extends an existing modelvoxel_sale_order_login_id (Sale Order login)
  • res.config.settings · extends an existing modelvoxel_sale_order_login_id

Text generated by AI (DeepSeek) from reading the Odoo 13.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 13.0

Configuration

Source · Odoo 13.0

To configure this module you have to belong to the access group 'Voxel manager' under 'Technical Settings', then:

  • Go to Settings > Users & Companies > Companies, open the companies you want to enable Voxel communication and set 'Enable Voxel' field to True.
  • In the login list, add the corresponding login for connecting with Voxel to import sales orders. The final URL from where sales order will be imported is '/Outbox'.
  • Save the form and edit it again, find 'Sale Order login' field and select the login to be used in the imports.
  • If you have the right access, go to Settings > Technical > Automation > Scheduled Actions, find the record named 'Edi Voxel: Get voxel sale order' and Adjust the data corresponding to that scheduled action, such as the frequency with which that action will be executed.

Note:

This module enqueue the imports in jobs in the background. To do that it uses queue_job module, so a configuration is required according to that. The jobs for impots are queued in the channel root.voxel_import.

Usage

Source · Odoo 13.0

To use this module, you don't need to do anything. Automatically every so often a 'scheduled action' will be executed that will try to import from Voxel the sales orders that have not been imported previously.

Imports will be performed for the companies that have the 'Voxel' field checked (See configuration section).

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.