Two-way sync
Changes in Hibob or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Keep Hibob 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.
Hibob 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 Fulfillment packages, Inventory, Returns and refunds, Promotions in TikTok Shop with Employment, Work, Salaries, Time off in Hibob 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 Hibob keep expense and purchase approval chains in TikTok Shop pointed at the right people.
Pay and compensation data from Hibob 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 Hibob, 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.
| Hibob objects | TikTok Shop objects | How this pairing syncs | |
|---|---|---|---|
| People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. | Fulfillment packages Shipment units where tracking numbers and carrier data are written back. | People (Employees) is specific to Hibob and Fulfillment packages to TikTok Shop — each maps to any object or custom field on the other side. | |
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Inventory Stock quantities per SKU, updated from the warehouse or ERP to prevent oversells. | Employment is specific to Hibob and Inventory to TikTok Shop — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Returns and refunds After-sale records reconciled into finance and support systems. | Work is specific to Hibob and Returns and refunds to TikTok Shop — each maps to any object or custom field on the other side. | |
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Promotions Discount campaigns that affect order pricing and settlement reconciliation. | Salaries is specific to Hibob and Promotions to TikTok Shop — each maps to any object or custom field on the other side. | |
| Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Shops The seller storefront; API access is authorized and scoped per shop. | Time off is specific to Hibob and Shops to TikTok Shop — each maps to any object or custom field on the other side. | |
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Products Listings synced from a PIM or ERP catalog, subject to platform review. | Lifecycle is specific to Hibob and Products 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.
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
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 Hibob through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–TikTok Shop connection.
Changes in Hibob or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Hibob 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 Hibob or TikTok Shop record.
Track your Hibob ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Hibob 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 Hibob 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 Hibob 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 Hibob and TikTok Shop: authenticate both systems, choose the objects to sync (such as Hibob's People (Employees) and Employment), map fields visually, and changes propagate both ways in milliseconds — no code required.
Hibob: REST API (the Bob API). Authentication: Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin. 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: Listings separate the product from its SKUs, and both inventory and price are managed at the SKU level, which mapping logic must respect. Hibob: The GET Read-all-company-employees and Read-by-ID endpoints are legacy; Bob steers reads to POST /people/search, which the docs rate-limit at 50 requests per minute. Stacksync's field mapping accounts for these differences between Hibob 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 Hibob 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 Hibob and TikTok Shop connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–TikTok Shop integration in-house.
Yes — Stacksync ships production-grade connectors for both Hibob 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 Hibob and TikTok Shop.