Linnworks to Starburst Enterprise integration — real-time, two-way sync

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

On the Starburst Enterprise side: Columns, Catalogs, Schemas, Tables, plus custom fields where Starburst Enterprise exposes them. On the Linnworks side: Locations, Purchase Orders, Suppliers, Channel Listings. 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 Starburst Enterprise: Where Linnworks runs operations: order and supply analysis; Group reporting across systems; Write-back where Linnworks exposes writable fields. Operational records become queryable tables in Starburst Enterprise, joinable with sales and finance data.

Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.

Starburst Enterprise: The engine stores no data itself; reads and writes pass through to the underlying sources, and write support depends on each connector. 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 Starburst Enterprise without custom code.