When we acquired Qsales in May of 2021, we did not plan to change the version sequence of the product. The Qsales version was 12.x at the time, and we stuck with that through the release of the API version (v13), and then with Classic (v14).

The problem we hadn’t anticipated at the time was that our licensing system would require us to release each new version in sequence, even when subsequent versions of API or Classic would skip a number each time. For instance, the next version of API would from from v13 to v15, and the next version of Classic would go from v14 to v16. This is confusing for users who are using either API or Classic, and are constantly skipping a version number with each upgrade.

The simple solution for this problem is to drop the version sequencing for both products, and move forward with build numbers for the API and Classic product names. What’s the difference? Well build numbers are like Act! updates, they’re not something you track for commercial purposes any more, but rather use them to ensure you’re current.

Commercially, this change was made possible when we switched to subscription last year. Instead of worrying about having to pay for an upgrade, Qsales subscribers are now always entitled to the latest version. The only thing they need to keep track of is which product they’re using, Classic or API, and whether they’re on the latest build. It’s that simple.

We believe this is product maintenance model is better and simpler for our customers, and avoids the confusing version sequence that started to develop (whatever happened to Windows 9, anyway?).

These changes will be implemented in the 3rd or 4th week of January.