Skip to content
Working Coupons

Contact Working Coupons: codes, corrections, stores

What to write to us about

Codes. If a code on our pages did not work for you, tell us. If you found a code we do not list, send it too. Reader submissions are shown as unverified until we test them, and a code only gets a "Works · tested {date}" label after it passes our own basket test. If it fails, it is shown as "Failed our test · {date}", not removed quietly.

Corrections. If a store fact is wrong, such as a delivery threshold, a return window or a currency, tell us which page and which line. Store facts are read on that country's storefront, in its currency, with the source link and read date, so a correction is usually a matter of re-reading the source and updating the fact.

Store questions. If you represent a store, or you are a shopper with a question about how a store appears on our pages, write to the same address. We cannot place orders, track deliveries or handle refunds for any store; those questions belong with the store itself.

What helps us act quickly

For a code: the store, the country storefront you used (for example the UAE or Saudi site), the code exactly as you typed it, the date you tried it and the message the cart showed. A short description of the basket, such as the category or rough total, helps when a code has a minimum spend or excludes some items.

For a correction: the page address, the sentence or number you think is wrong, and where you saw the right one. A link to the store's own page is the most useful thing you can send, because that is the source we check against.

You do not need to send screenshots of your account, order numbers or anything that identifies you. Please do not send card numbers, passwords or personal documents. We never need them, and we do not use them in our own tests: we test with a guest basket, never sign in, never enter personal data and never pay.

What happens after you write

A reported code is queued for testing. We test on the country storefront with a guest basket, try a made-up control code first (it must be rejected), then the listed code, and keep a cropped, dated screenshot of the coupon line before emptying the cart. Stores that block automated browsers are tested by hand on a phone. The result goes to the public ledger at /tested/ and into the CSV and JSON data, published under CC BY 4.0.

A correction is checked against its source link. If the fact was wrong, we fix it and log the change on /corrections/ with the date, so anyone can see what changed and when. If the source still says what we wrote, we reply with the link and the read date.

An editor reviews the page after each data change. Editors check every fact against its source link and check that labels and dates are right; they do not add facts of their own.

Reader votes and your privacy

You can also tell us whether a code worked without writing an email. The "Did it work?" vote under each code allows one vote per visitor per day per code. It is stored as a one-way hash, never your IP address, and the count is shown only after at least 3 votes. Votes are a signal for what to test next; they do not replace our own test.

When you email us, we use your message to answer you and to act on what you reported. The site itself runs no third-party scripts, no ads and no cross-site cookies; the full detail is on our privacy page.

Commercial questions

Some codes on the site are our affiliate-network codes, and when a reader buys with one the network may pay us a commission. That never changes the order of offers, which follows evidence: our network code, then codes tested in the last 3 days, the store's own offer, bank offers, codes listed elsewhere, and finally codes that are not working. Links to stores go through /go/ and are marked sponsored. If you have a question about any of this, the same address applies, and the how-we-earn page explains it in full.

Send us a code or a correction