The POS Software Blog

The POS Software Blog

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

Tagbookshop software

How to choose software for your independent bookshop

H

A bookshop isn’t like most other shops, and its software shouldn’t be either.

Local independent bookshops are unique, with a voice of their own that is vital to in-store and online representation.

A local indie bookshop carries thousands of titles, and plenty of them sell one copy a year. Customers ask for “the new one by the woman who wrote that lighthouse book”. Every supplier has its own rules for ordering and returns. Generic retail software isn’t built for any of this, and it doesn’t take long to show. Our software fore bookshops is specialty retail software.

Start with how your shop works

Before you look at any software, write down how a normal week runs. Receiving stock, special orders, returns, events, the book club, online orders.

Then mark the jobs that eat the most time and the mistakes that keep happening. That’s your list of problems to solve. Take it to every demonstration. It stops the presenter steering you towards features you’ll never use.

Title lookup and book data

When a new title arrives, you should be able to scan the barcode and have the title, author, publisher and category fill in. Typing them by hand is slow, and the typos come back to bite you every time you search or run a report.

Check that the software connects to the industry data you already use, such as TitlePage. Then ask how it handles imported titles with international barcodes. If you stock overseas editions, adding them should be no harder than adding local ones.

Finding books in your own stock

Customers rarely give you the full title. They remember a word from the cover, half a name or just the author’s surname. Your software should let you search by title, author, or part of either.

Test this in the demonstration with real requests from your counter. If it takes more than a few seconds to find a book, your staff will give up on the search and start walking the shelves instead.

Ordering and supplier connections

Ordering is one of the biggest admin jobs in a bookshop. Look for software that connects to the platforms book suppliers use, such as Pacstream. Ordering from inside your POS means less double handling and stock records you can trust.

Find out how supplier invoices get into the system, too. The less you have to type, the better.

Returns

Handled badly, returns tie up cash and shelf space. Good software shows you which titles are eligible to go back, based on when they arrived, how many have sold and how many are still on hand.

Ask the presenter to take you through a full return, start to finish. It should follow a clear process that matches the way publishers and distributors expect returns to arrive.

Special orders

Special orders build loyalty. Tracked on paper, or in someone’s head, they also go missing. Your software should record the order, track it until it arrives and help you let the customer know it’s in.

Check how the system flags a special order when the stock is received. The last thing you want is a customer’s book going onto the shelf and out the door with someone else.

Clubs, loyalty and community

Book clubs, school and library groups, author events and loyalty programs are a big part of why people choose an independent bookshop over a website.

Your software should keep customer records and purchase history, and handle loyalty rewards and group pricing. Being able to contact customers based on the authors and genres they buy is one of the simplest ways to bring them back.

Selling online

If you have a website, or plan to, check how the POS connects to it. Stock should stay in step between the shop and the site, so you don’t sell a book online that went out the door yesterday.

Shopify, WooCommerce and BigCommerce are common choices. Ask which ones the software supports. Choice matters here, because if your POS only works with one platform, changing later gets painful.

You want control over your online presence, including how you describe what you sell.

Accounting, rostering and payments

Your POS shouldn’t sit on its own. See whether it links to your accounting software, such as Xero, and to rostering tools such as Tanda or Deputy if you use them. Confirm which EFTPOS providers are supported, and whether the software adds transaction fees of its own.

Cloud or desktop

Some bookshops want cloud software they can reach from anywhere. Others want a desktop system that keeps trading when the internet drops out. Ask whether you get to choose, and whether you can switch later.

Support and training

On a busy Saturday with a queue at the counter, support matters more than any feature. Ask who provides it, where they’re based and what hours they keep. Support from the company that writes the software is usually faster and better informed than support from a reseller.

Training matters as well. Casual staff come and go, and good training material gets them confident on the counter sooner.

Questions to ask in every demonstration

  • Can you add a new title by scanning its barcode?
  • Can you find a book using part of the author’s name?
  • How does Pacstream ordering work from inside the software?
  • Can you walk me through a complete return?
  • How are special orders tracked, and how is the customer told?
  • How does stock stay in step with my website?
  • What does it cost each month, and what’s included?
  • Who answers the phone when I need help?

Bring real titles and real situations from your shop, and ask the presenter to work through them live. A polished script tells you very little about a wet Tuesday with two staff away.

Look past today

Ask how often the software is updated, how updates arrive and whether recent changes came from booksellers’ feedback. A company that’s still developing its product, and still listening, is a safer bet than one that’s coasting.

Some systems now offer AI-written product descriptions and automatic invoice importing. Both take a lot of the typing out of a big week of new releases.

How Tower Systems helps independent bookshops

Tower Systems has made and supported POS software for independent specialty retailers in Australia and New Zealand since 1981. Its bookshop software is built for local independent bookshops, not chains. Our software for bookshops is made for bookshops.

