3PL Central to Domo Integration

How Datrise loads 3PL Central into Domo

Datrise syncs 3PL Central's orders, receipts, inventory levels, items, customers, and warehouses into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How 3PL Central entities map to Domo

3PL Central entity	Domo object	Notes
orders	`tplcentral_orders`	id PK · custom fields → flattened columns for Magic ETL
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 Domo?

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

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

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect 3PL Central to Domo 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.