Map VeraCore facilities to warehouses
Your 3PL may operate one building or six. VeraCore calls each one a facility; SKU.io calls its own a warehouse. This page is where you say which is which.
Do it before anything else, because an unmapped facility has nowhere to put its data:
- Mirrored stock has no destination. Balances from an unmapped facility are excluded from the discrepancy report rather than reconciled against the wrong building — deliberately, because a wrong building is worse than a gap.
- Fulfillments and expected arrivals resolve their warehouse through this table. No mapping, no resolution.
Discover the facilities
Open the connection's Warehouse Mappings tab and click Discover From VeraCore.
Discovery runs as a background job — you get Discovery started — track progress in the job tray, and can watch it in the job tray while you carry on elsewhere. The table refreshes itself when the job finishes.
While a discovery is running, both Discover From VeraCore and Reload are disabled, with a tooltip saying why. Only a warehouse discovery blocks them: an inventory or product sync running at the same time will not grey these out.
The three counters at the top tell you where you are:
| Counter | Meaning |
|---|---|
| Facilities | How many were discovered from VeraCore |
| Mapped | Active and pointed at a SKU.io warehouse |
| Unmapped | Facilities with nowhere to land their inventory |
Unmapped is the number to drive to zero — or to a number you have consciously decided is fine.
Map each facility
Each row shows the VeraCore facility name with its VeraCore ID underneath, so you can tell two similarly-named buildings apart.
- In the SKU.io Warehouse column, pick the warehouse that mirrors that facility. The picker is searchable — useful once you have more than a handful.
- Repeat for every facility you care about.
- Click Save Mappings.
Until you save, an amber note sits in the footer: Unsaved changes — saving re-points the mirrored inventory. Revert discards everything unsaved and puts the table back the way the server has it.
Changing a mapping does not just change a label. The mirrored stock behind that facility moves to the newly-selected warehouse as soon as you save, and the page reloads from the server afterwards so the numbers you are looking at are the real ones rather than an optimistic guess.
Change a mapping deliberately, not experimentally.
You will see a confirmation counting what was saved. If some rows fail, you get a mixed result (3 saved, 1 failed) rather than a silent partial success — the successful rows stay saved.
Creating a warehouse without leaving the page
If a facility has no SKU.io counterpart yet, open its warehouse picker and click Create New 3PL Warehouse at the top of the list. Name it, click Create & Select.
The new warehouse is created as a 3PL warehouse and selected for that row — but the mapping is only staged. You still have to click Save Mappings to persist it, so the page keeps a single save action rather than half-committing behind your back.
Auto vs Manual
The Source column records how each mapping came to be:
| Chip | Meaning |
|---|---|
| Auto | SKU.io matched the facility to a warehouse during discovery |
| Manual | A person picked it |
| — | Not mapped |
Auto-mappings are a convenience, not an assertion. Check them the first time — particularly if two of your warehouses have similar names.
Turning a facility off
The Active switch keeps the mapping but stops mirroring inventory from that facility. Use it when your 3PL still lists a building you no longer use: turning it off is reversible and preserves the mapping, so nothing has to be rebuilt if you go back.
Deactivating is almost always better than deleting.
Forgetting a facility
The delete action on a row forgets the facility: the row and its mapping are removed, and the mirrored inventory behind it is re-pointed immediately.
It is not permanent. The facility reappears — unmapped — on the next discovery, because discovery reads whatever VeraCore currently reports. Deleting is a way to clear out a stale row, not a way to hide a facility your 3PL still operates.
To stop mirroring a facility that genuinely still exists, use the Active switch instead.
Keeping it current
Last Seen shows when each facility was last reported by VeraCore. Re-run Discover From VeraCore whenever your 3PL tells you they have opened, closed, or renamed a building — new facilities arrive unmapped, and a facility that has quietly stopped being reported will show a stale Last Seen date.
Use Reload (not discovery) when you just want to re-read what SKU.io already has, without calling VeraCore.
Next steps
- Sync the offer catalogue — pull the item list, now that stock has somewhere to land.
- The inventory model — what the mirrored numbers actually mean, including the aggregate fallback for installations that report no per-facility breakdown.