DEAR Inventory to Shipwire integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between DEAR Inventory and Shipwire: authenticate both systems, choose the objects to sync (such as DEAR Inventory's Products and Purchase orders), map fields visually, and changes propagate both ways in milliseconds — no code required.

On the Shipwire side: Returns, Purchase Orders, Trackings, Rates, plus custom fields where Shipwire exposes them. On the DEAR Inventory side: Stock levels, Sale orders, Purchase orders, Customers. 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 DEAR Inventory 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.

DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. 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: Stock and Rates are effectively read-only (inventory levels and quote estimates); Orders, Products, Receivings, Returns, and Purchase Orders support create and update. DEAR Inventory: Authentication uses a two-part credential, an account ID and an application key, passed as headers on every request. Stacksync's field mapping accounts for these differences between DEAR Inventory and Shipwire without custom code.