WooCommerce · money audit

Your store leaks money.Find every drop.

Profit Forge runs twelve audit rules over your WooCommerce orders — gateway fees, shipping, coupons, taxes, refunds, duplicates — and hands you a dollar report with evidence rows and fix steps.

See what it does See pricing

receipt #11002 $184.90

+$0.24 × 2,802 orders · 6 months · 12 rules

12audit rules, from fee reconciliation to coupon stacking

$0.00a clean store gives a clean zero — verified against a golden corpus of 2,802 orders

100%of the analysis runs inside your store — data never leaves it

The leak

Your store leaks money in cents. Cents compound.

6 rules, 2,802 orders, 6 months of a real store. None of these is a disaster on its own — a coupon that stacked, a label that cost more than the postage charged, a refund the stock never came back from. Together they are $418.51.

refunds coupons duplicates taxes shipping fees

Refunds without restock R7+R8

#10666 Pour-over stand · refunded $236.00 for 2 units · none returned to stock −$108.00

$196.50 across 5 orders in the window

Coupon stacking and double discounts R4+R5+R6

#10555 Pour-over stand · regular $120.00, sale $96.00, then SALE30 took another $41.50 −$41.50

$140.60 across 9 orders in the window

Duplicate paid orders R11

#11408 first payment · $28.90 · ppcp −$28.90

$51.55 across 2 orders in the window

Tax class with no rate R9

#10400 Paper filters, 100 · tax class “supplies” has no rate for US · $88.00 charged, no tax collected −$6.38

$19.14 across 3 orders in the window

Shipping charged below label cost R3

#10871 label $10.45 · customer paid $7.10 −$3.35

$7.55 across 3 orders in the window

Gateway fees vs rate card R1+R2

#10693 charged $17.54 · rate card 2.9% + $0.30 = $16.13 · on $545.90 −$1.41

$3.17 across 5 orders in the window

$418.51 found on the demo corpus

$69.75 is the median month of it — which is the number that matters, because it comes back every month until someone stops it.

Twelve rules

Twelve places money goes missing, and what to do about each.

Every finding is a dollar amount with the order ids behind it and the fix that stops it repeating.

Gateway fee reconciliation

Recomputes what your gateway should have charged against what it actually took, order by order.

Shipping under-charging

Flags orders where the customer paid less for delivery than you paid the carrier.

Coupon stacking

Catches discount combinations that quietly push an order below margin.

Tax configuration checks

Finds rates and rules that disagree with where and what you actually sell.

Refund & duplicate anomalies

Surfaces refund patterns and double orders that deserve a human look.

Evidence, not vibes

Every finding carries the raw rows behind it and the steps that stop the leak — in dollars.

The rate card

It will not name a fee it cannot prove you agreed to.

Almost nobody pays the published gateway price. So until you confirm your contracted rates, the fee rules say nothing at all — an invented tariff would invent a leak on every store that ever negotiated one.

order #10693 on $16.13

charged by the gateway $17.54

your rate card · 2.9% + $0.30 $0.30

−$1.41 on this one order — and the rule found the same shape on every order in the window.

rate card not confirmed

Gateway fees vs rate card silent

rate card confirmed

Gateway fees vs rate card $3.17

with source & date

And one rule deliberately does not count. “Paid orders stuck on hold” runs in observe mode: the amount is reported separately as at risk and stays out of the leak total, because that money is already in your account. A total padded with money you already have is a sales trick, not an audit.

The first audit

Install, run it, read the report.

Install and scan

The first audit walks your order history right in wp-admin. Nothing is uploaded anywhere.

Read the report

Findings are ranked by dollars lost, each with evidence rows you can verify yourself.

Fix and re-check

Apply the fix steps, run the monthly audit, watch the leaks stay closed.

Run it yourself

Press the button. This is what an audit looks like.

Twelve rules over 2,802 orders and 6 months of a real store, running exactly as they would in your admin — in batches, on request, and never on the storefront. Open any finding to see the evidence and the fix.

audit golden corpus dirty-store · 2802 orders · 6 months

found in the window $418.51 $69.75 in the median month — the part that comes back every month.

Refunds without restock

#10666 Pour-over stand · refunded $236.00 for 2 units · none returned to stock −$108.00
#11290 Pocket scale · refunded $126.00 for 3 units · none returned to stock −$54.00
#11500 order total $42.00 · refunded $62.00 −$20.00

Fix Check whether the goods physically came back. If they did, adjust the stock quantity by hand — the refund will not do it retroactively.

6 of the twelve rules found something: $418.51, with the evidence under each one.

Reads what you already have

Works with your money stack

WooCommerce

HPOS

Stripe

PayPal

CSV export import

WP-CLI

Zero-egress

Your numbers never leave the store.

The whole audit runs inside WordPress — 2,802 orders and 6 months of them, read on your own server. Gateway payouts come from CSV exports you upload. Outward: the licence check, and nothing else.

Pricing

Cheaper than your smallest leak.

No upsells, no surprises.

Pro

$69 /year

1 store

Get it on avakode.com

What runs where in Profit Forge

Which work happens inside your own install, what leaves it, what needs a paid plan, and what a lapsed licence leaves behind.

What the free tier does inside your own install

Evidence rows + fix steps in $
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.

What leaves your site when a feature is on, and where it goes

Findings are computed over your own WooCommerce tables; no order line is sent to Stripe.
Pro reads payouts and fees from https://api.stripe.com/v1 with your key, read-only.
Licence checks POST to https://api.avakode.com.

What needs Pro, credits or an outside service

Pro is a separate plugin under pro/; the free rules run without it.
Reading Stripe payouts and fees needs your own Stripe key.

What happens when the licence lapses

The licence transport has an explicit expired outcome; Pro rules stop and the free ruleset keeps running.
An expired licence is parsed as such rather than read as a network failure.
A lapse removes no findings: the table survives until uninstall, and even then the `pforge_keep_data_on_uninstall` option keeps it.

How long data is kept, and how you take it out

Uninstalling drops the findings table unless the option `pforge_keep_data_on_uninstall` is set to 1.
Pro exports a report as CSV.
Findings are kept indefinitely on a live site; the findings table is append-only and nothing prunes or expires old rows.

The same five questions for every tool →

FAQ

What store owners ask first

Does my sales data leave the store?

No. The whole analysis runs inside WordPress; the only thing that ever goes out is your licence check.

What if my store is clean?

Then the report says zero — and that's the point. The rules are tuned on a golden corpus where a clean store produces no findings, so anything it does flag deserves attention.

How is this different from a reporting plugin?

Reports tell you what you earned. Profit Forge tells you what you should have earned but didn't — by reconciling money in against money out and disputing the difference.

Will it work with my payment gateway?

Fee reconciliation ships with the major WooCommerce gateways first; every other rule — shipping, coupons, taxes, refunds, duplicates — works on any store.

Bring a torch