Skip to content
Work Expertise Services CV Portfolio Integrations Laravel packages Blog Sign in Get in touch

Digitalising second-hand

A shop full of unique items, without a supplier and without reordering, staffed by people who sometimes started last week. Almost all retail software assumes the opposite. Below is where that pinches and what I built for it.

Where it pinches

Retail software is built for new goods. There is a supplier, there is a purchase order, there is an article number with thirty identical items behind it, and the question the system answers best is how many of something are still on the shelf. In a reuse shop none of those four assumptions holds. What comes in, comes in because someone gave it away, every item is a thing of its own, and the question is not how many are left but whether it will go before it takes up space.

The result is that a standard package fits for eighty per cent and has nothing to say about the twenty per cent that makes the difference. That is where the work is: not building a new till system, but the layer next to it that answers the questions the package was not made for, and that keeps feeding the package so the bookkeeping and the till stay in agreement.

On top of that, a reuse shop is rarely just a shop. There is a social mission attached: people gaining work experience, a reuse centre that also collects and sorts, and an umbrella body that has to report across all locations to whoever helps pay for the operation. Each of those three lays its own demand on the system, and they regularly contradict each other.

What I built on it

Six pieces between a bag coming in and a number somebody can use.

From barcode to price

Scanning a book with the camera of a phone, and showing straight away what it fetches elsewhere. The scanner stores the isbn, retrieves title, author and edition, and keeps track of what has already come past. Whoever stands behind the table no longer has to estimate from memory.

Shops under one umbrella

A group of shops that each have their own till, their own range and their own bookkeeping, but want to report together. That asks for a data model in which a location really is a location, and not a filter field stuck on afterwards.

The loyalty card without paper

A card that gets lost, creased or left at home is a card that does not get scanned. In Apple and Google Wallet it is always in your pocket, works in every shop in the group, and a new balance appears on it by itself.

Reporting across locations

What comes in and goes out per shop, per product group and per period, pulled from the till system and put into a screen of your own. Not to replace an export but to answer the question without anyone having to make an export.

Signing up at the till

Someone who wants to become a member at the till has no appetite for a twelve-field form. A code on the screen, the phone alongside, done. The integration with the till system makes sure the card works from the next purchase on.

Ready for the product passport

Keeping data about an item, where it came from and what happened to it, in a structured way rather than in a free text field. Today that is administration; in a few years it will be the only way to get to a passport at all.

How it is put together

Five starting points that decide whether a system in this sector gets used or merely installed.

Every item is unique, so the article number is not

In ordinary retail everything hangs on an article number: thirty identical jumpers, a supplier, a purchase order. Here every jumper is a thing of its own with its own price and its own story. A system that assumes stock per article counts nothing useful here. What does work is a product group for the reporting and a unique item for the sale.

The range is whatever comes in

There is nothing to reorder. If a category empties out, that is not a shortage but a fact, and a "low stock" alert is then noise. What does matter is the flow on the other side: what came in, what of it went to the shop, and what stayed behind.

The shop is also a workplace

Some of the people behind the till are there to gain work experience, sometimes with a language barrier or after a long break. A screen that asks four clicks where one would do is not an inconvenience there but a barrier. That makes screen design a functional requirement and not a finishing touch.

Pricing is estimating, not looking up

The price comes from someone holding the item. Software can at most help: show what comparable items fetched, suggest a range, flag an outlier. Anyone who tries to automate that estimate gets a system that is ignored, and then the numbers after it are worth nothing.

Measuring what does not sell

The interesting number in reuse is not turnover but what does not make it round two. That is rarely in a till system, because that is built to count sales. Tracking it asks for a step of its own, and that step has to be small enough to still be taken on a busy day.

The digital product passport

Europe is working on a passport per product: a data carrier, usually a qr code, pointing to a file with what is in it, where it came from, how it can be repaired and what should happen to it when it is spent. The idea is that a product carries its own history along instead of leaving it behind at the manufacturer.

For those making new products that is an administrative task. For those reusing it is something else: you did not create that passport, you receive an item that may have one. The question then becomes whether you can find it, whether you may access it, and whether you can add to it when you repair or resell. Those three questions are technical, and they are being decided right now.

What a reuse organisation can already do with it: keep the data it collects anyway in a structured way rather than in a free text field, and record per item what happened to it. Today that is extra work without immediate return, and it is exactly the work that cannot be caught up on afterwards.

Do you work in reuse yourself

If you are running into a package that treats your items as articles, into numbers that add up per shop but not together, or into the question of what the product passport will mean for you, that is the kind of conversation I like to be in. Send a message.

The till and loyalty card side is under retail and point of sale, the api of the till system itself under the Tilroy integration, and a worked-out example in the case studies.