Real-time
Two-way sync
Changes in Linnworks or Paylocity instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Linnworks to Paylocity integration — real-time, two-way sync
Keep Linnworks and Paylocity 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 Paylocity
Sync the workers, org structure, and cost centers that Linnworks and Paylocity share in real time, so the people Paylocity manages stay current in the system that runs finance and operations.
Paylocity is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Linnworks runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Shipping Services, Open Orders, Processed Orders, Stock Items in Linnworks with Deductions (Pay Setup), Earnings (Pay Setup), Local and State Taxes, Direct Deposit in Paylocity field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Linnworks keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
- 02 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
- 03 React to the Employee Change webhook to pull the updated Employee record and propagate title, location, or manager changes to downstream apps within minutes.
- 04 Two-way sync of Employees between Paylocity and an HRIS or identity provider so new hires, terminations, and demographic edits flow both directions.
Common sync patterns
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure Paylocity maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Paylocity keep expense and purchase approval chains in Linnworks pointed at the right people.
Where Paylocity runs payroll: labor cost in the books
Pay and compensation data from Paylocity posts into Linnworks as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Linnworks and Paylocity
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 | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Returns & Refunds Post-sale records flow to finance and support systems. | Employees Core HR record keyed by companyId + employeeId; two-way via Create New Employee (POST) and Update Employee (PATCH), plus Get Employee / Get All Employees for reads. | Returns & Refunds is specific to Linnworks and Employees to Paylocity — 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. | Onboarding Create Employee Onboarding pushes new-hire data into Paylocity's onboarding workflow; Get Onboarding Status reads back partner onboarding progress. Write-in for hires from an ATS. | Shipping Services is specific to Linnworks and Onboarding to Paylocity — each maps to any object or custom field on the other side. | |
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Deductions (Pay Setup) Recurring deduction codes at the employee level; two-way via Upsert Deduction and Delete, with Get Deduction / Get All Deductions for reads. | Open Orders is specific to Linnworks and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Earnings (Pay Setup) Recurring earning codes at the employee level; two-way via Upsert Earning and Delete, with Get All Earnings and Get by earning code for reads. | Processed Orders is specific to Linnworks and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Local and State Taxes Two-way via Create/Update/Delete Local Tax and Upsert Primary / Non-Primary State Tax; Get by tax code and Get All for reads. | Stock Items is specific to Linnworks and Local and State Taxes to Paylocity — 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. | Direct Deposit Read-only: Get All Direct Deposit and Get Employee Bank Accounts return main and additional allocations. Bank details cannot be written through the API. | Stock Levels is specific to Linnworks and Direct Deposit to Paylocity — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Paylocity
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 Paylocity 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 Paylocity through its API, with automatic retries and rate-limit backoff.
Paylocity Linnworks Sub-second propagation
DetectionPaylocity notifies Stacksync of record changes through webhook events. Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL.
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.
- Paylocity: 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
What ships with Linnworks ⇄ Paylocity
Connect Linnworks and Paylocity for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Paylocity connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Paylocity 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 Paylocity record.
Observability
Monitoring
Track your Linnworks ⇄ Paylocity 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 Paylocity.
How the Linnworks and Paylocity 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
Paylocity
- Integration surface
- REST API (v1 and v2), JSON payloads
- Authentication
- OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company
- Change detection
- Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL; payloads carry only companyId and employeeId, so the receiver calls the relevant API to fetch changed values. Scheduled polling is used for objects without webhooks.
- Capabilities
- read · write · webhooks
- Rate limits
- 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
How it works
How to connect Linnworks to Paylocity — 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.
- 01
Connect your apps
Authenticate Linnworks and Paylocity with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Linnworks
connected
Paylocity
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Paylocity 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.
objects · Linnworks ⇄ PaylocityCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Linnworks PaylocityCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Paylocity integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Paylocity: authenticate both systems, choose the objects to sync (such as Linnworks's Returns & Refunds and Shipping Services), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Paylocity: One org structure; Reporting lines drive approvals; Where Paylocity runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure Paylocity maintains.
-
Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Paylocity: REST API (v1 and v2), JSON payloads. Authentication: OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company. Stacksync manages authentication, retries, and rate limits on both sides.
-
Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Paylocity: Every endpoint path is scoped to a Paylocity-assigned companyId (a company code, not a UUID), and employees are addressed by Paylocity's employeeId; there is no cross-company query. Stacksync's field mapping accounts for these differences between Linnworks and Paylocity without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Linnworks and Paylocity records are not retained after a sync operation.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 504 integrations available for Linnworks and Paylocity.
Popular · 6 of 504
-
Linnworks ⇄ Success Factors -
Linnworks ⇄ Hibob -
Linnworks ⇄ Ceridian Dayforce -
Linnworks ⇄ D2l Brightspace -
Paylocity ⇄ Infor M3 - Paylocity ⇄ Infor WMS
No integrations match .
