Real-time
Two-way sync
Changes in Salesforce or Shipwire instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ E-commerce
Salesforce to Shipwire integration — real-time, two-way sync
Keep Salesforce 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 Salesforce and Shipwire
Keep the customers and orders that Salesforce and Shipwire share aligned in real time, so sales works from live purchase history and the store works from current account details.
Salesforce 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 Cases, Campaigns, Tasks and Events, Products and Price Books in Salesforce to Returns, Purchase Orders, Trackings, Rates 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 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 02 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
- 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
One customer identity across sales and store
A person who exists as a contact in Salesforce and a buyer in Shipwire is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.
Where Shipwire records orders: purchase history on the account
Orders and their status from Shipwire appear on the matching contact or account in Salesforce, 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 Salesforce, so first-time and repeat buyers land in the relationship system without a manual import.
What you can sync between Salesforce 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.
| Salesforce objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Accounts is specific to Salesforce and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Contacts is specific to Salesforce and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Leads is specific to Salesforce and Trackings to Shipwire — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | 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. | Opportunities is specific to Salesforce and Rates to Shipwire — each maps to any object or custom field on the other side. | |
| Cases Support records; synced with help desk tools or internal databases for escalation workflows. | 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. | Cases is specific to Salesforce and Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | 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. | Campaigns is specific to Salesforce and Products to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Salesforce 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.
Salesforce Shipwire Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Salesforce: Daily API request allocations vary by edition and license count.
- 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 Salesforce ⇄ Shipwire
Connect Salesforce and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Salesforce 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 Salesforce or Shipwire record.
Observability
Monitoring
Track your Salesforce ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Salesforce and Shipwire.
How the Salesforce and Shipwire connectors work
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
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 Salesforce 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 Salesforce 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.
Salesforce
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Salesforce 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 · Salesforce ⇄ 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.
Salesforce ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Salesforce and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Salesforce and Shipwire: authenticate both systems, choose the objects to sync (such as Salesforce's Accounts and Contacts), 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 Salesforce and Shipwire connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Salesforce–Shipwire integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Salesforce and Shipwire. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). 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 Salesforce side: Cases, Campaigns, Tasks and Events, Products and Price Books, plus custom fields where Salesforce exposes them. On the Shipwire side: Returns, Purchase Orders, Trackings, Rates. 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 495 integrations available for Salesforce and Shipwire.
Popular · 7 of 495
-
Salesforce ⇄ Bigcommerce -
Salesforce ⇄ Channelengine -
Salesforce ⇄ Easypost -
Salesforce ⇄ Magento -
Shipwire ⇄ Close -
Shipwire ⇄ Copper CRM -
Shipwire ⇄ Creatio CRM
No integrations match .
