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

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

On the Rillet side: Custom Field, Account, Customer, Vendor, plus custom fields where Rillet exposes them. On the Linnworks side: Suppliers, Channel Listings, Returns & Refunds, Shipping Services. 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 Linnworks and Rillet: Subsidiary to headquarters; Where Rillet handles billing: invoices land in Linnworks; Migration without a hard cutover. Where Rillet serves a business unit and Linnworks is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.

Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Linnworks: Orders are modeled in two populations, open orders and processed orders, and syncs typically treat processing as the state transition that moves a record between them. Stacksync's field mapping accounts for these differences between Linnworks and Rillet without custom code.