> For the complete documentation index, see [llms.txt](https://docs.sellermagnet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sellermagnet.com/selling-tools/product-sourcer-overview/identifier-converter.md).

# Identifier Converter

Bulk-convert between ASIN (Amazon Standard Identification Number), UPC, EAN, and ISBN identifiers across Amazon marketplaces. Paste a list or upload a file and download the mapped results.

{% hint style="info" %}
**Difficulty:** 🟡 Intermediate · **Reading time:** \~7 min
{% endhint %}

{% hint style="success" icon="rocket" %}
**Open this page in your dashboard:** [**Go to Identifier Converter →**](https://dashboard.sellermagnet.com/sourcer/converter)
{% endhint %}

## 📋 Overview

A supplier sends you a wholesale list of 200 products, each one identified only by its UPC. To evaluate any of them you need the matching ASINs so you can pull them up on Amazon, but hand-searching 200 barcodes one at a time is a lost afternoon. The **Identifier Converter** turns that list into ASINs in a single pass.

The Converter is a bulk-conversion tool built into the Sourcer page. It lets you convert between Amazon product identifiers. ASIN, UPC, EAN, and ISBN, in large batches. Whether you have a supplier spreadsheet full of EAN codes and need the matching ASINs for a specific marketplace, or you need to reverse-lookup UPCs from a list of ASINs, the Converter handles it in seconds.

***

## Accessing the Converter

1. Log in to your SellerMagnet dashboard.
2. Navigate to **Sourcer** in the left menu.
3. Click the **Converter** tab at the top of the page.

***

## Input Methods

![SellerMagnet Identifier Converter](https://4139654583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fih2knSvVpBcq5rIeXVjM%2Fuploads%2Fgit-blob-bf267e4ab86624071e6dafa5a6d02c94f112846b%2Fidentifier-converter.png?alt=media)

The Converter accepts identifiers through two channels, displayed side by side:

### Text Input

| Feature              | Details                                                       |
| -------------------- | ------------------------------------------------------------- |
| **Input field**      | Multi-line textarea with monospace font                       |
| **Accepted formats** | One identifier per line                                       |
| **Accepted types**   | ASIN, UPC, EAN, ISBN-10, ISBN-13                              |
| **Max per batch**    | Up to 50 identifiers per conversion (extra lines are ignored) |

Paste your list directly. Each line should contain a single identifier. The system auto-detects the identifier type.

### File Upload

| Feature              | Details                                                    |
| -------------------- | ---------------------------------------------------------- |
| **Drop zone**        | Drag-and-drop area or click to browse                      |
| **Accepted formats** | `.csv`, `.xlsx`, `.xls`                                    |
| **Column detection** | Automatically identifies the column containing identifiers |

{% hint style="success" icon="rocket" %}
**Pro tip:** When using a CSV file, ensure the identifier column has a clear header like "ASIN", "EAN", or "UPC". This helps the auto-detection work reliably even in multi-column files.
{% endhint %}

{% hint style="info" icon="circle-info" %}
**Marketplace picker:** the Converter has its own **Marketplace** dropdown next to the Convert button, filled from the marketplaces your project's single-product search already uses. Pick the one the codes belong to before converting; it no longer silently follows your project's default marketplace.
{% endhint %}

***

## Credits, Quota, and Plan Requirement

{% hint style="warning" icon="triangle-exclamation" %}
**The Converter is metered.** Converting identifiers draws on an included quota, then on credits. It is not a free, uncapped tool.
{% endhint %}

| Situation                                                     | What you get                                                                                                           |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Trial** (the 14-day signup trial, or the 60-day Free trial) | 100 conversions for the whole trial. No credits: a credit pack bought during a trial cannot be spent on the Converter. |
| **Scout** (and the retired Boost +500 / legacy tiers)         | 1,000 converted codes included per billing cycle, then credits.                                                        |
| **Scout Pro / Sourcer Boost unlimited**                       | 2,500 converted codes included per billing cycle, then credits.                                                        |
| **Analytics plan**                                            | 1,000 converted codes included per billing cycle, then credits.                                                        |
| **No active Sourcer or Analytics plan**                       | 0 included; the Converter is not usable until you have one of those plans (or are in a trial).                         |

Only a **converted** code counts against the quota; a code that comes back "Not Found" is never billed. Once the included quota for the cycle (or the trial) is used up, the Converter switches to credits: **3 credits per converted code**, taken from your monthly credit pool first, then from bought credit packs. Converting on credits past the included quota requires an **active paid Sourcer plan (Scout, Scout Pro, or a legacy tier) or an active paid Analytics plan**; a trial account, a view-only team member, or a project with no Sourcer/Analytics plan at all cannot spend credits here, even with a positive balance, and sees the included quota as its hard cap. The usage bar above the results table shows what is left in the current cycle and, once that runs out, how many credits remain and whether buying more credit packs is available on your plan.

{% hint style="info" icon="circle-info" %}
**Pacing:** besides the quota, a project can only send so many codes per rolling hour (shared with the single-product Sourcer search), and the Converter also waits its turn behind a shared capacity pool used by every SellerMagnet customer's product lookups. On either limit, unsent rows come back marked **Busy**, not **Failed**: re-run them after a short wait, the identifiers themselves were fine.
{% endhint %}

***

## Running a Conversion

1. Paste identifiers into the text field **or** upload a file.
2. Click the **Convert** button.
3. A progress indicator shows the conversion status.
4. Results appear in a table below the input section.

***

## Results Table

The results table displays one row per input identifier:

| Column     | Description                                                                                        |
| ---------- | -------------------------------------------------------------------------------------------------- |
| **Input**  | The original identifier you provided                                                               |
| **Type**   | Auto-detected identifier type, shown as a colored badge (ASIN, EAN, UPC, or ISBN)                  |
| **ASIN**   | Amazon Standard Identification Number (links to the Amazon listing)                                |
| **EAN**    | European Article Number(s) mapped to the ASIN                                                      |
| **Title**  | Listing title. Always shown, and the cell is editable so you can tidy a label before exporting     |
| **Status** | Success, Failed, Busy (pacing or shared-capacity hit, resend it), or Limit (quota/credits ran out) |

***

## Statistics Bar

Above the results, a statistics bar summarizes:

| Stat            | Description                                       |
| --------------- | ------------------------------------------------- |
| **Total input** | Number of identifiers submitted                   |
| **Converted**   | Successfully converted identifiers                |
| **Failed**      | Identifiers with no matching Amazon catalog entry |

***

## 📤 Exporting Results

The **Export** button is a split menu. Pick **CSV** or **Excel** to download the results, including every column from the table, ready to import into your inventory management system, supplier negotiation spreadsheet, or listing tool.

{% hint style="info" icon="lightbulb" %}
**Tip:** The exported CSV uses UTF-8 encoding, which preserves special characters in product titles across all languages and marketplaces.
{% endhint %}

### 🚀 Analyze in Bulk Sourcer

Next to Export, an **Analyze in Bulk Sourcer** button hands the converted ASINs straight to the [Bulk Sourcer](/selling-tools/product-sourcer-overview/bulk-sourcer.md) so you can run the full profitability analysis over them in one job, no re-typing. It opens the Bulk Sourcer pre-loaded with the ASINs the conversion resolved (`/tools/bulk-sourcer?source=converter&asins=...`). Duplicate and unresolved rows are dropped automatically, so only the clean, unique ASINs are carried over.

{% hint style="info" icon="circle-info" %}
**Availability:** The Bulk Sourcer is a paid feature. If your plan does not include it yet, the hand-off still opens the tool and you land on the upgrade prompt.
{% endhint %}

***

## 🎯 Realistic Example

**Scenario:** You receive a wholesale price list from a European distributor with EAN codes. You need to find the matching ASINs to evaluate profitability.

1. Open the **Converter** tab.
2. Set the **Marketplace** dropdown to Amazon.de.
3. Copy the EAN codes from the spreadsheet and paste them into the text area (up to 50 per batch).
4. Click **Convert**.
5. In a few seconds, the results table populates. Most EANs match an ASIN; a handful return "Failed" (meaning the product is not yet listed on that marketplace).
6. Click **Analyze in Bulk Sourcer** to push the matched ASINs into the Bulk Sourcer for a full profitability run, or **Export** the results as CSV or Excel and paste the ASINs into the Sourcer's **Overview** tab one at a time.

***

<details>

<summary><strong>⚠️ Common Mistakes to Avoid</strong></summary>

| Mistake                                                        | Why It Hurts                                                                                                                                |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Mixing multiple identifier types in one batch without headers  | The auto-detection may misclassify some identifiers                                                                                         |
| Uploading a file with merged cells                             | Parsing fails on merged-cell spreadsheets; flatten them first                                                                               |
| Expecting a marketplace you have not selected in the Converter | Lookups run against the marketplace picked in the Converter's own dropdown; switch it there first if the codes belong to a different region |
| Including leading zeros in a text file opened in Excel         | Excel strips leading zeros from UPC/EAN numbers, use `.csv` format                                                                          |
| Submitting duplicates                                          | Wastes processing time; deduplicate your list before converting                                                                             |

</details>

\## ✅ Best Practices

1. **Deduplicate your list before uploading:** Remove duplicate identifiers to speed up conversion and avoid wasted lookups.
2. **Mind the marketplace you pick:** Identifier mappings are marketplace-specific. A UPC may map to different ASINs on Amazon.com vs. Amazon.de, so set the Converter's marketplace dropdown to the region the codes belong to before converting.
3. **Combine with the Sourcer:** After converting, use **Analyze in Bulk Sourcer** to score the whole batch at once, or paste matched ASINs into the Sourcer's Overview search to analyze them individually.
4. **Save exports for future reference:** Keep converted files organized by supplier and date for easy re-evaluation when prices change.
5. **Handle "Failed" results:** Products with no ASIN match may represent listing opportunities. Consider creating a new listing for those EANs.

***

## 🔧 Troubleshooting

If a conversion does not behave as expected, work through the situations below before re-running the batch.

### Mixed-identifier batches

The Converter auto-detects the type of each line, so a batch that mixes ASINs, EANs, and UPCs is allowed. The risk is misclassification: a bare 12- or 13-digit number can look like more than one code type, and a value with a stripped leading zero can be read as the wrong length. If some rows come back with an unexpected type or a "Not Found" you cannot explain, split the list so each batch holds one identifier type, or upload a file where the identifier column carries a clear header ("ASIN", "EAN", "UPC") so detection has a hint. Keeping types separate also makes the results table easier to read.

### Partial file-parse failures

When a file uploads but only some rows convert, the parser usually skipped cells it could not read cleanly. The common causes are merged cells, the identifier column not being detected (missing or ambiguous header), stray text or notes in the identifier column, and blank lines. Flatten any merged cells, give the identifier column a single clear header, remove non-identifier text from that column, and re-upload. If a spreadsheet keeps failing, export it to `.csv` first. CSV is the most predictable format for the parser.

### Identifiers that will not resolve on the marketplace you picked

A code that is valid but returns "Failed" is almost always a marketplace mismatch, not a bad identifier. Amazon catalog entries and their identifier mappings are marketplace-specific, so a UPC that resolves on Amazon.com may have no entry on Amazon.de, and the same product can carry different ASINs per region. Lookups run against the marketplace you picked in the Converter's own dropdown, so confirm that selection matches where the products are actually listed, then re-run. If the item genuinely is not listed on that marketplace, the "Failed" is correct. Treat those rows as listing opportunities rather than errors. Also re-check for typos and stripped leading zeros before assuming the catalog is at fault.

### Rows marked "Busy" instead of converting

"Busy" (not "Failed") means the row was never sent: your project hit its per-hour pace limit, or the shared capacity pool every SellerMagnet customer's lookups draw from was temporarily low. Wait a minute or two and re-run just the "Busy" rows; nothing about those identifiers was wrong.

### File format issues

Uploads must be `.csv`, `.xlsx`, or `.xls`. A file that is rejected on upload is usually the wrong extension (for example, `.txt` or `.numbers`). Re-save in a supported format, and remove unused columns and extra sheets so only the identifier data remains. Remember the per-batch cap as well: only the first 50 identifiers in any input are processed, so a large file will convert its first 50 rows and ignore the rest. Split long lists into batches of 50 and run them in sequence.

***

## ❓ FAQ

<details>

<summary><strong>How many identifiers can I convert at once?</strong></summary>

Up to 50 identifiers per conversion. If you paste or upload more, only the first 50 are processed. Split larger lists into batches of 50 and run them in sequence.

</details>

<details>

<summary><strong>Which marketplace does the converter use?</strong></summary>

Whichever marketplace you pick in the Converter's own **Marketplace** dropdown, next to the Convert button. It is filled from the marketplaces your project's single-product search uses; pick the one the codes belong to before converting.

</details>

<details>

<summary><strong>Why do some identifiers return "Failed"?</strong></summary>

"Failed" means the identifier has no matching Amazon catalog entry on the marketplace you picked. Common reasons: the product is new or not yet listed, it was delisted, or it exists only on a different regional marketplace. Verify by searching the identifier directly on Amazon; if it appears there, switch the marketplace dropdown to match or re-check the identifier for typos.

</details>

<details>

<summary><strong>Does each conversion consume search credits or quota?</strong></summary>

Yes. The Identifier Converter is metered: each billing cycle (or, in a trial, for the whole trial) you get an included number of conversions, then the Converter spends credits, 3 credits per converted code (a "Not Found" result is never billed). The included quota is 100 for a trial, 1,000 a month on Scout or an Analytics plan, and 2,500 a month on Scout Pro or an unlimited Sourcer tier. Converting on credits past that quota needs an active paid Sourcer or Analytics plan; a trial, a view-only team member, or a project with no such plan is capped at the included quota with no credit fallback. The usage bar above the results shows what is left. The only other cap is **50 identifiers per batch**, plus a pacing limit on how many codes a project can send per hour.

</details>

<details>

<summary><strong>Do I need a paid plan to use the Converter?</strong></summary>

You can convert during a trial (100 conversions, included, no credits). Outside a trial, converting at all needs an active Sourcer plan (Scout, Scout Pro, or a legacy tier) or an active Analytics plan; a project with neither has 0 included conversions and cannot spend credits here either.

</details>

<details>

<summary><strong>Can I convert ASINs to EANs (reverse lookup)?</strong></summary>

Yes. The converter works bidirectionally. Enter ASINs and the results will include the mapped EAN, UPC, and ISBN where available.

</details>

<details>

<summary><strong>What file formats are supported for upload?</strong></summary>

CSV, XLSX, and XLS files. Ensure identifiers are in a single column with a clear header row.

</details>

***

## ➡️ What's Next?

{% content-ref url="/pages/YtBP2GSz5q83gTVW9tOI" %}
[Product Sourcer](/selling-tools/product-sourcer-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/9BLtTr2v8wYs6EWCS7Ll" %}
[Chrome Extension](/selling-tools/product-sourcer-overview/chrome-extension.md)
{% endcontent-ref %}
