The Presets report is a Pro feature. On the free build there is no menu entry and no report — it is absent rather than switched off.
Where to find it
Analytics → Cart Presets, beside WooCommerce’s own reports. That is the only way in, deliberately. A report that lives in WooCommerce Analytics should be reached the way every other WooCommerce report is reached, so CartPresets’ own admin carries no link to it.What it shows
The date-range picker, the comparison, the chart controls and CSV export are all WooCommerce’s own components, so the page behaves exactly like the reports beside it.
Where the numbers come from
WooCommerce’s own order tables, joined against the preset ID stamped on every preset order line at checkout. That has three consequences worth knowing: Revenue is net of refunds. A refund carries negative revenue and its line items carry the preset meta, so the subtraction lands on the right preset. Order counts use parent orders only, so a refunded order is one order, not two. A sale is whatever WooCommerce says it is. The excluded-status list is WooCommerce’s own, so this page agrees with every other page under Analytics rather than keeping a second opinion. A deleted preset keeps its history, listed as Deleted preset #N. The money was real, and a report whose rows vanish with a preset disagrees with your accounts.What is not tracked
Link opens, add-to-carts, and checkout-reached are recorded nowhere. Following a preset link performs zero analytics writes. Sales enter the books when WooCommerce processes the order, on hooks that never run on your storefront. That is why the plugin can claim a near-zero storefront footprint and mean it. If you want click-level attribution, put UTM parameters on your preset links and read them in your existing analytics — see Preset links.A store with WooCommerce Analytics disabled gets no Presets page, and the plugin keeps no parallel record. Whether sales are tracked at all is your WooCommerce decision, and CartPresets follows it.
Upgrading starts with history
Because the report reads WooCommerce’s own books rather than a record of its own, upgrading from free does not start you at zero. The figures have been accumulating all along — the report simply had nowhere to appear.The Revenue column in the listing
The preset listing has a Revenue column on both builds. On free it shows a crown instead of a figure; clicking it explains what Pro would show. The column is drawn on both tiers on purpose. A column that appears and disappears with the tier is a worse answer than one that explains itself.Reporting and purchase limits are different systems
Purchase limits never read any of this. Limits count rows in the redemptions table, under yourredemption_statuses setting — so an on-hold order can consume a slot before it counts as a sale on this page.
The two answer different questions: may this link still be used? versus how did this preset do? A bank-transfer order is a real commitment for the first question and not yet revenue for the second.
For developers
cartpresets_sales_payload runs after totals, series, rows and the drill-down are assembled — append figures of your own or reshape what the report receives. cartpresets_sales_orders_cap raises how many orders the drill-down lists.
Both fire from Pro only, and the cartpresets/v1/sales routes are not registered on free — a request 404s like any unknown route. Check the tier before assuming they exist. See the hooks reference.