Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

BigCommerce will not let me change my checkout the way I need

Short answer

BigCommerce documents six ways to change checkout, from restyling its one-page checkout to building a custom one on its APIs. Its Checkout SDK cannot introduce new behaviour or create new shipping or payment methods. Which route you need depends on whether you want a new look or a new rule.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I want an extra step or field at checkout and I am told it cannot be done.
  • I want a different shipping or payment option shown for certain customers.
  • My agency changed the look of checkout but the behaviour is still the same.
  • A custom checkout works on the live store but not when my developer tests it locally.
  • I am told I must rebuild the whole store to change one thing in checkout.

Why does this happen?

  1. Restyling is not the same as new behaviour

    BigCommerce says you can modify the theme of its Optimized One-Page Checkout by overriding the style. That changes how checkout looks. For a custom checkout it points to other options.

  2. Open Checkout suits moderate changes

    BigCommerce describes Open Checkout as the open-source option of its one-page checkout, a foundation for added features or moderate-sized changes, running on the BigCommerce storefront.

  3. The Checkout SDK cannot add new rules

    BigCommerce says the Checkout JS SDK supports significant front-end customisation, but it does not let you introduce new behaviour, and you cannot create new shipping or payment methods with it, only filter existing shipping methods.

  4. Local testing has a documented gap

    BigCommerce says hosted payment forms do not work with Stencil on localhost, because the forms are served over https and Stencil only supports http, and suggests testing the order confirmation flow with offline payment methods.

  5. A fully custom checkout moves the work to you

    BigCommerce documents GraphQL and REST Storefront APIs and a REST Management API checkout feature for custom checkouts. The management route works outside a storefront session and handles payment through its Payments API, but it does not currently support store credit or gift certificates as payment methods.

What can I do about it today?

  1. Describe the change as a customer sees itWrite one sentence such as: a business customer should see a purchase-order field. A clear sentence tells a developer which route applies.
  2. Say whether it is a look or a ruleColours, wording and layout are styling. Who sees which shipping or payment option, or a new calculation, is behaviour.
  3. Ask for the document behind a noIf someone says it cannot be done, ask which BigCommerce page or error says so. A limit written in the docs and a limit of one theme are different things.
  4. Do not rebuild checkout yetA custom checkout takes over payment, shipping and error handling. Try the smaller routes first.
  5. Keep a record of what is already changedAsk for the list of checkout edits already on the store, so a new change does not undo an old one.

When should I bring someone in?

  • The change you need touches payment or shipping rules, not just appearance.
  • Checkout edits keep breaking after theme updates.
  • You are weighing a fully custom checkout and need to know what you would then own.

How do I handle it?

  1. Classify the requestI sort each wish into styling, a front-end change or a new rule, and match it to the BigCommerce route that documents it.
  2. Prefer the smallest routeIf restyling or Open Checkout covers it, that is the plan. A custom checkout is proposed only when nothing smaller can.
  3. Keep rules outside checkout where possibleLogic about pricing or eligibility can sit in a small separate service that the store calls, instead of in checkout code.
  4. Test the payment path honestlyBecause of the localhost limit, I test confirmation with offline methods first and then with real payment settings on a staging copy.
  5. Write down what you own afterwardsIf checkout is custom, you get a list of what now needs maintaining and who does it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I add a new payment method with the Checkout SDK?

BigCommerce says no: you cannot create new shipping or payment methods with the SDK, although you can filter existing shipping methods.

Can I build checkout outside my storefront?

BigCommerce documents APIs for that, including a management API route that works outside a storefront session. It also notes limits, for example no store credit or gift certificates as payment methods on that route.

Is a limited checkout a reason to leave BigCommerce?

Not by itself. First check whether the thing you need is a documented limit or a choice made in your theme or setup. My page on outgrowing BigCommerce covers that wider question.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.