Two-way sync
Changes in Namely or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Keep Namely 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.
Namely 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 Job Titles, Job Tiers, Groups, Teams in Namely 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.
A new person set up in Namely becomes an employee record in TikTok Shop in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in TikTok Shop roll up to the same structure Namely maintains.
Manager and reporting-hierarchy changes in Namely keep expense and purchase approval chains in TikTok Shop pointed at the right people.
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.
| Namely objects | TikTok Shop objects | How this pairing syncs | |
|---|---|---|---|
| Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. | Shops The seller storefront; API access is authorized and scoped per shop. | Profiles is specific to Namely and Shops to TikTok Shop — each maps to any object or custom field on the other side. | |
| Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. | Products Listings synced from a PIM or ERP catalog, subject to platform review. | Job Titles is specific to Namely and Products to TikTok Shop — each maps to any object or custom field on the other side. | |
| Job Tiers Leveling hierarchy grouping zero-to-many Job Titles; read to map seniority into warehouse dimension tables. | SKUs The purchasable variants under a product; inventory and price live at this level. | Job Tiers is specific to Namely and SKUs to TikTok Shop — each maps to any object or custom field on the other side. | |
| Groups Departments and locations that organize Profiles; synced to keep org structure aligned with a warehouse or IdP. | Orders Purchases pulled into an OMS or ERP for fulfillment and accounting. | Groups is specific to Namely and Orders to TikTok Shop — each maps to any object or custom field on the other side. | |
| Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. | Fulfillment packages Shipment units where tracking numbers and carrier data are written back. | Teams is specific to Namely and Fulfillment packages to TikTok Shop — each maps to any object or custom field on the other side. | |
| Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. | Inventory Stock quantities per SKU, updated from the warehouse or ERP to prevent oversells. | Reports is specific to Namely and Inventory 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.
DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.
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 Namely through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Namely–TikTok Shop connection.
Changes in Namely or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Namely 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 Namely or TikTok Shop record.
Track your Namely ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Namely 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 Namely 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 Namely 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 Namely and TikTok Shop: authenticate both systems, choose the objects to sync (such as Namely's Profiles and Job Titles), 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 Namely and TikTok Shop: New hires ready to transact in TikTok Shop; One org structure; Reporting lines drive approvals. A new person set up in Namely becomes an employee record in TikTok Shop in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
Namely: REST API (JSON over HTTPS). Authentication: OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1. 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: The platform pushes order status changes over webhooks, so integrations do not rely on polling alone. Namely: Namely exposes no webhooks; change detection relies on polling and comparing the updated_at timestamp on Profiles and related resources. Stacksync's field mapping accounts for these differences between Namely 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 Namely and TikTok Shop records are not retained after a sync operation.
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 400 integrations available for Namely and TikTok Shop.