Supplier / Vendor Catalog Import & EDI Bridge

ECOSIRE designs, builds and installs a custom Odoo module that reads whatever format each supplier gives you and maps it onto Odoo's own data model — product.template, product.product, product.supplierinfo (vendor pricelists), stock.quant / on-hand availability, and barcodes — using named, reusable field-mapping profiles. Instead of one brittle importer, you get a per-supplier mapping engine: column A maps to default_code, column D to the vendor's price, sheet 3 to the stock quantity, with unit and currency conversion, delimiter and encoding handling, and header-row detection baked in. Every run is idempotent — re-processing the same file will not create duplicates because matching is keyed on your chosen identity field (SKU, barcode, or vendor product code).

Feeds arrive on your schedule, not the supplier's. A custom automated action / ir.cron job polls FTP/SFTP endpoints, calls partner REST/SOAP APIs, or watches a mailbox for the daily price-list attachment, then queues each file for processing. For true EDI, the module parses and (optionally) emits ANSI X12 850 (Purchase Order), 855 (PO Acknowledgement), 856 (Advance Ship Notice) and 810 (Invoice), plus UN/EDIFACT equivalents (ORDERS, ORDRSP, DESADV, INVOIC, PRICAT), acknowledging with 997/CONTRL where your trading partners require it, and mapping segments to Odoo purchase.order, stock.picking and account.move records.

Crucially, nothing overwrites your live catalog blind. A delta-detection layer compares each incoming feed against current Odoo values and routes material changes — a cost jump beyond your tolerance, a discontinued line, a new SKU — into a change-approval queue. A buyer reviews, bulk-approves or rejects, and only then does the update commit, with a full audit trail of who changed what and when. Because it is your own module, security is enforced with Odoo's native ir.model.access.csv and record rules so only authorised purchasing roles touch supplier data, and every mapping, schedule and import run is a first-class Odoo record you can report on with standard views and QWeb outputs.

The module targets Odoo 17, 18 and 19 and works on Community or Enterprise (Enterprise studio/OWL niceties are used only where you already have them). It is delivered as clean, reviewable module code in your repository — not a locked black box — with a proper __manifest__.py, versioned models, and migration-safe upgrades. ECOSIRE scopes it to your actual suppliers and their real files during discovery, so on go-live day the mappings already match your feeds. This is a bespoke build with a typical 2–4 week lead time; it is not an instant download from the Odoo App Store — you are buying a module engineered, installed and supported for your exact catalog.