> 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/integration/bevica_warehouse_integration/warehouse_pre-advice_integration.md). # Warehouse Pre-Advice Integration Send purchase pre-advices to the warehouse for planned receipts. Bevica's Pre-Advice Integration allows you to send purchase and sales return order details to your warehouse in advance of their receipt date. This helps the warehouse manage orders more efficiently and can later automate the receipting process in Bevica. {% hint style="info" %} **Note** This service is only available with Vision managed warehouses (LCB, Vinotheque, Lanchester, EHD, and Coterie Vaults). {% endhint %} {% hint style="warning" %} **Prerequisites** Account with a Vision managed warehouse: LCB, Vinotheque, Lanchester, EHD, Coterie Vaults. Warehouse Outbound Document Integration has been set up. See [Warehouse Outbound Document Integration](/documentation/integration/bevica_warehouse_integration/warehouse_outbound_document_integration.md). {% endhint %} ### Vision managed warehouses Bevica utilises the **Goods Received** file provided by Vision. Notes from the Vision Help files: *Vision EDI has the ability to accept Pre-Advice notifications from customers, this may more commonly be known as the customers “Purchases” from suppliers or “Purchase Orders”. The facility allows the transmission of pre-advice information in advance of the goods arriving thus allowing the warehouse to plan resources more efficiently and effectively. A by-product of this is the timely receipt of goods when they arrive at the warehouse and the establishment of a single source for all information, such as product description and information.* For full information and limitations see here: [1201 Pre-Advices (PA)](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/934084817/1201+Pre-Advices+PA). ### Warehouse Pre-Advice API Setup See [Setting up Communication Engine for Vision Pre-Advices](/documentation/integration/bevica_warehouse_integration/setting_up_communication_engine_for_vision_pre-advices.md) for details on how to complete the setup to send pre-advices to Vision via the API. ### Managing Purchase Orders Pre-Advice requests can be sent on 'Release' or directly from the Purchase Order. * To send on 'Release' see Warehouse Integration Setup. * To send manually, navigate to your specific purchase order and select: Actions, Warehouse, **Add Request**. This creates an Outbound Request record. Existing request records can be removed from this option too. Requests can be **Removed** from the same ribbon option menu. The **Request Status** field lets you know where the purchase order is in the warehouse integration process, it can be used for filtering. See also [Warehouse Integration Role Centre Tiles](/documentation/integration/bevica_warehouse_integration/warehouse_integration_role_centre_tiles.md). {% hint style="info" %} **Note** In order to correctly display the 'Expected No of Cases' and 'Expected No of Lines' on your file to Vision, the Purchase Order must be placed using the items **Purchase Unit of Measure** which is set up from the **Item Card.** If an alternative Unit of Measure is used which does not match the item's Purchase UOM, Bevica cannot calculate the expected quantity for the Vision file. More information on Units of Measure can be found [here](/documentation/guides/items-and-inventory/item_units_of_measure.md). {% endhint %} ### Managing Sales Return Orders Pre-Advice requests can be sent on 'Release' or directly from the Sales Return Order. * To send on 'Release' see Warehouse Integration Setup. * To send manually, navigate to your specific sales return order and select: Actions, Warehouse, **Add Request**. This creates an Outbound Request record. Existing request records can be removed from this option too. Requests can be **Removed** from the same ribbon option menu. {% hint style="info" %} **Note** If the goods require collection by the warehouse, the 'Whse Collection Req.' flag must be set on the Sales Return Order. This flag will amend the document type in the file to inform the warehouse of the collection. If the flag is not set, the warehouse will treat this as an inbound delivery. {% endhint %} The **Request Status** field lets you know where the sales return order is in the warehouse integration process, it can be used for filtering. See also [Warehouse Integration Role Centre Tiles](/documentation/integration/bevica_warehouse_integration/warehouse_integration_role_centre_tiles.md). {% hint style="info" %} **Note** On Inbound Vision Request Files, the SinglesPerUnit field must be populated with the case quantity. Where the line is set to a base UoM, Bevica will calculate this field based on the items Sales Unit of Measure. If this is *not* set to a case UoM, the items Reporting Unit of Measure should be populated with the case UoM to ensure this field is correctly displayed for Vision Warehouses. More information on Units of Measure can be found [here](/documentation/guides/items-and-inventory/item_units_of_measure.md). {% endhint %} ### Warehouse Collections In order to properly communicate warehouse collections for your Sales Return Orders, there is a 'Whse. Collection Req.' flag. This flag can be toggled on or off in the Warehouse Integration tab found in the following places: * Customer Card * Ship-to Addresses * On the Sales Return Order The Sales Return Order will set the toggle by default from the values from the Ship-to Address, or in the absence of a Ship-to Address, this will default to the value from the Customer Card. This can be changed manually from the Sales Return Order if required. --- # 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/integration/bevica_warehouse_integration/warehouse_pre-advice_integration.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.