Kustomer to Linnworks integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Kustomer and Linnworks: authenticate both systems, choose the objects to sync (such as Kustomer's Custom Objects (Klasses) and Users), 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 Kustomer and Linnworks: Where Linnworks is the finance system of record: money status on the account; One customer master; Where Linnworks manages people and org data: keep Kustomer aligned. Invoice and payment state from Linnworks shows on the account in Kustomer, so reps see balances before promising the next order.

Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.

Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Stacksync's field mapping accounts for these differences between Kustomer and Linnworks 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 Kustomer and Linnworks records are not retained after a sync operation.