Two-way sync
Changes in Paylocity or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Keep Paylocity and TikTok Shop in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. TikTok Shop 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 Returns and refunds, Promotions, Shops, Products in TikTok Shop with Earnings (Pay Setup), Local and State Taxes, Direct Deposit, Pay Statements 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 TikTok Shop 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.
Manager and reporting-hierarchy changes in Paylocity keep expense and purchase approval chains in TikTok Shop pointed at the right people.
Pay and compensation data from Paylocity posts into TikTok Shop as labor cost, so finance sees workforce spend without re-entering it by hand.
When a worker is hired, moved, or offboarded in Paylocity, the matching employee record in TikTok Shop is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
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 | TikTok Shop objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Promotions Discount campaigns that affect order pricing and settlement reconciliation. | Earnings (Pay Setup) is specific to Paylocity and Promotions to TikTok Shop — 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. | Shops The seller storefront; API access is authorized and scoped per shop. | Local and State Taxes is specific to Paylocity and Shops to TikTok Shop — 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. | Products Listings synced from a PIM or ERP catalog, subject to platform review. | Direct Deposit is specific to Paylocity and Products to TikTok Shop — each maps to any object or custom field on the other side. | |
| Pay Statements Read-only detailed payroll statement data — earnings, deductions, taxes, and direct deposit allocations by year, check date, or date range. Pulled for reporting, never written. | SKUs The purchasable variants under a product; inventory and price live at this level. | Pay Statements is specific to Paylocity and SKUs to TikTok Shop — each maps to any object or custom field on the other side. | |
| Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Orders Purchases pulled into an OMS or ERP for fulfillment and accounting. | Company Codes is specific to Paylocity and Orders to TikTok Shop — each maps to any object or custom field on the other side. | |
| Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. | Fulfillment packages Shipment units where tracking numbers and carrier data are written back. | Custom Fields is specific to Paylocity and Fulfillment packages to TikTok Shop — 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 TikTok Shop through its API, with automatic retries and rate-limit backoff.
DetectionTikTok Shop notifies Stacksync of record changes through webhook events. Webhook push notifications for order and product status changes, with polling for reconciliation.
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–TikTok Shop connection.
Changes in Paylocity or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Paylocity or TikTok Shop 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 TikTok Shop record.
Track your Paylocity ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Paylocity and TikTok Shop.
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 TikTok Shop 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 TikTok Shop 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 TikTok Shop: authenticate both systems, choose the objects to sync (such as Paylocity's Earnings (Pay Setup) and Local and State Taxes), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. TikTok Shop: REST API (TikTok Shop Open Platform). Authentication: App key and secret with shop-scoped access tokens; requests carry a signature. Stacksync manages authentication, retries, and rate limits on both sides.
TikTok Shop: Sellers authorize apps per shop, so access tokens are shop-scoped and multi-shop or multi-region sellers require separate authorizations. Paylocity: The rate limit is 25 calls per second (1,500 per minute); full-employee reads must be paged and throttled to avoid HTTP 429 errors. Stacksync's field mapping accounts for these differences between Paylocity and TikTok Shop 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 Paylocity and TikTok Shop records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Paylocity and TikTok Shop connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Paylocity–TikTok Shop integration in-house.
Yes — Stacksync ships production-grade connectors for both Paylocity and TikTok Shop. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 503 integrations available for Paylocity and TikTok Shop.