Two namespaces, one explicit mapping
The identifier Temu puts on an order line belongs to Temu. Your SKU belongs to you. They are separate namespaces that happen to describe the same physical item, and the only reliable way to connect them is an explicit stored mapping that a person has confirmed.
The reason to insist on the confirmation is the blast radius. A mapping is not a one-off decision about one order; it applies to every future order on that listing. If it is wrong, the wrong SKU is decremented on every subsequent sale, and the error typically surfaces weeks later during a stock count, by which point both products’ figures are wrong and neither history is trustworthy.
Suggest automatically, commit manually
Automatic suggestion is genuinely useful: matching on title similarity or a shared barcode narrows the candidates to one or two, which is most of the work. Automatic commitment is where the damage happens.
In MaxInvent, an unmapped Temu line offers a product preview with the option to create a new central product or link to an existing one. Staff review the preview and confirm the match, and that confirmation is recorded. It takes seconds, and it happens once per listing rather than once per order.
The controls that make mapping safe
- One barcode, one product row. Duplicate barcodes across products are the second-largest cause of cross-mapped stock, and they break scanning precisely when you depend on it — at the pack bench with a customer’s parcel open.
- Unmapped lines block, not guess. An unmapped line means the system cannot say which item to pick. Flagging it before picking is the cheapest control available here; letting it through converts a data problem into a mis-ship.
- Confirmations are recorded. When a mapping is later questioned, you want to know who confirmed it and when, not to re-litigate it from scratch.
- Reconcile imported order lines. Check that imported lines resolve to the products you expect, rather than assuming the import was clean because it did not error.
Bundles: a limit to design around
In MaxInvent, a Temu goods identifier maps to one mapped central product. Ratio-based bundle mapping — where one listing deducts several component SKUs in proportion — is not part of the current scope.
The practical consequence: if you sell bundles on Temu, hold the bundle as its own product with its own stock rather than expecting the components to be deducted. That is a real constraint, and it is better to know it before you build a catalogue around the opposite assumption.
For the full connection walkthrough, see connect Temu to your inventory system. For what happens after mapping, see Temu fulfilment.