Skip to content
Database ⇄ E-commerce

Dynamo DB to Shipwire integration — real-time, two-way sync

Keep Dynamo DB 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 Dynamo DB and Shipwire

Give your engineers Shipwire's products, orders, and customers in Dynamo DB: 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 Dynamo DB 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 Dynamo DB, 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 Stream item changes from DynamoDB application tables into a Postgres or warehouse copy for SQL analytics.
  • 02 Sync customer records between DynamoDB-backed services and a CRM so support and sales see live application state.
  • 03 Two-way sync Orders between a storefront or ERP database and Shipwire so new orders create fulfillment requests and Stacksync writes Trackings and status (processed, submitted, delivered) back.
  • 04 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.

Common sync patterns

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.

React to store changes

Updates in Shipwire arrive as row changes in Dynamo DB, so jobs and triggers can respond the moment an order, price, or stock level changes.

Keep catalog and inventory current

Prices, stock levels, or product details maintained in Dynamo DB sync back onto Shipwire, so the storefront shows what your systems treat as true.

What you can sync between Dynamo DB 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.

Dynamo DB objects Shipwire objects How this pairing syncs
Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. Attributes is specific to Dynamo DB and Returns to Shipwire — each maps to any object or custom field on the other side.
Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. Partition and Sort Keys is specific to Dynamo DB and Purchase Orders to Shipwire — each maps to any object or custom field on the other side.
Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. Global Secondary Indexes is specific to Dynamo DB and Trackings to Shipwire — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records consumed for incremental sync. 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. DynamoDB Streams is specific to Dynamo DB and Rates to Shipwire — each maps to any object or custom field on the other side.
Global Tables Multi-region replicas relevant when syncs must read from a specific region. 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. Global Tables is specific to Dynamo DB and Orders to Shipwire — each maps to any object or custom field on the other side.
Tables The top-level containers a sync targets; each table is addressed independently. 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. Tables is specific to Dynamo DB and Products to Shipwire — each maps to any object or custom field on the other side.

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

Dynamo DB Shipwire Sub-second propagation

DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.

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

Shipwire Dynamo DB 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 Dynamo DB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
  • 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 Dynamo DB ⇄ Shipwire

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Dynamo DB and Shipwire connectors work

Dynamo DB

Integration surface
Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
Authentication
AWS IAM credentials with SigV4 request signing
Change detection
Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
Capabilities
read · write · CDC
Rate limits
Throughput is governed by the table's provisioned or on-demand capacity mode

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 Dynamo DB 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 Dynamo DB 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
    Dynamo DB connected
    Shipwire connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamo DB 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 · Dynamo DB ⇄ 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
    Dynamo DB Shipwire
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dynamo DB 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.

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 408 integrations available for Dynamo DB and Shipwire.

Popular · 7 of 408
Coworkers laughing in front of a laptop in a casual office setting

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