Skip to main content

Map an offer to a product

A mapping is the link between one VeraCore offer and one SKU.io product. Until it exists, that offer's stock, shipments, and receipts are invisible to SKU.io.

Most of your catalogue maps itself during the sync. This page is about the rest.

Where to start​

On the Products tab, click the Needs Review card, then the Unmapped card. That is the whole queue, in the order worth doing it.

Needs Review first: those offers already have a suggested product waiting, so each one is a confirm-or-correct decision rather than a search. Unmapped second: those need you to find the product yourself, or to decide the offer does not need a SKU.io counterpart at all.

Map one offer​

  1. Click the offer's map action in the table (or open the offer and use Map Product / Change Mapping). The Map VeraCore Offer dialog opens.

  2. If there are Suggested matches, they are listed first, each with the reason it was suggested. Click one to select it.

  3. Otherwise use the SKU.io product search. Type at least two characters — it searches SKU and name, and only offers sellable products.

  4. Click Save Mapping. You get a Mapping saved confirmation and the row updates.

Save Mapping stays disabled until you pick something, and tells you why on hover: Pick a SKU.io product to map this offer to, or This offer is already mapped to that product.

Remapping​

If the offer is already mapped, the dialog says so up front — Currently mapped to SKU. Saving replaces that mapping — and the previous product is pre-selected in the search field. Saving swaps the link; there is no separate unmap-then-remap step.

Removing a mapping​

Remove Mapping in the dialog unlinks the offer without touching either record. It is disabled when there is nothing to remove, with a tooltip saying exactly that.

You can also unmap directly from the table row. The confirmation is blunt about the consequence: ITEM will stop counting toward SKU.io inventory until it is mapped again.

That is the real cost of unmapping — not lost data, but a hole in your stock picture until you map it again.

Mapping from the offer page​

Click an Item in the table to open the offer. The SKU.io Mapping card at the top gives you the same actions with more context:

  • When mapped, it shows the product with a chip reading Mapped manually or Matched automatically, so you can tell your decisions apart from the matcher's.
  • When unmapped, it explains which case you are in — Automatic matching found more than one possible SKU.io product and could not choose between them, or No SKU.io product is mapped to this offer, so whatever VeraCore holds for it is invisible to SKU.io.
  • When there are candidates, they are shown as a table with SKU, Name, and Why — the reason the matcher put each one forward. Each SKU links to its product page, so you can check before deciding.

Use the offer page when the choice is not obvious and you want to look at the candidates properly. Use the table dialog when you already know the answer.

What the errors mean​

"already mapped" on save​

One SKU.io product can back at most one offer per connection. If the product you picked is already mapped to a different offer, the save is refused and the dialog shows the reason inline.

Unmap the other offer first, then come back. This is the same one-to-one rule the match ladder enforces, and the same rule most import validation errors exist to protect.

The multi-product warning​

If the offer is a kit, the dialog warns before you save:

This is a multi-product offer — its VeraCore balance is a roll-up of several items. Mapping it to a single SKU.io product will double-count that stock.

It does not block you, because there are legitimate reasons to want the link. But the warning is accurate: the balance behind a kit offer is not the balance of any one product, and mapping it to one makes SKU.io believe otherwise. In most cases the right answer is to leave a kit offer unmapped and map its components instead.

Mappings you make are permanent​

Every mapping made by hand — in the dialog, on the offer page, or by import — is recorded as manual. The automatic matcher never re-evaluates a mapped offer, so:

  • A later sync will not overwrite your choice.
  • A later sync will not "improve" it either.

If a manual mapping turns out to be wrong, change it here. Re-running the sync will not fix it for you.

Doing this in bulk​

Mapping fifty offers one dialog at a time is a bad use of an afternoon. Export the table, fill in the SKU.io SKU column in a spreadsheet, and upload it back — the headers already line up, so nothing has to be renamed.

Full column reference, matching rules, and validation behaviour: Product mapping import and export.

Next steps​

Last verified: