New Feature

[VA-10212] - Check widget for opportunities to use new opportunity total field

• We have added a new field to store the total value of an opportunity, allowing users to enter an opportunity amount without adding line items.

• Versa has also updated the widgets to use this field when displaying the total value of opportunities.

[VA-10439] - Match product by product name to Shopify SKU when a part has multiple trading names

• A user reported that when publishing a product to Shopify, Versa creates a new product instead of matching it to an existing Shopify product with the same SKU.
• Versa has been updated to correctly recognize SKUs containing special characters (such as &) during the product matching process, preventing duplicate products from being created in Shopify.
• Additionally, we have improved the product matching logic when a Shopify connection is updated or reassigned (for example, when switching the webstore connection between a part number and a trading name) to ensure the existing Shopify product is linked instead of creating a new one.

[VA-10459] - Warning about posting to GL account linked to PO item on bill item page

Bill Line Shipment Receipt Warning

Summary

When a user creates a bill line and selects the inventory value GL account associated with a shipment receipt, Versa now checks whether the user probably meant to use Link to Received Item from Receipt. If a matching receipt is available, a warning appears before the line is saved.

The user can choose Yes, Link to Receipt to switch to the normal receipt-linking workflow, or No, Post Directly to intentionally save the line to the inventory value account. Direct posting remains available because it is valid for uncommon inventory-value adjustments.

Problem and why

Users entering supplier bills can accidentally choose the inventory value GL account created when a shipment receipt was posted. When the bill pays for the purchase order item that was received, the bill line should normally be linked to the shipment receipt instead.

The warning reduces accidental direct postings while preserving the accounting team's ability to post a deliberate inventory-value adjustment.

What changed

• Saving a new bill line checks whether the selected GL account belongs to an available shipment receipt for the same entity, supplier, and currency.
• A warning identifies the receipt and purchase order before the line is saved.
• Yes, Link to Receipt selects the matching receipt and loads the receipt-linked bill line values. The direct GL posting is not saved.
• No, Post Directly confirms the user's intent and saves the bill line to the selected GL account.
• Ordinary expense accounts and bill lines already linked to a receipt continue to save without this warning.
• Existing bill lines are unchanged; this safeguard applies when creating a new bill line.

How to access

Affected areas

• New bill line creation and save behavior.
• Link to Received Item from Receipt selection and its automatic line-value loading.
• Inventory value / FIFO bucket GL account selection.
• Supplier and currency filtering for available shipment receipts.
• Bill posting after either a linked-receipt line or a confirmed direct GL line is created.
• Ordinary expense bill lines, fixed asset lines, service purchase order lines, and shipment-cost allocation lines as regression coverage.

Prerequisites

1. Use an entity with GL Posting and either Accounts Payable or Bill Entry access.
2. Have a posted shipment receipt for an inventoried purchase order item that has not yet been fully linked to a bill.
3. Know the inventory value GL account associated with that receipt.
4. Create an unposted bill for the same supplier and currency as the purchase order.
5. Have a second ordinary expense GL account for regression testing.

[VA-10463] - Speed up picklist scan for Glory Wheel
 

Summary

Improve picklist scanning speed by allowing ordinary picklist scans to post directly to the active picklist instead of first making a separate scanner-routing request.

This removes one HTTP request from each ordinary scan while preserving the current picking, packing, inventory allocation, lot/serial, and Bin Location behavior.

Problem and why

Each barcode scan currently sends one request to determine where the scan should be routed, followed by another request that performs the actual pick or pack operation.

When warehouse users scan many items, especially over mobile Wi-Fi, the additional round trip adds noticeable delay to every scan. On the Picklist screen, the destination is already known, so this routing request is unnecessary for ordinary product, part number, lot, serial number, and Bin Location scans.

What will change

• Ordinary scans made from an active Picklist screen will be submitted directly to that picklist.
• Product barcodes and exact part numbers will continue to be accepted.
• Lot-controlled and serialized products will continue to use the existing inventory validation and allocation logic.
• Bin Location scanning will continue to work.
• Picking and packing behavior, quantities, statuses, sounds, and messages will remain unchanged.
• The existing scanner-routing request will remain available for special system barcodes, URL barcodes, non-picklist screens, and fallback handling.
• No barcode lookup data will be cached in the browser as part of this task.

Affected areas

• Picklist picking
• Picklist packing
• Product barcode and part-number scanning
• Lot and serial-number scanning
• Bin Location scanning
• System-generated barcodes
• URL/navigation barcodes
• Scanner behavior on screens other than Picklists
• Mobile and Android handheld scanners configured for keyboard output

Prerequisites

• A picklist containing several ordinary products
• A lot-controlled product
• A serialized product
• A Bin Location-enabled entity, when available
• A scanner configured to send scans to Chrome as keyboard input
• Permission to pick and pack the selected picklist

[VA-10466] - Add setting to use customer's payment terms

• Versa has added a new setting to the Shopify integration that allows Shopify orders matched to an existing customer to use that customer's assigned payment terms.
• This is useful when an existing customer with non-immediate payment terms (for example, Net 30) places an order through the Shopify webstore. When this setting is enabled, the sales order will use the customer's existing payment terms instead of the default payment terms configured in the Shopify webstore settings.

[VA-10467] - Faire payout import: allow import for the same day

• For the Faire integration, Versa has been enhanced to support multiple payouts received on the same day.
• Users can now upload multiple payment files with the same payment date, allowing all payouts to be processed correctly.

[VA-9323] - Add bi-weekly to Invoice "make recurring" option

• Versa has added a bi-weekly recurrence option for recurring invoices. Versa has added support for this frequency and extended the same functionality to recurring bills, providing consistent scheduling options across both transaction types.