Connecting BigCommerce to Vortex IQ gives the AI OS a live read on your orders, products, customers, and revenue across every sales channel your store operates. BigCommerce’s multi-channel architecture means Vortex IQ can segment KPI cards by channel ID, giving you per-channel revenue, conversion rate, fulfilment, and refund breakdowns that most analytics tools flatten into a single number.Documentation Index
Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
Use this file to discover all available pages before exploring further.
What data Vortex IQ reads from BigCommerce
Vortex IQ connects to the BigCommerce API v2 and v3 and ingests the following data:Orders and revenue
Orders and revenue
- Order totals across all channels (Online Store, POS, marketplace channels, headless storefronts)
- Order status, payment status, and fulfilment status per order
- Discount codes and coupon amounts
- Refunds and returns
- Shipping methods and shipping revenue
- Tax amounts and gateway per order
- Failed and incomplete orders (declined payments)
Products and inventory
Products and inventory
- Product variants with current stock levels
- Product margin and COGS (where configured in BigCommerce)
- Product type, brand, and category
- SKU and barcode per variant
- Channel-specific product listings and inventory splits
Customers
Customers
- Customer records with email state
- Guest vs registered customer breakdown
- Order frequency and geography per customer
- Repeat purchase signals and churn risk indicators
BigCommerce uses credential-based authentication (API key + Store Hash) rather than OAuth. Vortex IQ shows step-by-step instructions for generating your API key inline in the connector drawer.
How to connect
Open Connected Sources
In your Vortex IQ workspace, go to Settings → Connected Sources. You need Admin role in the workspace to connect sources.
Find the BigCommerce card
Locate the BigCommerce connector card and click + Connect. The connector drawer opens with a credential form rather than an OAuth button.
Generate your API credentials in BigCommerce
Follow the inline instructions in the drawer to generate an API account in BigCommerce: go to Advanced Settings → API Accounts → Create API Account (V2/V3 API Token). Set the OAuth Scopes to at least: Orders (read-only), Products (read-only), Customers (read-only), Store Information (read-only).
Enter credentials in Vortex IQ
Copy the Client ID, Client Secret, and Access Token from BigCommerce and paste them into the corresponding fields in Vortex IQ. Also enter your Store Hash (found in your BigCommerce store URL:
store-{hash}.mybigcommerce.com).Verify and connect
Click Verify and Connect. Vortex IQ makes a test API call to validate the credentials. On success, the card flips to Connected. On failure, an inline error identifies the issue (typically a missing scope or typo in the store hash).
Set all API scopes to read-only. Vortex IQ does not require write access to any BigCommerce resource.
Available KPI cards
Vortex IQ populates 115 Nerve Centre cards from your BigCommerce data, including a set of channel-specific cards that are unique to BigCommerce’s multi-channel architecture.Revenue and growth
Total Revenue — Gross revenue across all channels for the period, compared to prior period. Alerts on a drop greater than 15% vs prior 30 days.Revenue Over Time — Daily revenue trend sparkline.Average Order Value — Revenue ÷ Order Count.Revenue by Channel — Per-channel revenue breakdown by channel ID.Revenue by Currency — Multi-currency revenue breakdown.Revenue by Device — Desktop vs mobile revenue split.Revenue by Hour — Intra-day revenue pattern.
Channel performance
Channel Revenue Mix — Share of total revenue by channel.Channel Revenue Trend — Per-channel daily revenue trend.Channel AOV — Average order value broken out by channel.Channel Conversion Rate — Conversion rate per channel.Channel Fulfilment Rate — Fulfilment performance per channel.Channel Refund Rate — Refund rate per channel.Channel OOS per Channel — Out-of-stock variants by channel.Channel Repeat Rate — Repeat purchase rate by channel.
Orders and payments
Order Count — Total orders placed.Orders by Channel ID — Volume per BigCommerce channel.Failed Orders Count — Orders that failed due to payment decline.Failed Orders Value — Revenue value of failed orders.Decline Rate by Payment Method — Which payment methods are declining most.Incomplete Rate — Orders started but not completed.Unrecovered Value — Value of failed orders not recovered.
Inventory and products
Products with Zero/Negative Stock — Live count of OOS variants. Alerts when any active variant hits zero.Stock vs Sales — Variants approaching stockout.Inventory Distribution — Stock level distribution across variants.Revenue by Brand — Revenue broken out by product brand.Revenue by Category — Revenue broken out by product category.Product Margin — Margin per product where COGS is configured.Top SKUs by Revenue — Highest-revenue variants in the period.
Customers
Customer Count — Total active customers.New Customers — First-time buyers in the period.Repeat Rate — Share of customers who bought more than once.Guest vs Registered — Breakdown of guest checkout vs account orders.Churn Risk — Customers showing lapse signals.Top Customers — Highest-value customers by lifetime spend.
Alerts and health
Revenue Drop Alert — Revenue falls more than 15% vs prior period.OOS Spike Alert — Out-of-stock count rises sharply.Refund Rate Spike Alert — Refund rate rises sharply.Fulfilment Delay Alert — Fulfilment rate drops below threshold.Abandoned Cart Spike Alert — Cart abandonment rate rises sharply.Channel Revenue Drop Alert — Revenue drops sharply on a specific channel.Store Health Score — Composite 0–100 score blending revenue trend, fulfilment rate, refund rate, and OOS count.
Cross-channel cards
When you also connect ad platforms or other data sources alongside BigCommerce, Vortex IQ unlocks additional cross-channel cards:| Card | What it shows |
|---|---|
| Active Ads on Out-of-Stock SKUs | Ad spend on OOS variants — pause candidates |
| Revenue at Risk from active incidents | Live revenue impact when a monitoring incident is open |
| Catalogue Drift vs Amazon | BigCommerce SKUs active on Amazon but OOS on the main store |
| Checkout Funnel Drop | Step-by-step checkout funnel drop-off correlated with ad traffic |
| Paid Traffic Waste | Ad spend landing on low-converting or OOS pages |
| Klaviyo Email Revenue Share | Email-attributed revenue as a share of BigCommerce total |
Troubleshooting
Credential verification fails
Credential verification fails
Check the following in order: (1) trailing whitespace on any pasted credential — re-copy and paste again; (2) the Store Hash matches the hash in your BigCommerce admin URL exactly; (3) the API account has the required read-only scopes for Orders, Products, Customers, and Store Information. If all three are correct and verification still fails, regenerate the Access Token in BigCommerce and retry.
Channel-specific cards are empty
Channel-specific cards are empty
BigCommerce channel cards require that your store has multiple channels configured. If you operate a single storefront, channel-breakdown cards will show data only for channel ID 1 (the default storefront). Cards that show “no data” for additional channels indicate those channels are not yet active in your BigCommerce account.
Revenue in Vortex IQ differs from BigCommerce analytics
Revenue in Vortex IQ differs from BigCommerce analytics
BigCommerce Analytics uses the order creation date in your store’s local timezone. Vortex IQ uses UTC. On boundary days, orders near midnight may fall on different dates in each system. The difference is typically less than one day’s revenue at the boundary and averages out over a 30-day window.
Declined and failed orders are missing
Declined and failed orders are missing
Failed orders are captured via the BigCommerce Orders API with
status_id values for incomplete and failed states. If declined orders are not appearing in the relevant Nerve Centre cards, check that the API account was granted access to the Orders scope and that the connection was established after the orders were created.