Skip to content
ERP ⇄ E-commerce

Microsoft Dynamics GP to Shipwire integration — real-time, two-way sync

Keep Microsoft Dynamics GP 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 Microsoft Dynamics GP and Shipwire

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

Shipwire runs the storefront and takes the orders; Microsoft Dynamics GP 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 Returns, Purchase Orders, Trackings, Rates in Shipwire with Company Databases, Customers, Vendors, Sales Documents (SOP) in Microsoft Dynamics GP field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Microsoft Dynamics GP, order and customer detail from Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 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.
  • 02 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
  • 03 Replicate GP company databases into a warehouse for financial and operational reporting.
  • 04 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.

Common sync patterns

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Microsoft Dynamics GP, tracking and status flow back to Shipwire so buyers see accurate updates.

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Microsoft Dynamics GP is the inventory system of record: stock stays accurate

Available quantities from Microsoft Dynamics GP publish to Shipwire, so the store shows what can actually ship and stops overselling.

What you can sync between Microsoft Dynamics GP 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.

Microsoft Dynamics GP objects Shipwire objects How this pairing syncs
GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Trackings to Shipwire — each maps to any object or custom field on the other side.
Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. 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. Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Rates to Shipwire — each maps to any object or custom field on the other side.
Company Databases Per-company SQL databases that define the scope of any sync. 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. Company Databases is specific to Microsoft Dynamics GP and Orders to Shipwire — each maps to any object or custom field on the other side.
Customers Receivables master records (RM tables) synced with CRMs and billing tools. 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. Customers is specific to Microsoft Dynamics GP and Products to Shipwire — each maps to any object or custom field on the other side.
Vendors Payables master records aligned with procurement and AP automation. Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. Vendors is specific to Microsoft Dynamics GP and Stock to Shipwire — each maps to any object or custom field on the other side.
Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. Sales Documents (SOP) is specific to Microsoft Dynamics GP and Receivings to Shipwire — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics GP 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.

Microsoft Dynamics GP Shipwire Sub-second propagation

DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.

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

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

Rate-limit considerations

  • 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 Microsoft Dynamics GP ⇄ Shipwire

Connect Microsoft Dynamics GP and Shipwire for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Shipwire.

How the Microsoft Dynamics GP and Shipwire connectors work

Microsoft Dynamics GP

Integration surface
SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
Authentication
SQL Server credentials or Windows authentication
Change detection
SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
Capabilities
read · write · CDC

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

    Choose tables

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

Microsoft Dynamics GP 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 463 integrations available for Microsoft Dynamics GP and Shipwire.

Popular · 7 of 463
All Microsoft Dynamics GP 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