No more version numbers

FreshStore has been on version 3.1 since last August. But plenty has shipped in the months since. New features, improvements, fixes. None of which you needed a version bump to use.

That’s how SaaS works. We deploy, your store has the update, you use it. No download, no install, no “upgrade” step. So the version number at the top of each release post has been doing very little for you, and quite a lot of extra work for us.

We’re dropping it.

Why version numbers don’t fit

Version numbers make sense for software that lives on your computer. You need to know which build you have so you can decide when to update. Everyone on FreshStore is already on the latest build the moment we push it, so the number is only ever decoration.

What it’s actually been doing:

• Creating pressure: “is this feature big enough to justify v3.2?” is not a question that helps anyone. It slows announcements and bundles everything into one annual-feeling post.
• Slowing the feedback loop: big releases means long gaps between posts. If a feature shipped in October, you probably heard about it in April. That’s not useful.
• Doubling up: we already post when a feature ships, then post again when it’s “included in” the next version. Same feature, two announcements, neither as clear as it could be.
• Not mattering to you: you care what your store can do today, not which number we’ve slapped on it.

How updates will be announced from now on

Three types of post. No schedule, no version numbers.

Feature posts. When we ship something significant, you get a standalone post about it. You’ve already seen this pattern with the AI Fill Categories feature, the Affiliate Link Checker, the AI Image Upgrade, and the Amazon Creators API credentials rollout. That becomes the default for anything substantial.

Catch-up posts. Not every improvement warrants a whole post. Quality-of-life tweaks, performance work, small fixes, minor additions all get bundled into a single catch-up summary when enough has built up. Might be monthly, might be every six weeks, might land when a particularly busy stretch demands it.

News posts. Pricing, policy, partnerships, anything else worth a proper announcement.

What’s next

A catch-up post landing this week covering everything that shipped between August and now that didn’t get its own announcement. There’s a lot of it.

After that, a run of standalone posts for the bigger features still waiting for their moment: the full REST API, Product Review Writer, Custom Offer Logo, and a couple of new tools for keeping your store tidy. One at a time, as they’re ready.

Thanks for sticking with us. The pace has picked up; the announcements are catching up with it.