DatriseAI-first ETL

PrestaShop to Metabase Integration

AI-first ETL from PrestaShop into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads PrestaShop into Metabase

Datrise syncs PrestaShop's orders, products, customers, carts, categories, and order states into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

PrestaShop: Open-source ecommerce storefront and catalog.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How PrestaShop entities map to Metabase

PrestaShop entityMetabase objectNotes
ordersprestashop_ordersid PK · custom fields → flattened columns for the question builder
productsprestashop_productsid PK · linked to prestashop_orders
customersprestashop_customersid PK · linked to prestashop_orders
cartsprestashop_cartsid PK · linked to prestashop_orders

FAQ

How does Datrise handle PrestaShop's custom fields in Metabase?

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

How does the PrestaShop to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect PrestaShop to Metabase 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.