Skip to content
Accounting and finance ⇄ E-commerce

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

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

Turn every Shipwire order into clean revenue: Pigment 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. Pigment 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 Applications, Metrics, Dimension lists, Tables in Pigment with Trackings, Rates, Orders, Products 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 Pigment — 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 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 03 Read Stock levels per warehouse into an operational database or storefront so availability and backorder state reflect real inventory.
  • 04 Sync Receivings (advance ship notices) and reconcile them against Purchase Orders so inbound supplier shipments are visible as they land.

Common sync patterns

Catalog and pricing stay aligned

Products, SKUs, and prices maintained on one side propagate to the other, so what the store sells and what the ledger books stay in step.

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 Pigment, so billing and reporting start without re-entry.

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

Pigment objects Shipwire objects How this pairing syncs
Metrics Multidimensional values holding plans and actuals; the main target for inbound data 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. Metrics is specific to Pigment and Orders to Shipwire — each maps to any object or custom field on the other side.
Dimension lists Master data like accounts, products, or employees that metrics are sliced by 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. Dimension lists is specific to Pigment and Products to Shipwire — each maps to any object or custom field on the other side.
Tables Row-based transactional data loaded into models from source systems Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. Tables is specific to Pigment and Stock to Shipwire — each maps to any object or custom field on the other side.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. Scenarios is specific to Pigment and Receivings to Shipwire — each maps to any object or custom field on the other side.
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. Data imports is specific to Pigment and Returns to Shipwire — each maps to any object or custom field on the other side.
Users and permissions Access controls governing which model areas a sync can touch Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. Users and permissions is specific to Pigment and Purchase Orders to Shipwire — each maps to any object or custom field on the other side.

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

Pigment Shipwire Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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

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

Rate-limit considerations

  • Pigment: 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 Pigment ⇄ Shipwire

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Pigment and Shipwire connectors work

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
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 Pigment 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 Pigment 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
    Pigment connected
    Shipwire connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Pigment 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 369 integrations available for Pigment and Shipwire.

Popular · 7 of 369
All Pigment 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