Our pricing is transparent.

Title lookup runs through TitlePage and ordering through Pacstream. Staff can search by title, author or part of either, and scan international barcodes. Returns follow a structured process that picks out eligible titles, and special orders are tracked from the first enquiry to collection. Book club management, loyalty tools and group pricing are built in.

For online sales, Tower works with Shopify, WooCommerce, BigCommerce and Magento. It also links to Xero, Tanda and Deputy. You can run it in the cloud or on desktop, and when you call for help, you’ll reach a local team.

If you’re reviewing software for your bookshop, bring a list of your own titles and situations. Tower Systems will happily work through them with you in a demonstration.

BOOK A BOOKSHOP DEMONSTRATION

Book a demo. We’ll set up Tower Systems as a book shop would use it, answer your questions and record the demonstration so you can review it whenever you like. Understanding your business comes first. If our software isn’t suited to something you need, we’ll be honest about that. Email sales@towersystems.com.au, or call 1300 662 957 in Australia or 0800 444 367 in New Zealand.

Free AI POS software support at 11pm: the Tower Systems chatbot

F

Questions do not keep business hours. A retailer reconciling at the end of a long day, or setting up a new supplier at ten o’clock at night, needs an answer then. Not the following morning.

The AI chatbot on the Tower Systems website sits in the bottom left hand corner of every page. Clicking the box opens it. From there, it is a conversation.

What separates it from general purpose AI tools is what it has been trained on. The chatbot is trained only on Tower Systems software and the company’s own documentation. It does not roam the internet and it does not invent answers. When it does not know something it says so, and it makes clear how to reach a human. That constraint is deliberate, and it is the reason the answers can be relied on.

The usage patterns have been telling. People are asking questions at nine, ten and eleven o’clock at night. One user worked through seven or eight questions in a single session, building on each answer as they went.

The scope is broader than software mechanics. Rather than only explaining which button to press, the chatbot offers context and helps with the decision sitting behind the question. One retailer described a tough trading period and received useful business advice in response.

It is also not generic. It was built for the channels Tower Systems serves: jewellers, garden centres, bike shops, newsagents, bookshops, pet shops, toy shops, music shops, camping and outdoors businesses, fishing businesses and firearms dealers. The advice reflects those specific trading realities.

More than forty languages are supported, which matters in Australian and New Zealand retail. The chatbot is available twenty four hours a day, seven days a week, at no cost, to anyone who visits the site.

It sits alongside the Retailer AI tools inside the software itself, where retailers report saving between five and ten hours a week on supplier invoices, insights, product descriptions and reordering. What those hours are worth in dollars is a story for its own post.

Human support has not gone anywhere. The chatbot simply means the wait is optional.

Tower Systems builds POS software for specialty retailers across Australia and New Zealand. Locally made. Locally supported.

What actually goes into a Tower Systems software update

W

We’re deep into building our next update right now, which seemed like a good reason to explain what that actually involves. It isn’t someone sitting down and writing new code for a few days. It’s a process, and most of it happens before a line of code changes.

We start with what customers tell us

Every update begins with a review: ideas submitted through Software Ideas, feedback from customers directly, and what our own support team hears on the phones every day. We look at what’s urgent and what will genuinely benefit customers, not just what’s easiest to build.

This step takes longer than people expect. We test what we’re told against the software itself before we act on it, because a suggestion that sounds right in a phone call doesn’t always hold up once you’re inside the actual system. Thoroughness costs time here, and we spend it.

Planning it properly

Once we know what we’re building, we scope it: what the change actually involves, and what else in the software it touches. A newsagency’s software talks to a lot of different parts of itself, magazines, lottery, gifts, loyalty, so a change in one place can affect something you weren’t expecting elsewhere. Understanding that before we start building saves everyone trouble later.

Building it, then testing it, and testing it again

This is the part most people picture when they think of software development, and it’s the smallest piece of the whole process, by far. After the build comes testing. Then more testing. Then testing again. It’s repetitive by design.

We document it before we release it

Once the change is solid, we write it up properly, so it can be explained clearly to customers rather than dropped into an update with no context. Good software isn’t just software that works. It’s software people understand how to use.

Beta testing, in real shops

Before anything goes to every customer, it goes to a small group of engaged customers in live, trading shops. Real stock, real customers, real Saturdays. That’s a different test than anything we can run in-house, and it catches things our own testing sometimes doesn’t.

Only then do we release it

All of that has to happen before an update reaches your till. It’s slower than just shipping code, but it’s why updates tend to work the way they’re supposed to when they land.

We’re in the middle of this right now, building the next one. It’s the same process every time, because it’s the one that works.

The POS Software Blog

Categories

Categories

Categories

Recent Comments

Monthly Archives