Two-way sync
Changes in Active Directory or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Keep Active Directory 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.
An ERP and an identity system describe the same workforce from two angles. TikTok Shop holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Active Directory controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in TikTok Shop and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Returns and refunds, Promotions, Shops, Products in TikTok Shop with Directory roles, Service principals & applications, Organizational units, Organizational contacts in Active Directory in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
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.
| Active Directory objects | TikTok Shop objects | How this pairing syncs | |
|---|---|---|---|
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Shops The seller storefront; API access is authorized and scoped per shop. | Groups is specific to Active Directory and Shops to TikTok Shop — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Products Listings synced from a PIM or ERP catalog, subject to platform review. | Group memberships is specific to Active Directory and Products to TikTok Shop — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | SKUs The purchasable variants under a product; inventory and price live at this level. | Devices is specific to Active Directory and SKUs to TikTok Shop — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Orders Purchases pulled into an OMS or ERP for fulfillment and accounting. | Directory roles is specific to Active Directory and Orders to TikTok Shop — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Fulfillment packages Shipment units where tracking numbers and carrier data are written back. | Service principals & applications is specific to Active Directory and Fulfillment packages to TikTok Shop — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Inventory Stock quantities per SKU, updated from the warehouse or ERP to prevent oversells. | Organizational units is specific to Active Directory 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.
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
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 Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–TikTok Shop connection.
Changes in Active Directory or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Active Directory 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 Active Directory or TikTok Shop record.
Track your Active Directory ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Active Directory 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 Active Directory 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 Active Directory 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 Active Directory and TikTok Shop: authenticate both systems, choose the objects to sync (such as Active Directory's Groups and Group memberships), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the TikTok Shop side: Returns and refunds, Promotions, Shops, Products, plus custom fields where TikTok Shop exposes them. On the Active Directory side: Directory roles, Service principals & applications, Organizational units, Organizational contacts. 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 Active Directory and TikTok Shop: Align group and department membership; One roster on a shared key; Create accounts from new records. When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
Active Directory: Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS). Authentication: OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS. 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. Active Directory: Writes require matching Graph application permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) with tenant admin consent; delegated and application scopes differ. Stacksync's field mapping accounts for these differences between Active Directory and TikTok Shop without custom code.
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 501 integrations available for Active Directory and TikTok Shop.