Early Access: This feature is being actively rolled out and may not be available to everyone yet. Contact support if you'd like early access.
Introduction
Customers can manage their own produce exclusions — their "Dislikes" — directly in your shop. A dislike is a produce item the customer never wants packed; once added, we note it on their order and packing materials.
You stay in control of how much they can do. Each shop has a limit you set for how many dislikes a customer may add themselves, and your staff can still add or remove exclusions on a customer's behalf in admin.
How it works at a glance
Customers see their dislikes on their Upcoming Orders page and on a dedicated "Dislikes" page in their account.
Removing a dislike is always allowed.
Adding a dislike is allowed only while the customer is under the limit you set.
A limit of 0 means customers can't add any dislikes themselves — but they can still remove ones already on their account.
Your staff can add exclusions in admin even beyond the customer's limit. The customer can then remove items to get back under it.
Setting your shop's dislike limit
The limit controls how many dislikes each customer can add for themselves. You can find this in the Orders section in your settings.
What the numbers mean:
0 (default) — customers cannot add dislikes. They can still see and remove any that already exist on their account.
1 or more — customers can add up to that many dislikes themselves.
The limit applies to what customers add themselves. It does not cap what your staff can record in admin — you can always add more on a customer's behalf. If a customer ends up with more dislikes than the current limit (for example, because your staff added some), they simply won't be able to add new ones until they're back under it. Nothing is removed automatically.
What your customers see
On the Upcoming Orders page: a "Dislikes" row summarises everything you won't be packing for them across all upcoming orders, with a "Manage" button alongside it that takes them to their Dislikes page.
On the Dislikes page (in their account): this is where customers manage their list. They'll see their current dislikes as removable chips, an "X of Y used" counter showing how much of their allowance they've used, and an "Add a dislike" search box for finding produce to exclude (when they have room under the limit).
The "Dislikes" link appears in a customer's account menu when your shop's limit is greater than 0 (i.e., there's something for them to add). Customers can always reach the page via the Manage button to remove existing dislikes.
Adding and removing dislikes
Adding: the customer searches for a produce item and selects it — the same smart search is used in admin, so typing "apple green" finds "Apple / Green". Once added, we leave that item out of every upcoming order.
Removing: the customer clicks the small 'X' on any dislike chip and confirms. We'll start packing that item in their orders again from their next order.
Removing is always available, even when your shop's limit is 0 or the customer is over the limit. This lets customers tidy up their own list at any time.
How parent and child produce behave
Some produce items are grouped as a parent with child varieties — for example, "Apple" (parent) with "Apple / Green" and "Apple / Red" (children). The system keeps a customer's dislikes tidy automatically:
Excluding a parent covers all of its children. If a customer excludes "Apple", they won't get any apple variety — and any individual apple varieties they'd already excluded are folded into the single "Apple" dislike.
Excluding a child when the parent is already excluded does nothing. The parent already covers it, so the customer sees a message saying so rather than a duplicate being added.
Adding the same item twice does nothing — no duplicates.
For more detailed information about your produce list and how the exclusions are applied, head to these articles:
Adding a parent counts as a single dislike even though it replaces several child dislikes. One edge case: if a customer is already at their limit, they can't add a parent that would tidy up several children, even though the end result would be fewer items. If a customer is stuck like this, removing a child first (or adjusting the limit) clears the way.
How this fits with staff-managed exclusions
Customer dislikes and the ongoing exclusions you record in admin are the same list — there's no separate customer-only set. That means:
Dislikes a customer adds appear in admin alongside any you've recorded and flow through to box labels for the packing team just like before.
A customer can remove an ongoing exclusion your staff added, since it's their list. If something must stay excluded, let the customer know rather than relying on it being locked.
This self-service feature covers ONGOING exclusions only. One-off exclusions (skipping an item for a single delivery) and replacements are still managed by your staff in admin. See this related article.
Conclusion
Letting customers manage their own dislikes saves your staff the back-and-forth of emailed requests while keeping you in control through the per-shop limit. Set a limit that suits your operation, and customers can fine-tune their boxes themselves — with the parent/child tidy-up and packing labels all handled automatically behind the scenes.