BigCommerce Specialists

BigCommerce: SaaS with an open architecture

BigCommerce is a SaaS eCommerce platform: hosting, security, availability and platform updates are handled by the provider. What sets it apart from other SaaS platforms is its open approach: catalogue, customers, orders and prices are accessible via API, so the store integrates with the rest of your systems without relying only on third-party apps.

That allows two ways of building the store: with a theme inside the platform itself, or with a separate (headless) front end that consumes its APIs, when the shopping experience or performance justifies it.

BMITZ has been building eCommerce since 2004 and we work with BigCommerce alongside Magento, PrestaShop, Shopify Plus and VTEX. We propose it when it is the best option for your case, not by default.

When to choose BigCommerce (and when not to)

BigCommerce fits companies that want the advantages of SaaS, with no servers to maintain, but need deep integrations with ERP, PIM or CRM and the freedom to decouple the front end. It also suits manufacturers and distributors selling to businesses: its B2B layer adds features such as company accounts, customer-specific price lists and quotes, and it is worth checking which plans include it.

Before deciding, bear in mind that its ecosystem of apps and providers geared to the Spanish market is smaller than that of other platforms. That is why we check early on the local payment methods, carriers and invoicing requirements you need, and whether a custom connector is required.

If you need full control of code and server, Magento or PrestaShop are a better fit; if speed to market with a very wide app ecosystem comes first, Shopify Plus. We compare the options by total cost and by what your team will be able to maintain, and review the subscription plan that applies to your case.

How we run a BigCommerce project

Scope and architecture: we define catalogue, markets, payment and shipping methods, which systems connect, and whether the store will use a platform theme or a headless front end. That decision shapes cost and maintenance, so we make it with data before designing.

Development: a bespoke theme or a separate front end as agreed, with logic the platform doesn't cover out of the box built through its APIs, avoiding workarounds that break with the provider's updates.

Migration: if you are coming from another platform, we move products, customers and order history and prepare 301 redirects from the old URLs to keep your search rankings.

After launch we continue with support, a review of installed apps and new features.

Integrations with ERP, CRM, PIM and payments

We integrate BigCommerce with ERPs such as SAP, Microsoft Dynamics 365, Oracle NetSuite, Odoo, Holded, a3ERP or Sage; with CRMs such as Salesforce, HubSpot or Zoho CRM; and with PIMs such as Akeneo or Pimcore. We use an existing connector when it is reliable and build our own when there isn't one or it falls short.

For payments we work with Stripe, Adyen and PayPal; if you need Redsys or another local method, we check at the outset which integration option exists. For each connection we define which data flows, in which direction and how often, with retries and alerts so no order fails to reach the ERP.