Track and cancel expected arrivals
Once a purchase order has been announced, the Expected Arrivals tab is where you watch what happens to it.
There is one rule that governs everything on this page: once the warehouse starts receiving, the announcement belongs to VeraCore. You cannot edit it, you cannot cancel it, and SKU.io will not pretend otherwise.
The status cards
Six cards sit above the table. Each one is clickable and filters the table to that status; click it again to clear.
| Card | Meaning |
|---|---|
| Total | Every arrival on this connection |
| Pending | Built in SKU.io but not yet accepted by VeraCore |
| Sent | VeraCore has the announcement and is waiting for the stock to arrive |
| Received | The warehouse has started receiving against this arrival |
| Errors | VeraCore rejected the announcement — see the error for what to fix. Turns red above zero |
| Cancelled | The announcement was withdrawn before receiving started |
Those descriptions are not paraphrases — they are the tooltips on the status chips themselves, so the same words follow you into the table.
The normal life of an arrival is Pending → Sent → Received. Two of the six are exceptions rather than stages: Error means it never got in, and Cancelled means you took it back out.
Errors is the card to look at first. An announcement sitting in error is one the warehouse does not know about, which means the delivery will arrive unannounced.
The receiving lock
When VeraCore begins receiving against an arrival, it locks it. SKU.io shows this as a padlock beside the status, with the reason spelled out:
VeraCore has started receiving this arrival, so it can no longer be edited or cancelled.
On the arrival's own page it is louder — a Receiving Started chip next to the status.
This is not a SKU.io restriction being cautious. VeraCore itself will refuse the change, because warehouse staff are already counting stock against that document. Withdrawing it mid-receipt would leave the receiving team holding pallets against a document that no longer exists.
If something is wrong with a locked arrival, the fix is a conversation with your 3PL, not a button in SKU.io.
Pulling in arrivals from VeraCore
Sync From VeraCore pulls the current state of every arrival back from your 3PL. Use it to:
- Pick up status changes — an arrival that VeraCore has started receiving.
- Discover arrivals created directly in VeraCore, without going through SKU.io at all.
The job runs under Sync VeraCore Expected Arrivals: and the page refreshes when it completes. While one is running the button is disabled: An expected-arrival sync is already running — track its progress in the job tray.
Arrivals that came from VeraCore rather than SKU.io are easy to spot — they have no purchase order. Their detail page says so:
This arrival came back from VeraCore without a matching SKU.io purchase order — it was most likely created directly in VeraCore.
That is worth noticing rather than ignoring. Stock is inbound to your warehouse with no purchase order behind it in SKU.io, which means it will not reconcile against anything when it lands.
Reading the table
| Column | Notes |
|---|---|
| Reference | VeraCore's key for the announcement. Opens the arrival |
| Purchase Order | Links to the SKU.io purchase order, or — if there is none |
| Client PO | The customer-side reference, when one was supplied |
| Facility | The VeraCore facility the stock is going to |
| Anticipated Arrival | The expected date. A date only — no time, no timezone conversion |
| Lines / Units | The size of the announcement |
| Status | The chip, with its tooltip, plus a padlock when locked |
| Last Error | VeraCore's rejection reason. Hidden by default; truncated with the full text on hover |
| Last Synced | Hidden by default |
Sorting defaults to anticipated arrival, newest first — the next delivery at the top.
Alongside search, two quick filters do most of the work: Status and Receiving, the latter splitting the list into Receiving started and Still editable. The second is the practical question when you are looking for something you can still change.
The advanced filters go further — reference, our PO, client PO, facility, owner, trading partner, status, shipping method, load type, the lock flag, and date ranges on anticipated arrival, last sync, creation, and update.
It is hidden by default because it is empty most of the time. When you are working through the Errors card, switch it on — it saves opening every row to find out what VeraCore objected to.
The arrival page
Clicking a reference opens the announcement in full, with the same framing at the top: An announcement that stock is inbound — never a record of stock received.
Arrival Details lists the reference, facility, owner, trading partner, our PO and client PO, anticipated arrival, shipping method, load type, and the sync and creation timestamps.
Announced Lines is the substance: one row per item, with the VeraCore item code (linked to that offer), any size/colour/version variant, the line key, the purchase order line it came from, and the quantity expected. The header totals lines and units.
An announcement with no lines gets a blunt message rather than an empty table: This announcement has no lines — VeraCore was told nothing is inbound. That is a real failure mode worth catching — the announcement exists, but tells the warehouse to expect nothing.
If VeraCore rejected the announcement, a red banner headed VeraCore rejected this announcement carries the reason.
Raw VeraCore Payload shows exactly what was sent or received. Most of the time you will not need it, but when VeraCore rejects something for a reason the interface does not surface, the answer is in there. The card says as much: useful when VeraCore rejects an announcement and the reason is in a field the UI does not surface.
Cancelling an announcement
Cancelling withdraws the announcement from VeraCore. Your purchase order is untouched — the order still exists, still has its lines, and can be announced again later.
From the table, use the row's cancel action. From the arrival page, use Cancel Announcement. Either way you get a confirmation naming the arrival and stating plainly that the purchase order itself is unaffected, with a red Cancel Arrival button.
The button explains itself when it is unavailable:
- VeraCore has started receiving this arrival, so it can no longer be cancelled.
- This announcement is already cancelled.
If the cancel fails
You can lose the race. The page might have loaded while the arrival was still editable, and the warehouse might have started receiving in the seconds before you clicked.
When that happens SKU.io shows VeraCore's own wording rather than a generic failure, and reloads the arrival so you can see its new state. The answer is not to retry — the arrival is locked now. It is to talk to your 3PL.
What cancelling does not do
| It does not | Because |
|---|---|
| Cancel the purchase order | The two are separate. The order is still live with your supplier |
| Stop the delivery | The truck is still coming. You have only withdrawn the paperwork |
| Remove received stock | Cancelling is impossible once receiving starts, so there is never received stock to remove |
If the delivery genuinely is not happening, cancel the purchase order too — otherwise you have a live order that nothing will ever receive.
Next steps
- Announce a purchase order to the warehouse — creating the announcement, and what to do when VeraCore refuses it.
- Review inventory and discrepancies — where the stock shows up once the warehouse has actually received it.
- Troubleshooting — when arrivals sit in error and the reason is not obvious.