Skip to content
ERP ⇄ E-commerce

Cin7 to Shipwire integration — real-time, two-way sync

Keep Cin7 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 Cin7 and Shipwire

Keep the storefront in step with the back office: Shipwire and Cin7 share products, inventory, and orders in real time, in both directions.

Shipwire runs the storefront and takes the orders; Cin7 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 Trackings, Rates, Orders, Products in Shipwire with Inventory levels, Sales orders, Purchase orders, Contacts in Cin7 field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Cin7, order and customer detail from Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Read Stock levels per warehouse into an operational database or storefront so availability and backorder state reflect real inventory.
  • 02 Sync Receivings (advance ship notices) and reconcile them against Purchase Orders so inbound supplier shipments are visible as they land.
  • 03 Write purchase orders created in a planning tool back into Cin7 for receiving.
  • 04 Consolidate stock movements from multiple branches into one reporting database.

Common sync patterns

Where Cin7 is the inventory system of record: stock stays accurate

Available quantities from Cin7 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 Cin7 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 Cin7 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.

Cin7 objects Shipwire objects How this pairing syncs
Products SKU records with options and pricing, synced with storefront and marketplace catalogs. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Purchase orders Supplier orders synced with procurement and accounting workflows. 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.
Stock adjustments and transfers Inventory movements read for audit and reconciliation 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. Stock adjustments and transfers is specific to Cin7 and Receivings to Shipwire — each maps to any object or custom field on the other side.
Credit notes / returns Return documents synced so finance and support see the same refund state. Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. Credit notes / returns is specific to Cin7 and Returns to Shipwire — each maps to any object or custom field on the other side.
Inventory levels Stock on hand by branch or location, published outward for availability. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. Inventory levels is specific to Cin7 and Trackings to Shipwire — each maps to any object or custom field on the other side.
Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. 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. Sales orders is specific to Cin7 and Rates to Shipwire — each maps to any object or custom field on the other side.

How changes propagate between Cin7 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.

Cin7 Shipwire Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.

Shipwire Cin7 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 Cin7 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
  • 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 Cin7 ⇄ Shipwire

Connect Cin7 and Shipwire for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Shipwire connection.

Real-time

Two-way sync

Changes in Cin7 or Shipwire instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Cin7 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 Cin7 or Shipwire record.

Observability

Monitoring

Track your Cin7 ⇄ Shipwire sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Cin7 and Shipwire.

How the Cin7 and Shipwire connectors work

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core

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 Cin7 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.

  1. 01

    Connect your apps

    Authenticate Cin7 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Cin7 connected
    Shipwire connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Cin7 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Cin7 ⇄ Shipwire
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Cin7 Shipwire
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Cin7 and Shipwire integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 458 integrations available for Cin7 and Shipwire.

Popular · 8 of 458
All Cin7 integrations All Shipwire integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own