How to configure "Delivery rules" to automatically schedule your deliveries

Getting Started Guide Opdateret 04/09/2026 6 min. læsning

Delivery rules can tell Breww how to schedule your deliveries automatically. This allows for deliveries to be easily organised onto the correct dispatch date and via the correct method (such as your own vehicle or a courier).

The delivery rules feature can be found in Settings -> Delivery settings-> Delivery rules. Rules always have a "Start" point, and then you can add "Conditions" (logic/decisions) to guide Breww to the right end result. Here's a screenshot of an example rule, which hopefully shows the power available to you and how intuitive it is to configure even very complex rules.

To further explain this, we've created a short video guide to walk you through how to configure this example rule in Breww:

It's worth noting that you can link multiple "Condition" results (the green ✓ or red ✗) to the same "Delivery" outcome. This can help you to save space, reduce clutter in your rules and ensure they're easy for you to understand and maintain in the future.

Note: If you use the Total value condition, be aware that non-revenue charges don't contribute towards the total value. In practice, this means container deposits from a deposit scheme that's set not to count deposit charges as revenue. You'll also see this explained on an information icon beside the condition while building your rules.

Note: The rules editor is best used on a desktop computer or another device with a wider screen.

How Breww works through your rules

Breww starts at the "Start" node and follows a single path through your rules. At each "Condition" it checks the order and takes either the green ✓ or the red ✗ branch. The first "Delivery" outcome it reaches is the one that's used, so exactly one outcome applies to any given order.

Because of this, the order in which you chain your conditions matters. Put your most specific conditions earlier in the chain, and use the last outcome on a path as your catch-all.

Every node needs to be fully connected for your rules to run. If Breww follows a branch and finds nothing connected to it, it stops without scheduling anything for that order rather than guessing.

Delivery rules only run for orders that require fulfillment, so an order with nothing to deliver is skipped.

What a "Delivery" outcome can set

Each "Delivery" outcome decides what actually happens to a matching order:

Schedule type - either schedule a delivery, or explicitly don't schedule one. Choosing "Do not schedule delivery" is useful as a deliberate catch-all for orders you want to handle by hand.
Delivery type - your own vehicle, a collection, or a courier. When you choose a courier, you then pick the courier and (optionally) the courier service to use. Only couriers you've enabled under Settings -> Delivery settings -> Couriers you use are available here.
Set delivery date to this many days after the order/organised date - 0 for the same day, 1 for the next day, and so on. This counts from the order date, or from the date you press the button if you're applying the rules manually.
Use delivery area's next delivery date - available for own-vehicle deliveries. When the order falls into a delivery area, Breww uses that area's next delivery date instead of the number of days above. Where more than one of your areas covers the address, Breww uses the one with the soonest run.
Delivery charge structure to apply - see Calculating delivery charges automatically.
Fulfillment site to assign and lock - see below.

Whichever way the date is worked out, Breww then moves it forward if it lands on a day you don't work or a day the customer is closed for deliveries, using the working days set in your general delivery settings.

Note: A delivery charge structure applied directly to the customer, their parent company or their customer type takes precedence over one set by a rule. A rule's charge structure is only used when there isn't one already on the order and the customer has none of their own.

When your rules are applied

Once your rules are set up, you can choose when Breww applies them automatically. Two switches at the top of the rules editor control this, and both are off until you turn them on:

Automatically schedule on order confirmation - Breww applies your rules as soon as an order is confirmed.
Automatically schedule when order is paid in full - Breww applies your rules once there's nothing left to pay on the order. Breww won't do this if the order already has a delivery or collection scheduled.

Your rules can also be applied on demand, without either switch turned on:

The Apply delivery rules action on an individual order.
The Apply automatic delivery rules bulk action on the Orders awaiting delivery list, for handling a batch of orders at once.
When creating an order, by choosing the delivery rules option for scheduling.
When orders arrive from a sales platform integration, or through your Trade Store.

Automatically assigning a fulfillment site

Each "Delivery" outcome in your rules has an optional "Fulfillment site to assign and lock" field. This lets a rule decide which of your sites an order should be fulfilled from, rather than leaving it to Breww's automatic, stock-based site selection.

When an order matches a rule that has this field set, Breww will:

Assign the order to the chosen site, and
Lock it to that site, so that Breww's automatic site selection won't move the order to a different site later on.

This has the same effect as manually choosing a site and enabling the "lock to this site" option on an order, but it happens automatically whenever the rule runs. For more on manual site selection and how Breww picks a site when no site is locked, see How to set which site will be used for which customers or handle "consignment"/"sale or return" stock.

Note: Only sites that can fulfill orders and aren't restricted to linked customers only can be selected here. This is the same set of sites that's available when choosing your brewery's default fulfillment site.

If you'd rather leave the site choice to Breww's automatic selection for a particular rule, simply leave this field blank.

When the site is left unchanged

To avoid disrupting orders that are already underway, Breww will leave the fulfillment site unchanged in these cases, even if a rule with a site set matches:

The order is already locked to a site (whether locked manually or by an earlier rule).
The order's delivery has already progressed, for example it's on a delivery run, has passed the duty point, or has had stock allocated to it.

Where this applies

The fulfillment site is assigned and locked wherever your delivery rules run, including:

When an order is confirmed
When you use the manual "Apply delivery rules" action
When an order is paid in full
When an order is first created
When orders are imported from an integration
In the Trade Store

When a rule sets the site, the order's activity log records that the fulfillment site was assigned (and notes that this was done by your delivery rules). The delivery-date log entry will also note when the delivery date was set by your delivery rules.