Veracore

📄️Create Integration Instance

Create a new Veracore integration instance.

📄️Show Integration Instance

Retrieve a Veracore integration instance by ID.

📄️Test Connection with Credentials

Test a set of Veracore credentials before saving an integration instance. The endpoint attempts to request an access token from the Veracore API using the supplied credentials and reports whether authentication succeeded.

📄️Test Connection for Instance

Test the Veracore connection for an existing integration instance using its saved credentials. The endpoint attempts to request an access token from the Veracore API and reports whether authentication succeeded.

📄️Preview Financial Line Type Impact

Preview how many financial lines and sales orders would be affected if the fulfillment-cost financial line type configured on this Veracore integration instance were changed to `new_type_id`. This is a read-only computation — no data is modified.

📄️Update Order From Fulfillment (Power User)

Re-dispatch a sales order fulfillment to Veracore. Requires Power User role.

📄️List Orders

List locally cached Veracore orders for an integration instance (paginated), serialized via Veracore order object. Each order exposes the SKU.io fulfillment link fields: `sku_fulfillment_id` (legacy order→SalesOrderFulfillment id, kept as a fallback), `sku_fulfillment_order_id` (order→FulfillmentOrder id), and `sku_fulfillment` (a resolved link object, or null when the order is not yet linked). Supply `include_json=1` to include the raw Veracore `json_data` payload.

📄️Show Order

Show a single locally cached Veracore order by its database id, serialized via Veracore order object. Exposes the SKU.io fulfillment link fields `sku_fulfillment_id`, `sku_fulfillment_order_id`, and the resolved `sku_fulfillment` link object (null when not linked). Supply `include_json=1` to include the raw Veracore `json_data` payload. Returns 404 when the order does not belong to the given integration instance.

📄️Sync Orders

Queue a background job that syncs orders from Veracore for this integration instance.

📄️Get Order Sync Progress

Get the progress of a queued Veracore order sync. Pass the `tracked_job_log_id` returned by the sync endpoint.

📄️Sync Order Detail

Refresh a single Veracore order's stored data by fetching full order detail from the Veracore API. The fetched detail (status flags, shipping, line items, addresses) is merged into the locally stored order and the detail-refresh timestamp is updated.

📄️Get Dashboard Metrics

Get aggregate metrics for a Veracore integration instance.

📄️List Activity Log Entries

List activity log entries recorded against a Veracore integration instance, including changes to the instance itself and to its Veracore orders. Entries are returned newest first.

📄️List Fulfillments

List SKU.io sales order fulfillments dispatched to this Veracore integration instance. Only fulfillments of the Veracore fulfillment type are returned, scoped to the warehouse linked to the instance when one is configured.

📄️Link Order to Fulfillment

Link a Veracore order to a SKU.io sales order fulfillment. Pass the fulfillment id as `sku_fulfillment_id` in the body — use the fulfillments list endpoint to find candidates.

📄️Unlink Order from Fulfillment

Remove the link between a Veracore order and its SKU.io sales order fulfillment. No request body is required.

📄️List Report Tasks

List Veracore report tasks for an integration instance. A report task represents one Veracore report run used to import shipment and tracking data for a date range. Tasks are returned newest first.

📄️Get Report Task

Retrieve one Veracore report task together with a row-by-row reconciliation of the report payload it brought back.

📄️Get Report Task Raw Payload

The report payload exactly as Veracore returned it, plus when the task was processed.

📄️Retry Report Task

Retry a Veracore report task. The original task is marked `superseded` (so it stops being polled) and a fresh task is created with the same report name and date range in `created` status. A background job is queued to submit and poll the new run against the Veracore API.

📄️List Shipping Method Mappings

Every carrier + service combination observed on this instance's Veracore orders, joined with its mapping to a SKU.io shipping method.

📄️Map Shipping Method

Create or update the mapping from a Veracore carrier + service combination to a SKU.io shipping method.

📄️Delete Shipping Method Mapping

Remove the mapping for a Veracore carrier + service combination so it is no longer translated to a SKU.io shipping method.

📄️List Source Code Mappings

All source code mappings for a Veracore integration instance.

📄️Create Source Code Mapping

Create a source code mapping for a Veracore integration instance.

