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

Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and MongoDB: 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.

Change detection on Linnworks: Polling on order and stock endpoints. On MongoDB: MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the MongoDB side: GridFS files, Databases, Collections, Documents, plus custom fields where MongoDB exposes them. On the Linnworks side: Shipping Services, Open Orders, Processed Orders, Stock Items. 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 MongoDB: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from MongoDB back into Linnworks, keeping the ERP authoritative.

Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. MongoDB: MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management. Authentication: Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required. Stacksync manages authentication, retries, and rate limits on both sides.