Map shipping methods
When VeraCore ships an order it tells SKU.io which carrier and service it used — as VeraCore's own strings, which mean nothing to SKU.io until you say what they correspond to.
The Shipping Methods tab is where you say it. Each VeraCore carrier/service pair gets matched to a SKU.io shipping method, and that mapping is stamped onto the fulfillment when tracking comes back.
This mapping is inbound only
That distinction is the single most important thing on this page, and the page leads with it:
Inbound only: when tracking comes back from VeraCore, the mapped SKU shipping method is stamped on the fulfillment — which is what determines the tracking company and tracking URL reported to your sales channels. It does not change the shipping method sent out to VeraCore when an order is submitted; that always comes from the sales order's own requested shipping method.
So:
| Direction | Determined by |
|---|---|
| Out — what SKU.io asks VeraCore to ship by | The sales order's own requested shipping method |
| In — what SKU.io records that VeraCore actually shipped by | This mapping |
Mapping a VeraCore service to a different SKU.io method will not make VeraCore ship differently. If orders are going out on the wrong service, the fix is in the sales order or the shipping-method setup, not here.
Why it matters anyway
The mapped method is what your sales channels see. It carries the tracking company and the tracking URL template, so an unmapped or wrongly mapped service means the customer gets a tracking number with no working link — or a link to the wrong carrier's website.
That is a customer-facing defect that never shows up in SKU.io. It is worth keeping this page tidy.
The list builds itself
There is nothing to import and no list to request from VeraCore. The page shows the carrier/service pairs observed on orders SKU.io has already synced.
That means a brand-new connection has an empty page:
No carrier/service pairs observed yet. Sync orders first to populate this list.
Run a sync on the Orders tab and come back. New pairs appear here as they turn up, so a 3PL that adds a service next month gives you a new unmapped row rather than a silent failure.
Map one
| Column | Notes |
|---|---|
| Carrier | VeraCore's carrier value |
| Description | VeraCore's service description, shown as code |
| Orders | How many synced orders used this pair |
| SKU Shipping Method | The dropdown. Reads Not mapped until you pick one |
Pick a SKU.io method from the dropdown and it saves immediately — Mapping saved. There is no Save button and no form to submit.
To remove a mapping, clear the dropdown. That is Mapping removed, and the row goes back to Not mapped.
The Mapped filter — All / Mapped / Unmapped — is how you work through the list. Switch to Unmapped and the page becomes a to-do list. Search covers carrier and description.
The Orders column is a sorted priority list in disguise. A pair with four hundred orders behind it is worth mapping before one with two. Sort on it, then work down.
Choosing the right method
Match the carrier and service, not just the carrier. VeraCore reporting "UPS" with a Ground description should map to your UPS Ground method, not to a generic UPS entry — the tracking URL is usually the same, but the shipping method also feeds reporting and cost analysis where the service matters.
Two situations that need a decision:
VeraCore has a service you do not. Create the SKU.io shipping method first, then come back and map to it. Mapping to a near-enough method makes every report about that service wrong.
Two VeraCore pairs mean the same thing. Perfectly fine — map both to the same SKU.io method. The mapping is many-to-one by design.
When something is unmapped
An unmapped pair is not an error and nothing breaks. The fulfillment simply carries no shipping method from VeraCore, which means:
- No carrier is attributed to it in SKU.io.
- The tracking number has no tracking URL, so links do not resolve.
- Shipping-cost reporting by method excludes it.
You will usually notice it as "the tracking link does not work" rather than as anything on this page. That is why the Unmapped filter is worth checking after any period of new services appearing.
Next steps
- Sync and link orders — where the carrier/service pairs come from.
- Set up tracking with Dynamic Reporting — the pipeline that delivers them.
- Map source codes — the outbound equivalent, telling VeraCore where an order came from.