Skip to main content
Raw data only. ShipBob lands as raw warehouse tables, not modeled dashboards or AI analysis. Raw tables are delivered only to organizations on a dedicated warehouse, for the tables picked under Warehouse → Raw data in your SourceMedium workspace. See Foundation and Pro.
ShipBob is a fulfillment provider that stores your inventory and ships your orders from its fulfillment centers. SourceMedium reads your ShipBob orders, shipments, products, receiving orders, inventory, fulfillment centers, and channels every six hours and lands them in your warehouse.
Sign in to SourceMedium, open your store, then choose Data sources → Connect data source and select the platform. You need an Admin or Editor workspace role.After you connect explains the first sync and connection statuses.

​
Vendor documentation

​
Requirements

  • The account’s root user. ShipBob runs API access as the account’s root user, so create the token while signed in as that user. The root user sees every channel, so the token reads orders from every channel.
  • A personal access token. Know what you are handing over: a ShipBob personal access token has full account access, read and write, and it does not expire. SourceMedium only reads; every request it makes is a read. ShipBob recommends rotating tokens periodically.

​
How to connect

1

Create a personal access token

Sign in to ShipBob as the account’s root user. Open Integrations > API Tokens (direct link) and click Generate New Token. Your first token also creates a “PAT Channel” in ShipBob. That is expected.
2

Add the token in SourceMedium

Find ShipBob in the connector picker and click Connect. Paste the token, then click Save.
3

Confirm it is connected

SourceMedium checks the token with ShipBob before saving it, so a token ShipBob rejects is not saved. The connection reads Awaiting first data until the first sync lands, then Connected.
To rotate the token, generate a new one, save it in SourceMedium, then revoke the old one in the same ShipBob screen. Revoking a token before you replace it stops the sync.
SourceMedium only ever reads from your connected platforms. It does not create, change, or delete anything, so create the key with read-only access wherever the platform offers it. Treat it like a password: keep it confidential and avoid sharing it over email or in spreadsheets. If the credential is rotated or revoked, follow this guide’s connection method to update SourceMedium.

​
What data syncs

ShipBob documents order totals in USD. Shipments carry their own invoice amount and currency, kept as ShipBob returns them. Recipient names, emails, phone numbers, company names, street lines, cities, and postal codes are not imported, on orders, on shipments, or on B2B retailer addresses. The recipient’s country and state are kept. Select the tables you want under Warehouse → Raw data in your SourceMedium workspace to receive them in your_project.sm_sources.

​
Refresh and history

  • Refresh: every six hours. Orders and products changed since the last completed sync are read again. Fulfillment centers and channels refresh once a day.
  • History: the first sync loads 365 days of orders, every product, and the receiving orders from the last 90 days.
  • Inventory: ShipBob’s API serves only current inventory levels, so SourceMedium records them on every sync and keeps one row per item, fulfillment center, and day, holding that day’s last reading. Inventory history starts the day you connect and cannot be filled in for earlier days.

​
Known gaps

  • Receiving orders. Each sync re-reads receiving orders created in the last 90 days. A change to an older receiving order is missed.
  • Not included: billing invoices and transactions, returns, and locations. The tables are not a complete picture of fulfillment cost.

​
Troubleshooting

  • Token rejected? Create it again while signed in as the account’s root user, then paste the new token.
  • The connection says ShipBob will not serve orders? The token works, but ShipBob refused the data. Ask ShipBob to enable API access for the account. Reconnecting with the same token does not help.