


Sales report for an Ecwid store
Reportkey connects to an Ecwid store through an app, reads orders and the platform's built-in reports, including revenue, sales funnel and visitors, and shows them to the client next to ad campaigns.
- Orders and revenue with a previous-period comparison from Ecwid's own reports.
- Refunds, partial refunds and coupon discounts on their own lines.
- Sales funnel, visitors by device, new versus repeat orders.


Ecwid integration: the owner installs the Reportkey app in the store and approves read access to orders and stats, the store is picked in a project, and orders, revenue, refunds, top products and the funnel go into a scheduled report.
Ecwid sales report for your client
Ecwid differs from most platforms because the store does not have to live on its own website. The storefront is embedded as a widget in a site on any builder, attached to a social page or run as a standalone mini-site. For a marketer this means sales and traffic almost always sit in different systems: orders in Ecwid, visits and goals in the main site’s analytics.
Reportkey brings them into one document. Through the app it reads Ecwid orders and ready-made reports, builds report blocks from them and places them next to ad accounts and analytics, delivered on schedule as a link or PDF.
Ecwid store analytics: orders and revenue
Ecwid has its own aggregated reports, and Reportkey uses them for the top block: orders and revenue by hour, day, week or month with a built-in previous-period comparison, plus average order value. The numbers match what the owner sees in the store’s reports section, so reconciliation does not turn into an argument.
Payments and refunds in the Ecwid API
The order list gives a finer cut. Payment status can be PAID, AWAITING_PAYMENT, CANCELLED, REFUNDED, PARTIALLY_REFUNDED or INCOMPLETE, and stores can add custom statuses. The report shows:
- Paid orders and their amount — PAID status only.
- Refunds — full and partial, with the amount from refundedAmount.
- Incomplete orders — placed but unpaid, useful for a talk about abandoned payments.
- Coupons — orders with a promo code and the coupon discount total.
Exporting Ecwid orders: top products
Order items include product, SKU, price and quantity, which produce a product ranking for the period with units and amount. The ranking is recalculated on every build with the same rules, so month-over-month comparison stays correct.
Store funnel and visitors
Ecwid also tracks storefront statistics: visitors, sales funnel steps from catalogue view to order, visitors by device and the share of new versus repeat orders. For widget stores this is especially useful, because the main site’s analytics sees the page but not always what happens inside the cart. The funnel shows where buyers drop off, and the repeat share shows whether retention works.
UTM tags in Ecwid orders
An Ecwid order can store UTM tags and the referrer of the visit that led to the purchase. Tags appear only for visitors who came through tagged links, so some orders will have no source. Treat it as a hint about which campaigns bring buyers, not as an attribution model.
Before connecting Ecwid
- The Ecwid API is available only on paid Ecwid plans.
- The total includes shipping and taxes; receipts and refunds are shown separately.
- Built-in reports and order list totals may differ because of status handling.
Ecwid with ads and analytics
Link sales with traffic by adding the main site’s Yandex Metrica or Google Analytics 4, Google Ads campaigns, Yandex Direct and VK Ads. If promo codes go out by email, add Unisender campaigns. Report branding, a sending schedule and AI insights are not on every plan. The freelancer demo report shows a document for a small contractor, all store platforms and payment providers are on the ecommerce integrations page, and trial terms are on pricing.
What goes into the Ecwid report
These are the metrics that the Ecwid integration already brings into Reportkey reports.
Ecwid reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Why teams connect Ecwid to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from Ecwid in client reports.
- The Ecwid store is embedded in a site built elsewhere, so sales live in one dashboard and traffic in another.
- Ecwid's built-in reports suit the owner but cannot be sent to a client together with ad results as one document.
- Coupons go out in newsletters and through bloggers, yet nobody counts how many orders they produced or what the discounts cost.
The Ecwid storefront sits on a corporate site as a widget. The agency report shows Ecwid orders and revenue next to site visits and ad spend, even though these are separate systems.
The same Ecwid catalogue powers the website and a social storefront. Each week the owner sees orders, leading products and the share coming from repeat buyers.
Each newsletter and each blogger gets a coupon. The report shows orders placed with coupons and the discount total, so partner performance is discussed with numbers.
How Ecwid appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.

A revenue line with the previous period dashed, a store funnel from visitors to orders, a top products table by SKU and a refunds row.
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What do I need to connect Ecwid?
Why does built-in report revenue differ from the order list total?
What does an Ecwid order total include?
How often is data refreshed?
Often connected together
Working sources that teams usually add to the same report.
Sales report for an Ecwid store
Sign up, install the Reportkey app in your Ecwid store and pick it in a project. Your first report in 5 minutes.


