Connect SHEIN: pull orders in, push fulfillment out
Authorize your store on the SHEIN open platform, exchange the tempToken for openKeyId and SecretKey, paste them into Integration, test, map, activate — orders flow in and fulfillment flows back.
The SHEIN connector pulls orders from your SHEIN store into OMS, and pushes fulfillment back to SHEIN. It can also push product and inventory updates to SHEIN, so orders, shipping, and stock stay in sync on both sides.
Prerequisites#
- A SHEIN seller account with a store you can manage in the SHEIN seller center.
- Access to the SHEIN open platform, with permission to authorize that store.
- Your appSecretKey, ready to decrypt the secretKey returned after authorization — without it you cannot get the SecretKey used for signing.
- Someone who can keep openKeyId and SecretKey safe — you will need them again if you reconnect.
Get your credentials#
- Find your Store code in your SHEIN seller center store info, and copy it exactly as shown.
- On the SHEIN open platform, authorize the store. Authorization gives you a tempToken.
- Exchange the tempToken via /auth/get-by-token, then copy the openKeyId from the result.
- Decrypt the returned secretKey with your appSecretKey. The decrypted value is the SecretKey (signing) — it is used for HMAC-SHA256 request signing. Save it somewhere safe.
Fill it into Integration#
- Open Integration → Connector Marketplace → SHEIN → New connection.
- Store code: paste the store code from your SHEIN seller center store info. It identifies which store this connection belongs to, so it must match that store exactly.
- openKeyId: paste the openKeyId you got by exchanging the tempToken via /auth/get-by-token. This field is required.
- SecretKey (signing): paste the SecretKey you decrypted with your appSecretKey. This field is required. Requests are signed with it using HMAC-SHA256; it is encrypted at rest and never echoed back.
Test the connection#
Click Test connection. The test sends a signed request — signed with your SecretKey using HMAC-SHA256 — together with your openKeyId and Store code to probe SHEIN. A pass means SHEIN accepted the signature and the store matches. If it fails, note the error and check the FAQ below before changing anything else.
Mapping / pick a template#
Pick the SHEIN standard template. It maps order number, line SKUs, quantities, ship-to address, and fulfillment status between SHEIN and the standard order. Check the mapping preview before activating, especially that each SHEIN SKU is paired to the right OMS product.
Activate#
After activation, Integration pulls new SHEIN orders on the schedule you set, pushes fulfillment with tracking back to SHEIN, and pushes product and inventory updates to SHEIN. Watch the first few orders in Runs / Logs before trusting it unattended.
FAQ#
Test fails: credentials rejected
The openKeyId or SecretKey in the connection is wrong. The most common cause is pasting the still-encrypted secretKey instead of the value decrypted with your appSecretKey, or copying the openKeyId incompletely, so SHEIN cannot verify the HMAC-SHA256 signature.
Redo the credential steps in order: authorize the store again on the SHEIN open platform, exchange the new tempToken via /auth/get-by-token, copy the openKeyId, decrypt the returned secretKey with your appSecretKey, paste both values into the connection, save, and test again.
Connection worked before, now every test fails
The token or key behind this connection has expired or is no longer valid — for example the store was authorized again, which issues a new tempToken and new credentials, so the openKeyId and SecretKey saved in the connection no longer match the store.
Get fresh credentials: exchange the latest tempToken via /auth/get-by-token, copy the new openKeyId, decrypt the new secretKey with your appSecretKey, replace both values in the connection, save, and test again.
Test fails: store not found or store mismatch
The Store code field holds the wrong value — often the code of a different store was pasted in, so the credentials and the store do not belong together and SHEIN cannot match this connection to the authorized store.
Go back to your SHEIN seller center store info, copy the Store code shown for the authorized store exactly, replace the value in the connection, save, and test again.
Connected but no orders come in
The connection itself is fine — testing passes — but this SHEIN store has no new orders yet, so there is nothing to pull.
Place a real order in your SHEIN store (or wait for the next customer order), then run a manual pull and check Runs / Logs. New orders appear once SHEIN has issued them.