Question 1

Does the SphereWMS integration require vendor support from SphereWMS?

Accepted Answer

No. The integration uses SphereWMS's standard API and does not require a support ticket or professional services engagement with SphereWMS. Your WMS admin and the Dock Optimizer team can complete setup without SphereWMS involvement.

Question 2

What version of SphereWMS do we need?

Accepted Answer

The integration requires SphereWMS with API access enabled. Contact us with your SphereWMS version and we will confirm compatibility before you begin setup.

Question 3

Is the SphereWMS integration bidirectional?

Accepted Answer

Yes. Dock Optimizer reads expected shipments and ASNs from SphereWMS to auto-create appointments, and writes check-in events and BOL data back to SphereWMS as freight is received.

Question 4

What happens if the integration connection drops?

Accepted Answer

Transient failures retry automatically with exponential backoff. If the connection is down for an extended period, missed events are queued and replayed when the connection restores. No data is lost.

Question 5

How is data conflict resolved if the same record is updated in both systems?

Accepted Answer

For most data types, Dock Optimizer treats SphereWMS as the system of record for inbound shipment data and Dock Optimizer as the system of record for appointment and check-in data. Conflict resolution rules are configurable during setup.

Question 6

Who sees the integration data in the Dock Optimizer UI?

Accepted Answer

Operators see the full SphereWMS shipment context — PO numbers, expected quantities, item descriptions — alongside the appointment record. Carriers only see what you choose to surface on the booking confirmation.