Guide · Temu Open Platform API
Temu's local seller integrations run on the Temu Open Platform, a partner API with app credentials, a per-seller access token, and a set of order, logistics, and goods methods. The rules in the fulfillment requirements guide are enforced by timestamps that come from these calls. This page follows one order from the moment it appears in the order list to the tracking upload and the inventory update that follows, with the method, the deadline it feeds, and the mistakes that show up as late shipments and API errors.
Step 0
A Temu integration is an app on the Temu Open Platform with an app key and secret, authorized against a specific seller account. The seller grants it in Seller Center under Apps, chooses the permission scopes (orders, fulfillment and tracking, goods and inventory), and generates an access token. Every later call is signed with the key and secret and carries the token. The US marketplace has its own API host, openapi-b-us.temu.com, distinct from other regions.
The most common Temu API failure is not a bug: it is a token generated before all the scopes were checked. An app authorized for orders but not fulfillment can list orders and cannot confirm shipments; one without the address scope gets orders with no ship-to. The fix is to edit the app's permissions in Seller Center, regenerate the token, and re-enter it. Do this once, correctly, at set-up.
Step 1
Orders come from the order list method (bg.order.list.v2.get), paginated and filterable by status and time window, with a detail call per parent order. Temu identifies orders by a parent order number (the PO-prefixed value the buyer also sees) and child order lines beneath it. Status moves from pending to awaiting shipment, then shipped, then delivered, with cancellation as a side exit. Temu also exposes combined-shipment groups: parent orders from the same buyer that may travel in one carton.
| Method (Open Platform) | What it returns | Feeds which clock |
|---|---|---|
| bg.order.list.v2.get | Parent orders by status and time, paginated | Handling time starts at order creation, not at your first pull |
| Order detail (v2) | Child order lines, quantities, SKU identifiers, expected ship-by | Ship-by deadline, expedited flag |
| Shipping info (v2) | Recipient name and address for the parent order | Nothing until you can read it; requires the address scope |
| Decrypt shipping info | Sensitive address fields in clear text, on request | Same; PII should be read at label time and not stored longer than needed |
| Combined shipment groups | Parent orders eligible to ship together | One label, several parent orders, one tracking upload each |
| Customization content | Personalization text and files for customized items | Handling time still applies; production time is yours to manage |
Poll cadence matters because Temu's handling clock starts when the order is placed, not when you see it. A daily pull can consume most of a 24-hour expedited window before the order reaches the warehouse. Continuous pulls on a short cycle are the norm; InfiPlex pulls Temu orders the same way it pulls every other channel and drops them into one queue sorted by ship-by deadline.
Step 2
Temu separates order data from shipping data. The order calls give you what to pick; the shipping-info call gives you where it goes, and the sensitive fields are returned decrypted only through the dedicated call and only to apps with that scope. Treat it the way Amazon's Restricted Data Token forces you to: fetch the address when the label is created, use it, and do not warehouse customer PII in systems that do not need it. Integrations that copy every address into a spreadsheet are the ones that fail a platform data review.
Step 3
Shipment confirmation (the logistics shipment confirm method) posts the carrier and tracking number for a parent order or a combined-shipment group. Temu validates the carrier against its supported list and the number against the carrier's format; an unsupported regional carrier or a mistyped number is rejected and the order stays awaiting shipment, which becomes a late-tracking mark even though the carton is gone. Confirm from the carrier manifest scan or the WMS ship event, never from an end-of-day batch, and map your carriers to Temu's list once during set-up.
For combined shipments, confirm the group with a single tracking number so each parent order in it is marked shipped. For customized items, the handling window is unchanged; production time has to fit inside it or the item should carry a longer handling time in the listing.
Continuous
The goods methods list your Temu SKUs and their identifiers and update stock quantities. Temu shows a listing as buyable because your last update said so, so the cadence of stock updates decides your seller-side cancellation rate. Push available-to-sell as every channel sells, hold a per-SKU buffer on fast movers, and map Temu SKU identifiers to your OMS SKUs once during onboarding so quantities land on the right listing. Price changes also flow through goods calls but are subject to Temu's pricing review before they take effect.
| Step | Method family | Deadline it protects | Failure mode |
|---|---|---|---|
| Authorize | Seller Center app permissions, access token | Everything downstream | Missing scope: no addresses, cannot confirm shipments |
| Pull orders | Order list v2, order detail | Handling time (1 to 2 business days; 24h expedited) | Daily polling eats the window |
| Read address | Shipping info, decrypt shipping info | Label creation | No address scope; PII stored where it should not be |
| Ship and confirm | Logistics shipment confirm | Tracking within 24 hours of dispatch | Unsupported carrier, typo, end-of-day batch |
| Update stock | Goods and inventory methods | Cancellation rate | Stale counts after sales on other channels |
Automation
InfiPlex is authorized once in Seller Center with the full scope set, pulls Temu orders continuously into the shared queue, reads addresses at label time, posts shipment confirmations from the ship scan whether the carton leaves your warehouse, ShipStation, or a 3PL WMS, and pushes inventory from the shared pool as every channel sells. Carrier mapping to Temu's supported list is part of set-up. The connection steps are on the Temu integration set-up article; the program rules the calls serve are in the fulfillment requirements guide.
Frequently asked
Questions from developers and operations teams connecting a Temu local seller account.
Authorize an app in Temu Seller Center under Apps, select the permission scopes it needs (orders, fulfillment and tracking, goods and inventory, shipping addresses), and generate an access token. The app signs calls with its app key and secret and sends the token; the US marketplace uses the openapi-b-us.temu.com host.
The app was not granted the shipping-address scope, or the token was generated before that scope was checked. Edit the app's permissions in Seller Center, regenerate the token, and re-enter it. Address data comes from separate shipping-info calls, with sensitive fields decrypted on request.
Temu's identifier for a customer order, prefixed PO, with child order lines beneath it. The buyer sees the same number, and shipment confirmations and customer messages reference it.
Continuously on a short cycle. Temu's handling clock starts at order placement, not at your first pull, so a daily poll can consume most of an expedited order's 24-hour window before the warehouse sees it.
Usually an unsupported carrier or a tracking number that fails the carrier's format check. Map your carriers to Temu's supported list during set-up and confirm from the scan so typos are not introduced by hand.
Yes, when Temu groups them as a combined shipment for the same buyer. Confirm the group with one tracking number and each parent order in it is marked shipped.
Push available-to-sell to Temu through the goods and inventory methods as every channel sells, from one shared pool, with a per-SKU buffer on fast movers. Stale counts are what cause out-of-stock cancellations, which count against you.
No. InfiPlex is the authorized app; you grant it the scopes in Seller Center and enter the token during onboarding. Orders, addresses, shipment confirmations, and inventory updates run through the connection automatically.
Resources
Authorized once, orders pulled continuously, tracking from the scan, inventory from one pool. Live in 1–3 business days.
Our team has authorized Temu Open Platform apps for sellers across categories. Tell us where the connection stalls and we will get orders flowing. Contact us, email info@infiplex.com, or call 888‑770‑0857.
InfiPlex™ is a trademark of InfiPlex. Temu is a trademark of Whaleco Inc. or its affiliates. Amazon, Walmart, Shopify, and other names are trademarks of their respective owners. InfiPlex is an independent integration provider and is not endorsed by or affiliated with Temu. Program rules, deadlines, fees, and penalties are set by Temu, differ by seller agreement and market, and change; verify current terms in Temu Seller Center before relying on them. ©2026 InfiPlex. All rights reserved.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License