CommerceHub, Overstock, Limango and the like are not marketplaces in the Amazon sense. They are retailer dropship networks: a chain sells on its own site, the order reaches you, and you ship straight to the end customer on the chain's behalf. The buyer does not know you exist, and that sentence contains nearly all the technical requirements.
The packing slip is not yours
It is the requirement that breaks most projects. The box reaching the customer carries the retailer's packing slip, with their logo, their order number and their returns text. In Odoo that means a report template per retailer and an external order number printed on it. It is not cosmetic: if your own packing slip goes out, you are in breach.
The shipping label may not be yours either
Many retailers impose their own carrier contract: they hand you a pre-paid label and you just stick it on and hand over. Others let you use yours but demand the tracking number before a given hour. Both are solved in Odoo, but with different mechanisms: in the first, the label arrives as a file and is attached to the delivery; in the second, the number comes from your own carrier connector and is pushed back to the network.
Running out of stock is penalised
On a marketplace, running out means you stop selling. In retailer dropship it means you cancel an order the retailer has already sold to its customer, and that is measured and penalised. In practice, stock publishing has to be more conservative than on any other channel: a higher safety buffer and publishing on confirmation, not in hourly batches.
And the catalog moves by file, not by a pretty API
A sizeable part of this industry still runs on files: catalogs by CSV, stock by FTP, confirmations by EDI. That is not a defect, it is what exists, and a serious connector has to speak that language without complaining. What you must demand of it is that it logs every exchange, because when an order goes missing the only way to prove what happened is the file sent and the file received.
What we do here
Plainly: we do not have a published CommerceHub connector on the Odoo App Store. What we do is build the integration to order against each network's specific operation, which is exactly what this kind of project needs, because no two retailers ask for the same thing. What we do have built and published are the classic marketplace connectors: Amazon, Mirakl, Temu and the rest of the catalog.
Frequently asked questions
Can dropship and own sales run in the same Odoo?
Yes, and it is advisable. What you separate are warehouse routes and packing slip templates, not the database. Stock is shared and that is the whole advantage.
What if the retailer uses EDI instead of an API?
That is the norm in this industry and it does not change the approach. What changes is the message transport; mapping to Odoo documents is the same work.
How long does such a project take?
It depends on how many messages the retailer demands and whether they impose the carrier. Order, confirmation and shipment is short; adding invoicing and returns lengthens it. Without seeing their spec nobody can give you a serious date.
Useful links inside FlexigoTech
A dropship network took you on and you do not know where to start?
Send us their integration document. We will tell you which messages are mandatory, what can be automated in Odoo and what will still need a person watching. Write to comercial@flexigobe.com or book a call.