How to Build a Mobile App for BigCommerce

Compare the ways to build a BigCommerce shopping app for iOS and Android, and learn how to test checkout, accounts and pricing before you commit.

A navy clay storefront building beside a mint smartphone showing a shopping bag icon.

Key Takeaways

  • The official BigCommerce app is for running your store. A branded app your customers shop in has to come from a builder, a managed service or a custom build.
  • An app builder recreates your store from BigCommerce’s APIs, while an app built on your existing storefront reuses what already runs there. A custom headless app gives you full control, but it takes the most engineering work.
  • Your checkout, customer logins, price lists and B2B workflows decide which route fits, far more than your catalog does.
  • Ask every vendor to run your hardest shopping journey on your own store, on iPhone and Android, before you sign anything.

Your BigCommerce store already handles the hard parts of selling online. It holds your catalog, prices products for each customer group, takes payments and sends orders to fulfillment.

A mobile app should add to that. It gives your best customers an icon on their home screen, a login that stays signed in and push notifications that bring them back.

But an app that can’t show a wholesale buyer their own prices, or that sends shoppers to a checkout that loses their cart, does more harm than good.

This guide explains the ways to build a BigCommerce mobile app, what each one reuses from your store and what it rebuilds. It also covers what your app has to carry over, how checkout works in each route, and what to test before the app goes into the App Store and Google Play.

What’s the Best Way to Build a BigCommerce Mobile App?

The best way to build a BigCommerce mobile app is the route that keeps your store’s critical workflows intact on both iOS and Android and leaves your team an amount of upkeep it can manage. For most stores, that means choosing between three routes, plus an agency if you go custom.

BigCommerce doesn’t build customer apps itself. Its own app on Google Play is for merchants: it “lets you create and manage orders, update your catalog, view customer details and access key performance metrics.” Your customers need a separate app with your brand on it.

Route What it reuses from your store What gets built for the app Who maintains it
App builder connected to BigCommerce Catalog, customer and order data through the API A new mobile storefront, plus support for your apps and custom logic The vendor maintains the platform; your team manages the app’s content
Native app built on your existing storefront Your theme, installed apps, checkout and pricing rules Native navigation, push notifications, login and app-only screens The vendor handles the native side; your team keeps running the store
Custom app on BigCommerce’s APIs BigCommerce’s commerce engine and data The whole app, including login, cart and checkout Your developers or agency

The first and third routes rebuild your storefront for mobile, while the second keeps the storefront you already run and builds the app around it.

Use a Builder That Connects to BigCommerce

An API-based app builder connects to your BigCommerce store, pulls in your products, customers and orders, and shows them in a mobile interface it designs and runs. You manage the app’s layout and campaigns through the vendor, and your catalog stays in BigCommerce.

JMango360 is one example. According to its setup guide, the app “fetches data directly from the BigCommerce backend and interacts with BigCommerce via the API.”

JMango360’s BigCommerce App Marketplace listing describes custom native iOS and Android development and “Deep BigCommerce API & Multi-Storefront Integration.” It also describes the work as a managed service, with custom pricing.

The setup guide also shows where this route takes extra work. JMango360 configures a web checkout “either as the default checkout or a fallback from a native checkout,” and installs a script in your BigCommerce backend to support it.

If you use customer groups, it asks for “information about the user group logic and access to each user group” so it can test them.

Integration depth is the main thing to check with any API-based builder. Your products will almost certainly come through. Your customer-group pricing, your installed apps and any custom code in your theme may not, unless the builder has integrated them.

BigCommerce’s App Marketplace has a Mobile category where you can find other options, and our guide to choosing an ecommerce mobile app builder explains how to compare them.

Build a Native App on Your Existing Storefront

A second route builds the app on the BigCommerce storefront you already run. The app is native, with its own navigation, push notifications and login, but its shopping screens come from your live store, so your theme, apps and checkout come with it.

MobiLoud works this way. Its team designs and builds a custom iOS and Android app on your existing BigCommerce store, then maintains it. According to its BigCommerce page, customers “check out through your existing BigCommerce checkout,” and price lists, customer groups and B2B Edition workflows apply in the app as they’re configured on the store.

