Minimum order value lets you set an order value threshold that customer orders must meet. This guide explains how it works, what your customers will see, and how the two action modes — Notify and Reject — differ.
Setting it up
You can configure minimum order value from your hub settings under the Orders section. There are three settings to look for:
Minimum Order Value — the order value amount customers need to meet (e.g. £30). Set this to £0 or leave it blank to disable the feature.
Minimum Order Value Action — choose Notify (default) to include orders below minimum and alert your crew, or Reject to exclude those orders and email the customer.
Core product exempt from minimum — toggle this on if you want to skip the minimum order check for any delivery that contains a core product (e.g. a veggie box).
How it works
When you set a minimum order value on your hub, every customer's order is checked against that threshold. How the system responds depends on the customer type and your chosen action mode.
New sign-ups and guest checkout are always blocked from completing checkout if their basket is below the minimum. This applies regardless of your Notify/Reject setting.
Existing subscribers can always save changes to their order, even if it drops below the minimum. They'll see a warning, but they won't be locked out. This is intentional — it lets customers reorganise their order (remove items, then add replacements) without getting stuck.
Notify vs Reject
You can choose what happens when an existing customer's order is still below minimum at delivery time.
Notify (default)
The order is included in the delivery event. Your crew receives an email listing which customers are below minimum, with wording like:
The following customers have orders below the minimum order value of £30. Their orders have been included but you may wish to follow up.
The customer is not contacted. It's up to you to decide what to do.
Reject
The order is excluded from the delivery event — it's skipped entirely, just like a customer over their debt limit. Your crew email changes to:
The following customers' orders have been rejected because they are below the minimum order value of £30. These customers have been notified by email.
The customer receives a rejection email letting them know their order wasn't processed and asking them to log in and update it. This email template is customisable from your Customer Emails settings under "Minimum Order Rejection".
Watch out for double emails
If you're using Reject mode and you close orders, customers below minimum will receive a rejection email at that point. If you then delete those orders and close them again, those customers will receive another email. Be mindful of this if you're closing and then deleting orders — your customers will get notified each time.
What your customers see
When a subscriber edits their order and it drops below the minimum for the first time, they see a pop-up dialog letting them know. If they continue making changes while still below minimum, the dialog doesn't keep reappearing — but a persistent red warning banner stays visible in their subscription drawer until they bring their order back up.
For example, if your minimum is £30 and a customer removes an item bringing their order to £25, they'll see:
Your Wednesday order is £25.00 but the minimum order is £30.00.
If you have configured the settings to Notify instead of Reject, they'll see:
Your Wednesday order is £25.00 but the minimum order is £30.00. Your order will still be submitted but may be subject to review.
Core product exemption
If you enable "Core product exempt from minimum", the minimum order check is skipped for any delivery that includes a core product (e.g. a veggie box). This applies to both subscriptions and pre-orders.
Examples (minimum order: £30)
Order | Core product exemption OFF | Core product exemption ON |
£40 of add-on produce | Above minimum | Above minimum |
£15 Veggie Box + £10 add-ons = £25 | Below minimum | Exempt (contains core product) |
£15 Veggie Box only | Below minimum | Exempt (contains core product) |
£15 of add-on produce | Below minimum | Below minimum (no core product) |
Multi-week orders and worst-case calculation
Many customers have items at mixed frequencies — some weekly, some fortnightly. When this happens, the system calculates the worst-case subtotal: the lowest amount the customer would pay in any single delivery week.
This matters because the minimum must be met every week, not just on average.
Example: minimum order £30
A customer orders:
- Veggie Box — weekly — £20
- Fruit Box — fortnightly — £15
In alternating weeks, their order looks like:
Week | Items | Subtotal | Meets £30 minimum? |
Week 1 | Veggie Box + Fruit Box | £35 | Yes |
Week 2 | Veggie Box only | £20 | No |
Week 3 | Veggie Box + Fruit Box | £35 | Yes |
Week 4 | Veggie Box only | £20 | No |
The worst-case subtotal is £20 (the weeks without the Fruit Box), so this customer is below minimum. Even though every second week they'd be at £35, the system flags the order because there are weeks where it falls short.
To fix this, the customer could either:
Increase their weekly items to meet the minimum on their own, or
Switch the Fruit Box to weekly
Another example: minimum order £15
A customer orders:
2 x Milk — weekly — £6
2 x Eggs — weekly — £6
Veggie Box — fortnightly — £15
Week | Items | Subtotal | Meets £15 minimum? |
Week 1 | Milk + Eggs + Veggie Box | £27 | Yes |
Week 2 | Milk + Eggs | £12 | No |
Worst-case subtotal is £12, so this is below minimum — even though the average across two weeks is £19.50.
If core product exemption is on, this order would be exempt in weeks where the Veggie Box is delivered (it's a core product), but would still be below minimum in the off-weeks when only Milk and Eggs are delivered. The exemption only applies to delivery weeks that actually contain a core product.
Summary
Scenario | What happens |
New sign-up below minimum | Checkout blocked |
Existing subscriber saves below minimum | Allowed with warning |
Delivery closes — Notify mode | Order included, crew notified |
Delivery closes — Reject mode | Order excluded, customer emailed |
Order contains core product (exemption on) | Minimum order check skipped for that delivery |
Mixed-frequency order | Checked against worst-case (lowest) week |
