Why There Are So Many Product Codes
If you've ever wondered why there are so many different ways to identify the same product, you're not alone. The short answer is that different systems were built by different organizations at different times, and each one created their own numbering scheme. In EDI, you'll encounter several types of product identifiers:
UPC / EAN (Universal Product Code)
This is the barcode printed on your product's packaging. In the US and Canada, it's a 12-digit UPC-A code. Internationally, it's a 13-digit EAN. This is the most widely used identifier in retail EDI. If you only set up one identifier, make it your UPC.
ASIN (Amazon Standard Identification Number)
This is Amazon's proprietary product identifier — a 10-character alphanumeric code (e.g., B08N5WRWNW). If you sell on Amazon through Vendor Central or Seller Central, your orders will reference ASINs. Each product variation (size, color) has its own ASIN.
Retailer-Specific SKUs
Many retailers assign their own internal SKU numbers to your products. For example, Target might call your vanilla extract TGT-81049372 while Walmart calls the same product WM-5529841. These are completely different from your own SKU and from the UPC.
How Mappings Work in RetailReady
A mapping tells RetailReady: "When this retailer sends an order with product code X, it means my product Y." Without mappings, RetailReady can't figure out which product the retailer is ordering.
Mappings are managed directly in the Products table. Each product row can be expanded to show retailer-specific mappings. To add a mapping:
- Go to Products and find the product in the table.
- Click the expand arrow to see existing retailer mappings.
- Add a new mapping row, select the trading partner, and enter the identifier they use for this product (UPC, ASIN, Buyer's SKU, etc.).
You can add multiple mappings per product — one for each retailer that uses a different identifier. A mapping without a specific retailer is treated as a "global" mapping that applies to all trading partners.
Example
| Your Product | Your SKU | UPC | Amazon ASIN | Target SKU |
|---|---|---|---|---|
| Vanilla Extract 4oz | VAN-EXT-4 | 012345678901 | B08N5WRWNW | TGT-81049372 |
| Vanilla Extract 8oz | VAN-EXT-8 | 012345678918 | B08N5XYZ12 | TGT-81049373 |
Common Problems with Missing Mappings
The most frequent EDI errors new suppliers encounter are related to product matching. Here's what happens when mappings are missing:
- Unmatched orders — A purchase order arrives, but RetailReady can't find the product. The order gets flagged as "needs attention" and you have to manually identify the product and add the mapping.
- Delayed acknowledgment — You can't send an 855 acknowledgment until all line items are matched. This can cause you to miss the retailer's acknowledgment deadline.
- Incorrect invoices — If you manually override a match without adding a proper mapping, future orders for the same product will have the same problem.
Tip: Set up your mappings before you go live with a retailer, not after. During practice mode, review the practice order line items and make sure every product maps correctly. Adding mappings proactively saves you from scrambling when real orders arrive.