The POS Software Blog

The POS Software Blog

News from Tower Systems about locally made POS software for specialty local retailers.

TagPOS feature requests

Small business retailers in control: Software Ideas: how our customers help shape what we build

S

Most software companies decide what to build behind closed doors. A roadmap is set somewhere, customers find out when a feature appears or does not, and the cycle continues without them. At Tower Systems, our customers help decide what we build next, openly and on the record.

We call it Software Ideas.

Transparent and democratic software enhancement discussion.

Software Ideas is many years old and remains a key tool that Tower Systems customers love.

How it works

Any customer can submit a suggestion — large or small, anything that would genuinely help their business. Before it goes anywhere, our team checks that it can realistically be built. Once it passes that check, it opens for all customers to vote on.

The ideas with the most support move up the list. That list shapes what we develop next.

Why we built it this way

We could have kept our roadmap private. Most companies do.

We did not, for a straightforward reason: customers deserve to see what has been suggested, what others are supporting, and where the software is heading. We also check viability before a suggestion goes to a vote, so we are not raising expectations for things we cannot deliver. What goes to a vote is something we can actually build.

Priorities are not set by the loudest voice or the largest account. Every customer gets a vote.

What it means in practice

The people who understand a trade best are the ones working in it every day. They see the small frictions and missed opportunities long before any vendor would. Software Ideas gives that knowledge a direct path into the product, rather than leaving it in a support ticket or a conversation at a trade event.

Why it fits how we work

We build, sell, train and support our software ourselves, here in Australia, because we want a direct relationship with the retailers we serve. A system that lets customers suggest, check viability, and vote on what gets built next is a natural part of that.

If you want a software partner that builds with you rather than at you, Software Ideas is worth a look.

How Retailers Help Shape Tower Systems POS Software Updates

H

Retail software should not stand still. A retail business changes all the time. Products change. Supplier requirements change. Customer expectations change. Staff workflows change.

That means POS software updates matter.

But there is a difference between software updates created in isolation and updates shaped by retailers who use the software every day. At Tower Systems, customer feedback is part of the development process.

This matters because independent specialty retailers often have complex needs. A newsagent, jeweller, garden centre, bike shop, toy shop, pet shop or uniform and safety business does not want generic software that ignores the detail of the business.

They need POS software that keeps improving.

Why customer-led software updates matter

Many retailers have had this experience. They use a software system every day. They can see a better way to do something. They know a small change would save time or reduce mistakes. But there is no clear path to suggest it.

That can be frustrating.

Retailers are close to the work. They know where the friction is. They know which tasks take too long. They know what staff struggle with. They know what customers ask for at the counter.

When those insights are captured and reviewed, software can improve in practical ways.

Customer-led updates help close the gap between software development and retail reality.

What Software Ideas does

Tower Systems gives customers a way to suggest improvements through the Software Ideas process.

The idea is simple. A customer identifies something they would like the software to do. They submit the suggestion. Tower Systems reviews it for clarity, technical possibility, cost and likely impact.

If the suggestion is possible and suitable, it can be made available for other customers to vote on. This helps show whether the idea solves a wider problem.

The process gives retailers a voice. It also gives the development team a clearer view of what matters across the customer base.

A practical process for real suggestions

Good software ideas need more than a wish list. They need context.

A useful suggestion explains the outcome the retailer wants to achieve. It may describe a current problem, a repeated task, a reporting gap or a workflow that could be improved.

Tower Systems reviews customer suggestions and checks whether the requested feature already exists. If it does, the customer can be pointed to the right tool or support information. If it does not, the idea can be assessed further.

This avoids unnecessary development. It also helps customers learn more about the software they already have.

Voting helps prioritise what matters

Not every idea can be built at once. That is true for any software company.

Customer voting helps identify which ideas have broader appeal. If many retailers support an idea, it can move higher in the development conversation.

This is useful for specialty retail because one business may raise a problem that many others share. A feature requested by a garden centre might also help a farm supply business. A jeweller’s workflow idea might help another repair-focused retailer. A newsagency stock process may be useful to other high-volume retailers.

Voting turns isolated feedback into a shared signal.

Closing the loop builds trust

A good feedback process does not end when the customer submits an idea.

Customers need to know what happened. Was the idea already possible? Was it unclear? Was it loaded for voting? Was it developed? Did it appear in update notes?

Closing the loop shows customers that their input matters.

Tower Systems identifies customer-suggested enhancements in update notes when those changes are included. That helps retailers see the link between feedback and product improvement.

The Beta Program adds live retail testing

Software Ideas is one part of the update story. The Beta Program is another.

A beta release is the point where new software moves beyond internal testing and into selected live retail environments. This is important because real businesses test software differently from a test lab.

Retailers use the software under pressure. They serve customers. They manage staff questions. They handle actual stock, real invoices and real sales. That environment reveals details that internal testing may not show.

Beta users can provide feedback on what works, what is confusing and what could be improved before a wider commercial release.

Why beta feedback improves release quality

A strong beta process helps refine more than the software code.

It can improve release notes. It can improve training resources. It can highlight wording that needs to be clearer. It can show where a button, setting or workflow may need adjustment.

This matters because an update is only useful if retailers understand how to use it.

For confident users, beta participation can also be rewarding. It gives them early access to new features and a direct role in shaping the final release.

Specialty retailers need software that listens

Generic POS software often works best for generic situations. Specialty retailers have different requirements.

A bike shop may care about repairs, parts, variants and service history. A jeweller may need repair tracking, labels and customer details. A garden centre may need outdoor stock handling, seasonal stock and supplier workflows. A uniform and safety business may need size, colour and style variants, group pricing and special orders.

These are not minor details. They are daily operations.

When retailers can suggest improvements, vote on ideas and participate in beta testing, the software has a better chance of staying aligned with their work.

Questions to ask when comparing POS software updates

Before choosing a POS system, ask how updates happen.

Useful questions include:

  • Can customers suggest software improvements?
  • Is there a transparent process for reviewing ideas?
  • Can other customers support or vote on suggestions?
  • Are customer-suggested features identified in update notes?
  • Is there a beta testing pathway for confident users?
  • Does feedback influence documentation and training?
  • Are updates shaped by real specialty retailers?

The answers can reveal a lot about the software company.

Software should improve with your business

Retailers do not need software that is frozen in time. They need software that evolves with their business and their marketplace.

Tower Systems’ approach to Software Ideas, customer voting and beta releases reflects a practical belief: retailers using the software every day have valuable ideas.

That makes the update process more than a technical event. It becomes a partnership.

Talk with Tower Systems about POS software that keeps improving with input from real retailers.

The POS Software Blog

Categories

Categories

Categories

Recent Comments

Monthly Archives