> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/warehousing-and-logistics/location_setup.md). # Location Setup Configure locations for picking, bins, duty status, and posting behaviour. Locations are places such as warehouses or store rooms where you buy, store or sell items. Locations help you to keep track of your inventory. ### Locations Overview Click on these links to find out more information on locations and how to set these up: * Set up locations - [Learn | Microsoft Docs](https://learn.microsoft.com/en-gb/dynamics365/business-central/inventory-how-setup-locations) * Set up locations, [bins and zones](https://learn.microsoft.com/en-gb/dynamics365/business-central/inventory-how-setup-locations#:~:text=Between%20Locations.-,Bins,-Bins%20represent%20the) ### Locations in Bevica Within Bevica you can set up multiple locations. The minimum required information when creating a new location is the Code, name, address and **Inventory Posting Setup**. You then need to decide which type of location it is and populate any other fields accordingly. There are 5 main types of locations: * The simplest location setup is one where stock is managed without bins or any warehousing related logic. Areas such as storerooms, office stock or return locations. * A location linked to a **3rd party warehouse**. Similar in setup to the one above but here there are Bevica EDI links to the warehouse. See [Warehouse Integration](/documentation/integration/bevica_warehouse_integration.md). * A location with a bin structure, picks and put-aways based on individual documents. This is typically referred to as an **Inventory Warehouse.** * A **Warehouse Management System (WMS)** warehouse. This introduces complex directed pick, put away logic and internal replenishment routines between zones / duty status, with the ability to manage multiple documents in bulk using Warehouse Shipments, Receipts, Put Aways and Picks. * An In-Transit location. This special category is used to make sure inventory is visible while moving stock between locations when processing Transfer Orders. ### Allowed Duty Type Use the **Allowed Duty Type** field to manage the duty status of stock within a Location. For example, where you have a Duty Paid warehouse/storeroom you can stop users accidentally receipting Duty Free stock. Location's Allowed Duty Type field options. | Option | Note | | --------- | --------------------------------- | | | No check is performed. | | Duty Free | Only Duty Free movements allowed. | | Duty Paid | Only Duty Paid movements allowed. | The check is performed on the following documents. | Document | Note | | -------------------- | ---------------------------------------------------------------------------------------------------------------- | | Purchase documents | OnRelease, the header and lines Duty Status / Variant code are checked against the Location's Allowed Duty Type. | | Sales documents | OnRelease, the header and lines Duty Status / Variant code are checked against the Location's Allowed Duty Type. | | Assembly documents | OnRelease, the header Duty Status is checked against the Location's Allowed Duty Type. | | Transfer Order | OnRelease, the header Duty Status is checked against the Location's Allowed Duty Type. | | Item Journal | No check is performed. | | Paid Reserve Journal | No check is performed. | ### Inventory Posting Setup As part of creating a new location, you need to create new records in the **Inventory Posting Setup** page to determine the G/L accounts that transactions for this location will be posted to, such as the stock control account. Search for **Inventory Posting Setup** and create new lines for the relevant combinations of **Location Code** and **Inventory Posting Group**. Important fields to populate: * **Inventory Account**: This is the inventory control account in the general ledger. Entries will be posted here when items are invoiced on sales or purchase transactions, or when journals involving inventory are posted. * **Inventory Account (Interim)**: Entries are posted here when sales orders are shipped, and purchase orders are received. These entries are reversed when the orders are invoiced. * **Inventory Account (Paid Res.)**: If you are using paid reserves then populate this with the GL account of your paid reserves stock. For more information on what entries are posted, and which accounts they are posted to within Bevica, see [Bevica Inventory Postings](/documentation/guides/items-and-inventory/bevica_inventory_postings.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.bevica.com/documentation/guides/warehousing-and-logistics/location_setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.