Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $499.00 USD
- Versions Odoo
- 17, 18, 19
- Temps d'installation
- 20160 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
Dropshipping & Supplier Fulfillment Automation
Auto-route dropship orders to the right supplier per SKU, send POs and feeds, sync stock and tracking, and reconcile margins in Odoo.
$499.00USD
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
Per-SKU supplier routing engine: on sale-order confirmation an automated action assigns each order line to the preferred dropship vendor using rules over product.supplierinfo (preferred vendor, price break, availability, priority fallback)
Automatic order splitting: a single multi-supplier sales order fans out into one purchase order or dropship shipment per supplier, each linked back to the originating SO line for full traceability
Multi-channel supplier PO / order-feed generation: dispatch a QWeb PDF purchase order by email, export a mapped CSV order feed, or push directly to a supplier API from one dispatch action
Supplier inventory feed ingestion: scheduled ir.cron jobs pull or receive CSV/JSON/API stock feeds, map supplier SKUs to your products, and update on-hand availability used by the router
Automatic re-routing on stock-out: when a preferred supplier reports a SKU unavailable, the engine re-evaluates rules and re-routes the line to the next eligible supplier without manual intervention
Tracking-number ingestion: shipment confirmations (email-parsed, CSV, or API) write carrier_tracking_ref onto the matching stock.picking and mark it done
Automated customer shipment notifications: tracking capture triggers Odoo's delivery-confirmation email/SMS so buyers get updates the moment a supplier ships
Per-line cost & margin reconciliation: computed fields (@api.depends) capture quoted supplier cost, billed vendor cost, and customer price to surface true realized margin per dropship line
Margin & fulfillment dashboards: OWL/pivot views and QWeb reports roll up margin by supplier, SKU, channel, and period, flagging negative-margin and cost-drift lines
Supplier scorecard: track fill rate, average ship latency, tracking-capture rate, and cost accuracy per vendor to inform routing priority
Exception queue: a dedicated view surfaces unroutable lines, failed feeds, missing tracking, and cost mismatches with owners and SLA aging so nothing silently stalls
Secured access model: ir.model.access.csv plus multi-company and supplier-scoped record rules so ops agents and supplier portal users see only their own data
XML-RPC / JSON-RPC endpoints to receive stock and tracking feeds or expose routing status to external OMS/marketplace connectors
Configurable feed mapping UI: define per-supplier SKU maps, field mappings, and file/API formats without code, so onboarding a new supplier is configuration not development
Works on Odoo 17, 18 and 19, Community or Enterprise, with a proper __manifest__.py, dependency declarations, and demo/config data for repeatable installs
À propos de ce produit
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.
Pourquoi choisir Dropshipping & Supplier Fulfillment Automation
Per-SKU supplier routing engine: on sale-order confirmation an automated action assigns each order line to the preferred dropship vendor using rules over product.supplierinfo (preferred vendor, price break, availability, priority fallback)
Automatic order splitting: a single multi-supplier sales order fans out into one purchase order or dropship shipment per supplier, each linked back to the originating SO line for full traceability
Multi-channel supplier PO / order-feed generation: dispatch a QWeb PDF purchase order by email, export a mapped CSV order feed, or push directly to a supplier API from one dispatch action
Supplier inventory feed ingestion: scheduled ir.cron jobs pull or receive CSV/JSON/API stock feeds, map supplier SKUs to your products, and update on-hand availability used by the router
Automatic re-routing on stock-out: when a preferred supplier reports a SKU unavailable, the engine re-evaluates rules and re-routes the line to the next eligible supplier without manual intervention
Tracking-number ingestion: shipment confirmations (email-parsed, CSV, or API) write carrier_tracking_ref onto the matching stock.picking and mark it done
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.
Ce que vous obtenez
- Full module source code: a versioned Odoo addon (models, views, security, data, QWeb reports) delivered to your repository with a documented __manifest__.py
- Installation and configuration on your target Odoo 17/18/19 instance (Community or Enterprise), including routing rules, supplier feed mappings, and cron schedules set up for your live supplier matrix
- Supplier integration setup: configuration of each agreed feed channel (email PO, CSV drop, or API) with SKU maps and field mappings for the suppliers scoped in the engagement
- ir.model.access.csv + record-rule security configuration reviewed for multi-company and supplier-portal isolation
- Admin & operations documentation plus a runbook covering routing rules, feed onboarding, the exception queue, and reconciliation reports
- A live training session for your ops team (recorded), plus handover notes so staff can add suppliers and adjust rules independently
- A post-launch support & bug-fix window (defined in your order) covering defects and configuration questions after go-live
- Version-compatibility statement and upgrade guidance for moving the module across Odoo 17 to 18 to 19
Pour qui c'est
Asset-light marketplace seller
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.
Dropship operations manager
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.
Finance / margin owner
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.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le module ZIP Dropshipping & Supplier Fulfillment Automation depuis le tableau de bord de votre compte.
Télécharger sur Odoo
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Installer le module
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Dropshipping & Supplier Fulfillment Automation et appuyez sur Installer.
Configurer les paramètres
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Vérifier et mettre en ligne
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
Comment Dropshipping & Supplier Fulfillment Automation se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| 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 |
Foire aux questions sur Dropshipping & Supplier Fulfillment Automation
How long until the module is delivered and installed?
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.
What support and updates do I get after go-live?
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.
Does this work with my Odoo version and edition?
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.
How is this different from Odoo's built-in dropship route?
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.
How do you connect to my suppliers, and what if they only accept email or CSV?
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.
Where does my data live and are there ongoing per-order fees?
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.
Modules associés
Dynamics 365 Business Central
Une fois
3PL / Outsourced-Warehouse Manager
A build-to-order Business Central AL extension that maps your 3PL warehouses into native sales and purchase flows — sending fulfillment orders, ingesting ASN and shipment confirmations, and reconciling on-hand quantities against each 3PL's stock balances.
Construit sur commandeÀ partir de 499.00 $
ERPNext
Une fois
3PL / Warehouse Billing for ERPNext
A build-to-order ERPNext app that lets 3PL operators bill each client for storage, handling, and value-added services with strict multi-owner inventory segregation and automated periodic invoicing. ECOSIRE builds, installs, and supports it for your warehouse.
Construit sur commandeÀ partir de 799.00 $
Shopify
Une fois
3PL Fulfillment Connector
A custom-built, two-way integration between your Shopify store and your 3PL or WMS. ECOSIRE builds, installs, and supports it — pushing orders, syncing inventory, writing back tracking, and routing by warehouse automatically.
Construit sur commandeÀ partir de 499.00 $
Demander un devis
Dropshipping & Supplier Fulfillment Automation
Auto-route dropship orders to the right supplier per SKU, send POs and feeds, sync stock and tracking, and reconcile margins in Odoo.
- Per-SKU supplier routing engine: on sale-order confirmation an automated action assigns each order line to the preferred dropship vendor using rules over product.supplierinfo (preferred vendor, price break, availability, priority fallback)
- Automatic order splitting: a single multi-supplier sales order fans out into one purchase order or dropship shipment per supplier, each linked back to the originating SO line for full traceability
- Multi-channel supplier PO / order-feed generation: dispatch a QWeb PDF purchase order by email, export a mapped CSV order feed, or push directly to a supplier API from one dispatch action
- Supplier inventory feed ingestion: scheduled ir.cron jobs pull or receive CSV/JSON/API stock feeds, map supplier SKUs to your products, and update on-hand availability used by the router