Real-time
Two-way sync
Changes in Reltio or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ E-commerce
Reltio to Shipwire integration — real-time, two-way sync
Keep Reltio and Shipwire 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 Reltio and Shipwire
Give your engineers Shipwire'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 Purchase Orders, Trackings, Rates, Orders from Shipwire into Reltio and keeps both sides consistent in real time. Whatever Shipwire 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 Shipwire 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 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
- 02 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 03 Sync Receivings (advance ship notices) and reconcile them against Purchase Orders so inbound supplier shipments are visible as they land.
- 04 Pull Returns and tracking.delivered events into a support or analytics database for reverse-logistics and delivery-SLA reporting.
Common sync patterns
React to store changes
Updates in Shipwire arrive as row changes in Reltio, so jobs and triggers can respond the moment an order, price, or stock level changes.
Keep catalog and inventory current
Prices, stock levels, or product details maintained in Reltio sync back onto Shipwire, so the storefront shows what your systems treat as true.
Order data where your code can use it
Orders and their status become rows in Reltio for routing, fulfillment, and reporting, without polling the platform.
What you can sync between Reltio and Shipwire
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.
| Reltio objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Products Catalog SKUs including kits, virtual kits, and marketplace products; created and edited via API, commonly mastered in a PIM or ERP and pushed into Shipwire with dimensions and pricing. | Interactions is specific to Reltio and Products to Shipwire — each maps to any object or custom field on the other side. | |
| 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. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Matches (Potential Matches) is specific to Reltio and Stock to Shipwire — each maps to any object or custom field on the other side. | |
| Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Activity Log is specific to Reltio and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Data Change Requests (DCR) is specific to Reltio and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Reference Data (RDM) is specific to Reltio and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. | |
| 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. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Entities is specific to Reltio and Trackings to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Reltio and Shipwire
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.
Reltio Shipwire 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 Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Reltio Sub-second propagation
DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Reltio ⇄ Shipwire
Connect Reltio and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Reltio or Shipwire 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 Reltio or Shipwire record.
Observability
Monitoring
Track your Reltio ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Reltio and Shipwire.
How the Reltio and Shipwire connectors work
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.
Shipwire
- Integration surface
- REST API (v3)
- Authentication
- Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
- Change detection
- Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
- Capabilities
- read · write · webhooks
- Rate limits
- No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works
How to connect Reltio to Shipwire — 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 Reltio and Shipwire with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Reltio
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Reltio and Shipwire 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 · Reltio ⇄ ShipwireCustomers 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.
Reltio ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Reltio and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Reltio and Shipwire: authenticate both systems, choose the objects to sync (such as Reltio's Interactions and Matches (Potential Matches)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Reltio and Shipwire. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Shipwire: Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM), plus custom fields where Reltio exposes them. On the Shipwire side: Purchase Orders, Trackings, Rates, 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.
-
Common patterns for Reltio and Shipwire: React to store changes; Keep catalog and inventory current; Order data where your code can use it. Updates in Shipwire arrive as row changes in Reltio, so jobs and triggers can respond the moment an order, price, or stock level changes.
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 Reltio and Shipwire.
Popular · 6 of 389
-
Reltio ⇄ Easypost -
Reltio ⇄ Magento -
Shipwire ⇄ SAP ASE (Sybase) -
Shipwire ⇄ Scaleway Postgres -
Shipwire ⇄ TiDB -
Shipwire ⇄ TimescaleDB
No integrations match .
