VeraCore tabs and columns reference
A VeraCore connection has fourteen tabs. Every one is always available — unlike some 3PL integrations, VeraCore exposes the same surface to every account, so there is no per-connection capability list that hides sections.
This page is the map: what each tab is for, every column on its table, and the filters above it.
| Tab | URL segment | Icon |
|---|---|---|
| Dashboard | /dashboard | mdi-view-dashboard |
| Warehouse Mappings | /warehouse-mappings | mdi-warehouse |
| Inventory | /inventory | mdi-package |
| Inventory Ledger | /inventory-ledger | mdi-clipboard-list |
| Products | /products | mdi-tag-multiple |
| Orders | /orders | mdi-package-variant |
| Fulfillments | /fulfillments | mdi-truck-delivery |
| Expected Arrivals | /expected-arrivals | mdi-truck-check |
| Report Tasks | /report-tasks | mdi-file-chart |
| Shipping Methods | /shipping-methods | mdi-truck-fast |
| Source Codes | /source-code-mappings | mdi-code-tags |
| Financial | /financial | mdi-currency-usd |
| Activity Log | /activity | mdi-history |
| Settings | /settings | mdi-cog |
All routes hang off /integrations/veracore/<connection-id>/.
Dashboard
The health page — orders, inventory, products, and receiving activity at a glance. It answers "is everything flowing?" without opening another tab.
Two buttons sit in the header. Refresh re-reads the figures SKU.io already holds. Refresh From VeraCore starts an actual sync, and is unavailable while one is running — hovering explains why: "A VeraCore sync is already running — track its progress in the job tray." The tiles update themselves when that job finishes, so you can leave the page open.
The KPI cards
Three headings group them.
Orders
| Card | Sub-label | Lands on |
|---|---|---|
| Total Orders | Across all statuses | Orders |
| Unlinked Orders | Missing SKU fulfillment | Orders, filtered to unlinked |
| Pending Reports | Queued or polling | Report Tasks, status polling |
| Failed Reports | Require retry | Report Tasks, status failed |
Inventory & Products
| Card | Sub-label | Lands on |
|---|---|---|
| Mirrored Offers | VeraCore Available | Inventory |
| Discrepancies | VeraCore vs SKU.io | Inventory, Discrepancies segment |
| VeraCore Products | Offers in the catalog | Products |
| Unmapped | No SKU.io product | Products, unmapped filter |
| Needs Review | Fuzzy match — confirm | Products, needs-review filter |
| Unmapped Facilities | No SKU.io warehouse | Warehouse Mappings |
Receiving
| Card | Sub-label | Lands on |
|---|---|---|
| Pending Expected Arrivals | Built, not yet announced | Expected Arrivals, pending |
| Announced to VeraCore | Awaiting receipt at the 3PL | Expected Arrivals, sent |
| Arrival Errors | Rejected — fix and re-push | Expected Arrivals, error |
Every card is clickable and lands on the tab and filter that explains it. A card only takes on a colour when its value is non-zero, so a screen of neutral tiles is a healthy one — a coloured number is the thing worth clicking.
The panels
Below the KPIs, five panels: one chart and four clocks.
| Panel | What it shows |
|---|---|
| Orders by Status | A bar per VeraCore order status, coloured by outcome — green shipped, blue in progress, amber waiting, red held. View all → opens the Orders tab |
| Orders Sync | Last order fetch |
| Tracking Sync | Last tracking update |
| Inventory Sync | Last Available-quantity mirror |
| Products Sync | Last Offer catalog pull |
The clocks read in plain language — Just now, 3 hours ago, 2 days ago — and a pipeline that has never run says Never synced rather than showing a zero. On a new connection that is the expected reading, not a fault.
The chart's empty state says so too: No order status data yet — run a sync to populate.
Warehouse Mappings
Which VeraCore facility corresponds to which SKU.io warehouse. Facilities are discovered automatically from the inventory feed.
| Column | Notes |
|---|---|
| VeraCore Facility | The facility name as VeraCore reports it |
| SKU.io Warehouse | The warehouse it maps to — editable inline |
| Saved As | The mapping that is persisted, versus the one you are editing |
| Active | Whether the mapping is in use |
| Source | Whether the mapping was auto-created or set by a person |
| Last Seen | When the facility last appeared in a sync |
The row menu offers Forget this facility? — removes a facility SKU.io discovered but you do not use.
See Map VeraCore facilities to warehouses.
Inventory
The biggest tab. It opens on four segment cards that split every item into one of four buckets, four balance cards summarising totals, and four sub-tabs.
The count chip stays visible even at zero. "Nothing is out of balance" is information, so the chip is never hidden.
While a sync is running, the sync button is disabled with the tooltip "An inventory sync is already running — track its progress in the job tray."
All Inventory
Every mirrored balance, one row per item per facility.
| Column | Notes |
|---|---|
| Item | VeraCore offer ID |
| Title | Offer title |
| SKU.io Product | The mapped product, or blank |
| Warehouse | The VeraCore facility |
| UoM | Unit of measure |
| On Hand | Physically in the building |
| Available | Free to sell |
| Committed | On Hand minus Available |
| Incoming | Expected in |
| Source | Whether the row came from a per-facility figure or an aggregate fallback |
| Last Synced | When VeraCore last reported it |
| Updated | When the SKU.io row last changed |
Filters: All Items / Mapped To A Product / Not Mapped, plus a warehouse filter (All Warehouses).
Discrepancies
Items where SKU.io and VeraCore disagree.
| Column | Notes |
|---|---|
| SKU | The SKU.io product |
| VeraCore Item | The offer it is mapped to |
| Warehouse | The SKU.io warehouse |
| Unit Cost | Used to value the variance |
| In Kits | How many kits use this component |
| SKU.io Qty | What SKU.io believes |
| VeraCore Available | What VeraCore reports |
| Discrepancy | The difference |
| Value | Discrepancy × unit cost |
| Last Synced | When VeraCore last reported it |
Selected rows can be turned into a stock take — see Create a stock take from discrepancies. The stock-take status filter offers Draft, Open (Initialized), and Closed (Finalized).
SKU.io Only
Products SKU.io holds stock for that VeraCore has never reported.
| Column |
|---|
| SKU · Name · Type · Unit Cost · SKU.io Qty |
VeraCore Only
Offers VeraCore reports that are not mapped to any SKU.io product.
| Column | Notes |
|---|---|
| Item · Title · Facility | Identity |
| On Hand · Available · Committed · Incoming | Balances |
| Status | Whether the offer needs review |
Inventory Ledger
What changed between two inventory snapshots. These are derived diffs, not warehouse transactions — see Read the inventory ledger.
| Column | Notes |
|---|---|
| Observed At | When the snapshot that produced this row was taken |
| Item | VeraCore offer ID |
| Title | Offer title |
| Warehouse | The facility |
| On Hand | The new on-hand figure |
| Available | The new available figure |
| Delta | The change since the previous snapshot |
| Source | Which kind of comparison produced the row — see Statuses reference |
Filters:
| Filter | Options |
|---|---|
| Direction | All Changes · Increases · Decreases |
| Source | Changes Only · Snapshot Change · No Longer Reported · First Observation · All Sources |
| Warehouse | All Warehouses, then one per facility |
Products
The mirrored VeraCore Offer catalogue, with the SKU.io mapping laid over it. Card title: VeraCore Offers.
| Column | Notes |
|---|---|
| Item | The VeraCore offer ID |
| Title | Offer title |
| Mapped SKU | The SKU.io product behind it |
| Mapping | Mapped / Needs Review / Unmapped |
| Owner | Which client account owns the offer at your 3PL |
| UOM | Unit of measure |
| Status | Offer status at VeraCore |
| Last Synced | When the catalogue sync last touched this offer |
Filters: All Offers / Mapped / Needs Review / Unmapped, and All Types / Multi-Product Offers / Single Offers. Search covers Item, Title, and Description.
Header actions: Import Mappings, Export, sync, and push. Unmapping asks "Unmap this offer?" first.
See Product mapping import and export.
Orders
Orders as VeraCore sees them, and whether SKU.io has linked each to a sales order.
| Column | Notes |
|---|---|
| ID | The SKU.io row id |
| Reference # | Your order reference at VeraCore |
| VeraCore ID | VeraCore's own order id |
| Status | VeraCore's order status |
| Customer | Ship-to name |
| Order Date | When the row was created |
| Ship Date | When it shipped |
| Tracking # | Carrier tracking, once known |
| Fulfillment | The linked SKU.io fulfillment, or blank |
Filters: the full thirteen-value status list (see Statuses reference), plus a link filter — All / Linked / Not Linked. Search covers Reference #, VeraCore ID, and Customer Email.
An unlinked VeraCore order is one the warehouse is working on that SKU.io cannot attribute to a sales order. See Sync and link orders.
Fulfillments
The fulfillment orders SKU.io sent to VeraCore — the outbound side of the same story the Orders tab tells inbound.
| Column | Notes |
|---|---|
| ID | The SKU.io row id |
| Fulfillment # | Opens the fulfillment in Orders |
| Sales Order | The order behind it — a link, or — if there is none |
| Status | The fulfillment's own status, not VeraCore's |
| Customer | Ship-to name |
| Tracking # | A working link once the shipping method is mapped; plain text until then |
| Shipping Method | What was requested on the order |
| Qty | Units fulfilled |
| Fulfilled / Created | Dates |
Filters: Status — All · Submitted · Acknowledged · Picked · Packed · Fulfilled · Awaiting Pickup · Canceled — and Shipping Method, listing every SKU.io method including archived ones. Search covers Fulfillment #, Tracking #, Sales Order, and Customer.
The Tracking # column only becomes a hyperlink when the fulfillment's shipping method is mapped, because the URL template comes from the mapped method. Plain-text tracking numbers here are the same defect your customers see in their shipping notification.
Expected Arrivals
Purchase orders announced to the warehouse as Advance Ship Notices.
| Column | Notes |
|---|---|
| Reference | The key VeraCore knows the arrival by |
| Purchase Order | The SKU.io PO it came from |
| Client PO | Your PO number as sent to VeraCore |
| Facility | Which VeraCore facility should receive it |
| Anticipated Arrival | The expected date |
| Lines | Number of lines |
| Units | Total quantity expected |
| Status | Pending / Sent / Received / Error / Cancelled |
| Last Error | Hidden by default. The reason a push or reconciliation failed |
| Last Synced | Hidden by default. When it was last reconciled |
Show the hidden columns with the column selector. Last Error is the one to turn on when an arrival is sitting in Error — it saves opening each row.
Filters: Status — All Statuses · Pending · Sent · Received · Error · Cancelled — and Receiving, which is the lock filter: All · Receiving started · Still editable. Search covers the reference, your PO, and the client PO.
Once the warehouse begins receiving against an arrival it can no longer be changed or cancelled from SKU.io. Filtering to Still editable shows only the arrivals you can actually do something about — see Track and cancel expected arrivals.
Cancelling asks "Cancel announcement?" first.
See Announce a purchase order to the warehouse and Track and cancel expected arrivals.
Report Tasks
The Dynamic Report jobs that carry tracking data back from VeraCore. Mostly a diagnostic surface — when tracking is missing, this is where you look.
| Column | Notes |
|---|---|
| ID | Task id |
| Report Name | The VeraCore report template requested |
| Status | Created / Polling / Done / Processed / Failed / Superseded |
| Date Range | The window the report covered |
| Rows Matched | How many rows produced a tracking update |
| Poll Attempts | How many times SKU.io asked whether it was ready |
| Created At | When the task started |
Status filter: All plus the six statuses. A failed task can be retried from its row.
See Set up tracking with Dynamic Reporting.
Shipping Methods
VeraCore carrier codes mapped onto SKU.io shipping methods.
| Column | Notes |
|---|---|
| Carrier | The carrier code VeraCore uses |
| Description | VeraCore's description of it |
| Orders | How many orders have used it — sort by this to prioritise |
| SKU Shipping Method | The SKU.io method it maps to, editable inline |
Filter: All / Mapped / Unmapped.
See Map shipping methods.
Source Codes
Sales channels tagged with the source code your 3PL expects on the order.
| Column |
|---|
| Sales Channel Instance · Sub Channel · Source Code · Actions |
See Map source codes.
Financial
A single setting, on its own tab: Fulfillment Cost Financial Line Type, which decides where VeraCore's freight charge lands in your books.
Changing it is not a forward-only setting — it rewrites financial lines on past fulfillments too, and the confirm dialog previews the impact before you commit. See Review fulfillment costs.
Activity Log
Every change made to the connection and its records — who changed what, when, and from what to what. Useful for answering "who unmapped this offer?" and "when did that setting change?".
| Column | Notes |
|---|---|
| ID | The log entry id |
| Date | When it happened |
| User | Who did it — System for anything automated |
| Event | Created · Updated · Deleted · Bulk Upsert |
| Source | What caused it — a manual edit, a sync, an import, a webhook |
| Subject | Which record was affected |
| Details | For an update, the actual before → after values |
Three behaviours are worth knowing:
- Settings changes are logged field by field, with the individual key and its old and new value — not an opaque blob.
- Bulk operations are grouped. A sync touching four hundred rows is one collapsible entry with a count, not four hundred entries. Expand it for the individual records.
- The Source filter separates automated from human. Filtering to Manual is the quickest way to answer "did somebody change this by hand?"
The Source filter has no VeraCore option — filter by Event or Subject to narrow to integration activity.
Settings
Six sub-tabs of configuration, each deep-linkable with ?tab=:
| Sub-tab | URL |
|---|---|
| General | ?tab=general |
| Sync | ?tab=sync |
| Authentication | ?tab=connection |
| Inventory Sync | ?tab=inventory |
| Fulfillment | ?tab=fulfillment |
| Tracking | ?tab=tracking |
Every field is documented in the Settings reference.