Sync and link orders
Once SKU.io is sending fulfillments to your 3PL, the Orders tab is the return path: VeraCore's own view of those orders, pulled back so you can see what the warehouse did with them.
The direction matters. SKU.io sends a fulfillment out; VeraCore turns it into an order, picks it, packs it, ships it, and this tab reports back on that. Nothing you do here changes anything at the warehouse.
Pull orders in
Click Refresh From VeraCore. You get Sync started — track progress in the job tray, and the job runs under Sync VeraCore Orders:. The table reloads itself when it finishes.
Refresh re-reads what SKU.io already holds without calling VeraCore — useful after you have changed a filter and just want the page current.
Reading the table
| Column | Notes |
|---|---|
| ID | SKU.io's row id |
| Reference # | The order reference. Opens the order |
| VeraCore ID | VeraCore's own identifier. Also opens the order |
| Status | VeraCore's status, as a chip |
| Customer | Name, with the email beneath |
| Order Date / Ship Date | When VeraCore recorded each |
| Tracking # | One line per parcel — see below |
| Fulfillment | The SKU.io fulfillment this order belongs to, or a None chip |
Search covers Reference #, VeraCore ID, and Customer Email. Sorting defaults to newest first, and the advanced filters cover date ranges on when the order was created and last updated.
The status filter has fourteen values
VeraCore tracks an order through more stages than most systems: Unapproved, Unprocessed, Accepted, Hold, Denied Credit, Pending, Processed, Picked, Backordered, Partially Shipped, Shipped, Complete, and Canceled.
Most of the time you only care about a few of them:
- Hold and Denied Credit — the warehouse is not going to ship this until something is resolved. These are worth checking regularly; an order sitting on hold is silently not happening.
- Backordered — VeraCore does not have the stock. Compare against the inventory tab, because a backorder your 3PL knows about and SKU.io does not is a discrepancy waiting to be found the hard way.
- Partially Shipped — some parcels went, some did not. Expect more than one tracking number, and expect the fulfillment link to only cover part of it.
- Canceled — the warehouse will not ship it. SKU.io's own order is untouched.
Multi-parcel tracking
A VeraCore order can ship in several parcels, and the Tracking column shows one line per parcel.
This is more careful than it looks. Tracking numbers are read from the structured parcel data VeraCore returns rather than by splitting a joined string, because some carriers issue tracking numbers that legitimately contain a comma — splitting on commas would quietly mangle them into two invalid numbers.
Only one parcel per order gets a clickable carrier link: the one matching the tracking number on the linked SKU.io fulfillment. That is deliberate. The carrier URL lives on the fulfillment, which carries exactly one tracking number, so linking every parcel to it would point most of them at the wrong package.
The column is narrow, so long lists are truncated — hover to see every number.
The Fulfillment column
This is the join between the two systems. When SKU.io created the fulfillment that became this order, the column shows #{reference} as a link straight to it, with a tooltip naming the exact record type and id behind the link.
When it shows a None chip, the order exists in VeraCore with nothing in SKU.io pointing at it. The Fulfillment quick filter — Linked / Not Linked — narrows to exactly that case, and it is the most useful filter on the page.
An unlinked order is usually one of:
- An order created directly in VeraCore, not through SKU.io.
- An order whose fulfillment was created before the connection existed.
- A matching failure, where the reference SKU.io sent is not the one VeraCore recorded.
The first two are expected. The third is worth investigating, because it means SKU.io cannot report on an order it originated.
The empty state tells you which problem you have
An empty table means one of two different things, and the page distinguishes them:
- Filtered: No orders match your filters / Adjust the search or filters to see the rest of the orders., with a Clear Filters button.
- Unfiltered: No orders yet / Run "Refresh From VeraCore" to pull orders for this integration.
Telling someone to run a sync when the orders are merely filtered out would send them chasing a problem that does not exist.
The order page
Clicking a reference opens the order, headed by its reference (or Order #{veracore id} if there is none), its status chip, and the VeraCore id, order date, and customer beneath.
Four cards summarise it: Status, Items, Carrier, and Fulfillment (Linked / Not Linked). Below them, expandable panels — Customer & Addresses, Line Items, and Shipping open by default.
| Panel | Contains |
|---|---|
| SKU Fulfillment | Only when linked. See below |
| Customer & Addresses | Name and email, plus the full shipping address as VeraCore holds it |
| Line Items | SKU, description, quantity, unit price, with totals when there is more than one line |
| Shipping | Carrier, service, requested shipping method, every parcel's tracking number, and the ship date |
| Raw VeraCore Data | Loaded on demand — see below |
Sync Details re-fetches this one order from VeraCore. Use it when a status looks stale and you do not want to run a full sync for a single order; the confirmation is Order details refreshed.
The SKU Fulfillment panel
When the order is linked, this panel is the whole picture of the SKU.io side: the fulfillment itself (linked, with the same type-and-id tooltip), the sales order behind it, the fulfillment's own status, the warehouse, the tracking number with its carrier link, and the fulfilled and created timestamps.
View Fulfillment opens it. Unlink breaks the connection.
Unlinking tells SKU.io this VeraCore order does not belong to that fulfillment. It does not cancel anything, at either end — both records survive, they simply stop referring to each other.
Use it when the link is genuinely wrong. Do not use it to "reset" an order: an unlinked order is one SKU.io can no longer report against, and nothing re-links it automatically.
Raw VeraCore Data
The last panel loads nothing until you ask. Click Load Raw Data from VeraCore and it shows exactly what VeraCore sent the last time SKU.io read this order — whether from a detail lookup or a list sync — formatted, with Copy JSON.
It is deliberately opt-in because it is rarely what you want. When it is what you want — a field on the order looks wrong and you need to know whether SKU.io mis-read it or VeraCore sent it that way — it settles the question outright.
If nothing has been stored yet: No raw VeraCore data available. Click "Sync Details" to fetch from VeraCore.
The Fulfillments tab
The Fulfillments tab is the other side of the same relationship: SKU.io fulfillments routed through this VeraCore connection, listed from SKU.io's point of view rather than VeraCore's.
Each row gives the fulfillment number (linked to the fulfillment), its sales order, status, customer, tracking number with carrier link, shipping method, quantity fulfilled, and the fulfilled and created dates. Search covers fulfillment number, tracking number, sales order number, and customer name.
The Status filter here uses SKU.io's fulfillment lifecycle, not VeraCore's: Submitted, Acknowledged, Picked, Packed, Fulfilled, Awaiting Pickup, Canceled. A second filter narrows by Shipping Method.
Use this tab when the question starts on the SKU.io side — did this sales order's fulfillment ever reach the warehouse? — and the Orders tab when it starts on the VeraCore side.
The same shipment appears in both tabs under different status words. A fulfillment that is Submitted in SKU.io may still be Unprocessed in VeraCore; Fulfilled on one side lines up with Shipped or Complete on the other. Neither list is wrong — they are each reporting their own system's state, and a mismatch usually just means a sync has not caught up.
Next steps
- Set up tracking with Dynamic Reporting — where the tracking numbers on these orders come from.
- Map shipping methods — how a SKU.io shipping method becomes the carrier and service on a VeraCore order.
- Troubleshooting — orders that never arrive, and fulfillments that never link.