You've just realised your WooCommerce store has been charging the wrong VAT. Maybe a customer queried 20% VAT on a zero-rated children's t-shirt, or your bookkeeper spotted that a chunk of standard-rated sales went out with no VAT at all. Either way, your VAT returns now contain numbers that don't match reality.
The good news: this is fixable, and HMRC has a clear process for it. The trick is knowing two things. First, how to find and fix the plugin setting that caused it, so it stops getting worse. Second, how to correct the VAT you've already declared, which depends on the size of the error.
This guide walks you through both. It's written for self-hosted WooCommerce sellers, where the responsibility for getting VAT right sits entirely with you, not with a marketplace. We'll use the current 20% standard rate for 2025/26 throughout and link every rule to the relevant gov.uk page.
A quick note before we start: this is general guidance, not advice on your specific store. VAT errors compound quietly, so if the numbers are large or you're unsure, get them checked before you file.
Why is WooCommerce different from Amazon or eBay for VAT?
With self-hosted WooCommerce, you are the only party responsible for VAT. There's no marketplace acting as a deemed supplier and no platform filing a report on your sales, so every figure on your VAT return is one you declared yourself.
That's the key distinction, and it changes how seriously you treat a plugin misconfiguration.
On an online marketplace like Amazon or eBay, the marketplace can be liable for the VAT on certain sales. For goods in consignments not exceeding £135 sold to UK customers through an online marketplace, the marketplace is liable for the VAT, and the seller is treated as making a zero-rated "deemed supply" to the marketplace (gov.uk: VAT and overseas goods sold using online marketplaces). Those platforms also report seller information to HMRC under the reporting rules for digital platforms, which took effect from 1 January 2024 with the first reports due by 31 January 2025 (gov.uk: Reporting rules for digital platforms).
WooCommerce is none of that. It's software running on your own hosting. There is no marketplace operator, no deemed-supplier VAT collection, and no digital-platform report filed about your store. You self-declare everything.
So when the plugin gets the VAT wrong, nobody else is catching it for you. The error flows straight onto your return, untouched, until you find it. That's why a single wrong tax-class setting can quietly distort months of returns.
Selling through your own WooCommerce store is one of our core niches. If you'd rather hand the VAT side to a specialist, see how we support ecommerce businesses.
How do I know my WooCommerce VAT plugin is set up wrong?

