Real-time
Two-way sync
Changes in Bigcommerce or Reltio instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ Database
Bigcommerce to Reltio integration — real-time, two-way sync
Keep Bigcommerce and Reltio 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 Reltio
Give your engineers Bigcommerce's products, orders, and customers in Reltio: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.
E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.
Stacksync mirrors Shipments, Products, Variants and SKUs, Orders from Bigcommerce into Reltio and keeps both sides consistent in real time. Whatever Bigcommerce holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in Reltio, such as new prices, stock levels, or fulfillment status, sync back into Bigcommerce with its validations respected.
Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.
Common use cases
- 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
- 03 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.
- 04 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
Common sync patterns
Controlled write-back
Choose exactly which tables and fields may flow from Reltio back into Bigcommerce, keeping the store authoritative on what it owns.
Read the store's data with a query
Records from Bigcommerce, whether products, orders, customers, or inventory, live in Reltio as ordinary tables or collections, joinable with the rest of your data.
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Bigcommerce API, rate limits, and retries.
What you can sync between Bigcommerce and Reltio
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Shipments is specific to Bigcommerce and Matches (Potential Matches) to Reltio — 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. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Products is specific to Bigcommerce and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Variants and SKUs Per-variant pricing and inventory; synced to keep stock and SKU data aligned with an ERP or WMS at the option level. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Variants and SKUs is specific to Bigcommerce and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Orders V2 Orders API header, line items, and shipping/billing addresses; read into an ERP or accounting system, with status written back. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Orders is specific to Bigcommerce and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Customers is specific to Bigcommerce and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Categories is specific to Bigcommerce and Relations to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Reltio
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 Reltio 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 Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Bigcommerce Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
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.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Bigcommerce ⇄ Reltio
Connect Bigcommerce and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Reltio 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 Reltio record.
Observability
Monitoring
Track your Bigcommerce ⇄ Reltio 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 Reltio.
How the Bigcommerce and Reltio 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.
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Bigcommerce to Reltio — 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 Reltio 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
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Reltio 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 ⇄ ReltioCustomers 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 ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Reltio: authenticate both systems, choose the objects to sync (such as Bigcommerce's Shipments and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Bigcommerce and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Bigcommerce–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce and Reltio. 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 Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Data Change Requests (DCR), Reference Data (RDM), Entities, Relations, plus custom fields where Reltio exposes them. On the Bigcommerce side: Shipments, Products, Variants and SKUs, Orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 389 integrations available for Bigcommerce and Reltio.
Popular · 7 of 389
-
Bigcommerce ⇄ MySQL -
Bigcommerce ⇄ MariaDB -
Bigcommerce ⇄ SQL Server -
Bigcommerce ⇄ Postgres Heroku -
Reltio ⇄ Easypost -
Reltio ⇄ Magento -
Reltio ⇄ Shipwire
No integrations match .
