Skip to content
Database ⇄ E-commerce

InterSystems IRIS to Shipwire integration — real-time, two-way sync

Keep InterSystems IRIS 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 InterSystems IRIS and Shipwire

Give your engineers Shipwire's products, orders, and customers in InterSystems IRIS: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.

E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.

Stacksync mirrors Rates, Orders, Products, Stock from Shipwire into InterSystems IRIS and keeps both sides consistent in real time. Whatever Shipwire holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in InterSystems IRIS, such as new prices, stock levels, or fulfillment status, sync back into Shipwire with its validations respected.

Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.

Common use cases

  • 01 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
  • 02 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 03 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
  • 04 Read Stock levels per warehouse into an operational database or storefront so availability and backorder state reflect real inventory.

Common sync patterns

Controlled write-back

Choose exactly which tables and fields may flow from InterSystems IRIS back into Shipwire, keeping the store authoritative on what it owns.

Read the store's data with a query

Records from Shipwire, whether products, orders, customers, or inventory, live in InterSystems IRIS as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Shipwire API, rate limits, and retries.

What you can sync between InterSystems IRIS 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.

InterSystems IRIS objects Shipwire objects How this pairing syncs
Views SQL views expose curated slices of data for outbound replication. 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. Views is specific to InterSystems IRIS and Products to Shipwire — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. Schemas is specific to InterSystems IRIS and Stock to Shipwire — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. Persistent Classes is specific to InterSystems IRIS and Receivings to Shipwire — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. Globals is specific to InterSystems IRIS and Returns to Shipwire — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. Namespaces is specific to InterSystems IRIS and Purchase Orders to Shipwire — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. Stored Procedures is specific to InterSystems IRIS and Trackings to Shipwire — each maps to any object or custom field on the other side.

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

InterSystems IRIS Shipwire Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

Shipwire InterSystems IRIS 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 applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published 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 InterSystems IRIS ⇄ Shipwire

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Shipwire connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published 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 InterSystems IRIS 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 InterSystems IRIS 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
    InterSystems IRIS connected
    Shipwire connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS 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 · InterSystems IRIS ⇄ 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
    InterSystems IRIS Shipwire
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS 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 425 integrations available for InterSystems IRIS and Shipwire.

Popular · 7 of 425
All InterSystems IRIS 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