Skip to content
Reportkey
PrestaShop
PrestaShop Webservice

Orders and payments report for a PrestaShop store

Reportkey reads orders through the PrestaShop Webservice and separates what the buyer owes from what was actually paid, broken down by status, payment module and product.

Sign up, enable the Webservice in the PrestaShop back office, add the key and pick the store in a project. Your first report in 5 minutes.
  • Amount due and amount actually received on two separate lines.
  • Multi-currency orders converted with the rate stored in each order.
  • A Webservice key limited to view rights on the resources the report uses.
Sample Reportkey client report
Sample Reportkey client report
PrestaShop Orders, paid amount, and top products
30+
integrations
5 min
setup
14 days
trial
TL;DR

PrestaShop integration: the store address and a Webservice key with view rights on orders are entered once, the store is picked in a project, and orders, amount paid, statuses, discounts, shipping and top products go into a scheduled report.

PrestaShop sales report for your client

PrestaShop is an open-source ecommerce platform especially common in Europe. The store runs on its own hosting, grows through payment and shipping modules and easily serves several countries and currencies. A report for such a store has to keep placed orders and real money clearly apart.

Reportkey reads orders through the built-in PrestaShop Webservice and turns them into blocks of a recurring report, placed next to ad campaigns and website analytics and delivered on schedule as a link or PDF.

PrestaShop store analytics: orders and amount paid

Every PrestaShop order stores two totals, which is the platform’s key detail:

  • Order amount — the total_paid value, what the buyer owes.
  • Actually paid — the total_paid_real value, what arrived according to the payment module.
  • Orders — count per day, week or month by order date.
  • Average order value — order amount per order.
  • Change versus the previous period for each line.

The gap between the first two lines is orders still awaiting money: cash on delivery, bank transfer or an abandoned card payment.

PrestaShop statuses and payment modules

An order status points to the order states list, which has names in the shop’s language: awaiting payment, payment accepted, processing, shipped, delivered, cancelled, refunded. Stores can add their own states, and Reportkey shows them under the back office names. The second breakdown is the payment module recorded on each order. Together with statuses, the table shows where payments get stuck.

Discounts and shipping in orders

A PrestaShop order splits its total into products, discounts and shipping. The block sums them for the period: the value of products sold, what the store gave away through cart rules and vouchers, and what buyers paid for delivery. It answers what the month’s promotion cost and why revenue grew more slowly than orders.

PrestaShop orders export: top products

Order rows hold product, quantity and price, which build a product ranking with units and amount. The ranking uses the same rules on every build, so month-over-month comparison does not depend on who exported data last time.

Currencies and multistore

Amounts are stored in the order currency together with the conversion rate to the default currency, and the report uses that rate. If one installation runs several shops, the Webservice key is bound to one of them, and each storefront gets its own project and report.

PrestaShop Webservice notes

  • The Webservice is off by default; an administrator enables it in Advanced Parameters.
  • View rights on orders, order rows, states and currencies are enough.
  • A standard order stores no traffic source.
  • Export speed depends on hosting; history covers the store’s whole lifetime.

PrestaShop next to ads and analytics

PrestaShop stores often advertise abroad. Add Google Analytics 4, Google Ads campaigns and Facebook* and Instagram* ads, and for Russian traffic Yandex Direct and Yandex Metrica. A logo on the report, scheduled delivery and AI insights are available, though not on every plan. The in-house team demo report shows a multi-channel brand document, other store platforms are on the online retail integrations page, and the 14-day trial is on pricing.

Metrics

What goes into the PrestaShop report

These are the metrics that the PrestaShop integration already brings into Reportkey reports.

Orders
Order total
Amount paid
Average order value
Top products
What this integration adds to the report
Orders, paid amount, and top products
Pricing

PrestaShop reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect PrestaShop to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from PrestaShop in client reports.

Pain points
  • The store sells in several countries and currencies, and the monthly total in the PrestaShop back office has to be converted by hand.
  • Payment modules mark orders differently, so the contractor's order total never matches what the payment provider transferred.
  • Discounts and free shipping are handed out generously, yet nobody sees what they cost over a month.
PrestaShop
European store with a remote marketing team

A PrestaShop store sells in euros while ads run in Google Ads and on Facebook*. The report joins both: campaigns, Google Analytics 4 sessions and store orders with the amount actually paid.

PrestaShop
Agency managing a multistore installation

The client runs separate storefronts for different countries on one installation. Each storefront gets its own Reportkey project with its own key and delivery schedule.

PrestaShop
Owner measuring the cost of promotions

The discounts and shipping block shows how much the store gave away in discounts and spent on delivery during the month next to the product total, so extending a promotion is a numbers decision.

Report preview

How PrestaShop appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey client report
Sample Reportkey client report
Monthly PrestaShop orders

Weekly order bars, two lines for order amount and amount actually paid, a status and payment module table and a tile with discounts and shipping cost.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the PrestaShop connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the PrestaShop store or site that should supply orders, payments, or leads to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need to connect PrestaShop?
The store address and a Webservice key. In the back office open Advanced Parameters, then Webservice, enable it and add a key. Grant view rights on orders, order_details, order_states and currencies, and in a multistore setup bind the key to the right shop. The report needs no other rights.
What is the difference between total_paid and total_paid_real?
The total_paid field is what the buyer owes for the order. The total_paid_real field is what actually arrived according to the payment module. Until payment comes in, the second value can be zero or lower. The report shows both amounts on separate lines.
How does the report handle several currencies?
PrestaShop stores each order amount in its own currency together with the conversion rate to the shop's default currency. The report converts orders with the rate saved in the order, so totals match how the store valued the sale on the day of purchase.
How often is data refreshed?
Orders are requested on every report build. The store server, not the platform, sets the pace: on busy hosting a large month loads page by page more slowly, but all orders up to build time are included.
Does the report show where buyers came from?
A standard PrestaShop order does not store the acquisition channel. Traffic sources come from neighbouring blocks such as Google Analytics 4, Yandex Metrica and ad accounts, while the PrestaShop block covers what was sold and what was paid.

Orders and payments report for a PrestaShop store

Sign up, enable the Webservice in the PrestaShop back office, add the key and pick the store in a project. Your first report in 5 minutes.

Start free