---
title: Corrections: how we fix mistakes | Working Coupons
url: https://working-coupons.com/corrections/
source: Working Coupons (working-coupons.com)
---

# Corrections: how we fix mistakes | Working Coupons

## What counts as a correction

A correction is any change we make because something we published was wrong or out of date in a way a reader could rely on. Examples: a store fact that does not match what the country storefront shows, such as a delivery threshold, a return window or a currency; a label that does not match the test record, for example a code shown as Works · tested {date} when our latest test failed; a date that is wrong; or a sentence on a store or guide page that says more than the source supports.
A code that stops working is not, by itself, a correction. Codes expire and stores change rules, and that is what the labels are for. When a code fails our test it is shown as Failed our test · {date}, and when an offer ends it is shown as Ran until {date}. Those changes appear on the page and in the public ledger at /tested/. If we showed a code as working when our own record said otherwise, that is a correction and it is logged here.
## How to tell us

Email hello@working-coupons.com. The same address handles codes, corrections and store questions. It helps if you include the page address, the country, what you think is wrong and, if you have one, a link to the store page that shows the correct information. You do not need to send personal details, order numbers or screenshots of your account, and we will not ask for them.
You can also use the "Did it work?" vote on a code. Votes are counted once per visitor per day per code and stored as a one-way hash, never the IP address. They are shown after at least three votes. A vote is a signal to retest, not a correction in itself; reader reports stay unverified until we test them.
## How we check a report

For a code, we run the same test we always run: a guest basket on that country's storefront, a made-up control code first, which must be rejected, then the code itself, a cropped and dated screenshot of the coupon line, and an emptied cart. We never pay, sign in or enter personal data. Stores that block automated browsers are tested by hand on a phone. The result goes into the code's history and the public ledger whichever way it goes.
For a store fact, we re-read the storefront page for that country, in its currency, and update the source link and read date. The editor responsible for that category then reviews the change: they check the fact against its source link, check the labels and dates on the page, and re-read the page after the data changes. Huda Al-Mansoori reviews fashion, beauty and babies; Khalid Al-Rashidi reviews marketplaces, electronics, home and bank offers; Mariam Al-Kuwari reviews food, groceries, travel, health and guides. If the source still shows what we published, we reply and explain what we read and when.
## How fixes are logged

Each correction is listed on this page with the date it was made, the page it affects and a short, plain description of what changed: what we said, what is correct, and where the correct information comes from. We do not quietly rewrite a page and move on. The corrected page itself carries the new read date or test date, so the fix is visible in both places.
Test results, including the ones a correction triggers, are also published in the ledger at /tested/ and in the CSV and JSON data, released under CC BY 4.0. Anyone can compare our labels with our own record.
