BigCommerce support is in development and has not been released. This page describes the integration being tested; it does not mean new production connections are available yet.
The integration connects a BigCommerce store through the QuickSync app. It reads the store’s products, variants, options, images, categories, orders, and inventory locations. Product content follows the selected master store, inventory follows changes from aligned stores, and eligible orders route to the selected fulfilment store.
The BigCommerce app offers supported marketplaces, point-of-sale and accounting integrations. New connections to competing storefront platforms are restricted. The connection picker shows the choices available to your account. Existing connected stores retain their identities and can reconnect to the same shop; this does not enable a different shop on a restricted platform.
Install and connect during testing
Use the app installation made available to your approved test store. A Developer Portal draft is not a public Marketplace release.
- Open QuickSync from the BigCommerce control panel. If the app shows a connection prompt, follow its separate-tab sign-in or create-account link.
- Sign in to the QuickSync merchant account that should own this connection. New accounts must finish email verification. Review the displayed BigCommerce store and QuickSync account, then confirm the link.
- Return to BigCommerce and reopen QuickSync. The workspace opens inside the control panel. Each BigCommerce user links their own authorized QuickSync account; another user’s link does not sign them in.
- Connect the other store in Settings. Connections open in a separate tab. After authorizing the store there, return to BigCommerce and refresh Settings. Choose the master store for product content and, when order syncing is available and enabled, the fulfilment store for routed orders. These choices have different purposes.
- Check that each selected variant has a unique matching SKU. Connect the intended inventory locations and start with one selected test product. Review the setup before starting sync; a saved location mapping alone does not re-sync existing quantities.
- Read the product and stock values in both native stores after the initial run. Then enable the intended product selection and supported ongoing sync features. Review any items needing attention before expanding the selection.
Use the embedded workspace
Overview shows connection and sync activity. Products shows the selected catalogue, product details, inventory locations and issues that need attention. Orders shows routed-order status and its retained destination copy. Settings manages connections and workspace preferences. Account or billing actions that require a separate tab provide that handoff explicitly.
Edit supported product content in the master store. Inventory updates may originate in either aligned store; QuickSync follows native sellable quantities and preserves BigCommerce’s safety-stock buffer. An unmapped location is not an extra stock source. If a session expires, reopen QuickSync from BigCommerce rather than sharing another user’s session link.
After an eligible test order, check the native source and destination amounts, line quantities and stock. Repeated delivery should retain the same destination order. Check supported tracking in the origin after fulfilment. A partial package cannot complete a WooCommerce order through its current whole-order tracking path; review that case instead of treating it as completed.
Each BigCommerce location must be paired with the corresponding location in the other store before inventory can sync. Unavailable stock is treated as unknown, and an inventory write is only reported as complete after a native stock read confirms it.
When inventory is shared with the source store, copied BigCommerce orders use native external SKU lines so the same sale does not deduct stock twice. The SKU and order-line identity remain available for fulfilment; those lines have no BigCommerce catalogue link.
Product variants need unique SKUs of at most 250 characters for reliable matching. Duplicate or missing identities require correction before the affected product or order can sync. Products with multiple shipping addresses require explicit allocation and are held for review. Digital files must be managed in BigCommerce itself.
Native product brands follow the master when available. BigCommerce accepts one brand per product; multiple source brands and names the destination cannot represent hold the product for review. Clearing the brand in the master removes the destination assignment. Brand logos, pages and taxonomy SEO remain managed in each platform.
Initial order notes are copied. Later changes to merchandise, amounts, addresses or notes on an existing BigCommerce copy require review; the accepted copy is preserved. Cancellation can still proceed after that review hold.
When the source provides a payment-method label, new BigCommerce order copies retain that label. This records order metadata; QuickSync does not charge the customer through that label. A later source payment-label change requires review of the existing copy.
A BigCommerce order without a confirmed create response is retained for reconciliation before another create can be attempted. Cancelling an order does not create a new fulfilment-store copy. Refund status is distinct from issuing a financial refund. Cancellation waits for review if the BigCommerce store would automatically restore stock.
Native tax copied to WooCommerce requires the supported QuickSync plugin and verified, uniform tax allocation in the same currency. Ambiguous tax or multi-address allocation needs review. Digital download files stay managed in BigCommerce. Supported public product details and metadata follow the selected source when that source exposes them; unobserved fields keep their native values.
For shared concepts, see inventory syncing, product syncing, and order syncing.
