By platform

Terms & Conditions Generator for BigCommerce

Written for BigCommerce checkout, its app marketplace, headless storefronts and multi-storefront setups.

Generate your terms and conditions Read the terms and conditions guide

BigCommerce stores frequently sell B2B as well as B2C, and the terms have to distinguish them - because consumer protection rules apply to one and not the other, and a single set of terms usually over-promises to one audience and under-protects against the other.

BigCommerce is used disproportionately by larger and more complex stores, which changes the compliance picture. Multi-storefront setups sell the same catalogue into several countries from one backend, headless builds move the storefront onto a separate front end entirely, and B2B features add company accounts with multiple buyers under one customer record.

Each of those raises a question a single-storefront policy does not answer. Multi-storefront means one backend covering several jurisdictions with different consent rules. Headless means the tracking lives in your own front end rather than in a theme BigCommerce controls. B2B means personal data about named individuals inside a business account.

BigCommerce provides a consent-management integration and its own script manager, which is where third-party tags are registered. That script manager is the single most useful inventory for building an accurate cookie and recipients disclosure.

What a terms and conditions for a BigCommerce store has to cover

Separate consumer and business terms, or clearly delineated sections
Trade account terms: credit, purchase orders, approval workflows
Consumer cancellation rights where you sell to consumers
Pricing, tax and duty handling across the markets each storefront serves
Delivery, risk transfer and shortfall handling

How a BigCommerce store actually moves personal data

Checkout and customer accounts

Billing and shipping data, order history and saved addresses, held per storefront but in a shared backend.

Script Manager tags

Analytics, advertising and support scripts registered centrally and injected into the storefront.

Headless front-end tracking

On a custom front end, tags live in your own code and are outside anything the platform gates by default.

B2B company accounts

Named buyers, approval hierarchies and purchase limits - personal data attached to a business relationship.

Multi-storefront customer segmentation

The same customer may exist under several storefronts with different applicable law.

Payment gateway hand-off

Stripe, PayPal, Braintree or an enterprise gateway, each seeing different fields depending on integration mode.

Third parties the draft will ask you about

BigCommerce · Stripe · PayPal · Braintree · Klaviyo · Google Analytics 4 · Avalara · ShipperHQ

The rules that apply

BigCommerce Terms of Service and DPA

BigCommerce processes store data on your behalf, with a published data processing addendum and sub-processor list.

Script Manager and consent

Third-party scripts are registered centrally and can be gated by consent category, but only if each script is categorised.

Multi-storefront jurisdiction split

One backend serving several markets means several sets of consent, cancellation and disclosure rules.

Headless storefront responsibility

With a custom front end, the tracking, the banner and the consent enforcement are yours rather than the platform’s.

B2B customer accounts

Company accounts contain personal data about named buyers, which is personal data even in a business context.

What the generated terms and conditions contains

Who the contract is with and how it is formed
Your legal entity, and the exact moment acceptance happens - account creation, checkout, or continued use.
The service, the licence and its limits
What you are actually providing, what the user may do with it, and what they may not.
Price, payment, renewal and cancellation
Billing cycle, auto-renewal, price-change notice, and how either side ends the arrangement.
Acceptable use and enforcement
The behaviour that gets an account suspended, and the process you follow before you suspend it.
User content and intellectual property
Who owns what, the licence you need to run the service, and the takedown route for infringing material.
Warranties, liability and indemnity
Disclaimers that survive local consumer law, and caps that are actually enforceable rather than theatrically broad.
Governing law, jurisdiction and disputes
The law that applies, the courts that hear it, and any pre-litigation steps you require.

Publishing the document on BigCommerce

Add each document as a web page and link it in the footer
BigCommerce also has a dedicated privacy policy setting that surfaces the link at checkout.
Audit Script Manager and categorise every entry
It is the authoritative list of what runs on the storefront.
Produce per-storefront variants where markets differ
One backend does not mean one legal position.
For headless builds, implement consent in the front end
And confirm nothing non-essential loads before it.
Document the B2B account model
Who can see what, and what happens when a named buyer leaves the company.

Where this usually goes wrong

One policy across every storefront

Different markets have different consent, cancellation and disclosure rules. A single policy is wrong somewhere.

Headless builds with no consent enforcement

The platform banner does not reach a front end it does not control.

Uncategorised scripts in Script Manager

Anything not assigned a consent category loads regardless of the banner.

B2B data treated as out of scope

A named buyer at a company is still a person with rights.

Tax and shipping services undisclosed

Automated tax calculation and rate shopping transmit address data on every quote.

Frequently asked questions

Does BigCommerce provide a privacy policy?

No. It provides hosting, a privacy policy setting that surfaces your link at checkout, a data processing addendum for its own role, and consent tooling. The content is yours.

How do I handle multiple storefronts in different countries?

Produce a variant per market rather than one document that hedges. Consent rules, cancellation rights and disclosure duties genuinely differ, and a single hedged policy is inaccurate in most of them.

What changes with a headless storefront?

Everything on the front end becomes yours: the tags, the banner, and the enforcement. Platform-level consent tooling does not reach a front end it does not render.

Are terms and conditions legally binding?

They are when the user had a genuine opportunity to read them and took a positive step to accept. Clickwrap - a ticked box next to a visible link - holds up far more reliably than a "by using this site you agree" line in the footer.

What is the difference between terms of service and terms and conditions?

Nothing substantive. "Terms and conditions" is the more common phrasing in the UK and Commonwealth markets, "terms of service" in the US and in SaaS. The clauses do the same job.

Can I limit my liability to zero?

No. Most consumer regimes void attempts to exclude liability for death, personal injury or fraud, and unfair-terms rules strike out caps a court considers unreasonable. A cap that is drafted to survive review is worth more than one that is struck out entirely.

Do I need terms if I sell nothing?

If users can register, post, comment or upload, yes - the terms are what let you moderate, suspend and remove content without being in breach of contract yourself.