Fixes

[VA-7862] - Custom field creation - the field is blocked
[VA-8319] - Package is not visible in Select Shipment Package List
[VA-10260] - Check alignment settings keep resetting
[VA-10293] - Customer Sales by Product Report Description column shows trading name, part number, and stocking description
[VA-10298] - Sales by customer report with dimensions is filtering by dimension on customers
[VA-10311] - User unable to get Product Labels from Bin locations Transactions>Upload transactions section

Release Notes

[VA-10236] - Improvement to AI form editing - form revisions

• After the user types in a prompt, we immediately edit the form and show the edited form to the user. Now we are adding a preview step. We want to first preview the form changes before it is saved, so the user can confirm that it is correct. When editing an existing form, the user will type in the prompt, and we will preview the changes (display HTML), and the user can confirm it is good (it will then be saved) or type in a new request (in addition to the original prompt) to change it. You can keep asking for revisions until satisfied. The preview page will show a Confirm Change button, which will save the form, and an Additional Revision button. When the user clicks on the Additional revision button, we will ask the user what additional changes to make. The system sends a series of revision requests along with the original edit form prompt and the latest form content to the AI model for each subsequent prompt. These revisions are not saved as form revisions as in 2 and 3, but as temporary revisions, so we can send them to the AI model. A new form revision is created after the user confirms the change. If the user never confirms the changes and abandons the effort, the form change is not saved.
• When using AI to create a new form from existing system forms, after the first prompt, we will create the new form like we do today, and if the user edits this form, it will follow the steps above.
• Create a new model to remember saved revisions made to a form by AI, so AI has access to the previous revisions. In case the user asks to change back to a previous version or refer to a change made previously. We need to include the previous revision as a prompt to the model and also tell the model if the user asks about a change made before, refer to the history, or the user can ask to undo and go back to a version. We will include the last 5 revisions as a prompt to the model.
• Add a form revision view (a link from the edit view), and the revision will include a brief description of the changes, a timestamp (display timestamp using FormatDateInCompanyTimezone), and a button to revert to this version. When a user reverts to an older version, we keep the revision history but add a new revision with description "Revert to xxx' with xxx being the description of the revision reverted to.

[VA-10280] - Load Management UI

Load Management

Overview

Load Management is a new module in Versa Cloud ERP that replaces spreadsheet-based truckload
planning. It allows users to group open Sales Order lines into Loads (truckloads) and manage those
Loads in an Excel-like workspace, finalizes them, and generates a consolidated Dropship Purchase
Orders to send to the manufacturer.

This feature is available only to firms with the Load Management subscription feature enabled.

Key Concepts

Load
A Load represents a single truckload. It groups one or more Sales Order lines and
carries operational information such as Manufacturer, Distribution Center, and Appointment
Information, Bill of Lading Number, and Shipment Status. Each Load belongs to a single entity
(internal organization).

Load ID
Each Load is assigned a unique, system-generated identifier within its entity. The ID is made
up of a user-chosen prefix (e.g., WMT-, NOVA-) followed by an auto-assigned number
(e.g., WMT-1042). Once assigned, the Load ID never changes.

Sales Order Line Assignment
A Sales Order line may be assigned to one Load only. A Load may contain lines from multiple
Sales Orders. Lines cannot be split across Loads — if a line has a quantity of 6, all 6 units
must go to the same Load. To split a quantity, the user must first split the Sales Order line
into two separate lines on the Sales Order itself.

Access and Permissions

Setup — Company → Loads

Accessible from the Setup menu under Company. Firm Admin only.

Load Prefixes

Users define one or more prefixes per entity (e.g., WMT-, NOVA-, TL-). When creating a new
Load, the user selects which prefix to use, and the system automatically assigns the next number
for that prefix.

• A firm may have as many active prefixes as needed.
• Prefixes can be deactivated — deactivated prefixes no longer appear when creating new Loads.
• Existing Loads keep their original Load ID regardless of prefix changes
• Prefix strings cannot be reused once a Load has been created with them

Extra Load Field Definitions

Beyond the five built-in Load fields, users may define additional custom fields to store on each
Load (e.g., special instructions, programme codes, carrier reference). These fields are defined
here and then appear on the Load record for data entry.

• Fields can be added at any time
• A field cannot be removed once any Load has data in it
• Fields can be reordered and relabelled

Logistics → Loads Management

The main operational screen. Accessible from the Logistics menu by users with Shipping
permission.

Screen Layout

The screen is divided into two areas:

• Left — SO Lines Grid: displays open Sales Order lines for the current entity in a
  spreadsheet-like table
• Right — Loads Panel: shows Loads relevant to the lines currently visible in the grid,
  plus a search box and a link to view all Loads

