Clearer.io Address Validator

Should you install it?

This does one job and the long-tenure reviews say it does it: fewer undeliverable packages, fewer UPS and FedEx address-correction fees, and the ability to refuse PO boxes, parcel lockers or Packstations that your carrier won't deliver to. Understand before installing that on a non-Plus store it prompts the customer on the thank-you page after they have paid, so it reduces bad addresses rather than preventing them; 2024-25 reviewers suggest the in-checkout path now works with Checkout Extensibility, but nobody in this set confirms the old pre-payment blocking for non-Plus. The real current risk is not the checkout timing — it is a thin but unbroken line of merchants, most recently June 2026, saying the rules they configured simply did not fire while they were still being billed, and those are precisely the reports the developer did not answer. Support is the app's strongest and most consistently evidenced feature across nine years: specific requests get built, sometimes the same day, and several reviewers raised their rating after contact. Best fit is a US store with meaningful UPS/FedEx correction-fee exposure or a 3PL with hard field-length limits; if you ship mostly outside the supported country list, or need validation to hard-block before payment without Plus, look elsewhere.

Fair evidence. The positive case rests on a large, specific, multi-year body of reviews from merchants at 1-5 years of use, which is solid. The current-state case does not: only 8 reviews in the last 12 months, two with no text, and the single recent negative is four words in Dutch ('Werkt niet.'), so the 12.5% recent negative share is one review and cannot be read as deterioration. 43% of all reviewers had the app under a month and at least 13 reviewed within a day, and a large block praises a named support rep without saying anything checkable about validation accuracy — both dilute the evidence. I can judge what the app is for and who it has served well; I cannot confidently judge its 2026 reliability, the current pricing (the $0.03-per-order figures are 2020-vintage), or whether the recurring 'rules don't fire' reports are a real defect or misconfiguration, because the developer never replied to them.

What will annoy you

Misses bad addresses, or configured rules don't fire at all — including house-number and character-length rules the merchant had switched on: 8 reviews, steady, last seen 2026-06.

How the developer behaves when it breaks

Replies on 5 of 8 negatives (62%), matching the stated rate, but only 21% overall. The replies split into two kinds. Where the complaint is about scope or billing, the reply is an explanation rather than a fix: the Plus/checkout limit is attributed to Shopify (2034, 4930, 4929, 3088), the billing dispute is answered with a dashboard count (6478), and the pricing model is defended (5538). Where the complaint is a concrete bug or a missing rule, they genuinely ship: a dropdown bug fixed fast enough that the reviewer raised 3★ to 4★ (0503), a Canadian merchant's issues resolved and review changed to 5★ (4495), parcel lockers deployed in under two hours (2223), Highway Contract boxes same day (5919), NZ and Romania coverage added on request (9961, 5469), ReCharge integration built after merchants asked (2957, 2696), city-length limits added for one store (3018). One store was helped to trace malicious code that turned out not to be theirs (8841). The gap worth knowing: the three bare 'it doesn't work' reports got no reply at all — 0750 (German, 2022-02), 5263 (2024-01) and 1913 (Dutch, 2026-06), the most recent negative in the set. So the pattern is responsive to specific, well-described requests and silent on vague breakage reports, especially non-English ones.