> 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_pick_confirmation_integration.md).
# Warehouse Pick Confirmation Integration
Process inbound pick and dispatch confirmations from the warehouse.
### Warehouse Pick Confirmation Integration
Bevica's **Warehouse Pick Document Integration** allows you to import Pick confirmation files from your third-party warehouse, compare them to the original Sales Order document and post them where they match.
{% hint style="info" %}
This service is available with Vision managed warehouses (LCB, Vinotheque, Lanchester, EHD and Coterie Vaults)
{% endhint %}
{% hint style="warning" %}
**Prerequisites**
Order notifications previously sent to the warehouse.
Bevica Warehouse Integration extension installed.
Communication Engine extension installed.
Account with a Vision managed warehouse: LCB, Vinotheque, Lanchester, EHD, Coterie Vaults.
{% endhint %}
### Vision managed warehouses
Bevica utilises the [**2340 Orders Picking Confirmation**](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/11731159/2340+Orders+Picking+Confirmation) file provided by Vision.
Notes from the Vision Help files:
| Overview | This output is used to show the previous picked order lines.
Operationally an order could be picked over more than a single output file, as this is based on the pick confirmation of each line of the order. Also bear in mind you may order a product but we may be picking this across several rotations so several lines may appear in the output for the same one product line you sent to the warehouse.
Order picked confirmation is generated when the stock movement takes place, this is slightly different depending on whether Distribution is in use, if this is not in use then it is generated when the order is marked as collected or despatched and in the event that you have underbond activities then the duty has to be posted onto the bond system.
|
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Limitations | This is designed for confirmation at the customer end, as such you will only be able to pull an order pick confirmation one time. Once downloaded this information will not be sent again, as such you can therefore poll for any order picks each time you ask and will be given all which have not previously been sent to you.
API requests for an individual confirmation are possible but follow the same pattern in relation to “you will only get new information”.
|
### Processing Pick Confirmations
1. Import Pick Confirmation details
2. Stock Transaction Entries
3. Post Bevica documents
4. Resolve discrepancies manually
The steps below detail how to manually process the file from the warehouse, this is useful for familiarisation, testing and troubleshooting. It is possible to automate the process, contact your Bevica consultant to help set this up.
### 1. Import Pick Confirmation details
Warehouse pick confirmation details can be imported manually, useful for familiarisation, testing and troubleshooting, or automatically via API.
See [Setting up Communication Engine for Vision Pick Confirmations](/documentation/integration/bevica_warehouse_integration/setting_up_communication_engine_for_vision_pick_confirmations.md) for details on how to set up the automated API import process. The manual process is detailed here:
* Navigate to **Warehouse Integration Inbound Requests.** This holds each imported file
* On the ribbon select **Process** and **Upload File**
* Select the appropriate **Warehouse Code**. The Supplier Request Code is usually left blank as this is automatically identified by the system using the file name or content. This is only required to be completed if the import routine cannot identify the file type
* Press OK and then navigate to the .xml file to upload. Once imported the file will show as **Request Status = Pending**\
* Select **Process Requests** from the ribbon. Select the appropriate options - Warehouse Code is mandatory and other filters can be used to process specific entries
* Once completed, the **Request Status** field will change to 'Generated' if the file is processed successfully. Any errors will be shown in the **Last Error Message** field for resolution
### Warehouse Integration Inbound Requests Error Handling
Any error messages are captured in the Last Error Message field for the file. You should resolve the error and then select **Revert to Previous Status** and **Process Requests** again.
If a file is to be ignored then use **Cancel Requests** to mark it as cancelled. It will then not be processed in future.
### 2. Stock Transaction entries
* Navigate to **Warehouse Integration Stock Transaction Entries.** You can also open the selected pick records from the Warehouse Integration Inbound Requests page ribbon.
The entries page shows the imported details and if they have been matched successfully against Bevica documents.
| Field | Note |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Order Type | If this is populated it means the Bevica document has been recognised. |
| Status | Status is initially 'Open' until you try to post the lines, then they will either be set to Error or Complete. |
| Document Qty. Outstanding (Base) | Where the document has been found this displays the quantity on the document line. If it's red it means there is a discrepancy with the warehouse details. |
### 3. Post Bevica documents
* Select the document(s) to be processed and choose **Post Selected Orders.** This will Ship & Invoice each selected document.\
Set the appropriate filters:
| Field | Comments |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Posting Date Method | Options: Use Transaction Date = uses the date from the pick file for the Posting Date, VAT Date and Document Date Custom Date = allows you to set a specific Posting Date, which will also be used as the VAT Date Work Date = uses the work date for the Posting Date and VAT Date |
| Posting Date | If 'Custom Date' has been selected set the Posting Date to use. This will also be used as the VAT Date |
| Look for Next Available Posting Date | If 'Use Transaction Date' has been selected this will automatically find the next available Posting Date if the Transaction Date is outside of the users posting date range through General Ledger Setup, Inventory Periods, or User Setup |
| Replace Document Date | If you select 'Custom Date' or 'Work Date' then you can choose to replace the Document Date and therefore the Due Date calculation which come from this |
| Stock Transaction Entry | If required you can filter to specific entries using these filters |
**Posting Notes:**
* Selecting any line on a document will process all lines for that document
* Documents must be 'Released' to be processed
* If any line on a document is incorrect the entire order will error
* You can select multiple documents as a single batch
Documents which have been processed successfully are marked as **Completed** and the **Posting Type** set to 'Automatic'.
### 4. Resolve Discrepancies Manually
The list may contain warehouse generated pick lines that cannot be posted automatically by the system. These should be shipped & invoiced manually, then return to the stock transaction entries page and **Set lines as Completed.**
---
# 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_pick_confirmation_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.