Every time I get called in to fix a retail system that has gone sideways, the people who know what actually happens are behind the till. Not the head office spreadsheet, not the dashboard, the person who knows that the blue jackets sell in a fortnight and the size 8 boots never move. So I was glad to read Oxfam's retail director arguing that stores and volunteers remain the engine behind its digital growth as the charity pushes into rental and livestream shopping.
That framing matters because the usual pitch runs the other way round. A supplier turns up with a platform, promises it will "unlock online revenue", and the shop floor becomes a fulfilment cupboard for someone else's website. Oxfam is doing something harder and smarter: treating the physical shop as the source of the data and the expertise, and building digital channels on top of it. That is the correct architecture, and it is also the more difficult build.
One-of-a-kind stock breaks most retail software
Here is the technical problem hiding inside second-hand retail, and it applies to a lot of independents in Northern Ireland too: antiques dealers, vintage clothing, craft makers, anyone selling salvaged or handmade goods. Standard retail software assumes a SKU represents many identical units. You have 40 of item ABC123. Sell one online, sell one in store, decrement the count.
Unique stock does not work like that. Every item is quantity one. That sounds simpler but it is actually worse, because the cost of getting it wrong is total. If two customers buy the same jacket within thirty seconds, one of them is getting a refund and an apology. And every item needs its own photograph, its own description, its own measurements. The labour is per-item, not per-line.
What I build for that scenario looks different from a normal shop system. A single stock record that both the till and the website read from, with a proper reservation state rather than a simple in-stock flag. An item goes from available, to held, to sold, and the hold expires. The till has to respect a web hold, which means the EPOS needs to talk to the same database in real time rather than syncing overnight. Overnight sync is where the double-sale problems live.
The other half is the intake workflow. If listing an item takes fifteen minutes of someone's time, you will never list enough of them to matter. I would put the effort into a phone-based capture tool: photograph, dictate or select attributes from a short pick list, price, print a label with a barcode that ties the physical item to the online listing. Get that under ninety seconds per item and online becomes viable. Leave it as a laptop-and-spreadsheet job and it dies within a month.
Rental and livestream are the same problem wearing different hats
Rental adds a time dimension. Your stock is not sold or unsold, it is booked for certain dates, out, back, being cleaned, available again. That is a booking engine bolted onto inventory, plus condition tracking, plus deposits. It is more work than most people expect, and I would not attempt it on a platform that only understands sell-and-decrement.
Livestream selling is a reservation problem under time pressure. Someone comments, you need to hold the item, take payment, and stop the shop floor selling it. If you are running a Facebook or Instagram live, that hold has to happen in seconds. The engineering answer is a small queue and a short-lived hold with an automatic release, not a member of staff frantically typing.
Both of these are achievable for a small business. Neither is achievable if the underlying stock data is not trustworthy first. Get the single source of truth right, then add channels.
What to ask before you sign anything
If a supplier is selling you an online ordering system or an ecommerce add-on, ask these:
- Is stock a single shared record between till and web, and how fast does a sale propagate? "Every 15 minutes" is a double-sale generator for unique stock.
- Can I export my full product, customer and order history in a usable format, on demand, without paying extra?
- What does per-item listing actually take, timed, on a phone, by someone who is not a developer?
- Does it handle quantity-one items and holds natively, or is that a workaround?
- What are the transaction fees on top of the monthly cost, and what happens to my data if I leave?
The answer for a lot of smaller retailers is a hybrid: a solid off-the-shelf EPOS for the counter, a lightweight custom layer for listing and reservations, and integrations that keep the two honest. That is most of the retail software Northern Ireland businesses actually need, and it costs a fraction of a full platform migration.
The bit I would underline from Oxfam's approach is the ordering. People first, data second, channels third. Digital growth that ignores what the shop floor already knows just automates the wrong decisions faster.
If you are weighing up an online ordering system for your Belfast shop, or your existing setup is quietly losing stock accuracy, get in touch and we can talk through what is worth building and what is not.