WooCommerce revenue tracking
When WooCommerce is active and your site is connected, the Voris plugin reports store revenue to Voris from your server, so sales show up in your dashboard even when a browser tag would miss them.
Nothing here runs without WooCommerce. If you do not have it, commerce features simply do not appear and nothing errors.
Why revenue is reported from the server
A browser tag cannot see revenue reliably. Ad-blockers drop the tag, page caches serve HTML with no fresh event, and many payments finish on the gateway’s own site — so the “thank you” page the tag needs may never load in the visitor’s browser. Reporting from PHP, when WooCommerce itself says an order completed, avoids all three problems.
Which events are reported
The plugin reports exactly two commerce events.
purchase — a completed order
A purchase is reported when an order reaches the Completed status — not when it is merely paid or still Processing. Fulfilment is the stabler signal and produces fewer corrections. Virtual and downloadable orders that auto-complete report right away.
Each completed order is reported once. If an order reaches “Completed” more than once, revenue is still counted a single time.
A purchase event carries only:
- your site ID
- the order total and its currency (ISO-4217, e.g.
EUR) - the order reference (its ID), for reconciliation
- the number of line items (a count, not what they were)
Free or fully-discounted orders (a total of zero) carry no revenue, so nothing is sent for them.
refund — a correction
Refunding an order — in full or in part — reports a matching negative correction, so your dashboard revenue stays accurate.
A refund event carries only:
- your site ID
- the refunded amount and currency
- the order reference and the refund reference
- a flag for whether the refund was partial
A refund is only reported when Voris confirmed receiving the original purchase. If the purchase was never delivered (for example, the site was not connected when the order completed), reporting the refund would leave your dashboard showing negative revenue against a sale Voris has no record of — so the plugin skips it and notes the skip in the delivery log.
What is never sent
The commerce events contain no customer data at all:
- no names, email addresses, or postal addresses
- no product names or line-item detail — only a count
- no IP address, and no visitor, session, or user identifiers
Order and refund references are validated before they leave your server. Because some stores template order numbers from customer fields, anything carrying an @, whitespace, or an over-long value is refused rather than sent — Voris would rather drop a reference than transmit something that might contain personal data.
See Privacy on WordPress for the full picture across the browser tag and the connection.
It never breaks your store
Reporting revenue must never interfere with an order. If Voris is slow or unreachable, the order status change, the customer’s experience, and your checkout all carry on exactly as if the plugin were not installed. Events are sent after the page has finished, with a short ceiling, and a failed send is retried in the background — never in the middle of a checkout.
The plugin also declares compatibility with WooCommerce High-Performance Order Storage (HPOS), so you will not see the “incompatible plugin” warning, and everything works whether or not HPOS is enabled.
Common questions
My store’s revenue is not showing up. Revenue is reported when an order reaches Completed, not when it is paid. Stores that leave orders in Processing indefinitely will not see revenue. Move the order to Completed (or configure your workflow to complete orders) and it reports.
A refund did not show up. A refund is only reported when Voris confirmed receiving the original purchase. If the original purchase could not be delivered, the refund is skipped to avoid negative revenue against a sale Voris never recorded — the skip is listed in the delivery log.
Does it slow my store down? No. The browser tag is deferred, and revenue events are sent after the page renders, with a two-second ceiling. Nothing about Voris blocks a page, an admin screen, or a checkout.