Yes. For Unicorn Petro both marketplaces connect to Odoo CRM by direct API, so an enquiry becomes a structured lead with buyer details, product interest and source tagging without anyone retyping it. Scheduled polling means capture does not depend on someone being logged in, and each enquiry carries its marketplace identifier so a repeated fetch updates the lead instead of duplicating it.

The full working pack. Unicorn Petro generates the proforma invoice, commercial invoice, packing list and shipper's letter of instruction directly from order data, with the bill of lading data set built on the same engine. Because all of them read one order record, the quantities, weights and values can never drift apart between documents.

Each buyer-specific format is built once as a reusable QWeb template and linked to the customer record, so the correct layout is resolved automatically at print time. The layout changes per buyer while the underlying order data stays identical, which turns a per-shipment compliance risk into a one-time configuration.

Yes, and that was an explicit goal here: unify the two without forcing one to behave like the other. They share one customer master, product master and pricing engine, then diverge where the business actually diverges. Export orders carry incoterms, ports, country of origin, HS codes and packing detail, while the domestic flow keeps its shorter path.

Manual documents are rebuilt per shipment, and every hand-built variation is a chance for a mismatch. Generated documents are views of one order record, so an invoice and its packing list describe the same goods by construction. Correcting an order regenerates the pack rather than requiring four separate edits, which is what keeps a shipment consistent at the port.

Seven working together: CRM, Sales, Purchase, Inventory, Accounting, Documents and Dashboards, all on a single database. That shared foundation is what allows a lead, an order, a stock movement, an export document and a management report to be different views of the same transaction rather than separate systems kept in step by hand.

Yes. Requisitions and purchasing are tied to sales demand, so raw material and packaging buying follows confirmed orders rather than a monthly estimate maintained on the side. Vendor terms and lead times sit in the same system, so purchasing decisions are made against recorded data.

Response time and lead survival. Enquiries reach the right salesperson the moment they arrive instead of after someone works through an inbox, so quotations go out while the enquiry is still warm. It also makes channel performance measurable, because every lead carries the marketplace it came from.

Yes, by design. All custom work lives in namespaced addons that extend Odoo through inheritance, with the core never edited. Document templates, pipeline stages and workflow rules ship as XML data records, so the whole setup is reproducible, reviewable and upgrade-safe.

It is the riskiest part, which is why it runs as a staged pipeline rather than a bulk import: extract and cleanse in staging, load in dependency order through the Odoo ORM so business rules still apply, then reconcile record counts and open-order values against the source before sign-off.

It depends on how many document formats and workflows are in play, which is exactly why requirement analysis comes first: mapping the real process document by document fixes the scope before configuration starts. Unicorn Petro ran seven phases, from requirement analysis and solution design through custom development, CRM integrations, document automation, user acceptance testing on live data, and a supported go-live.

KoderXpert is an Odoo Ready Partner that maps the real process before configuring anything, builds upgrade-safe custom modules with zero core edits, and treats export documentation as an engineering problem rather than a template exercise. Unicorn Petro's outcome: zero manual re-entry of marketplace leads and a five-document export pack generated from order data. Talk to KoderXpert about your export workflow.