# Adding stops and visits to delivery runs

Stops let you add a visit to an own-vehicle delivery run that isn't an order delivery. Typical examples are collecting a purchase order from a supplier, setting up equipment at a customer, or dropping off paperwork. A stop has its own address, duration and optional arrival window, sits on a run alongside your deliveries, is included when the run's route is optimised, and is marked as complete once it's done.

> **Warning:**
> Don't use a stop to deliver an order. Schedule the order's delivery as usual instead, so its stock, paperwork and invoicing are all handled. Linking an order to a stop is only for your own records, and doesn't deliver or fulfil it.

You need the **Deliveries** permission to add, edit or complete stops.

## Adding a stop

You can add a stop from three places:

- **A delivery date** - go to **Deliveries**, open the date, then choose **Actions** -> **Add a stop/visit**. The date and site are filled in for you.
- **A customer or supplier** - on their page, choose **New** -> **New delivery stop**. The customer/supplier and their delivery address are filled in for you.
- **A purchase order** - choose **Arrange a collection**. See [Collecting a purchase order](#collecting-a-purchase-order) below.

![The Add a stop/visit form with the Stop type set to Stop](https://storage.googleapis.com/breww-user-uploads/markdown-embedded/cfe84d3df246f2db96a89d67ac1cfc6aeb14ddc0eafea0461eda25afbebd8665.png)

The form has these fields:

- **Stop type** - choose **Stop** for a general visit, **Collect purchase order** to collect goods from a supplier, or **Overnight rest** to rest a vehicle overnight on a multi-day run (see [Planning multi-day delivery runs with overnight rests](https://breww.com/docs/multi-day-delivery-runs/)). The type can't be changed once the stop has been added.
- **Name** - what the stop is for, such as "Set up bar at summer festival". This is what you'll see on the run.
- **Date** - the day of the stop.
- **Customer/supplier** - optional. Link the stop to a customer or supplier so you can see who it's for.
- **Order** - optional, and only for your own records. Once you've chosen a customer, this list only shows that customer's orders.
- **Address** - where the stop is. This is filled in from the customer/supplier, order or purchase order you link, and you can enter any address to override it.
- **Duration (minutes)** - how long the vehicle spends at the stop.
- **Arrival window start** and **Arrival window end** - leave both blank if the stop can happen at any time. Set both to the same time for a fixed arrival time.
- **Notes** - anything the driver needs to know.
- **Site the run departs from** - the site whose runs the stop belongs to.

If you link a customer and an order, or a supplier and a purchase order, they must match. Breww will tell you if you pick an order or purchase order that belongs to someone else.

## Collecting a purchase order

When you need to collect goods from a supplier yourself, open the purchase order and choose **Arrange a collection**. Breww opens the stop form with:

- **Stop type** set to **Collect purchase order**
- the purchase order, supplier and supplier's address filled in
- the purchase order's delivery date as the date, as long as that date hasn't already passed
- the purchase order's **Site delivered** as the site the run departs from

The **Name** is optional for a collection. Leave it blank and the stop is shown as "Collect purchase order" followed by the purchase order number.

> **Note:**
> Collecting a purchase order doesn't receive its goods into stock. Once the goods are back, create an inventory receipt as usual. See [Inventory receipts](https://breww.com/docs/inventory-receipts/).

## Stops on the deliveries page

Stops appear in your own-vehicle deliveries for their date with a pink **Stop** badge, alongside your deliveries and uplifts. You can put a stop on a run in the same way as a delivery, and stops are included when you optimise routes. On the run and its map, a stop is a numbered drop like any other.

If a stop is linked to a customer, any vehicle attributes that customer requires also apply to the stop, so it's only routed to a suitable vehicle. With the Advanced Deliveries addon, the stop's arrival window is taken into account when optimising.

## Viewing and editing a stop

Use the view button on a stop's row to open its page. This shows the address, date, arrival window, estimated arrival time and run, along with the duration, linked customer/supplier, order and purchase order, the site, notes, and who arranged the stop and when. Use **Prev** and **Next** to move between the drops on the same day.

To change a stop, use the pencil button on its row, or **Edit stop** on its page. You can edit a stop until it has been completed or its run has been locked.

- Changing the stop's **Date** or **Site the run departs from** takes it off its current run, as a run is for a single date and site.
- Changing the address, duration or arrival window keeps the stop on its run, but the run's arrival times no longer apply. Optimise the run again to get fresh times.

## Completing a stop

On the stop's page, the **Completion** card lets you add optional **Completion notes**, such as what was collected or who was seen, then select **Mark stop as complete**. The card then shows when the stop was completed, by whom, and the notes.

Drivers can also complete stops from the Breww app, adding a note as they do.

With the Advanced Deliveries addon, the **Photos** card on the stop's page lets you upload photos, and drivers can take photos of a stop in the Breww app. [Find out more about Advanced Deliveries](https://breww.com/features/advanced_deliveries/).