> 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/cellarage-releases.md).
# Cellarage Releases
Release notes for the Bevica Cellarage extension, including worksheet/invoicing updates and resolved issues.
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 V18.3.10.0 (24/04/26)
#### New features
* Version prepared for 2026 Wave 1, V28.
* Help Pages linked to new Bevica Knowledge Base.
* Improvements to the **Cellarage Worksheet** to allow refining the creation/posting of documents using filtering
* Added **Vintage** as a placeholder to be applied to Cellarage Invoices in **Cellarage Setup**.
* Added **Your Reference** as a field on the Create/Update Cellarage Invoices routine.
#### Issues resolved
* Resolved an issue applying **Line No** filtering after using **Post Cellarage Documents** routine.
### Release V18.3.7.0 (25/11/25)
#### New features
* None
#### Issues resolved
* Changes to the **Suggest Cellarage** routine to increase the maximum length of the **Location Code** field.
### Release V18.3.6.0 (04/09/25)
#### New features
* Added the **Reverse Cellarage Ledger Entries** function to the Home icon.
#### Issues resolved
* Resolved an issue when creating sales invoices if a customer has **Sales Comments**.
### Release V18.3.4.0 (26/06/25)
#### New features
* The **Cellarage Worksheet** now allows charges across multiple periods.
* You can now update open cellarage invoices directly from the worksheet.
* You can now choose the sales invoice sort order from the worksheet before creating sales invoices.
#### Issues resolved
* The **Location** on **Cellarage Invoice Lines** now stays blank.
* Resolved an issue with **Rounding** on the **Cellarage Worksheet**.
### Release V18.2.4.0 (04/11/24)
#### New features
* None
#### Issues resolved
* Fixed an issue creating cellarage invoices where the Default Ship-to is Duty Free.
### Release V18.2.2.0 (07/05/24)
#### New features
* Improved tooltips and navigation.
#### Issues resolved
* None
### Release V18.2.1.0 (19/03/24)
#### New features
* Added new parameters for the **Line Description** on created cellarage invoices: **Unit of Measure Code** (`%11`) and **Quantity** (`%12`).
#### Issues resolved
* None
### Release V18.2.0.0 (26/02/24)
#### New features
* None
#### Issues resolved
* Fixed an issue in **Suggest Cellarage** where you could get `Customer No. does not exist`.
### Release V18.1.0.0 (18/08/21)
The Bevica Cellarage extension has been released. This functionality enables you to invoice customers for managing and storing Paid Reserves.
---
# 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/cellarage-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.