Team
The team behind Store Standards
We started in a Bristol stockroom, counting the same box of trainers three times.
How we got here
Store Standards started in 2021, in the stockroom of a bike shop in Bristol, with a spreadsheet that had been rebuilt four times and still could not say how many medium jackets were on the shelf.
The problem was never the counting. It was that counting happened in one place, and Shopify found out about it somewhere else, hours later, from someone who had not been there. Every store we have worked with since has some version of that gap.
So we build small apps that close it. We do not take client work, we do not run retainers, and we do not build anything we would not use on a Saturday morning with a delivery driver waiting. Everything we make goes on the Shopify App Store, and we live with the reviews.
There are nine of us. We answer our own support, we publish our uptime, and we still do a shift in a real stockroom every month, because it is the only reliable way to find out what we got wrong.
Team
Who we are
- PR
Priya Raghunathan
Founder, engineer
Ran stock control for a chain of six bike shops before writing a line of code. Started Store Standards after rebuilding the same receiving spreadsheet for the fourth time.
Still does one shift a month in a real stockroom.
- TB
Tom Beckwith
Engineer
Writes most of the code that talks to Shopify. Spent six years on warehouse software before that, which is why the sync queue is boring and never loses a scan.
Owns four barcode scanners and tests on the worst one.
- AS
Ana Sousa
Design lead
Designs every screen twice: once for a laptop and once for a cracked phone held in one hand. The second version usually wins and becomes the only version.
Keeps a folder of photos of bad supermarket signage.
- MI
Marcus Ilori
Support lead
Answers the support inbox and turns what comes in into the next month of work. Every recurring question ends up either fixed in the app or written up on this blog.
Has read more Shopify error logs than anyone should.
- FL
Freya Lindqvist
Engineer
Looks after the parts that have to work when the Wi-Fi does not. Built the offline queue that holds a scanning session together in a dead spot behind the racking.
Tests offline mode in a lift, on purpose.
- DO
Danny O'Rourke
Engineer, mobile
Makes the camera scanner read a scuffed barcode on a cold morning. Cares a lot about the gap between pressing a button and seeing something happen.
Collects damaged labels from suppliers as test data.
- NC
Nia Chambers
Product
Decides what we build next by watching people receive stock, not by reading feature requests. Says no to about nine ideas in ten, which is the job.
Visits two merchants a month, in person.
- SO
Sam Okafor
Infrastructure
Keeps the servers boring. Runs the load tests that decide whether a change ships on a Friday, and is usually the reason it does not.
Publishes our uptime numbers whether they are good or not.
- RA
Ruth Alderman
Words
Writes the help pages and edits everything on this blog down to plain English. Deletes about a third of every draft, including this one.
Reads every article aloud before it goes out.
How we build
Our standards
The rules we hold ourselves to, and the reason our apps feel different to use.
- 01
Fast on a bad phone
Every screen loads in under a second on a five-year-old Android. We test on one, on purpose.
- 02
Plain words
No jargon in the interface. If a screen needs a manual, we designed it wrong and we start again.
- 03
Least data possible
We store what the app needs to work and nothing else. You can export it or delete it whenever you like.
- 04
Feels like Shopify
We build on Shopify Polaris, so our apps look and behave like the admin your team already knows.
- 05
Works without signal
Scanning keeps working in the dead spot behind the shelves. Everything syncs when the phone finds Wi-Fi again.
- 06
A person, same day
Support goes to the team that built the thing. Most replies land within two hours during UK working days.
We hire slowly
We hire about one person a year. If you have worked in retail operations and you write code, get in touch.
Send us a note