TikTok Shop
Linking TikTok Shop SKUs to your supplier orders
Every dropshipping operation has one fragile join: the thing the customer bought, matched to the thing you buy from the supplier. Break it and nothing downstream can be trusted.
Why it breaks
It breaks because the two sides describe the product differently. TikTok has your SKU and a variant. The supplier has a product id, a colour name that is not quite your colour name, and a size chart that runs small.
A human bridges that gap fine the first twenty times. The twenty-first time it is late, the colour is "army green" on one side and "military green" on the other, and the wrong item ships.
Put the supplier reference in your SKU
The cheapest fix available is to encode the supplier identity in the SKU you set on TikTok. Not the whole URL - a short code that identifies supplier, product and variant unambiguously.
Then the order payload carries the answer. You do not look anything up; the thing you need to buy is written on the order.
- Keep it short enough to read aloud
- Make variants explicit, never implied
- Never reuse a code for a different product, even years later
- Avoid characters that break in spreadsheets or URLs
Keep a mapping table anyway
Encoded SKUs handle the common case. You still need a lookup table for the rest: products where the supplier changed, items you source from two places, bundles that map to more than one purchase.
One tab, one row per SKU, with the supplier link, the expected cost and the last date you verified it. That last column is the one that prevents slow decay.
Verify on a schedule, not on failure
Supplier listings change under you. Prices drift, variants disappear, the whole listing gets taken down. If the first you learn of it is an order you cannot fulfil, you are cancelling - and seller-driven cancellations are the expensive kind.
Walking your top twenty SKUs once a month takes twenty minutes and catches most of this before it becomes a cancellation.
Bundles need their own rule
A listing that is two items sold together is one TikTok order line and two supplier purchases. If your mapping is one-to-one, bundles silently break it. Decide early whether you support them, and if you do, make the mapping table capable of expressing one-to-many from the start.
Retrofitting that later means revisiting every row you already have.