The question is always the same: «do Temu orders come into Odoo on their own?». Yes, they do. What decides whether the operation works or turns into a swamp of manual reconciliation is not that they arrive, but with what they arrive. A badly mapped order shows up three weeks later, when someone tries to reconcile VAT or explain why there are two deliveries for the same order.
First: the identifier, or you will get duplicates
Every Temu order arrives with its own reference. That number must be stored on the Odoo order and be the key you look up before creating anything. If the import creates first and checks afterwards, any retry — a network drop, an overlapping cron, a manual sync launched while the automatic one was running — leaves you two identical orders and two deliveries. It is the number one defect we find when auditing connectors somebody else built.
Variants: Temu's SKU is not your SKU
Temu identifies each variant with its own code. Your Odoo has its own. Between the two you need a mapping, and it must be explicit and reviewable, not a function that guesses by slicing strings. When the mapping fails, the order comes in with a generic product or does not come in at all, and either way somebody finds out late.
Advice that saves grief: get the mapping done before opening the channel, not after the first order spike. Going through hundreds of orders with no product or a generic one by hand is a lost day.
Taxes and currency: the destination country sets them
If you sell in several countries, each order arrives in its own currency and with the tax that belongs to where the goods are going, not where your company sits. In Odoo that means a fiscal position per country and a price list per currency, configured before the first order lands. It is the same work covered in the piece on Temu in a multichannel operation, and it is where careless setups lose the most money.
The committed deadline overrides your warehouse
Temu does not ask you to ship when convenient: it gives a deadline per order, and missing it is paid for in account metrics. That data has to travel all the way to the Odoo delivery and be visible to whoever picks. An order that arrives without a deadline is an order picked first-in-first-out, and first-in-first-out is not the order Temu expects.
Cancellations: the case almost nobody prepares for
An order can be cancelled after it has entered Odoo and before it leaves the warehouse. If the import only knows how to create, the cancellation never arrives and you end up shipping goods nobody will pay for. The sync has to read status changes too, not only new orders, and it has to know what to do with an already validated delivery: that is no longer a cancellation, it is a return.
What our connector does
The Temu connector for Odoo (Odoo 17, 18 and 19, and Odoo 20 the day it ships) handles part of this out of the box, and it is worth knowing exactly which part. It looks every order up by its Temu reference before creating anything, and the database will not accept two orders with the same reference in the same shop. It matches each line to your variant by the seller SKU you use on Temu against the Odoo internal reference, or by the Temu identifiers it stores on the variant: there is no separate table, the mapping is your internal reference, and a line that finds no variant keeps the sales order in draft instead of confirming it. It creates the customer with the delivery country, which is what Odoo needs to apply the automatic fiscal position you have set up per country. It stores Temu's ship-by deadline on the Temu order record, linked from the delivery; it does not write it onto the delivery. And it reads orders by update date, not only new ones: if Temu cancels, it cancels the sales order, unless there is already a validated delivery or a posted invoice, in which case it leaves the order alone and posts a note on it.
Frequently asked questions
How often do orders come in?
By default every 15 minutes through a scheduled action, and sooner if you register the connector's webhook with Temu: status-change notifications are processed as soon as they arrive. The interval can be raised or lowered depending on volume; what you should not do is leave it at one hour, because Temu's shipping deadline eats that hour.
What if I already imported orders by hand?
The connector does not look up existing sales orders by reference: it links each Temu order to the sales order it creates itself, so typing the reference by hand does not prevent the duplicate. The first sync only looks back over a configurable window (24 hours by default), but it reads by update date: an order you imported by hand that changes status after you switch it on comes in again as a new order. The clean way is to stop importing by hand the day you switch it on and review those overlapping orders over the first days.
Does it work with your own warehouse and with 3PL?
With both. What changes is who validates the delivery and where the tracking number comes from; the order comes in the same way.
Useful links inside FlexigoTech
What we do about this
Opening Temu and would rather not reconcile by hand?
Tell us which countries you sell in, how many references you have and whether the warehouse is yours or a 3PL's. We will tell you what to prepare before switching the channel on. Write to comercial@flexigobe.com or book a call.