Sync the offer catalogue
VeraCore calls the things in its building offers. The catalogue sync copies that list into SKU.io — item codes, titles, units of measure, owners, barcodes where available — and then tries to match each one to a product you already have.
Nothing in this direction is destructive. The catalogue is read-only in SKU.io: a sync overwrites the mirror, never your products.
Run it
Open the connection's Products tab and click Sync From VeraCore.
It runs as a background job — the button reports it as queued, and the job tray shows progress under Sync VeraCore Products: while you carry on elsewhere. The table refreshes when it finishes.
While that job is running, Sync From VeraCore and Reload are disabled with a tooltip explaining why. An inventory sync or a product push running at the same time does not block them; only another catalogue sync does.
Reload re-reads what SKU.io already holds without calling VeraCore. Use it when you want the table refreshed but not re-fetched.
Read the four counters
The cards across the top are the whole point of the sync, and each one is clickable — clicking filters the table to exactly those rows.
| Card | Means | What to do |
|---|---|---|
| Offers | Everything VeraCore reports | Nothing — this is your denominator |
| Mapped | Its balance counts toward inventory | Nothing |
| Needs Review | Auto-match was ambiguous | Confirm or correct each one |
| Unmapped | Stock invisible to SKU.io | Map it, or decide it does not need mapping |
Needs Review and Unmapped are the queue. Everything else in this integration — inventory, discrepancies, fulfillment, receiving — reads through the mapping, so an offer sitting in either bucket is an offer the rest of SKU.io cannot see.
Work through them with Map an offer to a product for a handful, or Product mapping import and export for hundreds.
What the sync does to mappings
After the offers land, SKU.io walks every unmapped offer down the four-rung match ladder — exact SKU, normalised SKU, UPC, then exact name.
Two consequences worth holding on to:
- A mapping you made by hand is never touched. The matcher only considers offers with no mapping, so re-syncing is always safe. It will not undo your work, and it will not "improve" a decision you already made.
- Re-running the sync is how you pick up new matches. If you add the missing SKU.io products, or add WMS credentials so the UPC rung can run, the next sync maps whatever it now can.
The offers are items your 3PL holds for someone else (fine — leave them); the matching products do not exist in SKU.io yet (create them, then re-sync); or your item codes and SKUs genuinely differ (map them, once, by import).
Reading the table
Each row is one VeraCore offer:
| Column | Notes |
|---|---|
| Item | The VeraCore item code — click it to open the offer |
| Title | VeraCore's description |
| Mapped SKU | The SKU.io product, linked to its product page |
| Mapping | Mapped / Needs Review / Unmapped, with a tooltip explaining how it was matched |
| Owner | Whose stock it is, in a multi-client warehouse |
| UOM | Unit of measure |
| Status | VeraCore's own status for the item |
| Last Synced | When this row was last refreshed |
The search box covers item code, title, and description. The Mapping and Offer Type quick filters narrow to a bucket, and the advanced filters go further when you need to (owner, status, unit of measure, dates, and more).
Multi-product offers
An offer marked Multi-Product Offer is a kit at VeraCore: its balance is a roll-up of several underlying items rather than a count of one thing.
Those offers are excluded from discrepancies and stock takes, because comparing a roll-up against a single SKU.io product's stock produces a difference that is not real. Mapping one to a single product is possible but will double-count that stock — SKU.io warns you when you try.
Opening a single offer
Click any Item to open the offer's own page. It carries what the table cannot fit:
- SKU.io Mapping — the mapped product, and whether it was Mapped manually or Matched automatically. If it is unmapped, the suggested matches are listed here with the reason each was suggested.
- Offer Details — owner, unit of measure, product type, build type, BOM type and component count, status, lot tracking, and sync timestamps.
- UPC Codes — the barcodes VeraCore reports. If there are none, the page says so plainly: barcode matching was skipped for this offer.
- Related — one click through to this offer's inventory balances, and to its observed inventory changes.
- Raw VeraCore Payload — exactly what VeraCore sent for this offer.
VeraCore has no single-offer endpoint, so the payload shown is the one stored by the last catalogue sync, with its timestamp. Refreshing it means re-running the sync — the Reload button on that card re-reads what SKU.io stored, not what VeraCore holds right now.
When to run it
| Situation | Run a sync? |
|---|---|
| Right after connecting | Yes — this is step three of setup |
| Your 3PL added items for you | Yes |
| You pushed products to VeraCore | Yes — the mirror is what the next push checks against |
| Before a large mapping import | Yes — the importer matches on item codes it already knows |
| Inventory numbers look wrong | Usually no — that is an inventory sync, not a catalogue sync |
If automatic sync is on and Products (inbound) is enabled on the Settings → Sync tab, the catalogue also refreshes on its own schedule. The button is for when you do not want to wait.
Next steps
- Map an offer to a product — clear the Needs Review and Unmapped queues.
- How offers are matched to products — why a given offer matched, or did not.
- Push products to VeraCore — the other direction, for items your 3PL does not have yet.