Mapping Opportunities
Mapping Opportunities find vendor items that match your store products. This article explains each matching setting, the confidence score and the SKU prefix rules.
Mapping Opportunities find items in your vendor catalogs that match products in your store. Each match is a suggestion. Nothing is mapped until you accept it.
Go to Sites > Mapping Automation to set the matching settings and review the opportunities.
What a Mapping Opportunity is
A Mapping Opportunity is a suggested link between a store product and a vendor SKU. Each opportunity shows the product, the vendor, the vendor SKU, the kind, the confidence score and the reason (the setting that found it).
- Map: the product is not yet mapped to a vendor.
- Crossmap: the product is already mapped to a vendor. The opportunity adds one more vendor.
Mapping Opportunities never change a mapping on their own. They skip a vendor that the product is already mapped to. They also skip a vendor SKU that is already mapped to a different product.
Matching settings
Each card on the Mapping Automation page is one matching setting. Turn on a card to use it. Start with one setting, run a search, and check the results. Then add more settings.
| Setting | Compares | Example match |
|---|---|---|
| Exact Product SKU to Vendor SKU | Product SKU and vendor SKU | ABC-123 = ABC-123 |
| Product SKU to Vendor SKU | Product SKU and vendor SKU, after a prefix change | A15-001 → ABC-001 |
| Exact Product SKU to Part Number | Product SKU and manufacturer part number | B4-XA1-Z004A03 = B4-XA1-Z004A03 |
| Exact Product SKU to Vendor Part Number | Product SKU and the vendor's own part number | BILB4-XA1-Z004A03 = bilB4-XA1-Z004A03 (Turn 14) |
| Exact UPC | Product UPC and vendor UPC | 012345678905 = 012345678905 |
| Exact Brand & Part Number | Brand and part number together | Bilstein + B4-XA1-Z004A03 |
Exact Product SKU to Vendor SKU
The product SKU must be the same as the vendor SKU, character for character. Example: the store SKU ABC-123 matches the vendor SKU ABC-123.
Turn it on when your store uses the vendor's SKUs as your SKUs.
Product SKU to Vendor SKU
This setting uses the prefix table of each vendor. It changes the start of the product SKU to the vendor prefix. Then it looks for that vendor SKU. Example: with the rule A15 → ABC, the store SKU A15-001 matches the vendor SKU ABC-001.
Turn it on when your SKUs are the vendor SKUs with a different prefix. You must also add the prefix rules for each vendor. See "Vendor settings for SKU matching" below.
Exact Product SKU to Part Number
The product SKU must be the same as the manufacturer part number. Example: the store SKU B4-XA1-Z004A03 matches a vendor item with the part number B4-XA1-Z004A03.
Turn it on when your store uses manufacturer part numbers as SKUs.
Note: before November 2026, this card had the name "Exact Product SKU to Vendor Part Number". The setting did not change. If you had it on, it stays on.
Exact Product SKU to Vendor Part Number
The product SKU must be the same as the vendor's own part number. Some vendors add their own code to the manufacturer part number. Example: Turn 14 uses bilB4-XA1-Z004A03 for the Bilstein part B4-XA1-Z004A03. The match ignores upper case and lower case, so the store SKU BILB4-XA1-Z004A03 matches.
This setting is off by default. It works for vendors with a shared catalog that supply a vendor part number. Today, this is Turn 14.
Turn it on when your store uses the Turn 14 part number as the SKU.
Exact UPC
The product UPC must be the same as the vendor UPC. A UPC must have 8 or more digits. The setting skips other values, for example a part number in the UPC field, or all zeros.
For Ingram, Synnex and D&H, a UPC that is different only by leading zeros also matches. The reason shows "Normalized UPC Match". See Missing Leading Zeros When Mapping SKUs.
Turn it on when your products have correct UPCs. UPC is the most reliable signal.
Exact Brand & Part Number
The brand and the part number must both be the same. Example: brand Bilstein and part number B4-XA1-Z004A03. The product uses its own brand and part number. If it has none, it uses the values of a vendor SKU that it is already mapped to.
Turn it on to add more vendors to products that already have a brand and part number.
Worked example: a Turn 14 item
Your store has the SKU BILB4-XA1-Z004A03. Turn 14 has this item:
- Turn 14 item (vendor SKU): 831948
- Part number: B4-XA1-Z004A03
- Vendor part number: bilB4-XA1-Z004A03
- Brand: Bilstein
Result for each setting:
- Exact Product SKU to Vendor SKU: no match. The vendor SKU is 831948.
- Product SKU to Vendor SKU: no match. No prefix rule can change BILB4-XA1-Z004A03 into 831948.
- Exact Product SKU to Part Number: no match. BILB4-XA1-Z004A03 is not the same as B4-XA1-Z004A03.
- Exact Product SKU to Vendor Part Number: match. BILB4-XA1-Z004A03 is the same as bilB4-XA1-Z004A03 when case is ignored.
- Exact UPC: no match. The Turn 14 UPC field holds B4-XA1-Z004A03. That is not a UPC, so the setting skips it.
- Exact Brand & Part Number: matches only if the product already has the brand Bilstein and the part number B4-XA1-Z004A03.
The brand is the same and the UPC is not compared. If the costs are close or not known, the score is 100 (Very High).
Vendor settings for SKU matching
When Product SKU to Vendor SKU is on, the Mapping Automation page shows "Vendor settings for SKU matching", with one link for each vendor. Each link opens the Prefix matching section of the vendor's SKU Mapping page.
- Click the vendor name.
- Click Add rule.
- Type the Product SKU prefix, for example Product-SKU-Prefix-.
- Type the Vendor SKU prefix, for example Prefix-.
- Click Save prefix rules.
With this rule, the product Product-SKU-Prefix-12-345 matches the vendor SKU Prefix-12-345. If more than one rule fits a product SKU, the longest product SKU prefix is used.
Remove dashes from the matched vendor SKU: select this option when the vendor SKUs have no dashes. With the example rule, Product-SKU-Prefix-12-345 then matches Prefix-12345. The option removes dashes only from the part after the prefix.
Searching for Mapping Opportunities
Click Update & Find Mapping Opportunities to save the settings and search all products. A search can take from minutes to hours. A search does not change any mapping.
Spark Shipping also checks new products when it imports them. To check one product, open the product and click Re-scan in the Mapping Opportunities panel.
For vendors with a shared catalog, such as Turn 14, the search also looks in the full shared catalog. When it finds an item there, it adds the item to your vendor catalog.
Confidence score
Each opportunity starts at 100. Spark Shipping takes points off when other data does not agree. A check that it cannot make takes nothing off.
| Setting | Brand mismatch | Part number mismatch | UPC mismatch | Cost difference |
|---|---|---|---|---|
| Exact Product SKU to Vendor SKU | −20 (brand or part number) | −20 | 0 to −40 | |
| Product SKU to Vendor SKU | −20 (brand or part number) | −20 | 0 to −40 | |
| Exact Product SKU to Part Number | −20 | not checked | −20 | 0 to −40 |
| Exact Product SKU to Vendor Part Number | −60 | not checked | −20 (real UPCs only) | 0 to −40 |
| Exact UPC | −20 (brand or part number) | not checked | 0 to −40 | |
| Exact Brand & Part Number | not checked | not checked | −20 | 0 to −40 |
- Mismatch: both values are known and they are different. Brand and part number checks ignore case and extra spaces.
- Real UPCs only: the new Vendor Part Number setting counts a UPC mismatch only when both values have 8 or more digits. Turn 14 often puts the part number in the UPC field.
- Cost difference: Spark Shipping compares the vendor cost with the product cost. The product cost is the average cost of the vendors the product is mapped to. If there are none, it is the cost from your store. The deduction is the percent difference, up to 40. Example: $100 and $110 are 9.5% apart, so the score goes down by 9.5.
The score gives a label:
| Label | Score |
|---|---|
| Very High | 81 to 100 |
| High | 61 to 80 |
| Moderate | 21 to 60 |
| Low | 0 to 20 |
| Very Low | below 0 |
Example for Exact Product SKU to Vendor Part Number: a brand mismatch and a UPC mismatch give 100 − 60 − 20 = 20 (Low).
Accept Very High and High opportunities first. Examine Moderate, Low and Very Low opportunities before you accept them.
Accepting and rejecting opportunities
- Click Accept or Reject on a row for one opportunity.
- Click Accept All or Reject All for all open opportunities. When you filter the table, these buttons become Accept Visible Opportunities and Reject Visible Opportunities.
- Click Select Page, then Accept Selected or Reject Selected. A selection holds up to 1,000 opportunities.
- Click Unaccept or Unreject to undo.
Use the counters to show Open, Accepted, Rejected, Stale or All opportunities. An opportunity becomes Stale when the product or the vendor SKU was mapped in a different way first.
FAQ
Why do I see no match?
Check these causes:
- The matching setting is off, or you did not run a search after you turned it on.
- The values are not the same. For example, the store SKU has a brand code that the vendor part number does not have. Try a different setting.
- The product is already mapped to that vendor.
- The vendor SKU is already mapped to a different product.
- An opportunity for the same product and vendor SKU already exists. This includes a rejected one. Look in the Rejected or All counter.
- The product already has an open opportunity with that vendor.
- The UPC field does not hold a real UPC (8 or more digits).
- For Exact Product SKU to Vendor Part Number: the vendor does not use a shared catalog or does not supply a vendor part number.
What is the difference between Part Number and Vendor Part Number?
The part number is the manufacturer part number, for example B4-XA1-Z004A03. The vendor part number is the code that the vendor uses for the same part, for example Turn 14 bilB4-XA1-Z004A03. Use the setting that matches the values in your store SKUs.
Does a search change my mappings?
No. A search only makes suggestions. A mapping changes only when you accept an opportunity.