Data Panda brings your ProfitPlus Webshop 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.
ProfitPlus is an ERP built in Kortrijk for production and trade SMEs, covering purchasing, stock across multiple warehouses, sales and CRM, finance and the shop floor in one package. The webshop is part of that package rather than a separate tool bolted on: it reads the same article file, the same real-time stock levels and the same tiered pricing the rest of the business works with. You can run the fully integrated shop, or keep your own storefront and connect it over the API, in which case customer, order and invoicing data flows back automatically.
Inside ProfitPlus an online order sits next to your stock and your delivery notes. It does not sit next to what the click cost in Google Ads, what Bpost or GLS charged to ship that parcel, or what the same customer bought at the counter last quarter. In a warehouse those all join onto the order line, and margin per article, per channel and per customer stops being an estimate.
Web order lines joined to purchase price, carrier cost and returns, per article.
Let replenishment, order follow-up and customer updates run on live numbers.
Use the order and stock history to forecast demand and spot what is off.
Internal tools your team opens themselves, on data that is already current.
A list of concrete reports, automations and AI features we have built on ProfitPlus Webshop data. Pick the one that matches your situation.
What does an online order really earn us, after shipping and returns?
The web order line joins the purchase price from the article file, the carrier cost for that parcel and the return if it came back. Margin lands per article and per order instead of as an average over the whole shop, so the articles that look like volume winners but lose money once shipping is counted show up by name.
Which articles have not moved in six months?
Stock levels per location joined to the last sales and purchase movement of every article. You get a list with the value tied up per article, so the buying discussion and the clearance discussion start from the same number rather than from whoever last walked through the warehouse.
Does a customer who buys online and through a rep spend more, or just differently?
Web orders, counter sales and rep-entered orders roll up to one customer, since they already share the customer file in ProfitPlus. You see the yearly total per customer and the split per channel, so the question whether the webshop grows the account or eats into the rep gets an answer out of your own order book.
Revenue per channel, margin per article and tied-up stock value come out of the same article file the ERP posts from, so the web numbers already reconcile with the ledger when they reach you. Carrier invoices land next to the parcels they covered, which makes an overcharge visible per shipment rather than per monthly total.
Reps see what their customers ordered online between visits, and which articles those customers quietly stopped buying. A quote goes out against the same tiered pricing the shop applies, so a customer does not find one price on the site and another in the proposal.
Stock levels, picking times and carrier performance per order sit in one place, so the delivery promise on the shop rests on what the warehouse actually does. Replenishment reacts to real web demand per article instead of a reorder point somebody set two years ago.
The article file, the stock levels and the tiered pricing in ProfitPlus drive what Shopify shows, and every Shopify order comes back onto the ProfitPlus customer. Oversells drop away because the shop reads the same stock the warehouse picks from, and margin per article covers both channels at once.
Articles, variants and stock levels flow from ProfitPlus into WooCommerce, and orders flow back with the customer and invoicing details attached. Your shop team edits content in WooCommerce while price and availability stay owned by the ERP, so the two stop disagreeing in front of a customer.
Each shipment booked through SendCloud is matched to the ProfitPlus order it belongs to, with carrier, weight, zone and the invoiced cost on the row. Margin per article is then calculated after shipping, and a carrier surcharge that eats a small-order margin shows up before the monthly invoice does.
Web order lines and their invoices are matched to the bookings in Exact Online per period and per article group. A difference between what the shop sold and what the ledger booked surfaces during the month rather than during the close, and the person who has to explain it can see the individual orders behind the gap.
Order history, article groups and stock availability from ProfitPlus feed the segments in Klaviyo, so a campaign goes out on what somebody bought rather than on what they clicked. A back-in-stock flow only fires for articles the warehouse really has, which keeps the mail from selling something you cannot ship.
Sessions, sources and campaigns from GA4 join the ProfitPlus order they led to, so acquisition cost sits on the same line as purchase price, shipping and returns. A campaign that drives plenty of revenue on low-margin articles becomes visible for what it is, instead of looking like a winner on turnover alone.
These are the 31 tables we currently pull from ProfitPlus Webshop into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your ProfitPlus Webshop 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.
For reporting, less than you would expect. Both models keep the article file, the stock levels and the customer file in ProfitPlus, so the order lines you report on come from the same place either way. The difference sits on the storefront side: with your own shop, browsing and checkout behaviour lives in that platform, so we pull it from there and join it to the ProfitPlus order.
We keep the template and the variant as separate levels so you can report on both. A colour or size that never sells shows up at variant level, while purchasing and margin questions usually make more sense on the template. Collapsing the two into one line is the most common way a webshop report ends up flattering a range that is not working.
Article attributes that arrive from an external catalogue are part of the article file by the time we pull it, so they come along with the rest. If you also want to compare what the source delivered against what ended up on the shop, that is a separate pull from the source itself, and it is worth doing when catalogue quality is the actual problem you are chasing.
We review your ProfitPlus Webshop setup and the systems around it. Together we pick the first thing worth building.