3PL Central to MySQL Integration

How Datrise loads 3PL Central into MySQL

Datrise syncs 3PL Central's orders, receipts, inventory levels, items, customers, and warehouses into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

3PL Central: Third-party logistics warehouse and order operations.

MySQL: Widely used OSS relational engine (InnoDB).

How 3PL Central entities map to MySQL

3PL Central entity	MySQL object	Notes
orders	`tplcentral_orders`	id PK · custom fields → JSON columns
receipts	`tplcentral_receipts`	id PK · linked to tplcentral_orders
inventory levels	`tplcentral_inventory_levels`	id PK · linked to tplcentral_orders
items	`tplcentral_items`	id PK · linked to tplcentral_orders

FAQ

How does Datrise handle 3PL Central's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the 3PL Central to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect 3PL Central to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.