> 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/roadmap/bevica-roadmap/bevica-extensions/warehouse-integration-3pl-releases.md).
# Warehouse Integration (3PL) Releases
Release notes for the Warehouse Integration (3PL) extension, including new features, fixes, and deployment notes.
The list below highlights major enhancements and improvements that impact this extension (small hotfixes may not be listed).
Before applying any extension to the production environment, you should become familiar with new features in a sandbox environment first.
Please contact your system administrator to install this extension.
### **Release V20.22.25.0 (27/05/26)**
New features:
* Improved [SinglesPerUnit calculation](https://kb.bevica.com/roadmap/bevica-roadmap/bevica-extensions/spaces/fUgpGDVvyqBWVvwVIy9a/pages/0T8daPh2RqLtJ9TD5yzR#:~:text=On%20Inbound%20Vision%20Request%20Files) for Vision Inbound Request files.
Issue resolved
* None
### **Release V20.22.24.0 (24/04/26)**
New features:
* Version prepared for 2026 Wave 1, V28.
* Help Pages linked to new Bevica Knowledge Base.
Issue resolved
* Depreciated **Fax** fields from Vision Warehouse Integration Documents.
### **Release V20.22.21.0 (19/02/26)**
New features:
* Added a new '**Pay Customs Duty**' toggle to customer Ship-to Addresses. For more information on this please see [Pay Customs Duty](/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#pay-customs-duty).
* Added a new field to Warehouse Integration Setup '**Field for XML Brand Element**' to indicate which field is selected for 'Brand' on Pre-Advice Files. For more information, please see [Warehouse Outbound Document Integration](/documentation/integration/bevica_warehouse_integration/warehouse_outbound_document_integration.md#warehouse-integration-location-setup).
Issue resolved
* Updates to Pre-Advice files to ensure consistency between PO & SRO files and remove unrequired fields.
### Release V20.22.20.0 (27/01/26)
#### New features
* None
#### Issues resolved
* Resolved an issue when adding Warehouse Requests to manifests if the manifest already contained **Generated** or **Sent** requests.
* Updates to the **Post Stock Transactions** report (71309) to ensure **VAT Date** is aligned with **Posting Date**.
### Release V20.22.19.0 (15/01/26)
#### New features
* Added functionality to work alongside new Broking:
* Ensured Vision Pre-Advices are not sent for **Broking Purchase Orders**.
* **Broking Sales Orders** always populate the **Reserved from Stock** field as complete to ensure a Vision file is generated.
#### Issues resolved
* None
**Deployment note: Bevica Essentials 23.45.4.0 or later (15/01/26) must also be installed.**
### Release V20.22.18.0 (07/01/26)
#### New features
* Added a new field on the Custom Mapping Routines for the Warehouse Supplier Setup for SRO Exports
* Changes to the Compare Vision Inventory routine. See [Warehouse Item Reconciliation](/documentation/integration/bevica_warehouse_integration/warehouse_item_reconciliation.md) for further details:
* Ability to include or exclude frozen stock
* Amended calculation for items which are set as 'Whse. Integration Default to Case'
#### Issues resolved
* Updated the default files per record from 50 to 1 when creating new Warehouse Integration Setup records
* Changes to the Vision outbound request file for 'Q' type orders to ensure Sales Price is showing on the file
* Update to Vision outbound request file to remove spaces from the phone number
### Release V20.22.17.0 (25/11/25)
#### New features
* None
#### Issues resolved
* Changes to the **Reserved Status** and **Reserved from Stock** field on the Sales Header to ensure a Warehouse Integration file is only created if the **Reserved from Stock** field shows as **Complete**
### Release V20.22.15.0 (03/10/25)
#### New features
* None
#### Issues resolved
* Fixes to **Post Stock Transactions** codeunit to ensure non-item lines are posted
### Release V20.22.14.0 (01/10/25)
#### New features
* Warehouse Integration has been updated ready for deployment of Business Central Wave 2 2025 (V27)
#### Issues resolved
* None
### Release V20.22.13.0 (01/10/25)
#### New features
* None
#### Issues resolved
* Hotfixes
### Release V20.22.12.0 (22/09/25)
#### New features
* None
#### Issues resolved
* Changes to **Sales Return Order Pre-Advices** to ensure the field 'Singles Per Unit' correctly reflects the total number of singles per Sales Unit of Measure
* Updated the default collection times for Vision Warehouses. For more information on this, please see the following article from Vision on [SO XML Structure](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/933626253/SO+XML+Structure#:~:text=%3CHO%3E16-,CollectionTime,-You%20must%20provide)
### Release V20.22.11.0 (20/08/25)
#### New features
* Where [Automatic Transfer of Paid Reserves](broken://pages/LImaYZgcSb3FQXAbI2iw) is in use, processing the Inbound Request File from Vision will now update the Paid Reserves Item Ledger Entry to show the new rotation number and rotation reference supplied by Vision
#### Issues resolved
* Made changes to the **Compare Vision Inventory** report to ensure all fields are correctly updated if run multiple times
* Fixed an issue with the calculation of **Expected No of Cases & Expected No of Lines** on Pre-Advices for Purchase Orders. Please see [Managing Purchase Orders](broken://pages/0T8daPh2RqLtJ9TD5yzR) for more information
* The **Compare Vision Inventory** report can now be run for multiple batches at a time
* Applied a fix to the **Item Availability Factbox** displayed on the **Whse. Item Reconciliation** page
**Deployment notes: Bevica Essentials 23.43.0.0 or later (20/08/25) must also be installed**
### Release V20.22.9.0 (05/08/25)
#### New features
* Added an **'Allow Q Type Orders'** flag in **Warehouse Integration Setup** to ensure correct file generation for Vision Managed Warehousing & Paid Reserves. For more information on this, refer to: [Vision Sales & Transfer Outbound Requests](https://github.com/TVisionTech/GitBook_Bevica/blob/main/documentation/Bevica_Warehouse_Integration/Vision_Sales_&_Transfer_Outbound_Requests.md), [Paid Reserves - Transfer Duty Status](broken://pages/CQW0fTgkTLs6SYy6Gjdc) & [Duty Transfer Orders](broken://pages/uJivo9AXjrD2lk76Wk0X)
#### Issues resolved
* None
### Release V20.22.7.0 (29/07/25)
#### New features
* Added a '**Group Item**' feature for use with **Warehouse Item Reconciliation batches**. This feature will enable multiple instances of the same item number within a reconciliation batch to combine onto one line. For more information on this feature, see [Resolving Discrepancies](broken://pages/oU3EBapa9h51dVCWYQ5m)
#### Issues resolved
* None
### Release V20.22.6.0 (25/07/25)
#### New features
* Made a change to the display of Request Records, specifically to ensure the '&' character is visible in the request
* Added a new **Posting Date Method** for posting Stock Transactions. The field '**Work Date**' will now be available to select
#### Issues resolved
* Fixed an issue on timestamps for 'Cancelled' Warehouse Integration requests
### Release V20.22.3.0 (23/07/25)
#### New features
* None
#### Issues resolved
* Resolved an issue with processing **Warehouse Int. Stock Transactions** that was resulting in a '**Qty Mismatch**' error if the Sales Order lines and Pick Confirmation lines had been split either by Bevica due to reservations or by the Vision Managed Warehouse due to Rotations
* Removed default values on the 'Discrepancy Calculation Method' in the **Compare Vision Inventory report (71304)** to enable this to be run correctly from a Job Queue
### Release V20.22.2.0 (21/07/25)
#### New features
* None
#### Issues resolved
* Changes to the output file for **Sales Rtn Order Pre-Advice** to ensure the Address fields populate in the same way as a Purchase Order Pre-Advice
### Release V20.22.1.0 (08/07/25)
#### New features
* None
#### Issues resolved
* Fixed an issue preventing viewing of **Sales Return Orders** documents from the Whse. Integration Inbound Request page
* 'Prevent Partial Shipment' flag was preventing the automatic sending of outbound requests on Sales Return Orders. This has now been fixed
### Release V20.22.0.0 (26/06/25)
#### New features
* **Collection Details** fields have been added to the Vision file for **Sales Return Orders**
* **Purchase Order Vision Pre-Advice**. If Shipping Agent is populated, this will be passed in the file to Vision as 'ShipperName'
* **Coterie Vaults** have now been added as a Vision Managed Warehouse
#### Issues resolved
* **Address Fields** will now populate correctly on **Transfer Order** files
* Fixed an issue where **Sales Return Orders** were not generating a Pre-Advice if Sales Order Pre-Advice was disabled
* Warehouse Integration **Factbox** will now automatically refresh on page opening
### Release V20.21.3.0 (04/06/25)
#### New features
* **Transfer Order Vision Outbound notifications**. You can now manually 'Create' and 'Remove' outbound notifications from Transfer Order and List pages
* **Sales Rtn. Order Vision Pre-Advice**. This is now available to send, automatically from order 'Release' or manually from the card page
* **Whse. Integration Setup.** More granularity in deciding which documents to integrate with
#### Issues resolved
* **Purchase Order Vision Pre-Advice**: issues with line numbers, product strength and vintage fixed
### Release V20.21.1.0 (22/05/25)
#### New features
* None
#### Issues resolved
* **Purchase Order Pre-Advice**: issue fixed when releasing the purchase order
### Release V20.21.0.0 (13/05/25)
#### New features
* None
#### Issues resolved
* Fix issue where paid reserve withdrawals were being excluded from the Vision outbound request file
**Deployment notes: See V20.18.0.0**
### Release V20.20.0.0 (12/05/25)
#### New features
* Added functionality for [Pre-Advices](broken://pages/0T8daPh2RqLtJ9TD5yzR), [Goods Received](broken://pages/NM1tFpw2SUS5gJrxMEsM) and [Pick Confirmations](broken://pages/6CWBp0bDaAsn7t6ou0Wx)
#### Issues resolved
* None
**Deployment notes: See V20.18.0.0**
### Release V20.19.0.0 (30/04/25)
#### New features
* Improved visibility of communication engine message status and errors on outbound requests, sales orders and transfer orders for Vision outbound requests
#### Issues resolved
* None
**Deployment notes: See V20.18.0.0**
### Release V20.18.0.0 (25/04/25)
#### New features
* **RotationLineNo.** Vision's RotationLineNo has been integrated into outbound sales and transfer order files. See **Apply Rotation Line No.** here: [Warehouse Outbound Document Integration](broken://pages/ceRW4J80reD3ztZkFcdJ)
* **Manifests.** 'Outbound Request' action added to the Manifest Card
* **Vision Outbound file checking**. Additional checks on generation of the files
* Exclude **Duty Transfer** sales lines on Vision outbound requests, see [Paid Reserve - Transfer Duty Status](broken://pages/CQW0fTgkTLs6SYy6Gjdc)
#### Issues resolved
* None
{% hint style="danger" %}
**Deployment note**
Bevica version 23.40.0.0 (25/04/25) must be installed prior to installing this update. If the environment has Distribution Cost Management installed, you must also install Distribution Cost Management V21.16.0.0 and the Bevica Distribution Cost Connector V22.3.4.0
{% endhint %}
### Release V20.17.12.0 (04/04/25)
#### New features
* **Integration Setup 'Records per File'.** The default has been changed from 50 to 1 to help API integration
#### Issues resolved
* **Transfer Order 'Vision Service Code'**. The field is now copied to posted transfer order Receipt and Shipment
### Release V20.17.10.0 (27/03/25)
#### New features
* Added [**Contact Email Address**](broken://pages/uJivo9AXjrD2lk76Wk0X) to the Vision outbound request file. Note that whether this field is included in the file is controlled with the **Add Customer Email Address on SOs** field on the Warehouse Supplier Setup record. The relevant email field must only contain a single email address. Otherwise, the file will error when it is sent to Vision
* Added [**Delivery Issue Email Address**](broken://pages/ceRW4J80reD3ztZkFcdJ) to the Vision outbound request file to notify you if there is an issue with an order. This is in addition to the email address defined in the warehouse system
* New [**Role Centre tiles**](broken://pages/SK56Zf3j3NboCSRKLAH8) for outbound requests and Vision stock reconciliation
* Changes to [**Warehouse Item Reconciliation (Vision)**](broken://pages/oU3EBapa9h51dVCWYQ5m) functionality
* **Item number length** issue on the reconciliation batch page
* Routine now **excludes Non-Inventory items**
#### Issues resolved
* Fixed issue with the default **Collection Time** (Vision)
**Deployment notes: See V20.17.7.0**
### Release V20.17.7.0 (20/02/25)
#### New features
* **Sending Outbound Requests for Vision via the API from this version onwards will be sent via the Communication Engine**. Installing this version will need the Communication Engine configured (see [Communication Engine Setup for Vision Warehouses](broken://pages/ceRW4J80reD3ztZkFcdJ)) and Communication Engine V24.0.0.0 or later installed
* Ability to see the **response code** returned from Vision on the Communication Engine message (note that this change is in Communication Engine V24.0.0.0)
#### Issues resolved
* None
{% hint style="danger" %}
**Deployment note**
Prior to installing V20.17.7.0 you must:
* Install TVT Communication Engine V24.0.0.0 or later
* Set up the Communication Engine for Outbound Requests if they are sent to Vision
* On installation 'Schema Sync' Mode must be set to Force
{% endhint %}
### Release V20.17.6.0 (21/11/24)
#### New features
* None
#### Issues resolved
* Fixed issue with obsolete field
**See deployment notes below.**
### Release V20.17.5.0 (05/11/24)
#### New features
* **Item Reconciliation**. Compare stock balances between your warehouse and Bevica. Learn more: [Warehouse Item Reconciliation (Vision)](broken://pages/oU3EBapa9h51dVCWYQ5m)
#### Issues resolved
* None
**See deployment notes below.**
### Release V20.17.2.0 (31/10/24)
#### New features
* Sales Order list. The **Add Request** option can now create multiple requests if the list is filtered
* Integrated the Communication Engine extension into API messages in and out of Bevica
#### Issues resolved
* Improved record locking to prevent duplicate messages out
* We've added a message if the order is Credit Held when **Add Request** is selected from a Sales Order
* Fixed issue with **error messages** not clearing after each request record
* Changed the Phone No. on Great Bear outbound Sales Order requests
{% hint style="danger" %}
**Deployment note**
* Prior to installing V20.17.2.0 you must install TVT Communication Engine V1.9.6.0 or later
* On installation 'Schema Sync' Mode must be set to Force
{% endhint %}
### Release V20.16.2.0 (24/09/24)
#### New features
* None
#### Issues resolved
* Fixed issue with **error messages** not clearing after each record
### Release V20.16.1.0 (07/08/24)
#### New features
* **Vision Outbound Requests**: DeliveryAddress3 is now populated with the Vision Sub Account Code from the Ship-to Address on the Sales Order for normal orders, and for sales into reserves. See [Sales into Paid Reserve or a Reserve Sub-Account with another company](https://github.com/TVisionTech/GitBook_Bevica/blob/main/documentation/Bevica_Warehouse_Integration/Vision_Sales_&_Transfer_Outbound_Requests.md) for more information
#### Issues resolved
* None
### Release V20.16.0.0 (22/07/24)
#### New features
* Ability to create **Retention Policies** for Outbound Request records. See [Retention Policy Setup](broken://pages/ceRW4J80reD3ztZkFcdJ)
#### Issues resolved
* None
{% hint style="danger" %}
**Deployment note**
After installing the extension, if you are unable to see tables 71303 and 71304 when creating a Retention Policy, go to Extension Management and uninstall/reinstall the extension.
{% endhint %}
### Release V20.15.4.0 (19/07/24)
#### New features
* None
#### Issues resolved
* **Outbound Request** file for Great Bear. Amended how the **Booking Instruction** field is populated based on the Whse. Booking Required field
### Release V20.15.3.0 (11/07/24)
#### New features
* None
#### Issues resolved
* **Outbound Request** generation for Great Bear. **Comments** are now added when the request is generated rather than when the sales order is released
### Release V20.15.2.0 (01/07/24)
#### New features
* Outbound Request file format for Great Bear: create new lines for multiple orders on a single file
#### Issues resolved
* None
### Release V20.15.1.0 (28/06/24)
#### New features
* The **Whse. Booking Required** field has been added to the Ship-to Address and Customer to default onto sales orders. See [Booking Details](https://github.com/TVisionTech/GitBook_Bevica/blob/main/documentation/Bevica_Warehouse_Integration/Vision_Sales_&_Transfer_Outbound_Requests.md) for more information
* New Outbound Request file format for Great Bear
#### Issues resolved
* Removed additional Vision file node which was not required
### Release V20.14.1.0 (06/06/24)
#### New features
* Vision **outbound request** files with the **same item and** **rotation**. Sales lines with the same item no., rotation no. and unit of measure are now combined on the file sent to Vision
* Vision **outbound request** files, **CustomerPORef** field. The field length has increased from 15 to 20 characters
* New **Warehouse Supplier** option for **Lanchester** in Warehouse Integration Setup
* **Transfer Order Comments**. Ability to add Delivery and Pick Instructions which will be included in the Vision outbound request file. See [Transfer Order Comments and Notes](broken://pages/cWoJIBxNIHmjlsX1Nu2a)
#### Issues resolved
* **Warehouse Integration Process Outbound Requests** report. Field caption has been changed from Location Code to Whse. Integration Setup Code
* Fixed the Location Code error when running the **Add Outbound Orders** function
{% hint style="danger" %}
**Deployment note**
You must install Bevica Essentials 23.31.30.0 prior to installing Warehouse Integration 20.14.1.
{% endhint %}
### Release V20.14.0.0 (23/04/24)
#### New features
* Ability to link multiple Location Codes to a single warehouse integration site. This can be useful when you want to segregate stock in Bevica but operate one warehouse site/account. There is a new **Warehouse Integration Setup** field on the Location card, linking a location to a site. It is possible to have multiple locations on a sales order that link to the same site. See [Sales orders for multiple locations belonging to the same site](broken://pages/ceRW4J80reD3ztZkFcdJ)
#### Issues resolved
* None
{% hint style="danger" %}
**Deployment note**
When the extension is installed, any existing Warehouse Integration Setup records will be amended with the new setup automatically and the linked Location Code will have the Warehouse Integration Setup field populated. The job queue entry for report 71303 will also be updated.
{% endhint %}
### Release V20.13.8.0 (31/01/24)
#### New features
* Change logic for the **Contact Name** and **Contact Number**. If the Ship-to Code and the Sell-to Contact No. on the sales order are both blank, the Contact Name and Contact Number will now be taken from the Primary Contact No. on the sell-to customer record
* Delivery Address details for **sales into reserves** are now taken from the ship-to address details
#### Issues resolved
* None
### Release V20.13.7.0 (27/12/23)
#### New features
* Populate **DeliveryName** for sales into reserves from the Ship-to Name
#### Issues resolved
* None
### Release V20.13.6.0 (31/10/23)
#### New features
* Add the POST response message from the API onto the outbound request
#### Issues resolved
* None
### Release V20.13.5.0 (19/10/23)
#### New features
* **UX improvements** including a blank option on the Vision Delivery Collection Area drop-down
* Stop users deleting sales orders which have been sent to the warehouse
#### Issues resolved
* None
### Release V20.13.3.0 (01/08/23)
#### New features
* **Reserve withdrawals.** The price on the outbound request file sent to Vision is now taken from the paid reserve record
#### Issues resolved
* None
### Release V20.13.2.0 (01/08/23)
#### New features
* None
#### Issues resolved
* The **Contact Name** and **Phone Number** on Vision outbound requests are now taken from the Ship-to record, or the Sell-to contact no. record if the Ship-to is blank
* Allow sales orders containing only non-inventory, service items or GL accounts to be posted without an outbound request being generated
### Release V20.13.1.0 (05/07/23)
#### New features
* **Prevent outbound requests being generated if the sales order is partially reserved**
* Amended logic for **BookedOrCollectedDate** on Vision outbound requests. The date can now be used on its own to tell the warehouse of a specific delivery date, as well as in conjunction with Warehouse Booking Required or Shipping Agents
#### Issues resolved
* An outbound request is no longer generated if the sales order only contains non-inventory or service items
### Release V20.13.0.0 (26/06/23)
#### New features
* **Prevent automatic sending of warehouse requests**. See [Outbound Requests](https://github.com/TVisionTech/GitBook_Bevica/blob/main/documentation/Bevica_Warehouse_Integration/Vision_Sales_&_Transfer_Outbound_Requests.md) for more information
#### Issues resolved
* **None**
### Release V20.12.6.0 (11/05/23)
#### New features
* **Vision API communication**. Sales and transfer orders can now be communicated to Vision controlled warehouses via API
* **Additional Parcel Carrier details.** For Vision controlled warehouses, if using a Parcel Carrier Service, you can now specify: Parcel Carrier Service Code, Parcel Carrier Account No. and Parcel Carrier Extra Insurance Required. See the Shipping Agents section [here](https://github.com/TVisionTech/GitBook_Bevica/blob/main/documentation/Bevica_Warehouse_Integration/Vision_Sales_&_Transfer_Outbound_Requests.md)
#### Issues resolved
* **None**
### Release V20.12.5.0 (06/04/23)
#### New features
* **Vision Sub Account No**. New field on the customer ship-to address to hold the customer's sub account number used for sales into reserves. See [Sales into Paid Reserves](broken://pages/ozG6eQQiAW2R6e5vxXlN) for further information
#### Issues resolved
* **Sales Order lines without a unit of measure**. Prevent a sales order being released without a unit of measure on all item lines to ensure all outbound requests have the correct unit of measure
### Release V20.12.3.0 (05/01/23)
#### New features
* None
#### Issues resolved
* **Sales Order fields**. Amended the tooltip captions on some warehouse integration fields on the sales header
* **Transfer Order export**. A transfer order with multiple comment lines can cause the following error msg. `The following error occurred: The value of COPYSTR parameter 3 is outside of the permitted range. The current value is: -1. The permitted range is: from 0 to 2,147,483,647.`
### Release V20.12.1.0 (14/11/22)
#### New features
* None
#### Issues resolved
* **Sales Order export**. A sales order with multiple comment lines can cause the following error msg. `The following error occurred: The value of COPYSTR parameter 3 is outside of the permitted range. The current value is: -1. The permitted range is: from 0 to 2,147,483,647.`
### Release V20.11.07.0 (25/07/22)
#### New features
* **Reopening Sales Orders**. It is now possible to easily reopen a sales order that already has an Outbound Request record
#### Issues resolved
* **Credit Held Orders**. Credit Held orders and Outbound Requests are managed correctly
### Release V20.11.06.0 (16/06/22)
#### New features
* **Vision file name change**. Full stops in the file name were causing files to be rejected by the Vision system, Version V18.11.7 available for customers on V19
#### Issues resolved
* None
### Release V20.11.5.0 (24/05/22)
#### New features
* Upgraded to V20
* **SMTP deprecated**. Links to SMTP Setup have been removed. Email Accounts should be used instead
#### Issues resolved
* None
### Release V18.11.5.0 (16/02/22)
#### New features
* **Block Pending Order Re-Open**. Where Sales Order export is set to 'Manual' you can now stop orders from being re-opened if they have a pending outbound file. See [Warehouse Outbound Document Integration](broken://pages/ceRW4J80reD3ztZkFcdJ) 'Block Pending Order Re-Open'
#### Issues resolved
* Updates to posting matched picks on Sales Orders. See [Warehouse Inbound Document Integration](broken://pages/ceRW4J80reD3ztZkFcdJ)
* Fix an issue where re-opening an order with a processed/sent outbound request could identify the wrong record when checking whether the order could be re-opened
### Release V18.11.4.0 (06/12/21)
#### New features
* **Vision Booking / Collection details**. Where no specific booking date or time is added to a Sales Order or Transfer Order, the system default is today's date and 17:00. See Vision Outbound Requests
#### Issues resolved
* None
### Release V18.11.2.0 (01/11/21)
#### New features
* **Vision Service Code**. Service Codes are used by some Vision warehouses to denote vehicle requirements at the destination address. See Vision Outbound Requests
#### Issues resolved
* None
### Release V18.10.0.0 (27/10/21)
#### New features
* Update to Business Central V18
#### Issues resolved
* None
### Release V17.11.02.0 (16/10/21)
#### New features
* **Vision Pick Group**. Service Codes are used by some Vision warehouses to help warehouse planning operations. See Vision Outbound Requests
#### Issues resolved
* None
---
# 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/roadmap/bevica-roadmap/bevica-extensions/warehouse-integration-3pl-releases.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.