Flare: Delivery Date Picker

Should you install it?

This is a delivery-date picker that also controls which shipping methods and rates a customer sees, and the reviews say it handles genuinely awkward logic — dates by postcode or zip, per-product lead times, cut-off times, blackout dates and capacity limits — better than the date pickers merchants tried before it (3166, 8068, 0861). The consistent pattern is that the two founders configure it for you, up to manually entering long postcode lists and doing white-glove installs (2760, 2374), and build custom functionality on request (4436, 2068008-style requests in 6435, 7716). That is a real strength if you want it and a real dependency if you don't: the one merchant who described self-serving says the backend is overwhelming (6953), and there is no evidence in any review of what self-configuration looks like at scale. I looked specifically for billing surprises, data loss, silent breakage and support silence and found none — the only negative in 114 reviews is a site-glitch report from a store that uninstalled after 26 minutes in March 2025, which the founder answered publicly within two days (8836). Install it if you are a perishable-food, florist or gifting store with postcode-dependent dates and you want a vendor who will do the setup with you; be cautious if you need to own the configuration yourself, need a carrier other than FedEx named and proven, or need reporting on the feature.

Fair evidence. Three specific limits. One negative review in 114 gives almost no evidence about failure modes, so the failure section is built from caveats inside 5-star reviews rather than from merchants who were let down. About 18% of reviews were written within a week of install and several within hours (3009, 0127, 9581, 7049, 6452, 0250), so they describe onboarding, not operation. And roughly seven of the earliest reviews describe a different product entirely (6272, 6309, 2814, 5139, 8833, 9238, 9323), which inflates the count behind the current one. The long-tenure reviews at 8 to 11 months are what keeps this at medium rather than low.

What will annoy you

Doesn't fit out of the box for unusual setups — needs vendor tweaks, wording changes or custom work before it's right: 6 reviews, steady, last seen 2026-05.

How the developer behaves when it breaks

The founder replied publicly to the single 1-star within two days, apologised, gave his email address and offered free extended support (8836); the merchant never came back, so the outcome is unknown. In-app, reviewers repeatedly document problems being fixed: a date-selection bypass patched via chat (2324), a product-level issue "sorted it out right away" (0490), setup behaviour that didn't work as expected resolved by support (2527), ongoing tweaks delivered (8035), and a requested feature built within two weeks (4436). One caveat on the 80% reply rate: a large batch of replies is dated 2 to 6 February 2026 but sits on reviews from May to December 2025 (9581, 6583, 4806, 2839), so much of the reply rate is a retroactive backfill and doesn't evidence in-the-moment responsiveness. Those replies are also keyword-heavy listing copy naming features the merchant never mentioned — treat them as marketing, not as facts about the install.