Two-way sync
Changes in Paylocity or Shopify instantly reflect in both systems. No stale data, no manual imports.
Keep Paylocity and Shopify in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Shopify runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Paylocity. Paylocity is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Products, ProductMedias, ProductVariants, Orders in Shopify 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 Paylocity stays authoritative on roles and org structure while Shopify keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Paylocity marks a worker as departed, the matching user in Shopify is flagged or deactivated, so former employees do not keep CRM access after their last day.
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
A person recorded in Paylocity, such as a candidate or applicant, can create or update the matching contact in Shopify, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
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.
| Paylocity objects | Shopify objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Products Catalog entries; often mastered in a PIM or ERP and written into Shopify. | Employees is specific to Paylocity and Products to Shopify — each maps to any object or custom field on the other side. | |
| 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. | ProductMedias Synced with incremental and full sync per the Stacksync docs. | Onboarding is specific to Paylocity and ProductMedias to Shopify — each maps to any object or custom field on the other side. | |
| 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. | ProductVariants Synced with incremental and full sync per the Stacksync docs. | Deductions (Pay Setup) is specific to Paylocity and ProductVariants to Shopify — each maps to any object or custom field on the other side. | |
| 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. | Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. | Earnings (Pay Setup) is specific to Paylocity and Orders to Shopify — each maps to any object or custom field on the other side. | |
| 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. | Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. | Local and State Taxes is specific to Paylocity and Customers to Shopify — each maps to any object or custom field on the other side. | |
| 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. | Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. | Direct Deposit is specific to Paylocity and Abandoned Checkouts to Shopify — each maps to any object or custom field on the other side. |
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.
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 Shopify through its API, with automatic retries and rate-limit backoff.
DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Paylocity–Shopify connection.
Changes in Paylocity or Shopify instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Paylocity or Shopify data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Paylocity or Shopify record.
Track your Paylocity ⇄ Shopify sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Paylocity and Shopify.
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.
Authenticate Paylocity and Shopify with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Paylocity and Shopify 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Paylocity and Shopify: authenticate both systems, choose the objects to sync (such as Paylocity's Employees and Onboarding), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Paylocity and Shopify connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Paylocity–Shopify integration in-house.
Yes — Stacksync ships production-grade connectors for both Paylocity and Shopify. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Paylocity: 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. On Shopify: Webhook topics per resource, with polling on updated_at as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Shopify side: Products, ProductMedias, ProductVariants, Orders, plus custom fields where Shopify exposes them. On the Paylocity side: Deductions (Pay Setup), Earnings (Pay Setup), Local and State Taxes, Direct Deposit. 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 532 integrations available for Paylocity and Shopify.