At some point after listing products on Temu, you will receive a notification asking you to review a price order. Temu calls these price tasks — a formal request to change the base price of one of your products. They arrive without much ceremony and with a decision to make.
Most sellers either accept them reflexively or ignore them. Both are mistakes. A price task changes the base price of a product, and because the base price is what Temu pays you — your settlement — that decision moves your margin directly. Understanding what a price task is, what the status codes mean, and how to evaluate whether to accept is worth spending a few minutes on.
What a Price Task Is
A price task (also called a price order on the Temu Open Platform) is a Temu-generated request to modify the base price of a product — the price you as the seller set, which becomes your settlement per order.
The base price is not the price the customer sees — Temu's commission and any applicable VAT sit on top of it to form the customer-facing price, while what you receive as settlement is the base price you set. The full mechanics of how your base price becomes a customer-facing price and then a settlement are covered in Temu Seller Settlement: What You Actually Receive and Temu Commission Rates Explained.
When a price task requests a change to that base price, it is asking you to change the number you receive per sale. That is the key thing to hold onto before we get into the decision logic.
Why It Matters: The Direct Line to Margin
Price tasks matter more than they appear to at first glance, because they act on the one variable that determines your entire margin structure.
Your costs — product sourcing, packaging, shipping, return provisions — are fixed per unit. They do not move when Temu sends a price request. Only your base price (and therefore your settlement) moves. So if you accept a price-cut request, your revenue per unit drops while every cost line stays exactly where it was. The compression goes straight into your net margin.
Here is the trade-off in plain terms: a lower base price can increase your traffic and order volume, which may improve absolute profit if the volume gain is large enough. But it compresses per-unit margin, and on thin-margin products, it can turn a profitable SKU into a loss. A higher base-price invitation — yes, price tasks can go in either direction — has the opposite effect: margin improves per unit, but conversion or traffic may decline at the higher price.
This is not a small consideration. It is the same margin math the 8-step framework in How to Calculate Your True Profit Margin on Temu is built around, applied to one specific trigger event. The price task is the trigger; the margin impact is the consequence.
Price tasks can also be blocked in specific circumstances. If your product has an active promotion running, a price decrease may be rejected by the system — error 150010233 in Temu's API. This means you may need to wait until the promotion ends before a price reduction can be applied.
Worked Example: What Accepting a Price Cut Actually Does
The following example uses EUR and a product sold in France (VAT 20%). All figures are an example scenario.
A seller has a product with a base price of €16.00. The current margin looks like this:
Before price task — example scenario (EUR)
Net: €5.38Temu sends a price task requesting a base price reduction to €13.00 as a traffic-boost recommendation. If the seller accepts:
After accepting price cut — example scenario (EUR)
Net: €2.44The base price dropped €3.00 (18.75%). The net margin dropped from €5.38 to €2.44 — a compression of more than half. The product is still profitable, but the headroom for absorbing any cost increase, higher return rate, or future promotional discount has shrunk considerably.
This is the calculation worth running before responding to any price task. Not the price change in isolation — the full margin after the change.
The Status Code Table
Price tasks pass through several states as they are created, reviewed, and acted on. PilotSelling tracks these via the Temu Open Platform API using four status codes:
| Code | Status | Meaning | What to do |
|---|---|---|---|
100 | Under review | The price task has been submitted and is being reviewed by Temu | Wait — no action available yet |
101 | Pending merchant action | Temu has reviewed the task and is waiting for your decision | Evaluate the margin impact and respond: accept, reject, or negotiate |
201 | Approved | The requested price change has been approved | Confirm the new base price in your listings and recalculate your margin |
205 | Rejected | The price task was rejected (by you or by Temu) | No action required; monitor whether a new task follows |
When a price task reaches status 101, you have three options through the Temu Open Platform:
- Accept (
bg.local.goods.priceorder.accept) — agree to the requested base price change. The new price is applied. - Reject (
temu.local.goods.priceorder.reject) — decline the request. The current base price stays in place. - Negotiate (
bg.local.goods.priceorder.negotiate) — submit a counter-offer with your own proposed price. Useful when the requested price would compress margin below your threshold, but you are open to moving part of the way.
An appeal path also exists (appealorder.create) if you want to contest a rejected outcome through a formal process.
3 Common Mistakes with Price Tasks
1. Accepting Every Price Cut Without Checking Margin First
The most common error is treating price tasks as routine notifications to clear. You tap "accept" to move on, and at the end of the month you wonder why the SKU's profit figure is lower. The price-task decision is a margin decision. Run the before/after calculation — at minimum, check whether the new base price still covers your costs with enough margin to absorb normal return rates. If not, negotiate or reject.
2. Forgetting That Your Cost Lines Are Fixed
A €3 price reduction looks small in isolation. But your product cost, shipping, and logistics contribution do not drop €3 when the base price does. Every euro you give up in base price comes entirely out of net margin. On a product running 20% margin, a 15% base-price cut can eliminate most of that margin in a single decision. The compressing math is the same regardless of whether the product moves more units afterward — and higher volume at negative margin is worse, not better.
3. Treating Price-Cut Tasks and Price-Increase Invitations the Same Way
Not all price tasks are requests to lower your price. Temu also sends base-price-increase invitations (for example, when your product may have room to price higher relative to the category). The decision logic is different. For an increase: does a higher price reduce conversion or traffic more than the per-unit margin gain is worth? For a decrease: does the traffic or volume gain justify the margin compression? These are opposite questions. Collapsing them into a single "should I accept this?" habit leads to misplaced decisions in either direction.
How PilotSelling Handles Price Tasks
PilotSelling is a Temu profit tracker that connects to the Temu Open Platform API via the official Temu integration. It syncs your price tasks automatically, including their current status codes (100, 101, 201, 205), so you can see at a glance which products have pending merchant-action tasks and which have been resolved.
The key feature around price tasks is margin simulation: before you respond to a status 101 task, PilotSelling shows you the margin impact of the requested price change against your current cost inputs — the same before/after calculation illustrated in the worked example above. You can see what the new base price does to your net margin, your return-adjusted margin, and your margin per market (since VAT rates differ: FR 20%, DE 19%, ES 21%, IT 22%, NL 21%, US 0%).
The decision — accept, reject, or negotiate — stays with you. PilotSelling gives you the numbers to make it on real data rather than intuition.
FAQ
What is the difference between a price task and a regular price update?
A standard price update is a change you initiate yourself in Temu Seller Center or via the API — you decide to modify your base price and make it directly. A price task is a Temu-initiated request asking you to make a change. You can accept, reject, or negotiate. The mechanics of what changes when the price moves are the same in both cases: your base price changes, your settlement changes, and your margin changes. The difference is who originated the request.
Can Temu force me to accept a price task?
Based on the Temu Open Platform API documentation, price tasks at status 101 require merchant action — accept, reject, or negotiate. Nothing in the sourced API documentation indicates automatic acceptance or a penalty for non-response. That said, how Temu treats products with consistently rejected price tasks (for example, whether traffic or visibility is affected) depends on your account and category, and may change over time. If you have a specific concern about a pattern of rejections, the appeal path (appealorder.create) exists for contesting outcomes.
Does PilotSelling automatically accept or reject price tasks on my behalf?
No. PilotSelling syncs price tasks from the Temu Open Platform API and shows you the margin impact of a requested price change — but it does not act on the task automatically. It is designed to give you the information to make the decision: what does my net margin look like if I accept this price? What does it look like if I counter at a different number? The response is always yours to make. Use the calculator below to run a quick margin estimate on any price scenario.
Calculate your real Temu margin
Adjust the sliders to see how commissions, VAT, logistics, and returns eat into your profit.
Free for 14 days · no credit card needed