Temu API Error 150010140 "For Books, Only One SKU Is Allowed" — Cause & Fix

When publishing a product in a book category to Temu through the API (bg.local.goods.add), a request that carries multiple SKUs is rejected with error code 150010140. The call returns HTTP 200 with success: false, so it's easy to miss if you only check the status code — you have to read the response body.

The error message

Status_code: 200
Content: {"success":false,"errorCode":150010140,"errorMsg":"For Books, only one SKU is allowed"}

Why this happens

Temu treats Books as a category that must be a simple product: exactly one SKU, no variants. This is a category-level rule, not a general one — for most other categories you can attach a multi-SKU skuList (sizes, colors, bundle sizes) to a single product. For Books, Temu rejects any product whose skuList contains more than one entry. If you send a book product with several SKUs — for example different titles, editions, or pack sizes grouped under one bg.local.goods.add call — the whole submission fails with 150010140, even if every individual SKU is otherwise valid.

Note the request returns Status_code: 200. The failure is entirely inside the JSON body (success: false + errorCode), so your integration must inspect the body rather than trusting the HTTP status.

How to fix it

1. For any product in a book category, send a skuList with exactly one SKU per bg.local.goods.add call.
2. If you have several books (or several editions/pack sizes) that you were grouping under one product, split them into separate products — one API call each, one SKU each — rather than one product with a multi-entry skuList.
3. In your publishing pipeline, branch on category: when the target category is Books, enforce a single-SKU payload before you submit, so the rule is caught in your code instead of by Temu's rejection.
4. Always parse the response body for success and errorCode; don't treat HTTP 200 as success on Temu's Open API.

The practical takeaway: Books on Temu are one-SKU-per-product by design. Model them as simple products in your integration and the error disappears.

Having built multi-channel integrations across 20+ sales channels — Temu, Amazon SP-API, eBay, Shopify, TikTok Shop and more — I've hit plenty of these category-specific rules that only surface as an API rejection. If you need help with eCommerce support or marketplace API integration, check out Netalith's eCommerce support service or reach out to me directly on LinkedIn.