📄️Preview Source Code for Sales Order

Preview which Veracore source code would be applied to a given sales order under the current mappings. This is a read-only computation — nothing is stored and no call is made to the Veracore API.

📄️Update Source Code Mapping

Update a source code mapping. Only the fields provided are changed; `null` values are ignored.

📄️Delete Source Code Mapping

Delete a source code mapping. Orders from the affected sales channel fall back to the channel's catch-all mapping (if one exists) or to no source code.

📄️Get Warehouse Mappings

Every Veracore facility discovered for this integration instance alongside its SKU.io warehouse mapping.

📄️Sync Warehouse Mappings

Queue discovery of the Veracore facilities for this instance. Veracore exposes no warehouse directory, so facilities are harvested from the warehouse balances on the inventory feed: every facility that reports a balance is recorded, and facilities already known keep their existing mapping.

📄️Update Warehouse Mapping

Point a discovered Veracore facility at a SKU.io warehouse, or clear the mapping by sending `warehouse_id: null`.

📄️Delete Warehouse Mapping

Remove a discovered facility and its mapping. Mirrored inventory behind the facility is re-pointed straight away, so rows that lose their SKU.io warehouse drop out of the reconciliation report rather than reconciling against a warehouse that no longer applies.

📄️Get Inventory

Paginated Veracore inventory for an integration instance, one row per offer per facility.

📄️Refresh Inventory

Queue a full inventory pull for this instance. The pull replaces the mirrored balances and records the difference against the previous snapshot into the inventory ledger.

📄️Get Inventory Summary

Totals behind the inventory headline figures and the four reconciliation counts.

📄️Get Inventory Discrepancies

Mapped products whose SKU.io quantity disagrees with the Veracore balance for the same warehouse.

📄️Get Inventory Discrepancy Stats

Totals over the same filtered discrepancy set the discrepancies endpoint pages through.

📄️Get Products Without Veracore Inventory

Stocked SKU.io products that Veracore has never reported a balance for. These are usually products the 3PL has not been told about yet, or products fulfilled from elsewhere.

📄️Get Inventory Without SKU.io Products

Veracore inventory rows with no SKU.io product behind them — items the warehouse holds that this account has never mapped. `needs_review` marks rows where an automatic match was attempted and rejected, which is the shortlist worth mapping by hand first.

📄️Create Stock Take From Discrepancies

Turn the discrepancy report into a stock take that brings SKU.io in line with what the warehouse actually holds.

📄️Get Inventory Changes

Paginated ledger of observed inventory changes for an integration instance, newest first.

📄️Get Inventory Change Summary

Aggregate the ledger over exactly the rows the list endpoint would return: how many changes were observed, how many went each way, and the net and gross unit swing.

📄️Get Inventory Change

A single observed inventory change with its warehouse and the mirrored inventory row behind it.

📄️Get Products

Paginated Veracore offer catalogue for an integration instance, with the SKU.io product each offer maps to.

📄️Get Product Summary

Mapping counts for the whole Veracore offer catalogue on an integration instance, returned as a single aggregate rather than paging the catalogue.

📄️Export Products

Download the mirrored Veracore offer catalogue as a spreadsheet.

📄️Sync Products

Queue a pull of the Veracore offer catalogue for this instance. The pull refreshes mirrored offers and re-runs automatic matching against SKU.io products; manual mappings are never overwritten.

📄️Push Products To Veracore

Publish SKU.io products into the Veracore catalogue.

📄️Get Product

A single mirrored Veracore offer with its SKU.io mapping and, when the offer is unmapped, the ranked match candidates behind the review state.

📄️Get Product Raw Payload

The unmodified Veracore payload last stored for this offer, plus when it was captured. Use it to confirm what the warehouse actually returned when a mirrored field looks wrong.

📄️Update Product Mapping

Link a Veracore offer to a SKU.io product by hand. The mapping is marked as manual so later catalogue syncs leave it alone, and the review flag is cleared.

📄️Delete Product Mapping

Unlink a Veracore offer from its SKU.io product. The offer stays mirrored but drops out of the reconciliation report, because an unmapped item has no SKU.io quantity to compare against. Automatic matching may propose it again on the next catalogue sync.