Auto-route dropship orders to the right supplier per SKU, send POs and feeds, sync stock and tracking, and reconcile margins in Odoo. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
Auto-route dropship orders to the right supplier per SKU, send POs and feeds, sync stock and tracking, and reconcile margins in Odoo.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
Running an asset-light dropship business on many suppliers means your operations team lives in spreadsheets: manually deciding which supplier fulfills which SKU, emailing purchase orders, chasing stock levels, copy-pasting tracking numbers into customer emails, and reconciling what you actually earned per line after supplier cost. Odoo's native dropship route (MTO + "buy" with the supplier as the delivery address) gets you a purchase order per sales line, but it stops there — no per-SKU supplier preference logic, no automated supplier feeds, no inventory ingestion, no tracking capture, and no margin reconciliation. This build-to-order module closes every one of those gaps.
ECOSIRE designs, builds, installs, and supports a purpose-built Odoo application (compatible with Odoo 17, 18 and 19, Community or Enterprise) that turns your dropship workflow into a hands-off pipeline. On sale-order confirmation, an Odoo automated action evaluates your routing rules and assigns each order line to the correct dropship supplier — by preferred vendor per product (extending seller_ids / product.supplierinfo), by price break, by live availability, or by fallback priority. A generated purchase order (or exported order feed) is dispatched to that supplier over the channel they accept: a QWeb PDF PO by email, a CSV drop, or a direct API push. Inbound supplier inventory feeds are parsed on a scheduled cron (ir.cron) and mapped to your products so out-of-stock SKUs re-route automatically. When the supplier ships, the tracking number is ingested and written to the delivery (stock.picking.carrier_tracking_ref), which fires the customer shipment notification. Finally, a per-line reconciliation model (models.Model with @api.depends computed fields) captures quoted supplier cost versus billed cost versus the price you charged, so real margin — not assumed margin — is visible on every dropship line and roll-up dashboard.
Every model is secured properly with ir.model.access.csv rules plus multi-company and supplier-scoped record rules, so a supplier-facing portal user or an ops agent only sees what they should. Views are delivered as clean XML (with OWL components where an interactive dashboard adds value), integrations expose and consume XML-RPC / JSON-RPC endpoints, and the whole thing ships as a versioned addon with a proper __manifest__.py and dependency declarations. Because it is your module on your database, there are no per-order SaaS fees and no data leaving your Odoo instance.
This is not an instant download from apps.odoo.com. It is a build-to-order engagement: ECOSIRE scopes your supplier matrix and routing logic, builds and QAs the module, then installs and hands it over on your infrastructure — typically within 2 to 4 weeks depending on the number of supplier integrations and feed formats.
Runs a dropship catalog across many suppliers on Amazon, eBay, or their own store. Needs orders to route to the cheapest in-stock supplier per SKU automatically and hates the manual PO-emailing and tracking copy-paste that eats their day.
Owns fulfillment SLAs and supplier relationships. Wants an exception queue, supplier scorecards, and automatic re-routing on stock-outs so late or failed dropships surface before customers complain.
Needs to know true realized margin per dropship line after actual supplier billing, not the assumed margin at sale time. Relies on per-line reconciliation and supplier cost-drift reporting to protect profitability.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Per-SKU supplier routing rules (preferred vendor, price, availability) | Rules engine over product.supplierinfo with priority fallback | Possible but you design and maintain the rule logic yourself | Usually fixed to a single preferred vendor per product | |
| Automatic order splitting to multiple suppliers | One SO fans out to a PO/dropship per supplier, line-linked | Buildable per your spec at full custom cost | Varies; many split only within their own vendor model | |
| Multi-channel supplier feeds (email, CSV, API) | All three, mapped per supplier from one dispatch action | Each channel is bespoke development | Often one channel or a proprietary connector only | |
| Supplier stock feed ingestion + auto re-route | Scheduled ir.cron import with SKU mapping and re-routing | Feasible but you own parsing and mapping | Sometimes, for supported suppliers only | |
| Tracking ingestion + customer notification | Writes carrier_tracking_ref and fires delivery notifications | Custom-built integration required | Sometimes, tied to their carrier list | |
| Per-line cost & realized-margin reconciliation | Computed @api.depends fields, dashboards, cost-drift flags | Custom reporting build | Rarely at true per-line billed-cost level | |
| Ownership, data location & fees | You own the code; runs in your DB; no per-order fees | You own it; full custom price and timeline | Licensed module; may add SaaS/connector fees | |
| Odoo 17 / 18 / 19 compatibility & fit | Built and tested for your exact version and edition | Depends on your team's Odoo expertise | Depends on the vendor's version support |
This is a build-to-order engagement, not an instant apps.odoo.com download. Typical delivery is 2 to 4 weeks from a confirmed scope. Timeline depends mainly on how many suppliers you onboard and how varied their feed formats are: an email/CSV-only setup lands faster than one with several custom supplier APIs. After scoping we give you a firm date, then build, QA, install on your instance, and hand over.
Every engagement includes a post-launch support and bug-fix window (the exact length is stated in your order) covering defects and configuration questions. Because you own the module source, you keep it forever with no per-order SaaS fees. We also provide a version-compatibility statement and upgrade guidance so the module moves cleanly across Odoo 17, 18 and 19; extended support or a maintenance retainer for new suppliers and feature additions is available separately.
Yes. The module targets Odoo 17, 18 and 19 and works on both Community and Enterprise. It is delivered as a standard addon with a proper __manifest__.py and declared dependencies, so it installs like any other module. During scoping we confirm your exact version and any existing customizations it must coexist with.
Odoo core can dropship via the MTO + buy route, generating a purchase order with the customer as the delivery address, but it has no per-SKU supplier preference logic, no automated supplier feeds, no inventory ingestion, no tracking capture, and no per-line margin reconciliation. This module adds all of that: a rules-based routing engine, multi-channel PO/feed dispatch, scheduled stock-feed import with auto re-routing, tracking ingestion, and true realized-margin reporting.
We support three channels per supplier: a QWeb PDF or structured order feed by email, a mapped CSV drop, or a direct API push (and inbound XML-RPC/JSON-RPC or scheduled cron pulls for stock and tracking). Suppliers who only take email or CSV are fully supported through the feed-mapping configuration. We scope each supplier's format up front and map their SKUs to your products during setup.
Everything runs inside your own Odoo database on your infrastructure. No order, customer, or supplier data leaves your instance to a third-party SaaS, and there are no per-order or per-transaction fees. You own the module code outright; your only ongoing cost is any optional support retainer you choose.
Auto-route dropship orders to the right supplier per SKU, send POs and feeds, sync stock and tracking, and reconcile margins in Odoo.