VeraCore settings reference
The Settings tab of a VeraCore connection is split into six sub-tabs. Each one saves independently — the Save Changes button at the bottom of a sub-tab only persists that sub-tab's fields, and Revert Changes discards them.
Every sub-tab is directly linkable with a ?tab= query parameter, so you can bookmark or share a specific screen:
| Sub-tab | Link |
|---|---|
| General | …/settings?tab=general |
| Sync | …/settings?tab=sync |
| Authentication | …/settings?tab=connection |
| Inventory Sync | …/settings?tab=inventory |
| Fulfillment | …/settings?tab=fulfillment |
| Tracking | …/settings?tab=tracking |
General
Identity and deletion. The header reads "Configure your VeraCore integration settings."
At the top, Linked 3PL Warehouse shows the SKU.io warehouse this connection is bound to, as a link to that warehouse's page. It is set when you connect and is not editable here.
Basic Information
| Field | Type | Default | Notes |
|---|---|---|---|
| Instance Name | Text | VeraCore | The display name used across the app and in the integration tile. Purely cosmetic. |
Danger Zone
Delete Integration — "Permanently delete this VeraCore integration and all associated orders, report tasks, and shipping method mappings. This cannot be undone."
The Delete button opens a confirmation dialog titled Delete VeraCore Instance?: "Are you sure? This will remove all VeraCore orders and report tasks associated with this instance."
Deleting removes the VeraCore-side records SKU.io has mirrored — orders, report tasks, and shipping-method mappings. If you only want to stop syncing, pause the schedule on the Sync tab instead.
The button is only shown to users with the integrations.delete permission.
Sync
Master switches for the whole connection. The description reads: "Pause the whole VeraCore sync schedule, or turn individual capabilities on and off — pushing orders to VeraCore and importing tracking back. Changes take effect on the next scheduled run."
Sync Schedule
A two-button toggle — Active or Paused — with a matching status chip in the card header.
| State | What happens |
|---|---|
| Active | "Automatic sync is running. Each capability below governs its own scheduled job." |
| Paused | "All automatic sync is suspended for this integration. Scheduled jobs won't run until you resume. Manual Sync Now still works." |
Switching to Paused asks for confirmation ("Pause all automatic sync?").
What syncs
Below the schedule, each capability has its own switch, grouped by direction. VeraCore supports five:
| Group | Capability | What it does |
|---|---|---|
| Import from VeraCore | Tracking | Pull tracking from VeraCore into SKU. |
| Import from VeraCore | Inventory | Pull inventory from VeraCore into SKU. |
| Import from VeraCore | Products | Pull products from VeraCore into SKU. |
| Send to VeraCore | Orders | Send orders from SKU to VeraCore. |
| Send to VeraCore | Products | Send products from SKU to VeraCore. |
Turning an outbound capability off asks for confirmation — for example "Stop sending orders?" / "SKU will stop sending orders to VeraCore. You can turn this back on at any time."
While the schedule is paused, an inline note reads: "Sync is paused — these settings define what will sync once you resume."
A capability switch decides whether a scheduled job does its work. It does not change when the job runs — that is fixed by the sync schedule.
Authentication
Connection Credentials
"Update your VeraCore API credentials if your connection details have changed."
| Field | Type | Notes |
|---|---|---|
| Server Name | Text | The VeraCore server subdomain — for example rhu126. |
| System ID | Text | The VeraCore System ID your 3PL issued. |
| Username | Text | The VeraCore API user. |
| Password | Password | "Leave blank to keep existing password." |
WMS Credentials (Optional)
"A VeraCore Web Service User is bound to a single system, so warehouse-level product details live behind a separate WMS login. Add one to let product matching fall back to UPC. Leave these blank and the UPC step is simply skipped — it is never an error."
| Field | Type | Notes |
|---|---|---|
| WMS System ID | Text | Placeholder: "Leave blank to skip UPC matching". |
| WMS Username | Text | — |
| WMS Password | Password | "Required alongside the WMS username." Once set, the hint becomes "Leave blank to keep existing WMS password." |
Test Connection (visible with the integrations.sync permission) validates the credentials against VeraCore without saving them.
Without them, the match ladder skips its UPC rung. Offers that would have matched on barcode fall through to name matching or stay unmapped — nothing errors, you just get fewer automatic matches.
Inventory
Inventory Mirror
"VeraCore is the system of record for stock it holds. SKU.io mirrors the Available quantity it reports — it never writes stock back to VeraCore."
| Field | Type | Default | Notes |
|---|---|---|---|
| Enable Inventory Sync | Switch | Off | "Pull VeraCore inventory once a day and record what changed since the previous snapshot." |
| Daily Sync Time | Select, 00:00–23:00 | 02:00 | Only shown when inventory sync is on. "Shown in your account timezone. Pick a quiet hour — the mirror walks every Offer in the system." |
Inventory Ledger
| Field | Type | Default | Notes |
|---|---|---|---|
| Change Retention (days) | Number, 1–3650 | 180 | "How long snapshot-to-snapshot changes are kept before they are pruned (1–3650). These are derived diffs, not inventory movements — pruning them never changes stock." Out-of-range input shows "Enter a whole number of days between 1 and 3650". |
Receiving
| Field | Type | Default | Notes |
|---|---|---|---|
| Auto-push Expected Arrivals | Switch | Off | "Announce a purchase order to VeraCore as an Expected Arrival as soon as it is approved. An Expected Arrival is an announcement — it books no stock until VeraCore receives it. You can also send any purchase order by hand from the order itself, whether or not this is on." |
The announcement fires when the purchase order is approved — that is the transition SKU.io raises an event for. Moving a PO to Ordered does not fire it. If your workflow skips approval, use the manual Send to VeraCore action on the purchase order instead; it stays available whether or not this switch is on. See Announce a purchase order to the warehouse.
Fulfillment
Fulfillment Settings
| Field | Type | Default | Notes |
|---|---|---|---|
| Gift Card Note mapping to Sales Order Custom Field | Select | None | Routes the VeraCore gift-card note into one of your sales-order custom fields. Disabled when the company has no sales-order custom fields — the tooltip reads "This tenant has no Sales Order custom fields yet — create one under Settings → Custom Fields to map the gift card note." |
| Only submit orders with deliver by date | Switch | Off | "When enabled, orders submitted to VeraCore must include a deliver-by date." |
| Enable Fulfillment | Switch | Off | "SKU.io can automatically submit fulfillment requests to VeraCore if their default warehouse has enough stock to fulfill the order." |
Third Party Shipping
| Field | Type | Default | Notes |
|---|---|---|---|
| Shipping methods that allow third party billing | Multi-select (chips) | Empty | Pick the shipping methods that may bill a third-party carrier account. Disabled when no shipping methods exist — the tooltip reads "No shipping methods are configured yet — add them under Settings → Shipping Methods before choosing which allow third party billing." Remove a method by clicking the × on its chip. |
Until Enable Fulfillment is on, SKU.io never submits an order to VeraCore automatically. Turn it on only after your warehouse, product, and shipping-method mappings are in place — otherwise orders arrive at the warehouse with items or carriers it cannot resolve.
Tracking
Tracking & Sync Settings
| Field | Type | Default | Notes |
|---|---|---|---|
| Sync Days Back | Number, 1–90 | 7 | "How many days of historical orders to fetch when syncing (1–90)." |
| Dynamic Report Tracking | Switch | Off | "Use VeraCore dynamic reports to automatically fetch tracking data every 3 hours." |
| Report Name | Text | Empty | Only shown when Dynamic Report Tracking is on. "The name of the dynamic report template configured in VeraCore." Placeholder: e.g. SKU_Tracking_Report. |
Report Name points at a Dynamic Report template your 3PL has configured on their side. SKU.io requests it by name — it cannot create one. If the name does not match exactly, the report task fails. See Set up tracking with Dynamic Reporting.
The switch label says "every 3 hours" — the schedule was raised to hourly so a single missed cron run can no longer strand a day's shipments. See Scheduled syncs and commands.
The Financial tab is separate
Freight cost routing is not on the Settings tab — it has its own Financial tab. See Review fulfillment costs for the Fulfillment Cost Financial Line Type setting and the backfill it triggers.