BigCommerce

BigCommerce is a SaaS e-commerce platform for growing businesses.

Overview

The BigCommerce connector lets Spojit workflows read and write the core entities of a BigCommerce store: products, orders, customers, and categories. It targets the V2 and V3 REST APIs and exposes a raw-api-request escape hatch for endpoints not covered by dedicated tools.

Spojit users typically use BigCommerce as the storefront in a multi-system architecture - feeding orders downstream into NetSuite or ShipStation, pulling product data in from a PIM or other channels, and triggering finance and fulfilment automations the moment an order comes in.

What You Can Do

The BigCommerce connector exposes these tools:

list-orders - List orders with filters (status, date range, customer).
get-order - Fetch a single order with line items and addresses.
list-products - List products with filters (category, brand, status).
get-product - Fetch a single product with variants and images.
create-product - Create a product with variants and metadata.
update-product - Update product fields, pricing, or inventory.
delete-product - Delete a product by ID.
list-categories - List the store's category tree.
list-customers - List customers with filters.
get-customer - Fetch a single customer with addresses.
create-customer - Create a new customer record.
raw-api-request - Call any BigCommerce REST endpoint not covered by a dedicated tool (cart, checkout, shipments, etc.).

Authentication

BigCommerce uses a Store API token (an X-Auth-Token header). In the BigCommerce control panel, open Settings -> API -> Store-level API accounts -> Create API Account, choose the OAuth scopes your workflows need (Products, Orders, Customers, etc., usually with modify for any writes), then save. BigCommerce displays the token once - copy it immediately. You will also need the store hash from the API path BigCommerce shows you (looks like stores/xxxxxxxxxx).

Setting Up Your Connection

In BigCommerce, go to Settings -> API -> Store-level API accounts and click Create API account.
Pick the OAuth scopes that match your workflow's needs and save. Copy the access token and store hash.
In Spojit, go to Connections and click + Add Connection.
Search for BigCommerce and select it.
Enter the store hash and access token. Name the connection something descriptive (e.g. BigCommerce - US Production).
Click Save. Spojit verifies the credentials by hitting a lightweight read endpoint.

Using in a Workflow

Add a Connector node, select your BigCommerce connection, and pick a mode:

Direct Mode - Use for deterministic syncs (poll list-orders for new orders since the last run, then write them to NetSuite).
Agent Mode - Use for AI agents managing the store ("find this customer's recent orders and tag the latest one").

For endpoints not covered by a dedicated tool - carts, checkouts, shipments, refunds - use raw-api-request with the appropriate V2 or V3 path.

Tips

Use V3 endpoints via raw-api-request when available. V3 is faster and returns richer data; V2 is only kept for entities that haven't migrated yet (notably orders).
Set limit=250 for reads. The maximum page size on V3 is 250 - using it dramatically reduces round-trips.
Filter incremental syncs by date_modified. Both orders and products support range filters on this field.
Use webhooks for new-order workflows. Subscribing to store/order/created via the BigCommerce Webhooks API beats polling on latency.
Tag synced records. Setting a custom field on processed orders is the cheapest way to make a sync idempotent across reruns.

Common Pitfalls

Scope mismatch. If you create the API account with read-only scopes, writes fail with 401. Re-issue the token with broader scopes (the old one is invalidated).
Rate limits. BigCommerce uses per-store quotas - bursts above the budget return 429. The connector retries with backoff, but batching is cheaper.
Variant SKUs vs product IDs. Inventory and order line items reference variants; update-product operates on the parent. Don't conflate them.
V2 order pagination. Orders are still V2 - use page/limit not cursor pagination, and remember that an empty page is signalled by 204, not 200.
Sandbox vs production. Always test writes against a separate BigCommerce sandbox store - product and order deletes have no undo.

Common Use Cases

For technical API details and field specifications, see the BigCommerce connector documentation.