Real-time
Two-way sync
Changes in Kustomer or Shipwire instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ E-commerce
Kustomer to Shipwire integration — real-time, two-way sync
Keep Kustomer 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 Kustomer and Shipwire
Keep the customers and orders that Kustomer and Shipwire share aligned in real time, so sales works from live purchase history and the store works from current account details.
Kustomer holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Shipwire runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links Users, Teams, Tags, Notes in Kustomer to Stock, Receivings, Returns, Purchase Orders in Shipwire with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
Common use cases
- 01 Escalate conversation-derived signals into the CRM as tasks or opportunities
- 02 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 03 Pull Returns and tracking.delivered events into a support or analytics database for reverse-logistics and delivery-SLA reporting.
- 04 Two-way sync Orders between a storefront or ERP database and Shipwire so new orders create fulfillment requests and Stacksync writes Trackings and status (processed, submitted, delivered) back.
Common sync patterns
Where Shipwire records orders: purchase history on the account
Orders and their status from Shipwire appear on the matching contact or account in Kustomer, so reps see what a customer has bought and what is in flight before the next conversation.
New buyers become CRM records
A customer created in Shipwire creates or updates the matching contact or account in Kustomer, so first-time and repeat buyers land in the relationship system without a manual import.
Contact and address details stay consistent
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
What you can sync between Kustomer 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.
| Kustomer objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Customers is specific to Kustomer and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Conversations Support threads across channels sync outward for analytics and CRM context. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Conversations is specific to Kustomer and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Messages Individual messages within conversations support full-thread replication. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Messages is specific to Kustomer and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Companies Organization records group customers and map to CRM accounts. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Companies is specific to Kustomer and Trackings to Shipwire — each maps to any object or custom field on the other side. | |
| Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Rates Shipping cost quotes for a cart or order; read-only, called at checkout time to estimate carrier costs rather than synced as stored records. | Custom Objects (Klasses) is specific to Kustomer and Rates to Shipwire — each maps to any object or custom field on the other side. | |
| Users Agent records map conversation ownership to people in other systems. | Orders B2C fulfillment orders (create, update, cancel, get) with item, hold, routing, and tracking subresources; typically written from a storefront or ERP and synced back with status and trackings. | Users is specific to Kustomer and Orders to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Kustomer 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.
Kustomer Shipwire Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kustomer: Subject to the platform's API rate limits.
- 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 Kustomer ⇄ Shipwire
Connect Kustomer and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kustomer 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 Kustomer or Shipwire record.
Observability
Monitoring
Track your Kustomer ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kustomer and Shipwire.
How the Kustomer and Shipwire connectors work
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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 Kustomer 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 Kustomer 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.
Kustomer
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kustomer 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 · Kustomer ⇄ 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.
Kustomer ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kustomer and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kustomer and Shipwire: authenticate both systems, choose the objects to sync (such as Kustomer's Customers and Conversations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Kustomer side: Users, Teams, Tags, Notes, plus custom fields where Kustomer exposes them. On the Shipwire side: Stock, Receivings, Returns, Purchase 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 Kustomer and Shipwire: Where Shipwire records orders: purchase history on the account; New buyers become CRM records; Contact and address details stay consistent. Orders and their status from Shipwire appear on the matching contact or account in Kustomer, so reps see what a customer has bought and what is in flight before the next conversation.
-
Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Shipwire: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Shipwire: Webhook authenticity is verified via the X-Shipwire-Signature header (HMAC-SHA256 over the raw request body) with rotatable shared secrets. Stacksync's field mapping accounts for these differences between Kustomer and Shipwire without custom code.
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 376 integrations available for Kustomer and Shipwire.
Popular · 7 of 376
-
Kustomer ⇄ Shopware -
Kustomer ⇄ Akeneo -
Kustomer ⇄ Bigcommerce -
Shipwire ⇄ Intercom -
Shipwire ⇄ Kommo -
Shipwire ⇄ Nimble -
Shipwire ⇄ Nutshell
No integrations match .