The fastest signal is a mismatch between what your store collected and what your accounts say you should have collected. If your VAT control account and your WooCommerce tax reports diverge, something in the configuration is off.
Here are the symptoms worth checking for:
- A customer or supplier queries the VAT on an invoice. This is the most common trigger. Zero-rated goods showing 20% VAT, or standard-rated goods showing none.
- Your effective VAT rate looks wrong. Divide the VAT you collected by your net standard-rated sales. If you sell only standard-rated goods and the figure isn't close to 20%, dig in.
- Box 1 and Box 6 don't relate sensibly. On a standard-rated-only store, output VAT in Box 1 should be roughly 20% of the standard-rated portion of Box 6. A big gap points to mis-rated products. Box 1 is "VAT due in the period on sales and other outputs" and Box 6 is the "total value of sales and all other outputs excluding any VAT" (gov.uk: How to fill in and submit your VAT Return, Notice 700/12).
- New products default to the wrong tax class. A product added without an explicit tax class inherits the store default. If that default is wrong, every new line is wrong.
- Prices flip between VAT-inclusive and VAT-exclusive at checkout in a way you didn't intend.
If any of these ring true, treat it as a configuration fault until proven otherwise, then quantify it before you touch a return.
What settings cause over or under-charged VAT in WooCommerce?
Most WooCommerce VAT errors trace back to one of four settings. Knowing which one broke tells you both how to fix it and which sales were affected.
| Setting | What goes wrong | Typical VAT effect |
|---|---|---|
| Standard tax rate | Rate left blank, set to 0%, or set to an old figure instead of 20% | Under-charges output VAT on standard-rated sales |
| Product tax class | A zero-rated or reduced-rated item left in the "Standard" class (or vice versa) | Over or under-charges on those specific products |
| "Prices entered with tax" | Set to "inclusive" while you enter net prices, or the reverse | Calculates VAT on the wrong base, distorting Box 1 and Box 6 |
| Tax based on address | Charging UK VAT on sales that should be treated differently, or applying the wrong rule by region | Wrong VAT on cross-border or specific-location sales |
A couple of these deserve a closer look.
The tax-class trap
WooCommerce lets you assign each product a tax class: Standard, Reduced rate, or Zero rate (you can add your own). The plugin then applies whatever rate you've configured for that class. The UK standard rate is 20%, the reduced rate is 5%, and the zero rate is 0% (gov.uk: VAT rates).
The problem is that the default for a new product is usually "Standard". If you sell genuinely zero-rated goods, such as most children's clothing or certain books, and you forget to move them into a Zero rate class, the store charges 20% on something that should carry no VAT. That's an over-charge to your customer and an over-declaration on your return.
The inclusive-versus-exclusive mix-up
WooCommerce has a "Prices entered with tax" option. If you enter your catalogue prices as net (VAT-exclusive) figures but the setting says prices already include tax, the maths runs the wrong way and your VAT and net values both come out wrong. Always confirm this setting matches how you actually type your prices in.
How do I fix the WooCommerce settings so it stops happening?
Fix the configuration before you correct any returns. Otherwise you're cleaning up history while the error keeps generating new mistakes.
Work through this in order:
- Confirm your standard rate is 20%. In your tax settings, check the standard rate row shows 20% for the UK and applies to the right region.
- Audit your tax classes. Export your product list and check each item sits in the correct class: Standard for most goods, Zero rate for genuinely zero-rated lines, Reduced rate where 5% applies. Use the gov.uk VAT rates page and the detailed rate guidance to confirm the liability of anything you're unsure about.
- Check "Prices entered with tax" matches how you key in prices. Decide on net or gross and keep the whole catalogue consistent.
- Set a safe store default tax class so new products don't silently inherit the wrong one.
- Place a test order in each class and confirm the VAT line on the order and the invoice is exactly what you expect.
- Reconcile a sample period. Pull your WooCommerce tax report for one past quarter and tie it back to the VAT return you filed. The gap you find is the error you now need to correct.
Once the store is calculating correctly going forward, you can deal with the periods already filed.
How do I correct the VAT I've already declared to HMRC?
The method depends on the size of the net error and whether it was deliberate. Small, innocent errors are corrected on your next return. Larger ones must be reported to HMRC separately.
First, work out the net value of the errors. You add up the total VAT due to HMRC because of the errors, then the total VAT due to you, and take the difference. It's one net figure across all the affected periods, not each error counted on its own (gov.uk: How to correct VAT errors, Notice 700/45).
Then apply the thresholds:
| Net error value | Was it deliberate? | What you do |
|---|---|---|
| £10,000 or less | No | Adjust on your next VAT return (Method 1) |
| Between £10,000 and £50,000, and 1% or less of your Box 6 figure | No | Adjust on your next VAT return (Method 1) |
| Between £10,000 and £50,000, and more than 1% of your Box 6 figure | No | Report to HMRC separately (Method 2) |
| More than £50,000 | No | Report to HMRC separately (Method 2) |
| Any amount | Yes | Report to HMRC separately (Method 2) |
These thresholds and the netting rule come straight from gov.uk: How to correct VAT errors and make adjustments or claims (VAT Notice 700/45).
Method 1: adjusting on your next return
If you're within the limits above, you simply adjust your VAT account and include the net value of the correction on your current return. If you under-declared output VAT, you add it to Box 1. If you over-declared, you reduce Box 1 (or add the recoverable amount to Box 4 where appropriate). Keep a clear record of the error, how you worked it out, and the period it relates to.
Method 2: reporting to HMRC separately
For errors above the thresholds, or any deliberate error, you notify HMRC separately rather than burying the adjustment in a return. HMRC withdrew the old paper form VAT652 in September 2025; you now report online using HMRC's "tell HMRC about errors in your VAT Return" service, signing in with your VAT account (gov.uk: Correct errors in your VAT Return). You can still use Method 2 voluntarily for smaller errors if you'd prefer a clean separate record.
The 4-year time limit
You can generally only correct errors made in the previous 4 years. The limit runs from the end of the accounting period the error was in (or from the return's due date for under-claimed input tax). Deliberate errors have no time limit (gov.uk: VAT Notice 700/45). You also need to keep your VAT records for at least 6 years (gov.uk: keeping VAT records), so the evidence to support a correction should still be available.
Worked example: a netting and threshold walkthrough
Illustrative example. Priya runs a self-hosted WooCommerce store selling homeware and a small children's clothing range. She is VAT-registered and files quarterly. During a year-end review she finds two plugin errors spanning four past quarters.
Error 1: a batch of standard-rated homeware was left in the wrong tax class and went out with no VAT. Net sales affected over the four quarters were £18,000, so the under-declared output VAT is:
£18,000 x 20% = £3,600 due to HMRC.
Error 2: her children's clothing, which is zero-rated, was wrongly sitting in the Standard class for one quarter, so the store charged 20%. Net sales affected were £6,000, meaning she over-declared:
£6,000 x 20% = £1,200 over-declared (due to Priya).
Now she nets the two off:
£3,600 due to HMRC minus £1,200 due to Priya = £2,400 net error.
The net error is £2,400, which is well under £10,000. The error was innocent, a plugin misconfiguration, not deliberate. So Priya can use Method 1 and adjust on her next return: she'd increase Box 1 by the £2,400 net under-declaration and keep her workings on file.
Now change the numbers. Suppose the under-declaration had instead been £30,000 of VAT and the over-declaration £6,000, giving a net error of £24,000. Her Box 6 (total net outputs) on the return where she discovers it is £600,000, so 1% of Box 6 is £6,000.
£24,000 is between £10,000 and £50,000, and it's more than the £6,000 (1% of Box 6) limit. That tips her into Method 2: she must report the £24,000 to HMRC separately through the online error correction service, not just adjust the return.
The lesson: it's the net figure, measured against both the £10,000 floor and your own 1%-of-Box-6 line, that decides the route.
What if I overcharged VAT to my customers?
If the plugin charged VAT that shouldn't have applied, you've collected money from customers that wasn't really VAT. Correcting your return is only part of the job. Where you've overcharged your customers, you generally need to refund them the overcharged amount before you can reduce the VAT you account for, and you must keep records of how you put it right (gov.uk: VAT Notice 700/45).
In practice that usually means issuing a credit note or refund for the wrongly charged VAT, then reflecting the corrected position in your VAT account. You can't simply pocket the difference, and you can't reduce your declared VAT while leaving customers out of pocket.
This is the part sellers most often get wrong, so if a meaningful number of customers were overcharged, it's worth getting the mechanics checked before you process refunds at scale.
Frequently asked questions
Will HMRC penalise me for a WooCommerce VAT error?
A genuine, promptly corrected error made with reasonable care is treated very differently from a careless or deliberate one. Correcting it through the proper method, keeping your workings, and not sitting on it all help. Penalties and interest are more likely where errors are large, deliberate, or left uncorrected. See gov.uk: VAT Notice 700/45 for the correction rules.
How far back do I have to correct WooCommerce VAT errors?
Generally 4 years. The limit runs from the end of the accounting period the error was made in, or from the due date of the return for under-claimed input tax. Deliberate errors have no time limit (gov.uk: VAT Notice 700/45).
Can I just fix it on my next VAT return?
Only if the net error is £10,000 or less, or between £10,000 and £50,000 and no more than 1% of your Box 6 figure, and the error wasn't deliberate. Above those thresholds, or for any deliberate error, you must report it to HMRC separately (gov.uk: Correct errors in your VAT Return).
Is form VAT652 still how I report a large VAT error?
No. HMRC withdrew form VAT652 in September 2025. You now report errors that exceed the adjustment thresholds online through HMRC's "tell HMRC about errors in your VAT Return" service, signing in with your VAT account (gov.uk: Correct errors in your VAT Return).
Does WooCommerce report my sales to HMRC like Amazon or eBay do?
No. WooCommerce is self-hosted software, not an online marketplace, so it doesn't act as a deemed supplier and doesn't file a digital-platform report about your store. Those reporting rules apply to platforms such as eBay and Etsy, not to your own WooCommerce site (gov.uk: Reporting rules for digital platforms). On WooCommerce, you self-declare everything.
Do I need to register for OSS if I sell to EU consumers?
The VAT One Stop Shop (OSS) Union scheme is for reporting distance sales of goods from Northern Ireland to EU consumers, not for goods sold from Great Britain (gov.uk: Register to report and pay VAT on distance sales of goods from Northern Ireland to the EU). If you're based in Great Britain and selling into the EU, the rules differ, so check your position before configuring any EU VAT in your plugin.
Talk to an e-commerce accountant →
Get your WooCommerce VAT corrected properly
A plugin setting that's off by one tax class can quietly distort months of returns, and the fix has to cover both the software and the VAT you've already filed. If you'd like that handled cleanly, talk to a Zmartly accountant about your ecommerce VAT. We'll reconcile your WooCommerce tax reports to your returns, work out the net error, and correct it through the right HMRC method.





