# Stock take per location

**URL:** <https://community.breww.com/t/stock-take-per-location/3065>\
**Category:** Ideas & feature requests\
**Tags:** idea-not-required\
**Created:** [31 August 2023 08:31 UTC](https://community.breww.com/t/stock-take-per-location/3065 "2023-08-31T08:31:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![justin-hutton](https://community.breww.com/user_avatar/community.breww.com/justin-hutton/32/1402_2.png) [@justin-hutton](https://community.breww.com/u/justin-hutton)\
**Post date:** [31 August 2023 08:31 UTC](https://community.breww.com/t/stock-take-per-location/3065/1 "2023-08-31T08:31:47Z")

</div>

The new feature in order to do a stock take per site is a great improvement! I was hoping we could make it even better to be able to run it per site and per location?

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [31 August 2023 08:43 UTC](https://community.breww.com/t/stock-take-per-location/3065/2 "2023-08-31T08:43:14Z")

</div>

I fear that a stock take by location may actually cause you problems. What are your thoughts on this:

If you have a keg (say K01) at location A, then you do a stock take for location A only and tell Breww that the keg isn’t there. Breww will empty the keg. If you then do a stock take a location B and tell Breww about K01 being there, Breww will fill it from empty again and mess up your figures/tracking. By doing the stock take for the entire site in one go, this would just have been moved from location A to location B.

What are your thoughts on this situation with a stock take by location?

We’re also quite excited about building [Improve stock take to allow a web (non-CSV) based solution](https://community.breww.com/t/improve-stock-take-to-allow-a-web-non-csv-based-solution/1725) before we spend much more time on the spreadsheet-based stock take process, to be honest.

---

<div class="post-metadata">

**Author:** ![justin-hutton](https://community.breww.com/user_avatar/community.breww.com/justin-hutton/32/1402_2.png) [@justin-hutton](https://community.breww.com/u/justin-hutton)\
**Post date:** [31 August 2023 08:44 UTC](https://community.breww.com/t/stock-take-per-location/3065/3 "2023-08-31T08:44:46Z")

</div>

Hrmm get what you are saying. I wouldn’t even actually use it for location for products, i would use it more for stock items so i could have the brewery doing raw materials and the warehouse doing packaging stuff etc

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [6 September 2023 12:38 UTC](https://community.breww.com/t/stock-take-per-location/3065/4 "2023-09-06T12:38:59Z")

</div>

Sorry for the slow reply, Justin; it’s been a very busy week!

In that case, maybe [Sub-sections for stock takes to do some items at a time (split into Raw, POS, etc)](https://community.breww.com/t/sub-sections-for-stock-takes-to-do-some-items-at-a-time-split-into-raw-pos-etc/2165) would be a better fit, and I can close this in favor of that?

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [13 September 2023 15:06 UTC](https://community.breww.com/t/stock-take-per-location/3065/5 "2023-09-13T15:06:19Z")

</div>


