| 开发者 | davefx |
|---|---|
| 更新时间 | 2026年9月5日 20:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
No. The audit half — expiry, overlaps, orphans, scope — needs no cost data at all and works the moment you activate. Margins do need cost data, but not necessarily another plugin: WooCommerce has included its own Cost of Goods feature since 10.3, and it only needs switching on. If your shop already records cost in one of the third-party plugins listed above, this reads that instead — whichever one you tell it to believe.
Because none of its orders has a cost recorded against it. The plugin will not guess, and it will not quietly treat an unknown cost as zero, because that would report your revenue as your profit.
Either some order lines have no cost recorded, in which case the covered share is stated alongside; or your cost plugin only stores what a product costs today rather than what it cost when each order was placed. Both are useful. Neither is exact, and the screen says so.
One of them, chosen by you under WooCommerce → Coupon Audit Settings. It never mixes them.
It does not run on the storefront at all. Aggregation happens in the background through Action Scheduler, and the admin screens read precomputed figures.
Your shop's data, no — not a coupon, not an order, not a customer. Everything the plugin reports is worked out on your own server and stays there. The plugin does contact one outside service, Freemius, to check for updates and to license the paid version. It also asks whether you are willing to send diagnostics about the site itself, such as its address and the version of WordPress it runs. It asks before sending anything, you can say no, and saying no changes nothing about how the plugin works. "Third Party Services" below lists every field.
dfxcaaw_coupon_query_args filter has been removed. Use dfxcaaw_coupon_rows_where instead — it does the same job on every read the plugin makes, at any shop size. The old filter reached get_posts(), which the audit stopped using when it was rebuilt for large shops; what remained of it applied only to shops with fewer than three hundred coupons, so it worked on a small site and quietly did nothing on a large one. If you filter the audit and have not moved yet, this is the release that requires it.dfxcaaw_coupon_query_args; dfxcaaw_coupon_rows_where applies to every read, including this one.dfxcaaw_coupon_rows_where, which applies to every read the plugin makes. The older dfxcaaw_coupon_query_args still works where it always did, but it cannot reach the audit screen any more — that screen stopped reading through get_posts() when it was rebuilt. Anything relying on it to filter the audit needs to move to the new filter.dfxcaaw_margin_window_days, rather than a fixed cap. Thirty days remains the default; anything can change it, including a snippet in your own theme.