MobiLoud’s team handles submission under your own Apple and Google accounts, plus the native updates that come with new iOS and Android releases.

This route is a strong fit when your store relies on things an API-based app would have to rebuild, such as a heavily customized Stencil theme, checkout customizations or a stack of marketplace apps. Changes your team makes on the store reach the app too, so there’s no second storefront to merchandise.

There are trade-offs. The app depends on your mobile site, so slow or awkward mobile pages need fixing first. MobiLoud is a monthly subscription with no revenue share, and its pricing page puts multi-store and multi-country setups on its Enterprise plan. Promoting the app is still your team’s job.

Build a Custom App With BigCommerce APIs

A custom app is a headless build. Your developers create the mobile interface, and BigCommerce stays in the background as the commerce engine. BigCommerce’s headless documentation puts it simply: “With headless commerce, the storefront can be a CMS or an app.” BigCommerce still stores customer data, serves the catalog and processes payments.

The GraphQL Storefront API covers much of what a shopping app needs. It can query the catalog, return a signed-in customer’s details and “Create new carts, fetch existing carts, and initiate checkout.” But your developers still have to build a lot around it:

  • A sales channel. BigCommerce says you “need to create and configure a sales channel” before a headless storefront can show products.
  • Login. Signing customers in across the app and checkout usually means the Customer Login API, which uses JSON Web Tokens for single sign-on.
  • Payments. “For PCI compliance-related reasons, the GraphQL Storefront API does not handle payments,” according to BigCommerce’s end-to-end guide. A fully custom checkout uses the Payments API instead.
  • Your installed apps. Anything that runs on your current storefront, from reviews to loyalty, needs its own integration in the app.

There are smaller gaps too. BigCommerce notes that GraphQL “currently does not support sorting products based on pricing defined in Price Lists,” which matters if your wholesale buyers sort by their own prices.

Custom development is ideal for brands whose app needs genuinely go beyond what the other routes can deliver, and who have a mobile team to run it. Our guide to custom ecommerce mobile app development covers what that commitment looks like.

When Should You Hire a BigCommerce Agency?

You should hire a BigCommerce agency when you choose the custom route and don’t have mobile developers in-house, or when a builder needs integration work it won’t do itself. An agency can build the app, connect it to your store and other systems, and maintain it after launch.

BigCommerce’s agency directory lets you filter partners by services, including “Mobile App Development.” Use it to build a shortlist, then ask each agency three things:

  • A shopping app it has launched and still maintains, ideally on BigCommerce.
  • Who owns the source code, the developer accounts and the app listings.
  • What its maintenance retainer covers, from iOS and Android updates to API changes.

An agency that can answer all three clearly is one you can hold to a plan. One that can only show web projects is a risk for a mobile build.

What Does Your BigCommerce App Need to Carry Over?

Your BigCommerce app needs to carry over every workflow that customers rely on to buy from you, not just your product catalog. Write those workflows down before you talk to vendors, because they become both your brief and the demo script each vendor has to follow.

Start with the journeys that bring in the most revenue or the most repeat orders, and list what each one depends on:

  • Products: variants, options, bundles and anything a custom field controls.
  • Pricing: price lists, customer-group discounts, coupons and promotions.
  • Accounts: sign-in, saved addresses, order history and wishlists.
  • Checkout: your payment methods, shipping rules, tax and any checkout customizations.
  • Loyalty and reviews: the apps that show points, reviews and recommendations.
  • Orders: tracking, returns and reordering.

Two BigCommerce setups need extra attention. With Multi-Storefront, one backend can run storefronts with a different “language, currency, and domain.” Decide whether you want one app that switches between them or a separate app for each, and check the vendor’s plan covers it.

B2B Edition adds “Account pricing, buyer portals, quote workflows, and approval controls,” along with shared lists and reordering. If you sell wholesale, those workflows are the reason buyers would open your app, so the app has to support them.

Say you sell to both retail and trade customers. A good acceptance test is a trade buyer who opens the app, signs in, sees their account pricing on a product page and reorders last month’s order from a shared list. If any step fails, or shows retail prices, that route doesn’t work for your store yet.

Can You Keep Your BigCommerce Checkout?

