Data Panda brings your PrestaShop data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
PrestaShop is a self-hosted ecommerce platform written in PHP and MySQL on top of Symfony. It powers around 300,000 live shops, with the strongest concentration in France, Spain, Italy and the rest of Latin Europe. The merchant owns the code, the database and the modules from the PrestaShop Addons marketplace that fill in payments, shipping and marketing on top of the core.
The data shape is recognisable across versions. The core exposes products, combinations, categories, manufacturers, suppliers, stock movements, customers, addresses, carts, orders, order details, invoices, credit slips, returns and the per-country tax rules that make PrestaShop the platform of choice for merchants selling across French, Spanish and Italian VAT regimes. Built-in multi-shop lets one install run several storefronts, each with its own URL, currency, language and catalog scope.
The warehouse picks that apart cleanly. Orders, line items, returns and customers from every shop in the multi-shop tree land next to your accounting in Exact Online or Yuki, your shipping data from SendCloud, your product master in Akeneo and your campaign data in Klaviyo, with the addons that matter (the marketplace module, the loyalty module, the B2B module) pulled in as their own tables instead of squeezed into a custom field.
One profit picture across every shop in the multi-shop tree, with VAT per country ready for the accountant.
Keep PrestaShop in sync with the accounting, shipping and marketing tools that sit around it.
Turn PrestaShop's order, customer and catalog history into forecasts your team can act on.
Internal tools on PrestaShop data so customer service and merchandising stop living inside Back Office.
A list of concrete reports, automations and AI features we have built on PrestaShop data. Pick the one that matches your situation.
Which shop in our multi-shop tree is paying for the rest?
Profit per shop after goods cost, returns and shipping, on one timeline. Splits the French shop that runs on volume from the Italian shop whose smaller order count quietly carries the group's margin.
Did the last upgrade to PrestaShop core or a paid addon cost us orders?
Daily order count and checkout error log on the days a core or addons update went live, per shop and per device. Separates normal seasonal dips from the morning the payment module stopped working on Italian mobile checkouts.
How much of last month's revenue came from the loyalty addon versus the core catalog?
Order revenue tagged by the cart rule, voucher and addon module that triggered it, against the discount the addon gave away. Shows whether the loyalty programme earns its addon licence fee or just discounts orders that would have closed anyway.
Cross-shop margin with returns, shipping and addon licences treated the same way every month, plus VAT per French, Spanish and Italian jurisdiction ready for filing. Month-end stops being five PrestaShop CSV exports stitched together by hand.
Customer-group profitability, repeat-purchase rate and which voucher closed each B2B order, in one place. Account managers walk into a renewal call already knowing whether the negotiated price has eaten the margin.
Stock cover per supplier, carrier cost from SendCloud and return rate per SKU in one view. The morning after a core or addons upgrade, checkout errors and order drops surface before the support inbox fills up.
PrestaShop orders, invoices and credit slips land in Exact Online with the right VAT code per country and shop, and bank-feed matches against the gateway payouts. The Benelux month-end close stops waiting on a weekly Back Office export and a separate French VAT spreadsheet.
PrestaShop orders push into SendCloud for label creation, carrier choice and pickup, and the tracking number plus carrier status come back onto the PrestaShop order. Customer service answers 'where is my parcel' from one screen, and shipping cost lands in the warehouse next to the order it belongs to.
PrestaShop orders, returns and customer-group changes push into Klaviyo as profile properties and metrics. Winback, replenishment and post-return flows fire on days-since-order and reason-of-return, not on a weekly list import that misses last week's repeat buyers.
Akeneo holds the product master with attributes, translations and category mapping per channel; PrestaShop receives the products, combinations and per-language fields it needs to publish. Marketing edits the product copy once in Akeneo and the French, Spanish and Italian shops in the multi-shop tree pick it up on the next sync.
You keep the reporting tool you already have. We connect it to the warehouse where your PrestaShop data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Multi-shop is a built-in PrestaShop feature: one install runs several shops, each with its own URL, currency, language and catalog scope. The connector keeps shop, shop-group and store-view as first-class dimensions in the warehouse, so you can report at single-shop level for one country, roll up to a brand, or consolidate at group level without flattening the hierarchy.
Most paid modules from the PrestaShop Addons marketplace store their data in their own PrestaShop tables. The connector pulls those alongside the core orders, products and customers, so loyalty points, marketplace seller balances, B2B customer groups and similar addon data sit in the warehouse next to the base order table instead of hiding inside a serialised JSON column.
Self-hosted classic PrestaShop is the most common setup. The connector talks to the PrestaShop Webservice (the REST API) and reads from the MySQL database where needed, whether the site runs on a managed host, a VPS or PrestaShop's own Hosted offer. Hosting choice does not change the schema the data lands in.
We review your PrestaShop setup and the systems around it. Together we pick the first thing worth building.