By platform

Refund Policy Generator for BigCommerce

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

Generate your refund policy Read the refund policy guide

Multi-market selling makes the refund policy the hardest document to get right on BigCommerce, because the statutory position differs per storefront and a policy written for one market misstates the law in the others.

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 refund policy for a BigCommerce store has to cover

Statutory rights per market, stated separately rather than merged
Business versus consumer returns, which are governed differently
The return process, window and condition requirements
Who bears return shipping and any restocking fee
Refund timing consistent with the gateway on each storefront

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 refund policy contains

The statutory right, stated separately
Consumer cancellation rights exist whatever your policy says, so they are set out first and your goodwill terms second.
Time limits and how they are counted
When the clock starts, whether it runs in calendar or working days, and what stops it.
Condition and evidence requirements
What state goods must come back in, and what proof of purchase you accept.
Who pays return postage
Split between faulty and change-of-mind returns, because the law treats them differently.
Refund method and timing
Original payment method, and the deadline you commit to once goods or notice are received.
Exclusions, stated lawfully
Perishables, personalised goods, unsealed hygiene items and downloaded digital content - the exclusions the law actually permits.

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.

Can I run a no-refunds policy?

Not against statutory rights. In the UK and EU a consumer’s cancellation and faulty-goods rights apply regardless of what your policy says, and advertising "no refunds" is itself treated as a misleading practice.

Do digital products have to be refundable?

The cancellation right can be waived for digital content, but only if the customer gave express consent to immediate delivery and acknowledged losing the right. That acknowledgement has to be captured at checkout, not assumed.

How long do I have to issue a refund?

In the UK and EU, within 14 days of receiving the goods back or of the customer proving they returned them. Card scheme rules and marketplace policies often impose something tighter.