Skip to main content

Connect a store & sync orders

A bridge is a live connection to a platform you already run on, such as Shopify, ShipStation, WooCommerce, BigCommerce, or Amazon. Once a bridge is connected, Orderly pulls orders in and pushes fulfillment out, so everything lives in one place.

Open Bridges

Connect a bridge​

Go to Bridges and click Add Bridge. Pick the platform you want to connect. They are grouped by category (E-Commerce, Shipping & Fulfillment, Marketplaces, ERP, Marketing), and a ⚡ icon on a tile means that platform supports real-time webhooks.

What you enter next depends on how the platform authenticates.

Shopify (and other OAuth platforms)​

Shopify connects over OAuth, so you do not need an API key or access token.

  1. Give the connection a Display Name, for example "Main Store".
  2. Under Store Connection, type your store's subdomain in Shop Domain. That is the mystore part of mystore.myshopify.com.
  3. Click Connect with Shopify. You are redirected to Shopify to authorize, then returned to Orderly.

Back on the Bridges page you will see a Complete Your Setup prompt. Click Configure Webhooks to turn on real-time order sync (covered below). Without webhooks, Orderly falls back to scheduled polling.

BigCommerce and Amazon Seller follow the same OAuth pattern. Amazon also asks you to pick a Marketplace.

API-key platforms (ShipStation, WooCommerce)​

Platforms that use API credentials show an API Credentials section instead of the OAuth redirect. Fill in the fields the platform requires and click Connect. Orderly tests the credentials as part of connecting.

PlatformFields
ShipStationAPI Key, API Secret
WooCommerceSite URL, Consumer Key, Consumer Secret

Credentials are encrypted at rest. If a platform tile links to setup docs, use View setup documentation to find where each value lives in that platform's admin.

Klaviyo has its own page

Selecting Klaviyo opens a dedicated connect page (Bridges → Klaviyo) where you authorize over OAuth and choose which events to forward: Placed Order, Order Shipped, and Order Delivered. Use these to trigger your email and SMS flows.

What each bridge card shows​

Back on the Bridges page, every connection is a card with its status (active, paused, error, disconnected, or authorization needed), the last sync time (or Never synced), and any error message. From a card you can:

  • Sync now pulls immediately. Available only when the bridge is active.
  • Tasks opens the bridge's tasks and schedules (see below).
  • ⋯ → Configure edits the name, rotates credentials, or manages webhooks.
  • ⋯ → Pause / Resume stops or restarts syncing without deleting the bridge.
  • ⋯ → Remove disconnects the bridge. This cannot be undone.

Run and schedule sync tasks​

Each bridge exposes a set of tasks, the concrete things it can do, like grab-orders, push-fulfillment, or grab-shipments. Open a bridge's Tasks & Schedules page (from the card, or ⋯ → Tasks & Schedules) to work with them. It has three tabs:

  • Tasks lists every task the bridge supports. Hover a row and click ▶ to run it once. If a task takes parameters, such as a date range for a backfill, a Run Task dialog collects them first. Otherwise it runs immediately.
  • Schedules holds recurring runs. From the Tasks tab, click the 📅 button on a schedulable task to set a cadence. Run every offers presets from Every 5 minutes through Weekly on Monday, including Daily at 6 AM and Weekdays at 9 AM. Pause, resume, or delete a schedule from its ⋯ menu.
  • History shows the last runs with their status (pending, queued, running, success, failed, retrying) and any error. Use it to confirm a sync worked, or to see why one did not.

Scheduling grab-orders to run every 15 to 30 minutes is the usual way to keep a store in sync when webhooks are not available.

Turn on real-time webhooks​

Webhooks push new and updated orders the moment they happen, so you do not wait for the next scheduled poll. Open ⋯ → Configure on a bridge card. If the platform supports webhooks, a Real-time Webhooks section lists the available topics. Flip the switch on the ones you want.

Webhooks need HTTPS

Webhook destinations must be publicly reachable over HTTPS. Localhost and private network addresses cannot receive platform deliveries.

Next steps​