Real-time
Two-way sync
Changes in Linnworks or Success Factors instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Linnworks to Success Factors integration — real-time, two-way sync
Keep Linnworks and Success Factors 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 Success Factors
Sync the workers, org structure, and cost centers that Linnworks and Success Factors share in real time, so the people Success Factors manages stay current in the system that runs finance and operations.
Success Factors 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 Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks with Position, PerEmail and PerPhone, User, PerPerson in Success Factors 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 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
- 02 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 03 Keep Foundation Objects (department, location, cost center) aligned between SuccessFactors and an ERP so cost-center and org hierarchies match.
- 04 Write updated PerEmail, PerPhone, and User attributes back into SuccessFactors from an identity or directory system so contact data stays current.
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 Success Factors maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Success Factors keep expense and purchase approval chains in Linnworks pointed at the right people.
Where Success Factors runs payroll: labor cost in the books
Pay and compensation data from Success Factors posts into Linnworks as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Linnworks and Success Factors
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 | Success Factors objects | How this pairing syncs | |
|---|---|---|---|
| Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. | Stock Levels is specific to Linnworks and Position to Success Factors — each maps to any object or custom field on the other side. | |
| Locations Warehouse and fulfillment location records scope stock data during mapping. | PerEmail and PerPhone Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current. | Locations is specific to Linnworks and PerEmail and PerPhone to Success Factors — each maps to any object or custom field on the other side. | |
| Purchase Orders Replenishment POs sync with suppliers and accounting systems. | User Core identity/User entity behind role-based permissions; a model distinct from Employee Central, synced two-way with a directory or IdP and downstream apps. | Purchase Orders is specific to Linnworks and User to Success Factors — each maps to any object or custom field on the other side. | |
| Suppliers Vendor records keep procurement data consistent across tools. | PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. | Suppliers is specific to Linnworks and PerPerson to Success Factors — 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. | EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. | Channel Listings is specific to Linnworks and EmpEmployment to Success Factors — each maps to any object or custom field on the other side. | |
| Returns & Refunds Post-sale records flow to finance and support systems. | EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. | Returns & Refunds is specific to Linnworks and EmpJob to Success Factors — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Success Factors
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 Success Factors 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 Success Factors through its API, with automatic retries and rate-limit backoff.
Success Factors Linnworks Sub-second propagation
DetectionSuccess Factors notifies Stacksync of record changes through webhook events. Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling).
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.
- Success Factors: OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.
What ships with Linnworks ⇄ Success Factors
Connect Linnworks and Success Factors for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Success Factors connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Success Factors 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 Success Factors record.
Observability
Monitoring
Track your Linnworks ⇄ Success Factors 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 Success Factors.
How the Linnworks and Success Factors 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
Success Factors
- Integration surface
- OData V2 and V4 REST APIs (plus legacy SFAPI / Compound Employee SOAP API)
- Authentication
- OAuth 2.0 SAML Bearer Assertion — register an OAuth client for an API key (used as client_id), then exchange a signed SAML assertion for a short-lived access token; legacy HTTP Basic auth is being retired
- Change detection
- Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling); Intelligent Services can also push a fixed set of standard business events (e.g. Employee Hire) to a REST endpoint
- Capabilities
- read · write · webhooks
- Rate limits
- OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.
How it works
How to connect Linnworks to Success Factors — 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 Success Factors 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
Success Factors
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Success Factors 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 ⇄ Success FactorsCustomers 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 Success FactorsCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Success Factors integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Success Factors: authenticate both systems, choose the objects to sync (such as Linnworks's Stock Levels and Locations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Linnworks side: Stock Levels, Locations, Purchase Orders, Suppliers, plus custom fields where Linnworks exposes them. On the Success Factors side: Position, PerEmail and PerPhone, User, PerPerson. 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 Success Factors: One org structure; Reporting lines drive approvals; Where Success Factors 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 Success Factors maintains.
-
Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Success Factors: OData V2 and V4 REST APIs (plus legacy SFAPI / Compound Employee SOAP API). Authentication: OAuth 2.0 SAML Bearer Assertion — register an OAuth client for an API key (used as client_id), then exchange a signed SAML assertion for a short-lived access token; legacy HTTP Basic auth is being retired. 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. Success Factors: Two parallel data models exist — the User entity versus the Employee Central model (PerPerson / EmpEmployment / EmpJob) — each with its own lastModifiedDateTime, so a sync must query both to avoid missing changes. Stacksync's field mapping accounts for these differences between Linnworks and Success Factors without custom code.
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 Success Factors.
Popular · 5 of 504
-
Linnworks ⇄ Hibob -
Linnworks ⇄ Ceridian Dayforce -
Linnworks ⇄ D2l Brightspace -
Success Factors ⇄ Cin7 - Success Factors ⇄ DEAR Inventory
No integrations match .
