Skip to content
Database ⇄ ERP

Reltio to TikTok Shop integration — real-time, two-way sync

Keep Reltio 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Reltio and TikTok Shop

Give your engineers TikTok Shop's data in Reltio: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Returns and refunds, Promotions, Shops, Products from TikTok Shop into Reltio and keeps both sides consistent in real time. Whatever TikTok Shop is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Reltio sync back into TikTok Shop with its validations respected.

Common use cases

  • 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 03 Sync TikTok Shop orders into an ERP or order management system so fulfillment starts without manual export
  • 04 Push inventory levels from the warehouse or ERP to TikTok Shop to prevent overselling on live and video commerce

Common sync patterns

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the TikTok Shop interface, limits, and retries.

React to ERP changes

Updates in TikTok Shop arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.

Where TikTok Shop is the HR system of record: people data for internal systems

Worker and org records stay current in Reltio for provisioning, access, and reporting systems that read from the database.

What you can sync between Reltio and TikTok Shop

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.

Reltio objects TikTok Shop objects How this pairing syncs
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Promotions Discount campaigns that affect order pricing and settlement reconciliation. Reference Data (RDM) is specific to Reltio and Promotions to TikTok Shop — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Shops The seller storefront; API access is authorized and scoped per shop. Entities is specific to Reltio and Shops to TikTok Shop — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Products Listings synced from a PIM or ERP catalog, subject to platform review. Relations is specific to Reltio and Products to TikTok Shop — each maps to any object or custom field on the other side.
Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. SKUs The purchasable variants under a product; inventory and price live at this level. Crosswalks is specific to Reltio and SKUs to TikTok Shop — each maps to any object or custom field on the other side.
Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Orders Purchases pulled into an OMS or ERP for fulfillment and accounting. Interactions is specific to Reltio and Orders to TikTok Shop — each maps to any object or custom field on the other side.
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Fulfillment packages Shipment units where tracking numbers and carrier data are written back. Matches (Potential Matches) is specific to Reltio and Fulfillment packages to TikTok Shop — each maps to any object or custom field on the other side.

How changes propagate between Reltio and TikTok Shop

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.

Reltio TikTok Shop Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to TikTok Shop through its API, with automatic retries and rate-limit backoff.

TikTok Shop Reltio Sub-second propagation

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 Reltio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • TikTok Shop: Subject to the platform's per-app API rate limits.
What ships with Reltio ⇄ TikTok Shop

Connect Reltio and TikTok Shop for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–TikTok Shop connection.

Real-time

Two-way sync

Changes in Reltio or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or TikTok Shop data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Reltio or TikTok Shop record.

Observability

Monitoring

Track your Reltio ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and TikTok Shop.

How the Reltio and TikTok Shop connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

TikTok Shop

Integration surface
REST API (TikTok Shop Open Platform)
Authentication
App key and secret with shop-scoped access tokens; requests carry a signature
Change detection
Webhook push notifications for order and product status changes, with polling for reconciliation
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's per-app API rate limits
How it works

How to connect Reltio to TikTok Shop — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Reltio 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Reltio connected
    TikTok Shop connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Reltio ⇄ TikTok Shop
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Reltio TikTok Shop
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Reltio and TikTok Shop integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 428 integrations available for Reltio and TikTok Shop.

Popular · 6 of 428
All Reltio integrations All TikTok Shop integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own