Two-way sync
Changes in Acumatica or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica 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.
Shipwire runs the storefront and takes the orders; Acumatica 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 Purchase Orders, Trackings, Rates, Orders in Shipwire with Purchase Orders, Stock Items, Shipments, Payments in Acumatica field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Acumatica, order and customer detail from Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
As orders are picked, shipped, or invoiced in Acumatica, tracking and status flow back to Shipwire so buyers see accurate updates.
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
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.
| Acumatica objects | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Payments is specific to Acumatica and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Journal Transactions GL entries replicated into reporting databases. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Journal Transactions is specific to Acumatica and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Projects Project cost and billing structures synced with delivery tools. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Projects is specific to Acumatica and Trackings to Shipwire — each maps to any object or custom field on the other side. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | 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. | Opportunities and Cases is specific to Acumatica and Rates to Shipwire — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | 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. | Customers is specific to Acumatica and Orders to Shipwire — each maps to any object or custom field on the other side. |
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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Shipwire through its API, with automatic retries and rate-limit backoff.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Shipwire connection.
Changes in Acumatica or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Shipwire data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Shipwire record.
Track your Acumatica ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Shipwire.
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.
Authenticate Acumatica 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.
Pick the Acumatica 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Acumatica and Shipwire: authenticate both systems, choose the objects to sync (such as Acumatica's Purchase Orders and Payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Acumatica and Shipwire: One product catalog; Fulfillment and shipment status close the loop; One customer master. Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. 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.
Shipwire: List endpoints and webhook payloads return at most 20 sub-items per resource by default (recommended page max ~200), so orders or receivings with many line items must be traversed via next links. Acumatica: Custom fields defined in the instance can be added to the API entity contract, so tenant customizations participate in syncs alongside standard fields. Stacksync's field mapping accounts for these differences between Acumatica and Shipwire without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Acumatica and Shipwire records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 474 integrations available for Acumatica and Shipwire.