Profit Forge – Refund, Coupon & Order Audit for WooCommerce

Profit Forge scans the orders of your WooCommerce store and reports where money went missing. It gives you the order numbers behind each finding, the amount, and the steps that stop it happening again. No account, no key, no setup wizard. A store leaks money in small amounts. A coupon that stacked when it should not have. A refund where the goods never came back to stock. A customer charged twice because the checkout button was clicked twice. Each one is small. A month of them is not. What it reports

• Coupon stacking — an "individual use only" coupon that ended up combined with other coupons, and how much extra discount that gave away.
• Refund without restock — money refunded, goods never returned to stock, and the inventory value now missing.
• Duplicate paid orders — the same cart and email paid for twice within minutes, before the customer's bank turns it into a chargeback.

Every finding carries the order numbers behind it. Nothing is reported that cannot be shown on an order screen. Findings that share one cause are grouped into a case. After you apply a fix, the next scan re-tests the orders placed since and tells you whether the leak repeated and on which order. How it works

1. Activate the plugin.
2. Run a scan: it processes orders in the background in batches, so a busy store keeps serving customers.
3. Read the report: the total found, findings grouped by rule, the evidence for each finding and the fix steps.

You choose the window: a rolling number of days, the last full calendar month, or all the order history you have. Nothing about the scan is capped, metered or time-limited. Silent when it cannot prove its case A false accusation costs more than a missed leak. Every rule stays silent when it cannot prove its case: a coupon whose settings were deleted, a refund on a product that does not track stock, two orders from the same cart a week apart. If the report says nothing, nothing was proven; it does not mean the rule did not run. Rules that could not run are listed with the reason. Your data stays in your store The scan runs inside WordPress. This plugin makes no external requests at all — no analytics, no phoning home, no order data sent anywhere. Nothing leaves your server. The one place a request can happen is the separate Pro add-on reading your own gateway statement, and only if you give it a key — see External services below. The plugin reads your orders and writes only its own findings table; it never edits an order, a refund, a coupon or a product. Pro A separate add-on adds nine more rules (Stripe fees against your rate card, PayPal fees against your rate card, shipping charged below label cost, single-use coupon reuse, coupon on top of a sale price, partial refund above the line total, tax class with no matching rate, negative margin after cost of goods, paid orders stuck on hold), a printable report, CSV export and a monthly email. The shipping rule waits for carrier label costs. Those rules and screens live in the other plugin — they are not in this one, switched off. Everything this plugin ships is on, for everyone, with no key: every rule it has, the whole scan window, and every line of every report. A Pro licence also includes priority email support while it is active. It ends when the licence expires and comes back on renewal. Documentation: https://profit-forge.com/docs/

1.2.1

• On very large stores, a scan now remembers at most 20,000 carts between batches while it looks for duplicate paid orders, so memory use stays bounded. Past that, the oldest carts with a single order are forgotten first and carts that already hold a pair are kept. A duplicate whose first order was forgotten may not be reported.

1.2.0

• Deleting the plugin removes findings, scan history and settings only when "Delete Profit Forge data on uninstall" is checked. Licence and Stripe keys are always removed when the Pro add-on is deleted.
• Scans now distinguish unavailable coupon data from a store with no coupons, and report fixes only after checking the complete scan window.
• Starting a scan twice no longer creates competing runs; a stalled run with no queued work can be closed.
• Amounts follow the WooCommerce price format. Saved findings remain readable after a Pro licence expires.

1.1.3

• PayPal fees are now read from where the official PayPal Payments plugin records them (the fee on the order, with its own currency). Before, the plugin looked under names that plugin never writes and saw no PayPal fee at all.
• The payment id shown in a finding for a Stripe or PayPal charge now comes from WooCommerce's own transaction id on the order. Before, it was usually missing.
• When an order carries fee records from both Stripe and PayPal (the customer tried one, then paid with the other), the fee of the gateway the order was paid with is used. Before, Stripe always won.
• Gateway fees in currencies without cents, such as the Japanese yen, are read at their real size instead of 100 times too large.
• Orders placed in the last or first hours of a month are now counted in the right month on stores whose time zone is not UTC. Before, the last hours of a month could be counted in the next one, or the first hours of the next month in this one.
• Deleting the plugin with "Keep my findings" switched off now also removes the case history tables, not only the scan tables.
• The period shown on a finished report is now the real period on stores whose time zone is not UTC. Before, a report for January could be headed with dates that started on 31 December.

1.1.2

• The plugin now includes the CSV reader that Profit Forge Pro uses to import a gateway statement, so the import works with the version of this plugin from WordPress.org. Nothing changes for stores that do not use Profit Forge Pro.

1.1.1

• On stores where WooCommerce's Cost of Goods Sold feature is switched off, Profit Forge no longer writes a WooCommerce "called incorrectly" notice to the log for every line item of every order it reads. It now asks WooCommerce for the cost of goods only when that feature is on, and otherwise reads costs from the cost-of-goods plugins it already supports, as before.

1.1.0

• Before a scan runs, the screen now states what it will and will not check on this store, and why — with a real example line instead of a promise. A rule that cannot run names the data it is missing.
• The scan preview and the contract card now agree on how many orders are in the window; the two could previously quote different figures for the same scan.
• A case reopened by a later scan keeps its "fix applied" date, and a re-test can no longer quietly demote a finding you already confirmed.
• Findings and their re-test outcomes are now published in a shared format, so a dashboard plugin installed alongside can read this plugin's results without scraping the screen. Nothing leaves your server: this plugin still makes no external requests.

1.0.2

• The scan window is no longer capped. Any store can scan a rolling number of days, the last full calendar month, or its entire order history — the "All available order history" option is now always on the Settings screen.
• Findings that share one cause are grouped into a single case for everyone.
• The re-test outcome ("not repeated on N later orders" / "repeated on order X") is now shown to everyone. It was always being calculated; now it is always displayed.
• Nothing in this plugin is switched off pending a key, a trial or a quota.

1.0.1

• Text domain now matches the plugin slug, so translations load from translate.wordpress.org.
• readme: the Contributors field names the plugin owner's WordPress.org account.
• Fix: switching a rule off on the Settings screen now actually switches it off (rule ids kept their case in one place and lost it in another).
• Honest states: a run that skipped a rule no longer reports "every rule ran"; a finding that left the report window is no longer shown as resolved; a month with nothing found is told apart from a month in which the scheduled scan never ran; a report that cannot be fetched says so instead of staying silent.

1.0.0

• First public release: coupon stacking, refund without restock and duplicate paid orders, each with the order numbers behind it, the amount and the steps that stop it recurring.