Keep reading
All updates More in this category
Built with farmers.
Shipped in weeks.
Fifteen minutes with Ari. Bring the thing you wish your software did, and he'll tell you if it's already built.
what-a-hold-wont-stopCreating a hold tells members about orders it can't stopAugust 25, 2026Customer experienceThe hold dialog now says plainly that orders past cutoff and paid shop orders still come — before a member is surprised by one.Member account → Holds → Create hold
![]()
A member puts a hold on their deliveries for two weeks and reasonably assumes everything in those two weeks is paused. But a hold can't stop an order that's already past its cutoff, and it never stops a shop order. Nothing told them that — so a box still arrived, their card was still charged, and you heard about it.
The Create hold dialog now says it plainly, every time: orders past their cutoff, and anything already bought in the farm's shop, can't be skipped by a hold. And when the dates a member picks actually cover one of those orders, an alert names it specifically — the delivery date, that its cutoff has passed, and that it will still be delivered and charged. Shop orders get called out on their own.
It stays tidy — one line per delivery rather than per item, and farms are only named when a member buys from more than one, so most people never see the extra detail. And it never blocks anything: the member can still place or edit the hold exactly as before.
Hold behavior itself hasn't changed. This is about telling members the truth while they're making the decision, instead of after the charge.
.jpeg)
-p-500.png)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.png)
