There is one question worth answering before touching a single setting: where does the truth for each field live? It is not a philosophical question. If the price can be changed both by whoever opens the Temu panel and by whoever edits the product in Odoo, the next sync will crush one of those two changes, and nobody will know which or when.
Ownership, field by field
The split that works in practice and the one we recommend as a starting point: Odoo owns title, description, attributes, images, price and stock. Temu owns the publication status, category restrictions and any field its catalog imposes that Odoo does not have. And there is a third, dangerous group: fields Temu changes on its own, such as promotions applied from their side. Those must not flow back into Odoo as if they were your price, because they are not.
When in doubt, sync one way. A channel that only goes from Odoo to Temu is boring and predictable, and in operations that is a virtue. Two-way sync is added when there is a concrete reason, not by default.
Prices: a channel price, not the product field
The most common mistake is publishing the product's sales price to Temu and calling it done. It works on day one and breaks on day two, as soon as you want a different margin on that channel because of the commission. The right answer is a price of its own for the channel, stored separately from your shop's sales price, so you can move one without touching the other. Temu adds a twist: base price changes are not simply imposed, they are sent as a proposal that Temu reviews and can reject.
If you sell in several countries, the channel price multiplies by currency. It is the same work any serious multichannel operation demands and it is covered in Temu inside a multichannel operation.
Stock: the problem is not publishing it, it is when
Publishing stock is trivial. What causes overselling is lag: minutes pass between someone buying on another channel and Temu finding out, and in those minutes you sell what you no longer have. The two defences that actually work are shortening that lag — minutes, not an hourly batch — and not showing everything you have on Temu for your fastest-moving references. And a detail people forget: on-hand quantity in Odoo does not drop when an order is confirmed, only when the delivery is validated.
Images and attributes: where listings fail
Temu rejects listings for reasons that do not exist in Odoo: minimum image dimensions, category-mandatory attributes, title lengths. If the connector just pushes and does not collect the rejection reason, you end up with products you believe are published and are not. The error has to stay in Odoo, attached to the product, not buried in a log nobody opens.
What our module does
The Temu connector for Odoo publishes from the product form, variants included, after validating what Temu requires: weight and dimensions per variant, image URLs, the category's compliance documents and banned words in title and description. Each publication keeps its status and the rejection reason Temu returns, one click away from the product. Price is handled as a Temu base price per SKU, separate from the sales price: you can pull Temu's recommended price, request an estimate and send the proposal with its reason. Stock for linked SKUs goes out every 5 minutes by default and on demand, from the instance's warehouse or as a fixed quantity you set per variant. It runs on Odoo 17, 18 and 19, and Odoo 20 the day it ships. If what you need is the other half — orders coming in properly — that is in importing Temu orders into Odoo.
Frequently asked questions
Can I publish only part of the catalog?
Yes, and it is what we recommend at the start. With our connector, publication is launched product by product from its form, and stock is only sent to SKUs linked to Temu: whatever you do not publish is left untouched. Opening a channel with the whole catalog at once multiplies rejections and hides which one is failing.
What if I change the price in Temu's panel?
Our connector does not resend the price on every cycle: it only leaves Odoo when someone sends a base price proposal. But if someone later proposes a different price from Odoo, that is the one sent to Temu, and your panel change is overwritten. That is exactly why ownership must be decided up front.
Does it work alongside other marketplaces?
Yes. The approach is the same for Amazon, Mirakl or Shopify: one master stock and a price of its own per channel. It is covered in several marketplaces in one Odoo.
Useful links inside FlexigoTech
What we do about this
Want your catalog on Temu without maintaining it twice?
Tell us how many references you have, which countries you sell in and whether you are already on other marketplaces. We will tell you which ownership split fits and what to prepare first. Write to comercial@flexigobe.com or book a call.