OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
GET /catalog/products returns structured products.
BigCommerce working with catalog products ↗
GET All Products · Checked 2026-10-16
Bulk delivery -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed product lesson does not establish complete pagination semantics.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Query expressiveness -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Field selection is documented; scored structured filter contract remains unresolved.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Access cost barrier -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed BigCommerce route does not establish access cost barrier.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Store credentials explicitly support a manual third-party app connection.
BigCommerce API account models and third-party connections ↗
Choosing the right kind of API account · Checked 2026-10-16
Downstream permission -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed BigCommerce route does not establish downstream permission.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
POST catalog/products creates one product with modify scope.
BigCommerce Create Product reference ↗
Create Product / OAuth scopes · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Merchants create store API accounts for manual third-party integrations.
BigCommerce API account models and third-party connections ↗
Store-level API accounts · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Supported store event webhooks trigger external refetch.
BigCommerce webhook delivery and retry behavior ↗
Overview / Creating a webhook · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Plan-specific quotas, response headers and responsible retry guidance published.
BigCommerce API rate limits ↗
Rate limits by plan type / retry guidance · Checked 2026-10-16
CDC and deletion capture -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed BigCommerce route does not establish cdc and deletion capture.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Webhook retries stop after approximately 48 hours with deactivation.
BigCommerce webhook delivery and retry behavior ↗
Callback retry mechanism · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Product API responses expose records to the authorized application.
BigCommerce working with catalog products ↗
GET All Products · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed BigCommerce route does not establish post-cancellation access.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
Portable catalog product records; file and whole-store reconstruction unverified.
BigCommerce catalog scope and file limitations ↗
Products overview / Creating digital products · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
API accounts support third-party integration code.
BigCommerce API account models and third-party connections ↗
API accounts · Checked 2026-10-16
Rights to custom logic -
-
BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes.
The reviewed BigCommerce route does not establish rights to custom logic.
BigCommerce working with catalog products ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Store owners or users with high-risk API permissions create store-level credentials. Documentation explicitly supports manual connections to third-party apps; app-level OAuth and marketplace publication have separate requirements.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The catalog API exposes product records and related resources. Store and account-level credentials cover different boundaries; B2B and payments require additional product-specific scopes.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Store-level scoped API account | API key | Customer | No | store owner/high-risk permission creates account; x-auth-token authenticates selected store scopes | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Store quotas depend on the plan and are shared by all apps using the store. Rate-limit headers and retry guidance are published; minimum API entitlement and any fixed access fee remain unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Create Product documents POST /v3/catalog/products and product-modify permission. Extension-specific and payment writes require their own operation checks.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Webhooks send lightweight identities that require refetching state. Delivery retries end after about 48 hours and the hook is deactivated; deleting an API account also removes its webhooks.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed BigCommerce route does not establish cdc and deletion capture. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Webhook retries stop after approximately 48 hours with deactivation. | BigCommerce webhook delivery and retry behavior ↗Callback retry mechanismChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Product records can be held outside the platform. Complete digital product files, historical records and store configuration remain unverified (digital file attachment is handled separately from catalog APIs).
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Applications can implement customer logic with scoped APIs. Native workflow artifact rights and post-cancellation retrieval remain unresolved.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. GET /catalog/products returns structured products. | BigCommerce working with catalog products ↗GET All ProductsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed product lesson does not establish complete pagination semantics. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Field selection is documented; scored structured filter contract remains unresolved. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Store credentials explicitly support a manual third-party app connection. | BigCommerce API account models and third-party connections ↗Choosing the right kind of API accountChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed BigCommerce route does not establish access cost barrier. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed BigCommerce route does not establish downstream permission. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. POST catalog/products creates one product with modify scope. | BigCommerce Create Product reference ↗Create Product / OAuth scopesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Merchants create store API accounts for manual third-party integrations. | BigCommerce API account models and third-party connections ↗Store-level API accountsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Supported store event webhooks trigger external refetch. | BigCommerce webhook delivery and retry behavior ↗Overview / Creating a webhookChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Plan-specific quotas, response headers and responsible retry guidance published. | BigCommerce API rate limits ↗Rate limits by plan type / retry guidanceChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Product API responses expose records to the authorized application. | BigCommerce working with catalog products ↗GET All ProductsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed BigCommerce route does not establish post-cancellation access. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. API accounts support third-party integration code. | BigCommerce API account models and third-party connections ↗API accountsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -BigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. The reviewed BigCommerce route does not establish rights to custom logic. | BigCommerce working with catalog products ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBigCommerce single-store API accounts for REST catalog products and supported store webhooks; app-level OAuth distribution and account-level administration are distinct routes. Portable catalog product records; file and whole-store reconstruction unverified. | BigCommerce catalog scope and file limitations ↗Products overview / Creating digital productsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed access charges
- Deletion-event coverage for selected resources
- Durable consumer replay beyond webhook retries
- Whole-store files/configuration migration
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.