> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/orders/configure-order-setup/alternative-product-ids/using-alternative-product-ids-in-orders.md).
# How to map orders using alternative IDs
Learn how to review tracked alternative channel product IDs and enable alternative ID mapping for order matching.
Alternative ID mapping matches marketplace order items to the right product in your eCommerce platform when identifiers differ.
For example, a marketplace can return an EAN while your eCommerce platform uses an SKU.
### :memo-circle-check: Before you start
**You'll need:**
* The [How to add the order-sync add-on](/list-advertise/orders/order-connections/how-to-add-the-order-sync-add-on.md)
**Good to know:**
* Alternative ID mapping uses the unique product ID from your main import source. Each item needs an ID that matches its ID in that source.
* Alternative channel IDs don't need to exist in the main import source. You can add them through a secondary import or rules.
* If you sell variants, the identifier should exist on the sellable variant.
{% hint style="info" %}
#### Example: Shopify
For a main Shopify import source, each item needs its Shopify product ID in Channable (e.g. item one: Shopify ID `454`, item two: Shopify ID `876)` .
You can use [rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/using-rules.md) or import more product data to add listing IDs in Channable without adding them to Shopify. (e.g. create a rule to add listing ID `433343` to the item with Shopify ID `454`, and listing ID `325678` to the item with Shopify ID `876`.)
When the marketplace sends an order for `433343` or `325678`, Channable finds the matching Shopify item and creates the order in Shopify.
{% endhint %}
***
### Set up alternative ID mapping
{% stepper %}
{% step %}
### View alternative IDs
1. In **Setup > Order connections**, click **Settings** for the connection.
2. Open the **Alternative ID mapping** tab.
From here, you can view the alternative ids found on a channel level (**Alternative channel ID**) and from your import source (**Alternative import ID**).
Alternative channel ID table
* **Unique ID:** The primary item ID used by your eCommerce platform to reference and match to order items. Set under [Unique ID for alternative channel ID mapping](https://github.com/channable/feedscrubber/pull/url).
* **Alternative ID:** The project field set as the **Unique ID per item** in the channel's settings.
* **Value:** The actual value imported from your product catalog for this alternative ID.
* **Mapped on:** The time and date this item's unique ID was mapped to its alternative ID in Channable.
Alternative import ID table
* **Unique ID:** The primary item ID used by your eCommerce platform to reference and match to order items.
* **Alternative ID:** The project field set as the **Unique ID per item** in the channel's settings.
* **Value:** The item ID that is sent to the marketplace based on your **Unique ID per item** set in the channel's settings.
* **Mapped on:** The time and date this item's unique ID was mapped to its alternative ID in Channable.
{% endstep %}
{% step %}
### Check match results (channel-level)
1. If you're using a channel with an order connection, go to **Channels > \[your channel] > Order connections** and click the **Alternative ID mapping** tab.
2. Review your matching results:
* **Match:** One product matches the marketplace identifier.
* **No match:** No product matches the marketplace identifier.
* **Multiple matches found:** Multiple products use the same identifier.
If several identifiers on one item share the same value, Channable uses that item. If multiple products share the same value, Channable can't select an item reliably.
* To fix missing ids, add an identifier to the item.
* To fix duplicate ids, make the ids unique or change the marketplace id.
{% endstep %}
{% step %}
### Enable the right mapping method
Choose the setup that matches your workflow:
I have an active channel for the marketplace (recommended)
If you’re sending listings via a channel in Channable, we’ll prioritize mapping orders by channel ID before import ID.
1. Go to **Channels > \[your channel]**.
2. Click **Settings** for the channel you want to enable Alternative ID mapping for.
3. In the channel sidebar, click **Order connection** and go to the **Alternative ID mapping** tab.
4. Click the toggle for **Map orders by alternative channel ID** to use the **Unique ID per item** in your channel settings to match compatible items that we otherwise could not create orders for.
**Change source field of your eCommerce platform's unique IDs**
If you want to use a different field with unique IDs from your import source, you can change it in your ID field settings.
1. Go to **Setup > ID fields**.
2. For **Unique ID for alternative channel ID mapping**, select a field with unique IDs from your import source. This will be used to map channel-specific IDs back to your platform ID for creating orders.
3. Click **Save**.
I don’t use channels and only use the order connection feature
1. Go to **Setup > Order connections**.
2. Click **Settings** for the connection you want to enable mapping for.
3. Click the toggle for **Map orders by alternative import ID** to use the Unique ID per item in your project settings to match compatible items that we otherwise could not create orders for.
{% endstep %}
{% endstepper %}
Channable will now use alternative IDs to find the item with the matching unique product ID. When it processes an order, your order connection will:
1. Read the identifier from marketplace order data.
2. Match it against tracked platform unique IDs.
3. Create the order line when it finds one product.
### Troubleshoot matching
**Nothing found**
* It's not matching the same as your main import connection
**Cases where unique channel id and item id are the same**
* Your channel doesn't need alternative ID matching
Fix no match
Check that the marketplace identifier exists on the matching item in Channable. It doesn't need to exist in your ecommerce platform. Also confirm that the marketplace sends the identifier you expect.
Fix multiple matches found
Make each alternative ID value unique. If you cannot remove duplicates, use another identifier for matching.
Fix matching after a secondary import
Confirm that each item's unique product ID still matches its ID in the main import source. You can add alternative channel IDs through a secondary import or rules. Do not overwrite the unique product ID.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://helpcenter.channable.com/list-advertise/orders/configure-order-setup/alternative-product-ids/using-alternative-product-ids-in-orders.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.