Skip to content
ERP ⇄ Analytics

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

Keep Linnworks and Pendo 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 Pendo

Put Linnworks's records into Pendo as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Pendo computes back where Linnworks can use them.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Linnworks carries financials, operations, workforce data, or all three, those numbers belong in Pendo, next to the product, behavioral, and web data the team already measures.

Stacksync syncs Purchase Orders, Suppliers, Channel Listings, Returns & Refunds from Linnworks into Pendo continuously, handling API limits and schema drift as it goes, so each record type arrives as Visitors, Accounts, Feature Events, Page Events ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Pendo can be written back to fields in Linnworks where that is useful.

Common use cases

  • 01 Pull NPS scores and poll responses into a database so voice-of-customer sits next to revenue, renewal, and churn signals for analysis.
  • 02 Push warehouse-computed Account attributes (plan, ARR, renewal date, health score, CSM owner) onto Pendo Accounts via the Metadata API so segments and guide targeting stay current.
  • 03 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
  • 04 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels

Common sync patterns

Where Linnworks runs operations: inventory and fulfillment metrics

Operational records from Linnworks become measurable in Pendo, joinable with the rest of what the company tracks for supply and fulfillment reporting.

Where Linnworks is the HR system of record: workforce and cost analysis

Worker and organization data from Linnworks syncs into Pendo for headcount, cost, and utilization reporting alongside other company data.

Write-back where Linnworks exposes writable fields: segments and scores return

Segments, scores, or metrics computed in Pendo sync onto the matching records in Linnworks, so operations act on what the analysis found.

What you can sync between Linnworks and Pendo

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 Pendo objects How this pairing syncs
Processed Orders Completed orders feed accounting and warehouse-based margin reporting. Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. Processed Orders is specific to Linnworks and Feature Events to Pendo — each maps to any object or custom field on the other side.
Stock Items SKU records keep product data aligned with ERPs and PIMs. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Stock Items is specific to Linnworks and Page Events to Pendo — each maps to any object or custom field on the other side.
Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Stock Levels is specific to Linnworks and Guide Events to Pendo — each maps to any object or custom field on the other side.
Locations Warehouse and fulfillment location records scope stock data during mapping. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Locations is specific to Linnworks and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. Purchase Orders is specific to Linnworks and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Suppliers Vendor records keep procurement data consistent across tools. Visitors End-user records with agent-collected and custom fields; queried through the Aggregation API and enriched with custom fields written back via the Metadata API. Suppliers is specific to Linnworks and Visitors to Pendo — each maps to any object or custom field on the other side.

How changes propagate between Linnworks and Pendo

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 Pendo 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 Pendo through its API, with automatic retries and rate-limit backoff.

Pendo Linnworks Interval-based propagation

DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.

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.
  • Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
What ships with Linnworks ⇄ Pendo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Linnworks or Pendo 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 Pendo record.

Observability

Monitoring

Track your Linnworks ⇄ Pendo 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 Pendo.

How the Linnworks and Pendo 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

Pendo

Integration surface
Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
Authentication
Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
Change detection
Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
Capabilities
read · write
Rate limits
Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
How it works

How to connect Linnworks to Pendo — 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 Pendo 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
    Pendo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Linnworks and Pendo 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 ⇄ Pendo
    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 Pendo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Linnworks and Pendo 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 476 integrations available for Linnworks and Pendo.

Popular · 8 of 476
All Linnworks integrations All Pendo 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