.png)
BigCommerce Enterprise Integration Guide
BigCommerce Enterprise integrates with enterprise systems through REST APIs, Storefront GraphQL, selected webhooks, and resource-specific batch and media operations.
BigCommerce Enterprise integration options at a glance
BigCommerce Enterprise provides REST APIs for catalog administration, Products, Customers, Orders, Carts, checkout, promotions, channels, shipping, and related operations. Its Storefront GraphQL API supports headless and customer-facing experiences, while webhooks provide notifications for selected events such as order, product, customer, and cart activity. Resource-specific batch operations and product image APIs support larger catalog processes and media synchronization. Martini can consume these APIs, receive webhook notifications through an exposed endpoint, orchestrate scheduled reconciliation, map and transform data, and apply validation, retry, checkpointing, and idempotency controls. Credentials and webhook verification values can be managed as environment-specific secrets.
| Integration point | Supported by BigCommerce Enterprise? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Management and operational integrations for Products, Categories, Customers, Orders, Carts, checkout, promotions, channels, shipping, and related resources. | Martini can consume BigCommerce REST endpoints from workflows, paginate collections, transform payloads, and expose reusable APIs around the resulting processes. |
| Storefront GraphQL API | Yes | Headless storefront queries and mutations, product discovery, categories, carts, checkout-related experiences, and customer-facing applications. | Martini can consume the Storefront GraphQL API, manage storefront authentication, transform responses, and combine BigCommerce data with other enterprise services. |
| Webhooks and outbound callbacks | Limited | Selected order, product, customer, cart, and other documented store events. Coverage is event-specific and does not include every object or field change. | Martini can expose an endpoint or webhook workflow, validate inbound requests, deduplicate notifications, retrieve authoritative resources, and route processing asynchronously. |
| Bulk and batch APIs | Limited | Batch-style processing for selected resources, particularly catalog operations and larger product synchronizations. | Martini can combine supported batch operations with controlled concurrency, pagination, checkpoints, throttling, and retry handling. |
| Product images and catalog media | Limited | Synchronize product images and related catalog media through resource-specific REST operations. | Martini can retrieve or submit image-related data as part of catalog workflows, subject to the applicable endpoint requirements and limitations. |
| Authentication | Yes | Server-to-server access tokens, OAuth applications with scoped permissions, and separate storefront access tokens for Storefront GraphQL. | Martini can store BigCommerce tokens, client secrets, store identifiers, and webhook verification values in environment-specific secrets and apply them to API workflows. |
| Database access | Not confirmed | Direct SQL access to the hosted BigCommerce commerce database was not confirmed and should not be assumed. | Martini can integrate through documented APIs, webhooks, and supported exports or reporting interfaces rather than direct database connectivity. |
How BigCommerce Enterprise exposes data and business events
BigCommerce REST APIs
BigCommerce REST APIs are the principal mechanism for administrative and back-office integrations. They cover catalog, customers, orders, carts, checkout, promotions, channels, shipping, and related store operations.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the appropriate REST resource, retrieves or writes paginated data, maps the response to a canonical model, applies validation and business rules, and records checkpoints and correlation identifiers.
Implementation sequence
BigCommerce Storefront GraphQL
The Storefront GraphQL API supports storefront-facing and headless commerce experiences, including product discovery, categories, carts, and checkout-related interactions. It is not a complete replacement for management REST APIs.
Martini implementation pattern
Martini implementation pattern: a Martini API or workflow sends controlled GraphQL queries or mutations using a storefront token, combines results with enterprise services where needed, and returns a stable application-specific response.
Implementation sequence
BigCommerce Webhooks
BigCommerce supports webhook notifications for selected documented events, including certain order, product, customer, and cart activities. Coverage is event-specific, so reconciliation remains important.
Martini implementation pattern
Martini implementation pattern: an exposed Martini endpoint receives and validates the notification, acknowledges it promptly, deduplicates the event, retrieves the authoritative BigCommerce resource, and starts downstream processing through a workflow.
Implementation sequence
Catalog batch operations
BigCommerce provides batch-style operations for selected resources, particularly catalog operations. Batch support is endpoint-specific and should not be assumed across all REST resources.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow partitions a catalog workload, invokes supported batch endpoints, controls concurrency, persists progress, and retries only failed partitions or requests.
Implementation sequence
Product images and catalog media
Product image and related catalog media operations are available through resource-specific BigCommerce REST APIs. This is not a general-purpose attachment service for every object.
Martini implementation pattern
Martini implementation pattern: a workflow obtains image metadata or source URLs, validates resource requirements, maps media to the relevant Product or variant, and records failures separately from core catalog data.
Implementation sequence
Common BigCommerce Enterprise integration patterns
Pattern 1: Synchronize products and inventory with an ERP
When to use this pattern
Use this pattern when an ERP or product system owns catalog, pricing, or inventory information that must be reflected in BigCommerce. The reverse direction can be used when BigCommerce is the merchandising source.
Integration direction
Example Mapping
| BigCommerce Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| external_product_id | product.externalId | Product.id or custom identifier |
| item_name | product.name | Product.name |
| available_quantity | inventory.available | Product inventory value |
| category_code | product.categoryId | Category assignment |
Martini implementation pattern
A scheduled Martini workflow retrieves source data, normalizes Products, variants, categories, prices, and inventory, applies currency and identifier rules, and performs idempotent BigCommerce upserts. Pagination, supported batch operations, checkpoints, throttling, and retryable error paths make large catalog runs restartable.
Martini capabilities used
- scheduled workflows
- REST API consumption
- data mapping
- business rules
- validation
- checkpointing
- error handling
Pattern 2: Process orders and fulfillment updates
When to use this pattern
Use this pattern to move BigCommerce Orders into an ERP, warehouse, tax, payment, or fulfillment platform and return shipment or fulfillment information to BigCommerce.
Integration direction
Example Mapping
| BigCommerce Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| order_id | order.externalId | Sales order external ID |
| billing_address | order.billingAddress | Billing address |
| products[].quantity | order.lines[].quantity | Order line quantity |
| status | order.lifecycleStatus | Order or fulfillment status |
Martini implementation pattern
Martini receives a supported order event or polls for changes, retrieves the complete Order, validates payment and address requirements, maps line items and status values, and submits the result downstream. Fulfillment responses are correlated to the original order and sent back to BigCommerce with duplicate protection and retry handling.
Martini capabilities used
- webhook consumption
- REST API consumption
- workflow orchestration
- data mapping
- validation
- idempotency
- retry handling
Pattern 3: Synchronize customers with a CRM
When to use this pattern
Use this pattern when BigCommerce customer profiles and commerce activity must be available in a CRM, or when selected CRM account changes should update BigCommerce customer information.
Integration direction
Example Mapping
| BigCommerce Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| id | customer.externalId | Contact external ID |
| customer.email | Contact email | |
| first_name | customer.firstName | Contact first name |
| last_name | customer.lastName | Contact last name |
Martini implementation pattern
A Martini workflow combines selected BigCommerce customer events with scheduled reconciliation, chooses an email or external identifier according to the integration policy, maps consent and profile fields, and upserts the CRM profile. Guest shoppers, duplicates, and conflicting ownership are routed through explicit business rules.
Martini capabilities used
- event-driven workflows
- scheduled synchronization
- data mapping
- business rules
- duplicate detection
- error handling
Pattern 4: Expose a headless storefront API façade
When to use this pattern
Use this pattern when a web or mobile storefront needs BigCommerce Storefront GraphQL data combined with pricing, inventory, loyalty, personalization, or other enterprise services.
Integration direction
Example Mapping
| BigCommerce Enterprise Field | Canonical Field | Target Field |
|---|---|---|
| query.productId | storefront.productIdentifier | GraphQL product identifier |
| cart.items | cart.lines | BigCommerce cart line items |
| customer.token | shopper.session | Storefront authentication context |
Martini implementation pattern
Martini exposes a controlled API that validates the client request, calls Storefront GraphQL with a separate storefront token, invokes additional enterprise services, applies response and error rules, and returns a stable contract. This isolates BigCommerce credentials and platform-specific query details from the frontend.
Martini capabilities used
- API exposure
- GraphQL API consumption
- workflow orchestration
- data transformation
- business rules
- security configuration
- error handling
Applications commonly integrated with BigCommerce Enterprise
BigCommerce Enterprise can be integrated with adjacent enterprise applications for commerce operations, customer engagement, fulfillment, tax, and platform migration. Martini can coordinate these flows through documented BigCommerce APIs, selected webhooks, scheduled workflows, and reusable mappings without requiring a dedicated BigCommerce connector.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize BigCommerce Customers, Orders, and commerce activity with customer, sales, and service processes. | BigCommerce Enterprise → Martini → Salesforce | Receive selected BigCommerce events or run reconciliation workflows, retrieve authoritative Customers and Orders through REST APIs, map identities and commerce activity, and upsert Salesforce records with duplicate detection and retry handling. |
| NetSuite | Exchange Products, Customers, Orders, inventory, invoices, and fulfillment information between ecommerce and ERP operations. | BigCommerce Enterprise → Martini → NetSuite | Use scheduled and event-driven workflows to retrieve or receive BigCommerce data, normalize catalog and order structures, apply ownership and status rules, and exchange records with NetSuite using reusable mappings and checkpoints. |
| SAP S/4HANA | Coordinate enterprise product, inventory, pricing, customer, order, and fulfillment processes with the commerce storefront. | BigCommerce Enterprise → Martini → SAP S/4HANA | Poll or process BigCommerce webhooks, transform Products, Customers, and Orders into SAP-specific structures, apply validation and business rules, and manage retries for downstream availability or rate-limit failures. |
| Microsoft Dynamics 365 | Synchronize ecommerce orders and customers with finance, supply chain, sales, and fulfillment operations. | BigCommerce Enterprise → Martini → Microsoft Dynamics 365 | Orchestrate bidirectional API workflows, use external identifiers for correlation, transform order and fulfillment states, and isolate transient failures through retryable workflow paths. |
| ShipStation | Send BigCommerce Orders for fulfillment and return shipment, tracking, and status information to the commerce platform. | BigCommerce Enterprise → Martini → ShipStation | Receive or poll Orders, retrieve complete order details, map shipping and line-item data to ShipStation, then process shipment and tracking updates back to BigCommerce with idempotent status handling. |
| Avalara | Exchange order or transaction data for tax calculation and return tax results to checkout or order-processing flows. | BigCommerce Enterprise → Martini → Avalara | Expose a controlled Martini API or invoke Avalara from a workflow, transform BigCommerce cart or order data, validate tax responses, and return consistent results while recording failures for review. |
| Klaviyo | Synchronize Customers, products, order events, and behavioral activity for segmentation and marketing automation. | BigCommerce Enterprise → Martini → Klaviyo | Consume supported BigCommerce events or scheduled extracts, normalize customer consent and commerce events, and submit mapped payloads to Klaviyo with duplicate-event controls. |
| Adobe Commerce | Support commerce migration, coexistence, marketplace consolidation, or phased platform transition. | BigCommerce Enterprise → Martini → Adobe Commerce | Build controlled migration workflows for Products, Categories, Customers, and Orders, preserve cross-platform identifiers, transform platform-specific catalog models, and checkpoint large transfers for restartability. |
How to build a BigCommerce Enterprise integration in Martini
Objective
Establish environment-specific access to BigCommerce REST or Storefront GraphQL APIs and configure webhook verification material without embedding credentials in workflows.
Instructions in Martini
- Choose REST, Storefront GraphQL, webhook, or a combined integration approach
- Store access tokens, OAuth secrets, store identifiers, and storefront credentials as Martini secrets
- Use least-privilege permissions and separate development, test, and production values
- Configure the target system credentials and correlation identifiers
Objective
Select an event-driven, scheduled, API-led, or batch trigger based on the BigCommerce resource and the completeness of webhook coverage.
Instructions in Martini
- Use a Martini API or webhook workflow for supported BigCommerce events
- Use a scheduler for reconciliation and resources without suitable notifications
- Use bounded batch processing for large catalog workloads
- Define the synchronization watermark and restart behavior
Objective
Obtain authoritative BigCommerce data rather than relying on incomplete event payloads or a single unpaginated response.
Instructions in Martini
- Validate webhook authenticity and event structure
- Retrieve the referenced Product, Customer, Order, Cart, or Channel through the appropriate API
- Iterate through REST pagination
- Persist checkpoints and correlation identifiers
Objective
Coordinate BigCommerce calls, downstream applications, transformations, and business decisions in a maintainable Martini workflow.
Instructions in Martini
- Separate notification receipt from longer-running processing when appropriate
- Route catalog, customer, order, and fulfillment flows according to ownership rules
- Control concurrency and honor rate-limit responses
- Use reusable workflow logic for common authentication and error paths
Objective
Convert BigCommerce structures into canonical and target-system models while handling catalog and order complexity explicitly.
Instructions in Martini
- Map Products, variants, Categories, Customers, Orders, Carts, and Channels to the target schema
- Validate required fields, identifiers, addresses, statuses, and consent values
- Apply currency, category, tax, fulfillment, and channel rules
- Preserve safe unknown fields where the target model permits it
Objective
Perform idempotent downstream and reverse-direction writes with clear ownership for each business state.
Instructions in Martini
- Use upsert or duplicate-detection behavior where available
- Correlate external identifiers across systems
- Update BigCommerce fulfillment or catalog resources only when the integration owns those states
- Record successful writes and resource identifiers
Common BigCommerce Enterprise data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Products | Synchronize sellable catalog items, pricing, variants, custom fields, images, and inventory-related attributes. | ERP, PIM, warehouse, tax, commerce, and marketing platforms | Martini retrieves or receives product-related changes, maps variants and catalog structures, applies validation and identifier rules, and supports paginated or batch processing. |
| Categories | Maintain catalog taxonomy and organize Products across storefront and channel experiences. | ERP, PIM, Adobe Commerce, and analytics platforms | Martini maps source taxonomy identifiers and hierarchies, applies ordering and ownership rules, and synchronizes changes through REST workflows. |
| Customers | Represent shopper profiles and customer account information for commerce, CRM, and marketing processes. | Salesforce, NetSuite, Microsoft Dynamics 365, and Klaviyo | Martini correlates customer identifiers, maps consent and profile fields, handles guest-customer rules, and prevents duplicate upserts. |
| Orders | Carry purchases, billing, shipping, line items, payment-related information, and fulfillment context. | ERP, warehouse, tax, fulfillment, payment, and CRM platforms | Martini validates webhook or polling inputs, retrieves complete authoritative Orders, transforms line items and statuses, and records idempotent processing outcomes. |
| Carts | Represent active shopping carts and their line items for storefront and checkout orchestration. | Headless storefronts, pricing, tax, loyalty, and personalization services | Martini can consume REST or Storefront GraphQL data, apply business rules, and expose an application-specific API façade when multiple services are involved. |
| Channels | Represent storefronts, marketplaces, and other sales-channel destinations associated with a store. | ERP, PIM, marketplace, catalog, and reporting platforms | Martini maps channel identifiers and assignments, applies channel-specific routing rules, and includes channel context in catalog synchronization workflows. |
Authentication and security considerations
Credentials and permissions
BigCommerce REST integrations can use access tokens or OAuth applications with store-specific permissions. Storefront GraphQL uses separate storefront authentication mechanisms. Use least-privilege access and keep management API credentials separate from storefront credentials.
Secrets and webhook protection
Store access tokens, client secrets, storefront tokens, store identifiers, and webhook verification material should be stored as environment-specific Martini secrets. Validate the authenticity and structure of inbound webhook requests before starting business processing.
Data protection
- Separate development, test, and production credentials.
- Do not write authorization headers, tokens, payment information, or unnecessary customer data to logs.
- Restrict exposed Martini APIs and protect them with appropriate authentication and authorization.
Operational considerations for BigCommerce Enterprise integrations
Rate limits and pagination
BigCommerce quotas and rate limits can vary by store, plan, API, and request type. Workflows should inspect response behavior, limit concurrency, use pagination, and apply exponential backoff. Large catalog jobs should use supported batch operations where appropriate.
Events and reconciliation
Webhooks cover selected events rather than every object or field change. Validate and deduplicate notifications, retrieve the authoritative resource, and retain scheduled reconciliation for missed, delayed, or unsupported changes.
Idempotency and state
Use durable keys based on event and resource identifiers, upsert behavior, synchronization watermarks, and checkpoints. Define ownership for order status, payment state, shipment information, catalog data, and customer identity.
Schema and testing
Use documented API versions and fields, test representative Products, variants, Customers, Orders, and media, and monitor deprecation notices. Treat catalog complexity, channel assignments, price lists, and order-state transitions as explicit mapping concerns.
Why use Martini instead of scripts or point-to-point integrations?
One orchestration layer
Martini coordinates BigCommerce APIs, webhooks, enterprise applications, and scheduled reconciliation in workflows rather than scattering logic across independent scripts or point-to-point calls.
Reusable integration logic
Mappings, validation, authentication configuration, business rules, checkpoints, idempotency, and retry paths can be reused across catalog, customer, order, and fulfillment processes.
Controlled APIs and operations
Martini can expose a controlled API façade over Storefront GraphQL or REST-backed workflows, while providing centralized error handling, monitoring, environment-specific secrets, and deployment practices for maintainable enterprise integrations.
Frequently asked questions
BigCommerce Enterprise can be integrated through its REST APIs for management and operational data, its Storefront GraphQL API for headless storefront experiences, and webhooks for selected events. Scheduled REST synchronization, resource-specific batch operations, and product media APIs can support reconciliation, large catalog processing, and asset exchange.
Yes. Martini can consume BigCommerce REST APIs and the Storefront GraphQL API, receive supported BigCommerce webhook events, expose APIs for storefront or enterprise use cases, and orchestrate mapping, validation, synchronization, retry, and reconciliation workflows.
No. A dedicated BigCommerce connector is not required. Martini can use BigCommerce's documented REST APIs, Storefront GraphQL API, authentication methods, and supported webhook events through API and workflow capabilities.
Lonti does not charge an additional per-connector or per-vendor fee to integrate BigCommerce Enterprise. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from BigCommerce, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use the REST APIs for Products, Customers, Orders, catalog administration, and most back-office operations. Use Storefront GraphQL for customer-facing and headless commerce experiences. Use webhooks for supported event types, supplemented by scheduled REST reconciliation where coverage is incomplete.
Yes. BigCommerce supports webhook notifications for selected documented events, and Martini can expose an endpoint or workflow to receive them. Coverage is not universal, so workflows should validate notifications, retrieve authoritative resources, deduplicate deliveries, and reconcile through scheduled API calls.
Martini retrieves or receives BigCommerce Products, Categories, Customers, Orders, Carts, or Channels, maps them to a canonical or target model, and applies validation and business rules before writing downstream. Pagination, checkpoints, external identifiers, and idempotent upserts support reliable recurring synchronization.
Martini workflows can inspect API responses, apply backoff for rate-limit responses, retry transient failures, and route persistent errors for review. Webhook and retry duplicates should be controlled with durable idempotency keys based on event, resource, type, and version or timestamp. Martini can also expose an API façade over Storefront GraphQL when a controlled enterprise contract is required.
Related Martini documentation
Operations
Build your BigCommerce Enterprise integration with Martini
Use Martini to connect BigCommerce Enterprise APIs, webhooks, storefront experiences, and enterprise applications through maintainable workflows, reusable mappings, secure configuration, and reliable operational controls.