Inventory Integration Setup

Use this guide when an ERP or warehouse system owns inventory quantities and must keep Velosity current. Velosity uses the resulting inventory data for planning and availability; the source system remains responsible for its inventory and purchasing transactions.

1. Enable the module and assign ownership

Ask Velosity to enable Inventory for the tenant. Decide which system owns item data, locations, stock movements, reservations, purchasing, receiving, and adjustments. Document that ownership before enabling synchronization.

An integration should be the only automated writer of inventory balances. Avoid combining an ERP feed with unrelated manual changes to the same records unless the reconciliation process accounts for them.

2. Create the integration identity

Create a dedicated API key from the Velosity user profile and store it in your integration's server-side secret store. Send it in the X-APIKEY request header. Do not put the key in browser code, URLs, source control, or shared spreadsheets.

Start against a sandbox or demo tenant. Use the API reference to confirm the current request and response schemas before implementation.

3. Map master data

Map every ERP item identifier to its Velosity item ID and item number. Create or synchronize the required items before any inventory records are written. Map each ERP warehouse, bin, or stocking area to a Velosity inventory location, and retain both IDs in the integration's mapping store.

Use stable source identifiers. Do not derive a mapping solely from a display description, because descriptions can change.

4. Establish locations and opening balances

Create the inventory locations first. Next, load a controlled opening balance from a known ERP snapshot. Reconcile the item count, location count, and total quantity before enabling incremental updates.

The Inventory API supports reading inventory status and item inventory, and creating inventory entries or transaction types such as receiving, moving, and shipping. Location endpoints support listing, reading, creating, updating, and deleting locations. Refer to the API reference for the exact endpoint contracts and required fields.

5. Synchronize transactions safely

Process source transactions in a repeatable order and retain the source transaction ID, Velosity result, and processing time. Make retries safe: a network failure must not result in duplicate inventory movement. Log failures with enough source context to repair the mapping or data and replay only the affected work.

If the source system publishes periodic balance snapshots as well as transactions, define how the snapshot corrects missed or late transactions. Do not assume that an on-hand balance represents available-to-promise quantity without applying the source system's allocation and reservation rules.

6. Verify and operate

After the opening load, compare representative items at every location against the source system. Test a receive, move, and ship workflow in the non-production tenant, then verify the resulting inventory status and audit trail.

Monitor failed writes, unmapped items or locations, quantity variances, and synchronization lag. Reconcile totals on a schedule and investigate discrepancies before they affect planning or customer commitments.

For the operational checklist used by warehouse and implementation teams, see Get Inventory Up and Running.