Software Update: July 7th 2026

This update includes improvements to SMS configuration, trade-in workflows, label printing, reporting access, supplier management, and performance when working with larger data sets.

SMS and Communication Improvements

  • Added support for defining approved SMS sending numbers for an organization.
    • This allows multi-location organizations to specify which phone numbers should be used for outbound SMS messages without requiring separate POS subaccounts for each location.
    • This change also helps streamline SMS setup and may simplify the 10DLC compliance process. Previously, each store needed to be put into its own subaccount so that when the POS queried the SMS provider for a list of sender numbers available, it would only receive numbers designated for that store. Now we can explicitly tell the POS which number use, which negates the need to setup subaccounts (simplifying the 10DLC process).
    • To use, go to Settings > Manage Organizations and edit your store. In the box on the upper right labeled SMS Settings, you would add a new parameter called “filter_numbers” with the value being the number from your SMS provider to use for that store (example: +16025842483″).
  • Fixed an issue where Grindless was not properly responding to incoming text commands such as “Shifts” or “Balance” with the appropriate information.

Trade-In and Labeling Improvements

  • Added support for notes inside of trade-ins, similar to notes available on a sale. This gives stores a clearer way to record additional context or internal details during the trade-in process.
    • Adding notes works similarly to how it does for customer orders. Next to the trade-in number is a paperclip button. Click on this button to show a pop-up where you can add notes that will be tied to the current trade.
  • Improved support for printing bin barcode information on labels.
    • This provides better flexibility for trade-in label workflows where a standard Barcode element may not be the ideal option. It allows you to print a barcode for a binned item and when scanning that label, the POS will know which product (and in which bin) you’re pulling the item (i.e. game disc) from without having to select it during a sale.
    • To use this, go to Settings > Manage Labels and open a label template. Add a new element and give it the name “BinSKU”.

Sales and Performance Improvements

  • Fixed an issue on the Tasks >Price Tags page where selecting a large number of entries could cause the client to crash or become unresponsive.
  • Improved Sale screen performance when using the Quick Sale customer account with a large number of completed orders. Previously, if a Quick Sale customer had a large amount of orders (i.e. tens of thousands of dollars worth of orders) associated to it, the POS would lag when adding products to a Quick Sale order due to how it looks up past sales information. This has been fixed.
  • Added Support for eBay orders to properly sync to Grindless through the Shopify Marketplace App for clients who have Shopify integration enabled in the POS. This may also enable other marketplace sources beyond eBay to sync orders to Grindless as well. If you have a Shopify site that’s linked to Grindless and you sell through their marketplace app on other platforms beyond eBay, we welcome your feedback about this topic.

Reports, Events, and Support Fixes

  • Fixed an issue where the Attendees section could be missing when viewing past events. You can now see what customers participated in past events as expected.
  • Restored the Permissions section in submitted bug reports, giving Grindless Support better context when reviewing reported issues.
  • Fixed an issue where certain roles could receive an “Unauthorized” message when loading the Trade-In Summary from the Sales Report page.
  • Fixed an issue where the Supplier Orders report could incorrectly display an “Unauthorized” message for some users.

Supplier Fixes

  • Fixed an issue where saving an existing supplier could result in a critical error.
  • Fixed an issue where editing a newly created supplier could also trigger the same save error.

 

Schedule a Demo