Skip to content
ERP ⇄ Analytics

Linnworks to Microsoft Power Bi integration — real-time data sync

Keep Linnworks and Microsoft Power Bi 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 Microsoft Power Bi

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

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into Linnworks, so Linnworks always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

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 Microsoft Power Bi, next to the product, behavioral, and web data the team already measures.

Common use cases

  • 01 Sync admin Activity Events into a warehouse for tenant-wide security, access, and usage reporting.
  • 02 Read Users and workspace access for periodic access reviews reconciled against an HR or Microsoft Entra ID source of record.
  • 03 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
  • 04 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports

Common sync patterns

Where Linnworks runs order-to-cash: customer and account analytics

Orders, invoices, and account records from Linnworks join the behavioral and usage data Microsoft Power Bi already tracks, so customer analysis spans activity and dollars in one view.

Where Linnworks runs operations: inventory and fulfillment metrics

Operational records from Linnworks become measurable in Microsoft Power Bi, 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 Microsoft Power Bi for headcount, cost, and utilization reporting alongside other company data.

What you can sync between Linnworks and Microsoft Power Bi

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 Microsoft Power Bi objects How this pairing syncs
Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Stock Levels is specific to Linnworks and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
Locations Warehouse and fulfillment location records scope stock data during mapping. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Locations is specific to Linnworks and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. Purchase Orders is specific to Linnworks and Workspaces (Groups) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Suppliers Vendor records keep procurement data consistent across tools. Activity Events (Audit Log) Admin audit log of user and content actions read via GET /admin/activityevents; loaded for security, access, and usage reporting across the tenant. Suppliers is specific to Linnworks and Activity Events (Audit Log) to Microsoft Power Bi — 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. Users and Access Workspace users and roles read via GET /groups/{id}/users or the admin scanner APIs; read for access reviews and identity reconciliation against an IdP. Channel Listings is specific to Linnworks and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side.
Returns & Refunds Post-sale records flow to finance and support systems. Datasets (Semantic Models) Tabular models behind reports; their rows are read with DAX via POST datasets/{id}/executeQueries, and datasource and refresh metadata via REST list endpoints. Returns & Refunds is specific to Linnworks and Datasets (Semantic Models) to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between Linnworks and Microsoft Power Bi

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 Microsoft Power Bi 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.

DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating Linnworks records.

Microsoft Power Bi Linnworks Interval-based propagation

DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.

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.
  • Microsoft Power Bi: Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
What ships with Linnworks ⇄ Microsoft Power Bi

Connect Linnworks and Microsoft Power Bi for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Linnworks ⇄ Microsoft Power Bi 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 Microsoft Power Bi.

How the Linnworks and Microsoft Power Bi 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

Microsoft Power Bi

Integration surface
Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
Authentication
Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope.
Change detection
Pull-based: no webhooks or change-data-capture. Content is polled via REST list endpoints, dataset changes are inferred from Refresh History and the admin Activity Events audit log, and the scanner API's GetModifiedWorkspaces reports workspaces changed since a given time.
Capabilities
read
Rate limits
Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
How it works

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

    Choose tables

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

Linnworks and Microsoft Power Bi 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 436 integrations available for Linnworks and Microsoft Power Bi.

Popular · 7 of 436
All Linnworks integrations All Microsoft Power Bi 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