Dock Optimizer + SphereWMS — Pull WMS data into your dock schedule automatically.
Dock Optimizer polls SphereWMS's REST API v2 on a configurable interval — typically every 15 minutes — to bring inventory levels and order/receipt feeds into your dock appointments. Change-detection sync means only updated records are fetched each cycle.
How the sync works
Dock Optimizer is the polling client. SphereWMS is the system of record. Data flows one way: from SphereWMS into Dock Optimizer.
| Data type | Poll frequency | Use case |
|---|---|---|
| Inventory levels | Configurable poll (typical: 15 min) | Dock Optimizer surfaces live WMS inventory context on appointments — operators know what's available before the truck arrives. |
| Order / receipt feeds (POs, expected items) | Configurable poll (typical: 15 min) | PO numbers and item descriptions auto-populate the dock appointment record — no re-keying from the WMS print queue. |
| ASNs / expected shipments | Configurable poll (typical: 15 min) | Inbound appointments are auto-matched to SphereWMS receiving records so dock staff and warehouse staff see the same picture. |
Change-detection sync
Each poll cycle fetches only records that changed since the last run. Unchanged records are skipped — no unnecessary load on SphereWMS's API.
Conflict detection — external wins
When the same record is updated in both systems between poll cycles, SphereWMS wins by default. The external-wins policy keeps SphereWMS as your authoritative WMS source of record.
Multi-client 3PL scoping
Each SphereWMS client can be scoped to its own connector instance. Data from Client A never bleeds into Client B's appointment view — essential for 3PLs managing multiple customers on one WMS.
Setup in 5 steps
Typical setup time: under 2 hours. No SphereWMS professional services required.
Enable API access in SphereWMS
WMS adminYour WMS admin enables REST API v2 access in SphereWMS settings and generates an API key. No SphereWMS professional services engagement required.
Enter credentials in Dock Optimizer Integration Hub
Dock Optimizer adminPaste the API key and your SphereWMS tenant URL into the Integration Hub connector wizard. Dock Optimizer auto-discovers available endpoints — you select which feeds to enable.
Configure poll interval and 3PL client scoping
Dock Optimizer adminSet the poll interval (default: 15 minutes) and, for 3PLs, map each SphereWMS client ID to the correct Dock Optimizer tenant. Pre-built defaults work for most single-client configurations.
Test with a live record
BothCreate or update a record in SphereWMS and confirm it appears in Dock Optimizer within the next poll cycle. Review field mapping and adjust if needed.
Enable production sync
Dock Optimizer adminFlip the connector to production mode. The integration runs on the configured poll schedule. Health and last-sync timestamps are visible in the Integration Hub dashboard.
Built for reliability in production
Every integration failure mode is handled automatically. Transient network errors retry with exponential backoff. Permanent failures go to a dead-letter queue with a plain-English reason and a one-click requeue.
- Exponential backoff retry on transient failures (30s → 8 min)
- Dead-letter queue with plain-English failure reasons
- One-click message requeue from the Integration Hub dashboard
- Connector health monitoring with last-sync timestamp
- Cursor-based pagination for high-volume shipment queues
Authentication
API key with automatic rotation support. Credentials are encrypted at rest and never logged.
Typical setup time
Under 2 hours for a standard SphereWMS configuration. Complex field mapping or multi-client 3PL scoping may take longer.
Who needs to be involved
Your WMS admin (for API key generation) and your Dock Optimizer admin. IT may be needed for network allow-listing.