# Collecting non beer items

**URL:** <https://community.breww.com/t/collecting-non-beer-items/4351>\
**Category:** Ideas & feature requests\
**Tags:** idea-duplicate\
**Created:** [13 May 2024 08:41 UTC](https://community.breww.com/t/collecting-non-beer-items/4351 "2024-05-13T08:41:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jon-kyme2](https://community.breww.com/user_avatar/community.breww.com/jon-kyme2/32/1926_2.png) [@jon-kyme2](https://community.breww.com/u/jon-kyme2)\
**Post date:** [13 May 2024 10:13 UTC](https://community.breww.com/t/collecting-non-beer-items/4351/2 "2024-05-13T10:13:48Z")

</div>

There’s a FR:

> [@Include a "visit" on a (delivery) run/route](https://community.breww.com/t/include-a-visit-on-a-delivery-run-route/1700):
>
> I can think of a number of situations in which it would be useful to include a generic “visit” on a delivery run. We often drop bulk beer (in an Arlington) at 3rd party packagers. So even though this needn’t be associated with an order, it would be useful to have it on the Delivery Manifest, and ideally, have a delivery note (or similar) available. Likewise, collecting packaged beer. Currently, this can be worked-around by scheduling an “uplift” (with no containers), which does get the visit …

---

_[View the full topic](https://community.breww.com/t/collecting-non-beer-items/4351)._
