Real-time
Two-way sync
Changes in Rillet or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ E-commerce
Rillet to Shipwire integration — real-time, two-way sync
Keep Rillet 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 Rillet and Shipwire
Turn every Shipwire order into clean revenue: Rillet and Shipwire keep customers, orders, and payment status aligned in real time, in both directions.
Shipwire runs the storefront — the catalog, the orders, and the buyers placing them. Rillet records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.
Stacksync syncs Charge, Reimbursement, Custom Field, Account in Rillet with Products, Stock, Receivings, Returns in Shipwire field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shipwire, its paid-or-overdue state from Rillet — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.
The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.
Common use cases
- 01 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- 02 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- 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
Refunds and credits reconcile
Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.
Where Shipwire originates orders: sales flow into the books
A new or updated order in Shipwire creates or updates the matching invoice or revenue record in Rillet, so billing and reporting start without re-entry.
Where Rillet is the money system of record: payment status on the order
Paid, overdue, and refunded state from Rillet lands on the order or account in Shipwire, so the store and support see what has actually been collected.
What you can sync between Rillet 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.
| Rillet objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Customer Synced with incremental and full sync per the Stacksync docs. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Customer is specific to Rillet and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Vendor Synced with incremental and full sync per the Stacksync docs. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Vendor is specific to Rillet and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Invoice Synced with incremental and full sync per the Stacksync docs. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Invoice is specific to Rillet and Trackings to Shipwire — each maps to any object or custom field on the other side. | |
| Credit Memo Synced with incremental and full sync per the Stacksync docs. | 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. | Credit Memo is specific to Rillet and Rates to Shipwire — each maps to any object or custom field on the other side. | |
| Bill Synced with incremental and full sync per the Stacksync docs. | 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. | Bill is specific to Rillet and Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | 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. | Journal Entry is specific to Rillet and Products to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Rillet 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.
Rillet Shipwire Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Rillet 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 Rillet through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Rillet: Subject to the platform's 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 Rillet ⇄ Shipwire
Connect Rillet and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rillet 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 Rillet or Shipwire record.
Observability
Monitoring
Track your Rillet ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rillet and Shipwire.
How the Rillet and Shipwire connectors work
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Subject to the platform's 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 Rillet 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 Rillet 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.
Rillet
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rillet 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 · Rillet ⇄ 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.
Rillet ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rillet and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and Shipwire: authenticate both systems, choose the objects to sync (such as Rillet's Customer and Vendor), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). 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 Rillet side: Charge, Reimbursement, Custom Field, Account, plus custom fields where Rillet exposes them. On the Shipwire side: Products, Stock, Receivings, Returns. 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 Rillet and Shipwire: Refunds and credits reconcile; Where Shipwire originates orders: sales flow into the books; Where Rillet is the money system of record: payment status on the order. Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.
-
Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. 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 385 integrations available for Rillet and Shipwire.
Popular · 7 of 385
-
Rillet ⇄ Easypost -
Rillet ⇄ Magento -
Rillet ⇄ Shopware -
Shipwire ⇄ Chargebee -
Shipwire ⇄ Hyperline -
Shipwire ⇄ Pigment -
Shipwire ⇄ QuickBooks
No integrations match .
