Real-time
Two-way sync
Changes in Bigcommerce or Pigment instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ Accounting and finance
Bigcommerce to Pigment integration — real-time, two-way sync
Keep Bigcommerce and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bigcommerce and Pigment
Turn every Bigcommerce order into clean revenue: Pigment and Bigcommerce keep customers, orders, and payment status aligned in real time, in both directions.
Bigcommerce runs the storefront — the catalog, the orders, and the buyers placing them. Pigment records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.
Stacksync syncs Data imports, Users and permissions, Applications, Metrics in Pigment with Price Lists, Shipments, Products, Variants and SKUs in Bigcommerce field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Bigcommerce, its paid-or-overdue state from Pigment — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.
The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.
Common use cases
- 01 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 03 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
- 04 Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.
Common sync patterns
Refunds and credits reconcile
Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.
Where Bigcommerce originates orders: sales flow into the books
A new or updated order in Bigcommerce creates or updates the matching invoice or revenue record in Pigment, so billing and reporting start without re-entry.
Where Pigment is the money system of record: payment status on the order
Paid, overdue, and refunded state from Pigment lands on the order or account in Bigcommerce, so the store and support see what has actually been collected.
What you can sync between Bigcommerce and Pigment
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Bigcommerce objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Categories is specific to Bigcommerce and Dimension lists to Pigment — each maps to any object or custom field on the other side. | |
| Brands Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent. | Tables Row-based transactional data loaded into models from source systems | Brands is specific to Bigcommerce and Tables to Pigment — each maps to any object or custom field on the other side. | |
| Inventory Product- or variant-level stock, plus multi-location counts via the V3 Inventory API; written from a WMS to reflect on-hand quantities. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Inventory is specific to Bigcommerce and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Price Lists V3 price lists and records driving customer-group and B2B pricing; pushed from an ERP so tiered prices stay current. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Price Lists is specific to Bigcommerce and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. | Users and permissions Access controls governing which model areas a sync can touch | Shipments is specific to Bigcommerce and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Products Catalog V3 records with custom fields and images; mastered in a PIM or ERP and written to BigCommerce, or read out to a warehouse. | Applications Planning models organized by domain such as finance, sales, or workforce | Products is specific to Bigcommerce and Applications to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Pigment
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Bigcommerce Pigment Sub-second propagation
DetectionBigcommerce notifies Stacksync of record changes through webhook events. Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more).
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Bigcommerce Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Bigcommerce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bigcommerce: OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
- Pigment: Subject to the platform's API rate limits.
What ships with Bigcommerce ⇄ Pigment
Connect Bigcommerce and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Bigcommerce or Pigment record.
Observability
Monitoring
Track your Bigcommerce ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bigcommerce and Pigment.
How the Bigcommerce and Pigment connectors work
Bigcommerce
- Integration surface
- REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
- Authentication
- OAuth API account credentials — a store-generated client ID and permanent access token sent in the X-Auth-Token header, limited to the OAuth scopes granted when the account is created (e.g. store_v2_orders, store_v2_products)
- Change detection
- Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers
- Capabilities
- read · write · webhooks
- Rate limits
- OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Bigcommerce to Pigment — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Bigcommerce and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bigcommerce
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Bigcommerce ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bigcommerce PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Pigment: authenticate both systems, choose the objects to sync (such as Bigcommerce's Categories and Brands), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Bigcommerce: Inventory can be tracked at the product or variant level, and multi-location stock uses the separate V3 Inventory API, so writes must target the right model. Stacksync's field mapping accounts for these differences between Bigcommerce and Pigment without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Bigcommerce and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Bigcommerce and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Bigcommerce–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Bigcommerce: Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 369 integrations available for Bigcommerce and Pigment.
Popular · 7 of 369
-
Bigcommerce ⇄ Chargebee -
Bigcommerce ⇄ Hyperline -
Bigcommerce ⇄ QuickBooks -
Bigcommerce ⇄ Stripe -
Pigment ⇄ Shipwire -
Pigment ⇄ Shopware -
Pigment ⇄ Akeneo
No integrations match .
