Skip to main content
All CollectionsNew Releases
Release Notes - 6.5.44
Release Notes - 6.5.44

Release notes for Ample Organics version 6.5.44

Andrew Day avatar
Written by Andrew Day
Updated over 6 months ago

In this update, we added an exciting new feature- GTIN-12 Barcode scanning for Order Fulfillment, as well as a number of new additions and bug fixes.


New Feature: GTIN-12 Barcode Scanning 🤖

The GTIN-12 Barcode scanning feature is now available on the Gun App! This feature helps streamline order fulfillment by allowing for the scanning of third-party GTIN-12 barcodes for both cannabis products and accessories, instead of internally generated QR codes.

Check out the resources below to learn how to setup GTIN scanning, and see how it works!

How to Enable GTIN Scanning 📖

For Cannabis Products:

In order to enable GTIN scanning for cannabis products, the following requirements need to be met:

  • SKU GTIN: The SKU’s “GTIN” field must contain the 12-digit number that matches the barcode’s GTIN, excluding the two leading zeros. This can be found on the SKU setup page.

  • Bulk Lot Name: The “Name” of the Bulk Lot must match the Lot number of the barcode.

  • Inventory Packaged On: The “Packaged On” date of a Received Inventory or Packaging Run must match the Pack Date of the barcode.

    Found under a Product’s Inventory tab, select either Packaging Runs or Received Inventory. Users can edit the Packaged On date so that it matches the date on the barcode. 📅

For Accessories:

In order to enable GTIN scanning for Accessories, the following requirements need to be met:

  • SKU GTIN: The SKU’s “GTIN” field must contain the 12-digit number that matches the accessory barcode’s GTIN, excluding the two leading zeros.

Please Note: If all requirements listed above are not met, GTIN scanning will fail and the following expected error message will be displayed:


If you encounter this error, please review the initial three requirements (GTIN, Name, Packaged On) to ensure there are no typos or mistakes in the data setup.

Once those required steps are complete, users can now begin scanning the product.

GTIN Scanning Process on the Gun App 🔫

  1. After logging into the gun app, choose Order Fulfillment. GTIN scanning will only work in the Order Fulfillment module.

  2. Use the “hamburger” menu to choose your desired Picking Mode and scan one of the GTIN codes to pick the bottle. If volume is enabled on the scanner, users should hear a beep after successfully scanning the GTIN

  3. Once all items have been scanned the user will be notified the order has been successfully picked.


Need help or want to learn more about GTIN Scanning?

Reach out to our team for support!


Additions & Enhancements💡

We've also added several enhancements and usability improvements to this version!

Allow Received Inventories to be archived in Wholesale

We've made a few small changes to allow users to archive Packaged, Unpackaged (Bulk), and Accessory Received Inventories through the Wholesale module.

Round Bulk Lot Current Weight and Volume when creating a shipment

We have also made a change to fix trailing decimals for wholesale Sales Order Shipments.

Allows Sales Orders to have a total of $0

We have added the ability to create Sales Orders with totals of $0. This will help LPs by facilitating transfers between their facilities

Other Enhancements:

  • Sort Vendor Addresses by Name: We changed the way Vendor addresses are sorted in the Wholesale module. Addresses are now shown in alphabetical order.

  • Add Restrictions for Multiple Product Discounts: We have introduced a safeguard to prevent eligible order discounts from exceeding the order item subtotal.

  • Add Archived-On Column to Sales Order by Line Item Reports: Ample now notes the time when a Sales Order was last archived, and we have added an Archived On column to the Sales by Line Item reports.

  • Add Vendor Shipping Address Name to Both Sales by Line Item Reports: We have added a column to the Wholesale reports which allows clients to report on which retailer is purchasing their products, with greater visibility and insight.

  • Add a Created By Column to the VAC Active Patients Report: We have added a column to the VAC Active Patients report to show the full name of the user who created the policy.

  • Add Pagination for Shipment Batches: We have improved the overall speed of the Shipping module substantially by adding pagination. Previously all Shipment batches were on a single page.


📝Did you know?

Users are able to reclaim units via the Product Inventory page; this functionality is only available through the web app, accessible through the browser on your PC.

Users can also destroy units on the Bulk Lot’s Destruction tab.


Bug Fixes 🔧

In this version we've squashed a few bugs! See the list below:

  • Fixed! Duplicate Weight Events when Re-Entering Bulk Lot Destruction: We introduced a change that prevents users from being able to quickly resubmit a second Bulk Lot destruction. This will prevent duplicate weight events from occurring in error.

  • Round Current Bulk Lot Weight to Four Decimals: We have fixed a rounding issue when reclaiming units from packaging runs, which will help resolve weight discrepancies in the bulk lot.

  • Fixed CTLS Unpackaged Closing Inventory: We have made an adjustment to when Ample pulls values to calculate the CTLS closing inventory to better reflect work done in the reporting month.

  • Optimize Bulk Lot Current Weight & Volume: We have increased the timeout threshold to improve performance when viewing Bulk Lots, and Bulk Lot Weight Events

  • Add Pagination for Shipment Batches: We have improved the overall speed of the Shipping module substantially by adding pagination. Previously all Shipment batches were on a single page.

  • Fixed Sorting of Bulk Lots and Productions within the Work Orders Module: Bulk Lots and Productions are now sorted alphabetically within the Work Order module. Previously, they were sorted chronologically.


You are part of this and we really appreciate that! 🥰

Would you like to send us a suggestion or a feature improvement? Please contact our Technical Support Team at [email protected].

Did this answer your question?