Connect Temu: pull orders in, push fulfillment out
Get your App Key and App Secret from Temu Partner Platform, authorize your app in Seller Center for an access token, paste them into Integration, test, map, activate — orders flow in and fulfillment flows back.
The Temu connector pulls orders from your Temu store into OMS, and pushes fulfillment back to Temu. It can also push products and inventory, so listings, stock, and shipping stay in sync on both sides. One connection per store: each store authorizes its own access token.
Prerequisites#
- A Temu seller store, with access to Seller Center.
- Access to Temu Partner Platform, with an app you can manage under App management.
- Permission in Seller Center to authorize your app under Authorization Management — the access token comes from that authorization.
- Know your store region before you start: the Region field must match the seller store region (us, eu, or global).
Get your credentials#
- Go to Temu Partner Platform → App management, and copy the App Key.
- On the same page, copy the App Secret. It is used for request signing — copy it exactly, with no extra spaces.
- Go to Seller Center → Authorization Management, authorize your app, and copy the access token. The token belongs to the store you authorized — authorize the store you actually want to connect.
- Note the region of that store: us, eu, or global. You will fill the same value into the Region field in the next step.
Fill it into Integration#
- Open Integration → Connector Marketplace → Temu → New connection.
- App Key — required: paste the App Key you copied from Temu Partner Platform → App management.
- App Secret — required: paste the App Secret from the same page. It is used for request signing, encrypted at rest and never echoed back.
- Access token — required: paste the access token you copied from Seller Center → Authorization Management after authorizing your app.
- Region: fill us (the default), eu, or global. It must match the seller store region, or the connection will point at the wrong store.
Test the connection#
Click Test connection. The test checks two levels: connectivity (the App Key, App Secret, and access token are accepted and the signature verifies) and a document-level preview (pull one real order and show platform fields → standard order side by side). If the store has no orders yet, place a test order in Temu first — the preview needs one real document. If the test fails, note the exact error and check the FAQ below before changing anything else.
Mapping / pick a template#
Pick the Temu standard template. It maps order number, line SKUs, quantities, ship-to address, and fulfillment status, and it carries the fields used when products and inventory are pushed back. Check the mapping preview with one real order before activating — especially that every Temu SKU is paired to an OMS product.
Activate#
After activation, Integration pulls new orders on the schedule you set, pushes fulfillment with tracking numbers back to Temu, and pushes product and inventory changes so both sides stay in sync. Watch the first few orders in Runs / Logs before trusting it unattended.
FAQ#
Test fails: credentials rejected
The App Key, the App Secret, or the access token is wrong. The most common causes are a value copied with a missing character or an extra space, the App Key and App Secret taken from different apps, or a token that belongs to a different store than the one you are connecting.
Re-copy all three values from their source pages and test again: App Key and App Secret from Temu Partner Platform → App management, and the access token from Seller Center → Authorization Management for the store you are connecting. Paste each value into its own field — do not swap App Secret and access token.
It worked before, now the token is expired
The access token from the store authorization is no longer valid, so Temu rejects the calls even though the App Key and App Secret are still correct. Orders stop pulling and pushes stop going out until the token is renewed.
Go to Seller Center → Authorization Management, authorize your app again for that store, copy the new access token, paste it into the Access token field of the connection, save, and test again.
Connection points at the wrong store
The store identifiers do not line up: the Region does not match the seller store region, or the access token was authorized for a different store. The connection can then test against the wrong region or pull nothing for the store you expected.
Check the two values together: set Region to the region of the store you want — us, eu, or global — and, in Seller Center → Authorization Management, confirm the access token was authorized for that same store. If it was not, authorize the right store, copy its token into the connection, and test again.
Connected but no new orders are pulled
The connection itself is fine — the store simply has no new orders in the pull range, so there is nothing to import yet.
Place a test order in your Temu store, check that its time falls inside the pull range, then run a manual pull and confirm the order appears in the preview or in Runs / Logs.