Commerce

Connect Shopify and WooCommerce stores

Mirror external products, stock, customers and orders into shared SupaChrome records.

How to do it

  1. Open SupaCommerce → External stores. Commerce and Integration administration permissions are required to configure, test, pause and retry connections.
  2. Connect Shopify with its permanent myshopify.com domain and a valid Admin API token, or merchant-owned app client credentials. The app and store must belong to the same Shopify organization for client credentials. Grant product, inventory, customer and order read access. Customer data and older orders may need additional Shopify approval.
  3. For WooCommerce, create REST API consumer keys with read access, use the HTTPS store origin and choose a webhook signing secret of at least 16 characters. No store secret is returned to the browser.
  4. Test & enable verifies the store and its currency. The store and organization currency must match; this connector supports two-decimal currencies. Use Full sync for a backfill or Sync changes for incremental changes.
  5. Copy the connection webhook address. Subscribe to the product, customer, order and inventory topics shown in its setup panel. Signed callbacks are deduplicated and queued. The platform worker processes the durable queue and scans hourly; when no worker is available, use Process queue.
  6. Products match existing BU SKUs, customers match unambiguous email or international phone identities and source Orders reuse the shared Order service. Each store has its own source-owned stock channel, which cannot be enabled for POS.
  7. Review jobs in Synchronization activity. Partial refunds, unsupported lines, amended historical orders, identity conflicts and unreconciled totals stop for review. Retry latest source fetches current data rather than blindly replaying an obsolete update.
  8. Use Orders, Reports → External store orders, Channel P&L, Business pulse and Data Handler exports to inspect the shared source records.

Check your result

Replaying a signed event cannot create another Order, invoice, stock deduction or sale journal. Invalid signatures and cross-BU connection IDs are rejected.

Good to know

This is source-to-SupaChrome synchronization; edit store transactions and inventory in the source store. Source invoices and customer receipts remain authoritative. Paid unfulfilled orders are held as deposits; fulfilment posts revenue and saved costs; cancellation retains a refund liability until the source confirms refund. Product cost defaults to zero until configured. Fees, settlements, partial refunds and currency conversion require reviewed Finance work. Live provider access must be verified with each business’s credentials.

Still need help?

Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.

Contact SupaChrome support