Review VeraCore inventory
The Inventory tab is where you find out whether SKU.io and your 3PL agree about what is in the building.
It is a mirror, not a controller: SKU.io copies what VeraCore reports and compares it against its own stock. Nothing here changes anything at the warehouse. If the numbers disagree, the fix is either a mapping, a conversation with your 3PL, or accepting VeraCore's count — never editing this page. The Comparison tab works that out, the same way for every 3PL: see Compare 3PL inventory with SKU.io.
If the quantity columns do not mean what you expect, read The inventory model first. VeraCore's available is not SKU.io's available, and that difference is behind most surprises.
Refresh the mirror
Click Refresh From VeraCore. You get Inventory sync queued — track its progress in the job tray, and the job runs under Sync VeraCore Inventory:. The page reloads itself when the job finishes.
While one is already running the button is disabled: An inventory sync is already running — track its progress in the job tray.
Reload re-reads what SKU.io already holds without calling VeraCore. Use it when you just want the page refreshed.
The subtitle under the heading tells you how current the mirror is — VeraCore Offer balances mirrored into SKU.io. Last synced: …, or Not synced yet. if it has never run.
Deal with unmapped facilities first
If any VeraCore facility has no SKU.io warehouse, a warning sits above everything else:
{n} VeraCore facilities are not mapped to a SKU.io warehouse. Balances from them are mirrored but cannot be compared against SKU.io stock.
The Map Facilities button next to it takes you straight to Warehouse Mappings.
Clear this before you trust anything below it. Stock from an unmapped facility is mirrored but sits outside the comparison entirely, so the comparison answers a narrower question than it looks like it does.
Read the numbers
The cards total the mirrored stock: Available + Reserved, Available, Committed and Incoming.
The Warehouse selector at the top scopes the cards and All Inventory to one building. It lists only warehouses that are actually mapped, because an unmapped facility can't scope a comparison. Leave it on All Warehouses for the overall picture.
Under the cards, two tabs split the page: All Inventory and Comparison. The open tab is written into the URL, so a link to it can be shared or bookmarked and survives a refresh. Old links to the retired Discrepancies, SKU.io Only and VeraCore Only segments open Comparison.
All Inventory
Every mirrored balance row, one per offer per facility.
Item, Title, SKU.io Product, Warehouse, UoM, then On Hand, Available, Committed and Incoming, then Source, Last Synced and Updated. Rows with no mapping show an amber Unmapped chip instead of a SKU; a facility with no warehouse shows Not mapped under its name.
Source is the column people miss:
| Chip | Means |
|---|---|
| Per-facility | VeraCore reported this balance against a specific facility |
| Aggregate | VeraCore reported no per-facility split, so the aggregate balance was mirrored against the default facility |
An Aggregate row is not wrong, but it is less precise — the quantity is real, the building it is attributed to is an assumption. See the aggregate fallback for when this happens and what it costs you.
Rows carrying the purple kit icon are multi-product offers, left out of the comparison. The tooltip repeats the reason on hover.
The View Ledger action on each row opens the inventory ledger filtered to that item. Search covers item, title, and facility; the advanced filters go further — quantities, flags, dates, facility.
Compare with SKU.io
Open the Comparison tab. SKU.io compares VeraCore's sellable on-hand with its own, for each mapped warehouse, at the same moment, every day. It shows which products are off and why, and lets you accept VeraCore's count with a stock take. See Compare 3PL inventory with SKU.io.
What used to be separate segments are now statuses on that tab:
| Was | Now, on Comparison |
|---|---|
| Discrepancies | SKU.io higher and 3PL higher rows. Click the Off by more card |
| SKU.io Only | SKU.io only rows |
| VeraCore Only | 3PL only rows. Map them on the Products tab |
An Aggregate row is compared like any other, but its warehouse is assumed. Keep that in mind before you accept a count for it.
How often to do this
Enable the inventory capability on Settings → Sync and the mirror refreshes on its own schedule. The button here is for when you do not want to wait — before a stock take, after your 3PL tells you they have adjusted something, or when a number looks wrong.
The comparison itself runs every day on its own, and you can change its schedule in its Settings. Reviewing it is worth a regular slot. A small difference caught weekly is a mapping fix; the same difference found after a quarter is an inventory investigation.
Next steps
- Compare 3PL inventory with SKU.io — find what's off, and accept your 3PL's count.
- Read the inventory ledger — when a balance moved, and by how much.
- The inventory model — what each quantity column actually means.