You can keep your BigCommerce checkout in a mobile app, but how much of it you keep depends on the route. Checkout is where most of your store’s rules come together, so it’s the part to test hardest.

There are three broad approaches:

Approach How it works What to watch
Reuse your storefront checkout The app shows the same checkout your website uses Your mobile checkout pages need to be fast and easy to use
Hand off to BigCommerce’s hosted checkout The app builds the cart, then sends the shopper to checkout The cart, login and discounts have to survive the handoff
Build a custom checkout Your developers rebuild checkout in the app Payments, tax and shipping all need their own integration

BigCommerce supports the second approach directly. Its docs explain that you can use a cart’s “checkout_url URL to redirect the customer to the BigCommerce hosted checkout page,” or embed that hosted checkout in an iframe.

The third approach uses the Storefront Checkout API and the Payments API, which gives you complete control but the most to build and maintain.

Whichever approach a vendor uses, walk through these on a real device:

  • Does a signed-in customer stay signed in at checkout?
  • Do coupons, gift certificates and customer-group prices still apply?
  • Do shipping options and tax match what the website shows?
  • What happens when a payment fails, and can the shopper try again?
  • Does the shopper land back in the app after paying, with the order confirmation?

If a checkout passes all five, your customers won’t notice where the app ends and BigCommerce’s checkout begins. If it fails one, they’ll notice it at the worst possible moment.

Testing Your BigCommerce App Before Launch

Before you submit your BigCommerce app to the App Store and Google Play, run a complete real order on both platforms. Use a real product, a real customer account and a real payment method, then refund it.

Then test the moments that go wrong in practice:

  • A declined or abandoned payment, followed by a retry.
  • A push notification that opens a specific product or order.
  • An out-of-stock product, an expired coupon and a slow connection.
  • Signing out, resetting a password and signing back in.
  • Each storefront, currency or customer group your app has to support.

Check the accounts and ownership too. The app should publish under your own Apple and Google developer accounts, so the listings and the install base stay yours.

Agree who handles updates when iOS, Android or BigCommerce change, and who fixes the app when something on your store breaks it. Our ecommerce app launch checklist and guide to submitting an app to the app stores go through these steps in detail.

Plan the launch as well. Your existing customers are the first people likely to install, so use your email list, your website and your order confirmations to tell them. Our guide to promoting an ecommerce mobile app covers that in more depth.

Final Thoughts

No single route is right for every BigCommerce store.

An API-based builder can work well for a store that runs close to BigCommerce’s defaults. An app built on your existing storefront suits a store that depends on its theme, apps, checkout and pricing rules. A custom headless app suits a brand with a clear product reason to go further and a team to run it.

The deciding factor is how each route handles your own store. So write down the journeys your customers depend on, ask each vendor to run them on your store, and test checkout until you’re sure it holds.

Then choose the route that passes, with the upkeep your team can actually take on.

BigCommerce Mobile App FAQs

What Is the Official BigCommerce App For?

The official BigCommerce app is for merchants running their store from a phone. It lets you manage orders, update your catalog, view customer details and check store performance. It isn’t an app your customers download to shop, so a branded shopping app has to come from a builder, a managed service or a custom build.

Will My BigCommerce Apps Work in My Mobile App?

Your BigCommerce marketplace apps will work in a mobile app only if the route you choose supports them. An app built on your existing storefront can keep apps that run on that storefront, such as reviews or loyalty widgets, while an API-based or custom app needs a separate integration for each one.

Either way, list the apps your customers actually see and test each one in the finished app.

Can One App Serve Multiple BigCommerce Storefronts?

One app can serve multiple BigCommerce storefronts, but it depends on the vendor and the plan. Some apps let shoppers switch between storefronts, while others use a separate app for each region or brand. Confirm how the app handles each storefront’s catalog, currency, language and checkout, and whether a multi-store setup costs more.

Do You Need a Developer to Build a BigCommerce App?

You don’t need your own developer to build a BigCommerce app if you use an app builder or a managed service, because the vendor does the technical work. You’ll still need someone to set up your Apple and Google developer accounts, supply your brand assets and test the app.

A custom headless app is different: it needs mobile developers, either in-house or from an agency, for the build and every update after it.