sales-bigcommerce
starsforks
How to install sales-bigcommerce?
sales-skills/sales/sales-bigcommerce
$npx -y skills add sales-skills/sales --skill sales-bigcommerceBigCommerce platform help — open SaaS commerce platform for makers and growing DTC/B2B stores: products, orders, customers, carts, checkout, and headless storefronts via REST Management APIs (v3 plus legacy v2 Orders), GraphQL Storefront and Admin APIs, and thin notification-styl
SKILL.md
| 1 | # BigCommerce Platform Help |
| 2 | |
| 3 | ## Step 1 — Gather context |
| 4 | |
| 5 | If `references/learnings.md` exists, read it first for accumulated platform knowledge. |
| 6 | |
| 7 | Figure out what the user actually needs before diving in: |
| 8 | |
| 9 | - **Goal** — building/debugging an API or webhook integration, choosing a plan, a checkout/conversion question, or a store-ops task? |
| 10 | - **Surface** — REST Management API (v3 / legacy v2), GraphQL Storefront API, GraphQL Admin API, webhooks, or the no-code control panel? |
| 11 | - **Account type** — store-level API account (token from control panel), app-level (OAuth, Dev Portal), or account-level (GraphQL Account API across stores)? |
| 12 | - **Plan** — Standard, Plus, Pro, or Enterprise? (Rate limits and a few features scale by tier; some plan names appear as Core/Growth/Scale/Performance on the current pricing page.) |
| 13 | |
| 14 | Skip-ahead rule: if the prompt already says what they need, go straight to Step 2. |
| 15 | |
| 16 | ## Step 2 — Route or answer directly |
| 17 | |
| 18 | If the question is really a cross-platform strategy, hand off with the exact command: |
| 19 | |
| 20 | | If the user wants… | Route to | |
| 21 | |---|---| |
| 22 | | Checkout conversion / order bumps / cart-abandonment tactics across carts | `/sales-checkout {question}` | |
| 23 | | Whether to use a Merchant of Record for global VAT/sales tax | `/sales-merchant-of-record {question}` | |
| 24 | | Digital-product pricing & launch strategy | `/sales-digital-products {question}` | |
| 25 | | Wiring BigCommerce into another tool via iPaaS | `/sales-integration {question}` | |
| 26 | | Post-purchase email / abandoned-cart sequences | `/sales-email-marketing {question}` | |
| 27 | |
| 28 | Otherwise it's a BigCommerce-specific question — answer it here. |
| 29 | |
| 30 | ## Step 3 — BigCommerce platform reference |
| 31 | |
| 32 | **Read `references/platform-guide.md`** for the full reference — capabilities and what's API vs webhook vs UI-only, pricing/plan gates, data model with JSON shapes, and quick-start recipes. For raw endpoint/auth/rate-limit/webhook detail, read `references/bigcommerce-api-reference.md`. |
| 33 | |
| 34 | Answer using only the relevant section — don't dump the whole guide. |
| 35 | |
| 36 | ## Step 4 — Actionable guidance |
| 37 | |
| 38 | - **Treat webhooks as a doorbell, not a delivery.** Every callback carries only `scope`, `store_id`, and `data.{type,id}` — fetch the real record with a follow-up REST call. Budget for that extra call against your rate limit; consider de-duping on the resource id + `created_at`. |
| 39 | - **Know the version split.** Most resources are v3 (`/v3/catalog/products`, `/v3/customers`, `/v3/carts`, `/v3/hooks`), but the classic **Orders API is v2** (`/v2/orders`). New work should prefer v3 where it exists. |
| 40 | - **Pace requests to the 30-second window.** Standard/Plus get ~150 requests/30s, Pro ~450; read `X-Rate-Limit-Requests-Left` and sleep for `X-Rate-Limit-Time-Reset-Ms` on a 429. |
| 41 | - **Use the minimum OAuth scopes.** A missing scope returns 403, not empty data; and a stray trailing slash on a path also 403s. |
| 42 | |
| 43 | If you discover a gotcha or fix not in `references/learnings.md`, append it there with today's date. |
| 44 | |
| 45 | ## Gotchas |
| 46 | |
| 47 | *Best-effort from research (2026-06) — re-verify plan gates, fees, rate limits, and API versions against live docs.* |
| 48 | |
| 49 | - **Thin webhook payloads.** Callbacks never include the changed object — only the id. You must call the API to get the data, which effectively doubles API usage per event. |
| 50 | - **No webhook delivery logs.** There is no activity dashboard or delivery-history endpoint; if an event goes missing you can't trace it on BigCommerce's side. Log everything you receive and reconcile against the API. |
| 51 | - **Webhooks auto-deactivate.** Repeated 4XX/5XX responses (or long inactivity) deactivate a subscription — respond 2XX fast (do work async) and re-check `is_active`. |
| 52 | - **No HMAC signing.** Unlike Shopify/Stripe, BigCommerce does not sign payloads. Secure the callback with a sec |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
