BIGCOMMERCE · SKU-MD v1.0.0-beta

Publish a minimal BigCommerce root, then add sourced knowledge only when needed

Enter a public storefront or catalog, or one public product page. Generate the minimal root first, then optionally add one Source-linked Product knowledge document.

Open BigCommerce generator

No credentials · No private APIs · No bulk crawl · No automatic publication

BigCommerce runs live commerce; SKU-MD carries reviewed knowledge

The integration keeps dynamic transactions and durable product knowledge in the systems that can actually support them.

BIGCOMMERCE

Live commerce authority

Owns current products, variants, channel pricing, inventory, shoppers, carts, orders, and checkout behavior.

SKU-MD

Minimal public document contract

Publishes a v1 root at /sku.md and, only when useful, one optional Source-linked Product knowledge document.

The current generator uses public evidence only

The flow is intentionally limited to public inputs and locally generated files.

01
Enter a public URL
Provide a public storefront or catalog, or one public product page.
02
Generate the minimal root
Create and validate the v1 root before adding any optional document.
03
Add knowledge only when sourced
Optionally create one Source-linked Product knowledge document from the explicitly submitted product page.
04
Publish and validate
Publish /sku.md, then run the document, published, and graph validation scopes.

BigCommerce capabilities solve different parts of the lifecycle

These are documented BigCommerce surfaces. Listing them does not mean the current public generator calls them.

PUBLIC

Storefront, catalog, or product page

The current generator reads only the public URL submitted by the user. It does not infer extra products or crawl the catalog.

STOREFRONT

GraphQL Storefront API

Queries visible products, variants, prices, storefront metafields, routes, and content. Requests require an appropriate bearer token; the current generator accepts none.

MANAGEMENT

REST Management API

Authorized API accounts can manage catalog and store data using scoped credentials. This is a future server-side synchronization input, not a public browser source.

AUTH

API accounts and OAuth

Store-level and app-level accounts carry access tokens and OAuth scopes. Secrets stay server-side and least privilege is required.

EVENTS

Webhooks

HTTPS, Pub/Sub, or EventBridge delivery can trigger incremental refresh. Receivers still need authentication, idempotency, retry handling, and reconciliation.

STOREFRONT UI

Scripts API

Authorized apps can add channel-aware storefront scripts. Scripts can announce discovery links, but client-side code is not the requested Markdown response.

DELIVERY

Stencil and headless storefronts

Stencil custom templates are assigned to existing page types. A merchant-controlled headless or edge layer can implement an exact same-origin document route.

The reviewed official sources do not document BigCommerce adoption of SKU-MD. Platform capability, compatible discovery, strict conformance, and live authority remain separate claims.

Choose delivery by the response you can prove

The generated Markdown is the same in every mode. Only the deployed route determines whether publication is compatible or strict.

DISCOVERY

Stencil storefront

Add a visible or machine-discoverable link through a theme, existing content page, or app-managed script.

Stencil templates render existing storefront page types; Scripts API installs scripts. Neither alone proves a root-path text/markdown response.

STRICT CANDIDATE

Merchant-controlled headless route

Serve immutable, pre-validated files from the storefront application while keeping canonical and parent links on the same origin.

Require exact HTTP 200, Content-Type: text/markdown, byte identity, valid document graph, predictable cache replacement, and exact unknown-file 404.

STRICT CANDIDATE

Same-origin edge route

Serve stored documents at /sku.md and product document paths before requests reach the hosted storefront.

A routing rule is not proof. Verify the real response after every publication change.

Mode	What it can do	Evidence boundary
Stencil	Use a theme, custom page, or Scripts API integration to expose discovery guidance.	Compatible discovery only; the documented surfaces do not establish an arbitrary root-path Markdown response.
Headless	Serve accepted files from the merchant-controlled storefront application on the store origin.	Strict only after the exact route, media type, bytes, graph, cache replacement, and 404 behavior pass.
Edge	Intercept same-origin document paths before the hosted storefront and return stored accepted bytes.	Strict only after the public response is verified independently from configuration.

