VeraCore integration overview

VeraCore is a third-party logistics (3PL) platform: your warehouse partner runs it, holds your stock, and ships your orders. The SKU.io integration makes that warehouse a first-class part of your operation — orders and receiving announcements flow out to VeraCore, and inventory balances, the offer catalogue, order status, and tracking numbers flow back in.

What the integration does

SKU.io talks to VeraCore's Public API as a normal API user — the same credentials your 3PL issues for any integration. There is no middleware, no file drop, and no webhook: VeraCore does not push events, so everything inbound is polled on a schedule (see the Scheduled syncs and commands reference).

Five things move across the connection:

Direction	What moves	Driven by
Out to VeraCore	Sales orders, as fulfillment requests	The fulfillment dispatch, when Enable Fulfillment is on
Out to VeraCore	Purchase orders, as Expected Arrivals (ASNs)	Manual push, or Auto-push Expected Arrivals
Out to VeraCore	Products, created or updated as VeraCore items	The manual Push to VeraCore action
In from VeraCore	The Offer catalogue, matched to your SKUs	Hourly product sync
In from VeraCore	Inventory balances per facility	Daily inventory mirror
In from VeraCore	Order status, shipments, tracking, freight cost	Hourly order detail + Dynamic Report tracking

VeraCore is the system of record for the stock it holds. SKU.io mirrors the quantities VeraCore reports and never writes stock levels back.

Where to find it

VeraCore is not in the top-level navigation. Go to Apps & Integrations, then open the VeraCore tile in the Shipping & Fulfillment category (the navy VC logo). Its catalog description reads "Automate order fulfillment with VeraCore."

You can only connect one VeraCore account per company. Once connected, the tile deep-links straight into that connection's Dashboard.

One connection, one 3PL warehouse

Connecting VeraCore links it to exactly one SKU.io warehouse, chosen during setup. If you pick a direct warehouse it is converted to a 3PL warehouse — the setup screen warns you before you save. See Connect VeraCore.

The fourteen tabs

Unlike some 3PL integrations, VeraCore exposes the same surface to every account — there is no per-account capability list, so every tab is always visible.

Tab	What it is for
Dashboard	KPI roll-up and the "last synced" clock for every sync
Warehouse Mappings	Which VeraCore facility maps to which SKU.io warehouse
Inventory	Balances, discrepancies, and the two "only in one system" gap lists
Inventory Ledger	What changed between inventory snapshots
Products	The VeraCore Offer catalogue and its mapping to your products
Orders	Orders as VeraCore sees them, linked to your sales orders
Fulfillments	Fulfillment orders SKU.io sent, with status and tracking
Expected Arrivals	Purchase orders announced to the warehouse
Report Tasks	The Dynamic Report jobs that carry tracking data back
Shipping Methods	VeraCore carrier codes mapped to SKU.io shipping methods
Source Codes	Sales channels mapped to VeraCore source codes
Financial	Which financial line type receives the freight cost
Activity Log	Every change made to the integration and its records
Settings	Credentials, sync controls, and all behaviour toggles

Column-by-column detail for each of these is in the Tabs and columns reference.

What you need before you start

• VeraCore API credentials — a username, password, System ID, and your server name (the VeraCore subdomain, for example rhu126). Your 3PL issues these.
• A warehouse in SKU.io to represent the 3PL location. It becomes a 3PL warehouse when you connect.
• (Optional) WMS credentials — a second VeraCore login for the warehouse system. These are only used to enrich product matching with UPCs. Leave them blank and the UPC matching step is simply skipped; it is never an error.

Where to go next

Start here — the fast path

Four steps get you from nothing to a working two-way connection: Connect VeraCore → Map VeraCore facilities to warehouses → Sync the offer catalogue → Map an offer to a product. Everything else builds on those mappings.

Start here

• Connect VeraCore — enter your credentials, test the connection, and pick the 3PL warehouse.
• Map VeraCore facilities to warehouses — tell SKU.io which of your warehouses each VeraCore facility is.
• Sync the offer catalogue — pull every VeraCore Offer and let the matcher pair them with your products.
• Map an offer to a product — confirm suggestions and fix the ones the matcher could not place.

How-to guides

• Push products to VeraCore — create or update items in VeraCore from SKU.io.
• Review inventory and discrepancies — compare what VeraCore holds against what SKU.io thinks.
• Create a stock take from discrepancies — turn a variance list into a counted correction.
• Read the inventory ledger — see what changed between two inventory snapshots.
• Announce a purchase order to the warehouse — send an Expected Arrival so receiving is ready.
• Track and cancel expected arrivals — follow an announcement to received, or pull it back.
• Sync and link orders — pull VeraCore orders and match them to your sales orders.
• Set up tracking with Dynamic Reporting — the report-based pipeline that returns tracking numbers.
• Map shipping methods — turn VeraCore carrier codes into SKU.io shipping methods.
• Map source codes — tag orders by sales channel for your 3PL.
• Review fulfillment costs — route VeraCore freight onto a financial line type.
• Troubleshoot the VeraCore integration — match a symptom to its cause and fix.

Concepts

• How the VeraCore sync works — polling, schedules, and what runs when.
• The inventory model — on hand, available, committed, and why they differ.
• How offers are matched to products — the four-rung match ladder and what needs review.
• Receiving and expected arrivals — what an announcement is, and what it is not.
• Creating vs updating products at VeraCore — why the two operations behave differently.

Reference

• Product mapping import and export — the file format, the match key, and every validation message.
• Settings reference — every field on all six settings tabs.
• Statuses reference — every status value the integration can show.
• Tabs and columns reference — every tab, column, and filter.
• Scheduled syncs and commands — what runs automatically, and when.