Skip to content
ERP ⇄ Storage

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

Keep Linnworks and Sharepoint in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Linnworks and Sharepoint

Move the documents and data that Linnworks produces into Sharepoint as files, and let files stored in Sharepoint update the records they belong to in Linnworks, continuously and without exports or manual filing.

Linnworks runs the business on structured records: Open Orders, Processed Orders, Stock Items, Stock Levels. Sharepoint holds files and the metadata that describes them: Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Linnworks touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Sharepoint, from signed contracts to vendor bills to receipts, describe a transaction Linnworks needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.

Stacksync keeps Open Orders, Processed Orders, Stock Items, Stock Levels in Linnworks and Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages in Sharepoint in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Sharepoint already labeled and filed, and metadata captured against a stored file can create or update the matching record in Linnworks. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.

The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Linnworks and the file in Sharepoint never describe two different versions of the same document.

Common use cases

  • 01 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
  • 02 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
  • 03 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.
  • 04 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.

Common sync patterns

Audit-ready retention

Every transaction's supporting file lives in Sharepoint beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Linnworks.

Documents filed with their context

Files that Linnworks produces land in Sharepoint labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.

Metadata that files itself

Record fields from Linnworks, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Sharepoint, so storage stays organized without anyone tagging by hand.

What you can sync between Linnworks and Sharepoint

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Linnworks objects Sharepoint objects How this pairing syncs
Locations Warehouse and fulfillment location records scope stock data during mapping. Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. Locations is specific to Linnworks and Lists to Sharepoint — each maps to any object or custom field on the other side.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. Purchase Orders is specific to Linnworks and List items to Sharepoint — each maps to any object or custom field on the other side.
Suppliers Vendor records keep procurement data consistent across tools. Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. Suppliers is specific to Linnworks and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. Channel Listings is specific to Linnworks and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Returns & Refunds Post-sale records flow to finance and support systems. Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. Returns & Refunds is specific to Linnworks and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Shipping Services Carrier and service definitions support label and tracking data in order syncs. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Shipping Services is specific to Linnworks and Site pages to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Linnworks and Sharepoint

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Linnworks Sharepoint Interval-based propagation

DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.

DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.

Sharepoint Linnworks Sub-second propagation

DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.

DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Linnworks: Per-endpoint rate limits apply on the Linnworks API.
  • Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with Linnworks ⇄ Sharepoint

Connect Linnworks and Sharepoint for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Sharepoint connection.

Real-time

Two-way sync

Changes in Linnworks or Sharepoint instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Linnworks or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Linnworks or Sharepoint record.

Observability

Monitoring

Track your Linnworks ⇄ Sharepoint sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Linnworks and Sharepoint.

How the Linnworks and Sharepoint connectors work

Linnworks

Integration surface
REST API
Authentication
Application credentials and an install token exchanged for a session token
Change detection
Polling on order and stock endpoints
Capabilities
read · write
Rate limits
Per-endpoint rate limits apply on the Linnworks API

Sharepoint

Integration surface
Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
Change detection
Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
Capabilities
read · write · webhooks
Rate limits
SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works

How to connect Linnworks to Sharepoint — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Linnworks and Sharepoint with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Linnworks connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Linnworks and Sharepoint objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Linnworks ⇄ Sharepoint
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Linnworks Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Linnworks and Sharepoint integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 495 integrations available for Linnworks and Sharepoint.

Popular · 7 of 495
All Linnworks integrations All Sharepoint integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own