Channels

BigCommerce setup

Last updated 14 March 2026

BigCommerce uses an API account model — similar to WooCommerce's REST keys but generated inside the BigCommerce admin.

Create an API account

In BigCommerce admin, go to Settings → API → API accounts → Create. Choose "V2/V3 API token", name it "Meridia", and grant these OAuth scopes: Orders (read-only), Products (read-only), Customers (read-only), Information & Settings (read-only), Store Inventory (read-only).

Copy credentials

You'll see the Client ID, Access token, and API path. Paste all three into Meridia's BigCommerce connect screen. The store hash is the subdomain-like string in the API path (e.g. stores/abc1defgh/v3).

Webhooks

Meridia subscribes to store/order/created, store/order/updated, store/order/statusUpdated, and store/refund/created. These drive real-time sync; the hourly poll acts as a safety net.

Multi-channel on BigCommerce

If you use BigCommerce's Channel Manager to push to Amazon or eBay, connect those platforms directly in Meridia as well — Meridia's attribution works better when talking to each marketplace as a first-class source.

Was this helpful?

Connect Shopify

Install the Meridia app and approve scopes — orders, payouts, and fulfilment.

Connect eBay

OAuth, the 18-month order history quirk, and how Meridia handles eBay fee structures.

WooCommerce setup

REST API keys, webhook registration, and the WordPress plugin.

Etsy setup

OAuth v3, Etsy Payments reconciliation, and listing fee handling.