Real-time
Two-way sync
Changes in Epicor ERP or Shipwire instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ E-commerce
Epicor ERP to Shipwire integration — real-time, two-way sync
Keep Epicor ERP 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 Epicor ERP and Shipwire
Keep the storefront in step with the back office: Shipwire and Epicor ERP share products, inventory, and orders in real time, in both directions.
Shipwire runs the storefront and takes the orders; Epicor ERP owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Receivings, Returns, Purchase Orders, Trackings in Shipwire with Customers, Suppliers, Parts, Sales orders in Epicor ERP field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Epicor ERP, order and customer detail from Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
- 02 Read Stock levels per warehouse into an operational database or storefront so availability and backorder state reflect real inventory.
- 03 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
- 04 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.
Common sync patterns
Where Epicor ERP is the inventory system of record: stock stays accurate
Available quantities from Epicor ERP publish to Shipwire, so the store shows what can actually ship and stops overselling.
New orders reach the back office
An order captured in Shipwire creates the matching record in Epicor ERP with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
One product catalog
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
What you can sync between Epicor ERP 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.
| Epicor ERP objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Purchase orders Synced with procurement systems and matched against receipts. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Suppliers Vendor masters kept aligned with procurement and AP automation tools. | 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. | Suppliers is specific to Epicor ERP and Products to Shipwire — each maps to any object or custom field on the other side. | |
| Parts Item masters that anchor inventory, BOM, and order line syncs. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Parts is specific to Epicor ERP and Stock to Shipwire — each maps to any object or custom field on the other side. | |
| Sales orders Created from won CRM opportunities; status and line changes sync back out. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Sales orders is specific to Epicor ERP and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Jobs is specific to Epicor ERP and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Quotes Estimates that pair with CRM opportunities during the sales cycle. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Quotes is specific to Epicor ERP and Trackings to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Epicor ERP 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.
Epicor ERP Shipwire Interval-based propagation
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Epicor ERP 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 Epicor ERP through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
- 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 Epicor ERP ⇄ Shipwire
Connect Epicor ERP and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Epicor ERP 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 Epicor ERP or Shipwire record.
Observability
Monitoring
Track your Epicor ERP ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Epicor ERP and Shipwire.
How the Epicor ERP and Shipwire connectors work
Epicor ERP
- Integration surface
- REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
- Authentication
- API key combined with basic or token authentication, depending on version and deployment
- Change detection
- Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
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 Epicor ERP 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 Epicor ERP 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.
Epicor ERP
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Epicor ERP 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 · Epicor ERP ⇄ 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.
Epicor ERP ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Epicor ERP and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Epicor ERP and Shipwire: authenticate both systems, choose the objects to sync (such as Epicor ERP's Purchase orders and Suppliers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. 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 Shipwire side: Receivings, Returns, Purchase Orders, Trackings, plus custom fields where Shipwire exposes them. On the Epicor ERP side: Customers, Suppliers, Parts, Sales 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 Epicor ERP and Shipwire: Where Epicor ERP is the inventory system of record: stock stays accurate; New orders reach the back office; One product catalog. Available quantities from Epicor ERP publish to Shipwire, so the store shows what can actually ship and stops overselling.
-
Epicor ERP: REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints. Authentication: API key combined with basic or token authentication, depending on version and deployment. 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.
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 468 integrations available for Epicor ERP and Shipwire.
Popular · 7 of 468
-
Epicor ERP ⇄ Shopware -
Epicor ERP ⇄ Akeneo -
Epicor ERP ⇄ Bigcommerce -
Epicor ERP ⇄ Channelengine -
Shipwire ⇄ Syspro -
Shipwire ⇄ TikTok Shop -
Shipwire ⇄ Unleashed Software
No integrations match .
