SYSPRO and ShipBob integration

What moves between them

Orders flow from ShipBob into SYSPRO via webhooks. When ShipBob receives an order, ml-connector captures the order.shipment event, maps ShipBob items to SYSPRO inventory SKUs, and posts a confirmed sales order into SYSPRO's ArInvoice and ArCustomer tables. Inventory flows in both directions: SYSPRO inventory masters are polled and sent to ShipBob to keep stock levels current, and ShipBob warehouse receiving orders (WRO) trigger SYSPRO inventory transactions. Shipment tracking flows from ShipBob back into SYSPRO so sales orders reflect actual fulfillment status.

How ml-connector handles it

ml-connector stores SYSPRO session tokens and ShipBob OAuth tokens encrypted, refreshes ShipBob tokens when they expire (1-hour lifetime), and manages SYSPRO session logons to keep the session alive across polling intervals. On the ShipBob side it verifies every webhook signature using the stored webhook secret and HMAC-SHA256 before processing the event. When an order arrives via webhook, ml-connector looks up the ShipBob sales channel to find the matching SYSPRO customer, maps ShipBob items against SYSPRO InvMaster records by SKU, and writes the order into SYSPRO via Business Objects REST. For inventory syncs, ml-connector polls SYSPRO OData for InvWarehouse and InvPrice records on a regular interval and pushes updates to ShipBob's inventory endpoint, tagged with the shipbob_channel_id for the correct fulfillment center. Receiving orders trigger SYSPRO InvWarehouse transactions to adjust on-hand balances. ShipBob rate limits are handled with exponential backoff and jitter.

A real-world example

A mid-sized fashion distributor uses SYSPRO ERP to manage production, purchasing, and sales across five warehouses, and uses ShipBob to fulfill orders placed online and through partners. Before the integration, the warehouse team received picking lists from ShipBob via email and manually entered confirmed orders into SYSPRO by end of day, which created delays and SKU mismatches when SYSPRO quantities differed from ShipBob stock. With SYSPRO and ShipBob connected, orders confirmed in ShipBob flow into SYSPRO automatically with correct SKUs and quantities, warehouse staff pick from ShipBob with confidence that SYSPRO inventory is in sync, and receiving orders update stock in both systems in real time. Order-to-cash cycle time dropped and inventory variance closed.

What you can do

• •Receive ShipBob orders via webhook and post confirmed sales orders into SYSPRO's sales ledger with correct customer and SKU mapping.
• •Keep SYSPRO inventory balances in sync with ShipBob fulfillment center stock levels via scheduled polling and inventory updates.
• •Sync warehouse receiving orders from ShipBob into SYSPRO inventory transactions so stock counts reconcile across both systems.
• •Authenticate ShipBob with OAuth2 bearer tokens and SYSPRO with session tokens, managing token refresh and logon persistence.
• •Verify ShipBob webhook signatures, handle 429 rate limits with backoff, and maintain a full audit trail on every record moved.

Questions

Which direction does data move between SYSPRO and ShipBob?

Orders and shipment tracking flow from ShipBob into SYSPRO via webhooks, so new orders are posted to SYSPRO's sales ledger and fulfillment status updates SYSPRO sales orders. Inventory flows in both directions: SYSPRO inventory masters are polled and pushed to ShipBob to keep stock current at fulfillment centers, and ShipBob warehouse receiving orders trigger SYSPRO inventory transactions so on-hand balances reconcile.

How does the integration handle SYSPRO's customer-hosted deployment and multiple authentication methods?

ml-connector accepts the full SYSPRO server URL per customer and stores both the OData credentials (HTTP Basic Auth) and the Business Objects session token per customer. It polls SYSPRO OData for read-only data and uses Business Objects REST for order writes, managing session token logons to keep the session alive between polling intervals so connection overhead is minimized.

How are ShipBob webhooks secured and what happens if a signature verification fails?

Every ShipBob webhook is signed using HMAC-SHA256 with a webhook secret. ml-connector verifies the signature on every event using the stored secret and the webhook-id, webhook-timestamp, and webhook-signature headers. If the signature fails, the event is rejected immediately and logged, so no unsigned or tampered orders enter SYSPRO.