Keep the v1 document family minimal

The dedicated generator uses the same v1 builders and validator as the generic workflow.

Minimal root first

Create the v1 catalog root with the public store identity and a catalog entrypoint.

One optional product document

Add product knowledge only for the one public product page explicitly submitted by the user.

Source-linked facts

Every included fact links to a public Source; the graph validator checks the resulting document relationships.

Conservative scope

If usable sourced product knowledge is unavailable, keep the valid root and do not create the optional document.

Validate every publication scope

Creation and publication are separate steps, so each scope has its own evidence.

document
Validate generated bytes
Run the active v1 document validator before publication.
published
Validate the public response
Check the real /sku.md response, status, MIME type, and bytes.
graph
Validate relationships
Check every referenced document and Source relationship.
REPEAT
Verify after each change
Re-run all scopes whenever the published files change.

The current workflow does not connect to BigCommerce accounts or publish files automatically.

Current-release permissions and limits

The public workflow stays narrow, inspectable, and merchant-controlled.

No BigCommerce login, API account, OAuth flow, access token, storefront token, or private token.
No REST Management API or GraphQL Storefront API request and no catalog crawl.
No order, customer, cart, checkout, payment, or private product access.
No Webhook subscription, background synchronization, theme edit, script installation, or automatic refresh.
No DNS, proxy, edge, cache, or production publication change.
No claim of BigCommerce endorsement, partnership, official SKU-MD support, or adoption benefit.

The brand perspective

Explore what SKU.md adds to your platform and where a small product-knowledge pilot can begin.

BigCommerce SKU.md integration

Official sources reviewed on 2026-08-07

BigCommerce capability statements come from docs.bigcommerce.com. SKU-MD delivery requirements are labeled separately as independent verification rules.

Developer Quick Start ↗
Platform overview, sandbox, credentials, REST, and GraphQL entrypoints.
API accounts ↗
Account types, access tokens, OAuth scopes, and authentication boundaries.
GraphQL Storefront authentication ↗
Storefront, private, and customer token requirements.
GraphQL products ↗
Visible product, variant, price, metafield, and catalog fields.
Webhooks ↗
Event delivery mechanisms, callbacks, retries, limits, and security.
Scripts API ↗
Channel-aware script installation and storefront limitations.
Stencil custom templates ↗
Supported page types, assignments, and URL mapping boundaries.
Headless routes ↗
GraphQL route lookup for products, categories, pages, blogs, and redirects.
Headless site content ↗
Pages, rendered regions, blogs, banners, and route-based content retrieval.

BigCommerce integration FAQ

Does the generator connect to a BigCommerce account?

No. It reads public HTML and one explicit same-origin product page. It has no login, token, OAuth flow, or BigCommerce API connection.

Why not call GraphQL Storefront API directly?

BigCommerce requires an appropriate bearer token. The public generator deliberately accepts no credential and does not proxy private tokens.

Can Stencil publish /sku.md directly?

The reviewed custom-template documentation covers existing brand, category, product, and page types; it does not establish an arbitrary root-path Markdown response.

Can Scripts API publish the file?

Scripts API installs client-side storefront scripts. A script can announce a discovery link, but it is not the requested HTTP 200 text/markdown document response.

What can headless storefronts do?

A merchant-controlled headless application can implement the route, but strict delivery exists only after the real same-origin response passes status, MIME, byte, graph, cache, and 404 checks.

What does the generator create first?

It always creates the minimal v1 root first. The Source-linked Product knowledge document is optional.

Does the knowledge document replace live catalog data?

No. It contains only explicit Source-linked facts and carries no live price or inventory state. BigCommerce still owns carts, checkout, payment, and orders.

Does BigCommerce officially support SKU-MD?

No reviewed official source says so. This independent guide maps documented BigCommerce capabilities to a merchant-controlled workflow; it does not document official BigCommerce adoption of SKU-MD.

Start with public evidence, then publish only what you can verify

Create a reviewable draft without credentials. Use Stencil for discovery or a merchant-controlled headless or edge route for verifiable Markdown delivery.