ShopKeeprr 1.1.2 is here — download the free core. Get it from download.shopkeeprr.com. ShopKeeprr Store is live

Our commitment · the 1.1 line

Ecommerce doesn’t need rebuilding.
It needs reinvigorating.

ShopKeeprr is our answer to a simple problem: too much commerce software treats every merchant as a reason to start over. We think the better work is keeping a good store alive — current, upgradeable, portable and yours.

Updated 16 November 2026 · Applies to ShopKeeprr 1.1.2

Our position

The checkout is not the frontier. Keeping it alive is.

Commerce has spent decades solving the hard parts: catalogs, carts, tax, fulfilment, refunds and reconciliation. Those patterns deserve respect, not a rewrite. The part that has aged badly is everything around them — whether a merchant can upgrade without a project, move data without a consultant, and keep the software after the launch is over.

So we renew the useful parts. We keep the storefront, the admin and the data model current; we make migrations ordinary; and we leave the door open for you to leave. That is a different ambition from building a new ecommerce religion. It is also more useful.

We keep the core moving.

Software does not stay current by accident. Every release gets a version, a migration path, an upgrade note and a test pass against the behaviour people depend on. We would rather ship a smaller release that can be trusted than a theatrical launch that cannot be upgraded.

01

Maintained, not abandoned

Bug fixes, dependency updates, security work and compatibility changes are part of the product. The 1.1 line is current at 1.1.2, with WooCommerce migration, tax import and the upgrade work that came with it.

02

Upgrades are a feature

Database changes ship as migrations. Release notes explain what changed and what to check. Signed updates, backups and rollback are there for the moments when a release needs to be undone.

03

Compatibility over novelty

Existing products, orders, customers and extensions matter more than a clean-sheet data model. We add capability without asking a working store to become a migration project.

04

Plain answers

When something changes, we say what changed. When something is not included, we say that too. A release note should reduce uncertainty, not create a new support queue.

Reinvigorate. Don’t rebuild.

There is a difference between modernising a store and starting a new one. We are interested in the first. The second is how merchants end up with two catalogs, a stalled migration and a new set of monthly fees.

The rebuild instinct

Start again. Import later.

  • Rewrite the checkout around a new set of assumptions.
  • Treat existing data and workflows as legacy.
  • Make the platform the centre of the relationship.
  • Add features faster than the upgrade path can carry them.
  • Call migration a service you buy after the fact.

The renewal instinct

Keep what works. Fix what doesn’t.

  • Respect proven commerce flows and remove friction around them.
  • Bring existing data with you — including WooCommerce stores.
  • Keep the merchant in control of the server, code and database.
  • Ship upgrades that ordinary store owners can follow.
  • Make leaving possible, so staying is a choice.

That is why the 1.1.2 migration tool is more than a feature bullet. It is the commitment in practice: a store can come from another platform, keep its products, variations, customers, orders and standard tax rates, and become a ShopKeeprr store without beginning again.

What renewal looks like in 1.1.2

Bring the store with you

WooCommerce migration imports products, variations, customers, orders, standard tax rates and supported tax options through CSV/ZIP or a read-only REST API, with dry runs and resumable batches.

Make the upgrade boring

The 1.1.2 upgrade added four migrations while leaving existing data in place. The 1.1.2 tax import is additive and needs no schema change: back up, replace the files, clear the cache.

Keep the fundamentals

PHP 8.3+, Laravel 13, MySQL or SQLite, four store models, the builder, themes, extensions and signed updates — the base stays usable and portable.

Freeware, without the fog.

ShopKeeprr is freeware in the everyday, zero-cost sense. It costs nothing to download, install, run or modify for personal or commercial use. There is no account, activation, trial clock or feature paywall. The source is included.

“Freeware” is not a certification or a single legal definition. It is a distribution label, and it is often used for closed-source software that is free of charge but restricts modification or redistribution. ShopKeeprr is more open than that in one direction and less open in another:

QuestionShopKeeprr
Does it cost anything?No. The core is free to download, install and run, including for client work.
Is the source included?Yes. The application source ships with the download.
Can I modify it?Yes. You may modify the core for your own use or a client project.
Can I redistribute the core?No. The license does not permit reselling, redistributing, sublicensing or publishing the core as a competing product.
Is it OSI open source?No. The redistribution restriction means it does not meet the Open Source Definition.
Is it freeware?Yes. Free in the zero-cost, source-included sense, and now the public label we use. It is still more precisely described as free and source-available because “freeware” often implies closed source.

The practical answer

There is nothing technical to change to call ShopKeeprr freeware. The core is already free, the terms are published, and no payment is required to run a complete store. Freeware is a label, not a switch you flip in the codebase.

If the goal is a stricter label, the license is the lever: OSI open source would require permitting redistribution of the core. That is a deliberate business decision, not a packaging step. We have chosen to keep redistribution restricted so the free core is not republished as a competing product. Paid plugins, themes and services remain optional and do not change the core’s free-to-use terms.

The standard we hold

If we can’t explain the upgrade, it isn’t ready.

No schema change without a migration. No release without a note. No migration that traps the data. No feature that makes leaving harder. That is the standard behind the 1.1 line, and it is how we intend to keep earning the word “maintained.”