Filters

At the top of the screen:

Only open Sales Order lines are shown. There is no status filter — the dataset is already
restricted to open SOs.

Grid Columns

Fixed columns (always visible):

Custom field columns (scrollable, user-defined):

All active custom fields defined for Sales Order lines are shown as additional scrollable
columns to the right of the fixed columns. These vary by firm. Examples for Trifuno Sales:

{*} These are user-defined Sales Order line custom fields, not built-in Versa fields.

Sorting: Load ID, SO #, Customer, SKU, and all custom field columns are sortable by clicking
the column header. Click once for ascending, again for descending.

Column visibility: Users can show or hide columns using the Columns picker (⚙ icon).

Loads Side Panel

Displays Loads that are relevant to the lines currently visible in the grid after filters are
applied. Includes a search box to further narrow by Load ID. A "Show all loads" link opens the
full Loads index.

Each Load in the panel shows:

• Load ID
• Status (Draft or Finalized)
• Total quantity of lines assigned

Actions available when a Load is selected:

Creating a New Load

Clicking New Load opens a modal:

1. Select a prefix from the list of active prefixes for the entity
2. The system shows a preview of the generated Load ID (e.g., WMT-1043)
3. Click Create — the Load is created and appears in the panel immediately

Assigning Lines to a Load

1. Select one or more rows in the grid using the checkboxes
2. Click Assign to Load and choose a Load from the list (or create a new one)
3. The selected lines are assigned to the chosen Load
4. The Load ID column in the grid updates to show the assignment

Rules:

• A line cannot be assigned to more than one Load
• Assigning a whole line is the only option — no quantity splitting
• Lines cannot be assigned to a Finalized Load

Removing Lines from a Load

1. Select one or more rows that are currently assigned to a Load
2. Click Remove from Load

Rules:

• Cannot remove lines from a Finalized Load (unless Firm Admin has unlocked it)
• Cannot remove lines if a Dropship PO has already been created for that Load

Finalizing a Load

Marks the Load as ready. A confirmation prompt is shown before finalizing.

Once finalized:

• No lines can be added or removed (unless Firm Admin unlocks)
• Load attributes can no longer be edited (unless Firm Admin unlocks)
• Shipping users can still view the Load and its lines in read-only mode

Unlocking a Finalized Load

Firm Admin only. Clears the finalized status and allows editing to resume.

Creating a Consolidated Dropship PO

Available only on a Finalized Load, only for users with Purchasing permission.

1. Select the Finalized Load in the panel
2. Click Create Dropship PO
3. A modal shows the Load ID, number of lines, and total quantity
4. User selects the supplier (manufacturer)
5. Click Create PO — one consolidated Purchase Order is created containing all lines from the Load
6. The PO is linked back to the Load and to the originating Sales Order lines for full traceability

One PO is created per Load. The resulting PO can then be emailed to the manufacturer from
within Versa using standard PO email functionality.

Load Record

Each Load has the following built-in fields:

Plus any extra fields defined by the user in Setup → Company → Loads.

Workflow Summary

1. User imports Walmart POs as Sales Orders (standard Versa import)
2. User opens Logistics → Loads Management
3. User filters the grid to the relevant orders
4. User creates Loads using active prefixes and assigns SO lines to them
5. User reviews Load totals and line groupings
6. User finalizes each Load when ready
7. User creates one consolidated Dropship PO per Load, selecting the manufacturer.
8. PO is emailed to the manufacturer from within Versa
9. Standard Versa shipment, invoicing, and payment workflows continue from here

[VA-10282] - New opportunity listing page

• The opportunity listing page is a simple list-based page, and we will redesign it to be more like a dashboard. There is a widget called Pipeline that should be used as the interface for the new opportunity listing page. 
• Versa will retain the listing page and rename the Opportunities menu item to 'Listing'. The new page will be called Opportunities, which will take the current name.
• The user should be able to choose the pipeline to view on the page (in the widget, the user needs to click on the settings icon to change the pipeline). Show the pipeline list at the top left of the page. At the top of the page, add a button to create a new opportunity which will redirect to a new page to create a new opportunity. Similar to the listing page. The user can filter opportunities by Date.

[VA-10306] - Shipping Address New Import Format

• User wants to be able to upload a new shipping address easily using a new format. 
• Versa will use the company name to match the customer by name. If a customer is not found, we will skip the lines and move to the next.
• Create a new dedicated import just for shipping to the address in the tools, imports and exports, after the sales order import (in the left menu on the page)
• In addition, Versa will log the import results in events with event detail (each line in the file will have an event detail). Either we skip, import with success, or import with an error.

[VA-10312] - Move transfer menu to be inside the logistics Menu to reduce # of main menu items