Two-way sync
Changes in Infor CRM or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Keep Infor CRM 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.
Infor CRM 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 Leads, Opportunities, Tickets, Activities in Infor CRM to Purchase Orders, Trackings, Rates, 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.
A customer created in Shipwire creates or updates the matching contact or account in Infor CRM, so first-time and repeat buyers land in the relationship system without a manual import.
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.
Lifecycle stage, tier, or account owner set in Infor CRM syncs onto the customer record in Shipwire, so the buying side can act on how the relationship is classified.
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.
| Infor CRM objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Activities Calls, meetings, and tasks synced for engagement reporting. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Activities is specific to Infor CRM and Trackings to Shipwire — each maps to any object or custom field on the other side. | |
| Campaigns Marketing containers linked to leads and opportunities. | 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. | Campaigns is specific to Infor CRM and Rates to Shipwire — each maps to any object or custom field on the other side. | |
| Custom entities Deployment-specific objects added through the customizable entity model. | 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. | Custom entities is specific to Infor CRM and Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Accounts Company records matched against ERP customer masters in syncs. | 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. | Accounts is specific to Infor CRM and Products to Shipwire — each maps to any object or custom field on the other side. | |
| Contacts Person records synced with marketing and support tools. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Contacts is specific to Infor CRM and Stock to Shipwire — each maps to any object or custom field on the other side. | |
| Leads Unqualified records synced in from marketing sources. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Leads is specific to Infor CRM and Receivings to Shipwire — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Infor CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified timestamps.
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
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 Infor CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor CRM–Shipwire connection.
Changes in Infor CRM or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor CRM or Shipwire data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Infor CRM or Shipwire record.
Track your Infor CRM ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor CRM and Shipwire.
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.
Authenticate Infor CRM 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.
Pick the Infor CRM 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Infor CRM and Shipwire: authenticate both systems, choose the objects to sync (such as Infor CRM's Activities and Campaigns), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Infor CRM side: Leads, Opportunities, Tickets, Activities, plus custom fields where Infor CRM 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 Infor CRM and Shipwire: New buyers become CRM records; Contact and address details stay consistent; Where Infor CRM segments customers: status travels to the store record. A customer created in Shipwire creates or updates the matching contact or account in Infor CRM, so first-time and repeat buyers land in the relationship system without a manual import.
Infor CRM: REST-style SData API over the CRM entity model. Authentication: User credentials; Infor OS-managed authentication in cloud deployments. 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.
Infor CRM: Infor CRM descends from SalesLogix and exposes the SData protocol, a REST-style API over its entity model. Shipwire: Authentication uses account-generated ShipwireKey tokens (max two per account) sent as `Authorization: ShipwireKey ...`, not OAuth or Basic auth; a separate sandbox runs at api.beta.shipwire.com. Stacksync's field mapping accounts for these differences between Infor CRM and Shipwire without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 480 integrations available for Infor CRM and Shipwire.