Home › Guides › Amazon fulfilment setup

Setup guide · Temu Order Fetcher

Connecting Amazon fulfilment

Amazon Multi-Channel Fulfilment (MCF) lets Amazon send orders placed on other marketplaces. This guide shows you how to connect it through Amazon's Selling Partner API (SP-API). Your three private connection details go only into your own Fetcher installation. The Fetcher can then send an order after you approve it and return Amazon's tracking numbers to the right Temu items.

Before you start

What you need

Amazon account access

  • A UK/EU Seller Central account with stock eligible for Multi-Channel Fulfilment
  • The account's Primary user for app self-authorisation
  • Apps and Services → Develop Apps
  • The Fetcher's Connections → Amazon MCF panel
  • A safe place to hold the Client Secret and Refresh Token during setup
  • Temu SKUs and their matching Amazon Seller SKUs
Allow time for approval. Amazon may review developer registration and the Amazon Fulfilment role. Do not send orders through Amazon until the role is approved and the Fetcher's connection test passes.

The five steps

  1. Register as an Amazon developer
  2. Create a private app with the right role
  3. Copy Client ID and Client Secret
  4. Authorise it and copy the Refresh Token
  5. Save, test and map SKUs
1

Register as an Amazon developer

Sign in to Seller Central as the Primary user, open Apps and Services → Develop Apps, accept Amazon's Selling Partner API terms and complete the developer profile and data-security questions.

Use truthful answers for this installation. The Fetcher is self-hosted and processes recipient data on your server. Amazon receives the address only after you choose Amazon fulfilment and approve the order.
Amazon Seller Central Apps and Services menu with Develop Apps highlighted
Develop Apps is under Apps and Services.
2

Create a private app and request Amazon Fulfilment

In the Developer Console, choose Add new app client, give it a clear name, select SP-API and keep it private. Request only Amazon Fulfillment: “Ship to Amazon, and Amazon ships directly to customer”.

Request only what the Fetcher needs. It does not need the Finance and Accounting role. If Amazon asks whether personal customer information will be shared with another developer's app, this self-hosted setup does not share it with sitelead.
Amazon Developer Console Add new app clientAmazon SP-API app registration form
Create a private SP-API app and request the Amazon Fulfillment role.
3

Copy the Client ID and Client Secret

Open View beside your app's Login with Amazon credentials. Copy the complete Client ID and Client Secret, without leading or trailing spaces.

Keep the secret private. Do not email it or include it in screenshots. Store it only in the Fetcher's database or your own Google Secret Manager project.
4

Authorise the app and copy the Refresh Token

From the app's action menu choose Authorize app for your own seller account. Copy the Refresh Token shown after approval. If it is lost or revoked, authorise the app again for a new token.

5

Save, run the read-only test and map SKUs

In Connections → Amazon MCF, enter the Client ID, Client Secret and Refresh Token. Confirm the marketplace ID (A1F83G8C2ARO7P for Amazon UK), select the shipping speed, save and run Test Amazon MCF connection. The Fetcher connects to Amazon's UK and EU service. The test reads status only and does not create a fulfilment order.

Then open Settings → SKU and parcel mappings and match each Temu product code (SKU) to the Amazon Seller SKU holding the stock. On the first real order, use preview, check the address and quantities, then confirm that you want to send it to Amazon.

Amazon may split an order. The Fetcher stores each package, carrier, tracking number and exact Temu line quantities. Partial, cancelled, unfulfillable or uncertain results stop for review instead of being silently submitted again.

If the test fails

The usual causes

Wrong user

Self-authorisation normally requires the Seller Central account's Primary user.

Role still pending

Check that Amazon Fulfillment is approved, then authorise the app again and retest.

Stale credential

Re-copy all three values. Re-authorise the app if the Refresh Token was revoked.

Amazon fulfilment costs money. Amazon storage, picking, packing, delivery and other applicable fees remain payable. The Fetcher asks for confirmation before creating the order, but review Amazon's own fee preview and account terms.

FAQ

Common questions

Does the connection test create an order?

No. It only checks that Amazon accepts the connection details and that the app has the required permission.

Can the same Temu order be sent twice?

The Fetcher gives each order one fixed reference with Amazon and locks it to that single attempt. Before any retry it checks with Amazon what actually happened, and anything uncertain is held for your review rather than sent again automatically.

What if Amazon uses two packages?

Each package is recorded separately. Amazon's package-to-item allocation is mapped to the original Temu order lines so each tracking number is returned only for its own quantities.

Will sitelead see my connection details or recipient data?

No. The connection details stay in your own installation or your own Google Secret Manager. Recipient data goes directly from your server to Amazon only when you approve Amazon fulfilment for that order.

Connect only after the read-only test passes.

Then match your Temu product codes to Amazon's and preview the first order before asking Amazon to fulfil it.

See Temu Order Fetcher