What Is a Game Store Operating System? (and Do You Need One)
The Oskii team6 min read
On this page
It's 6:40 on a Friday night. A teenager wants the last foil copy of a card she saw on your counter screen. Your phone has two messages about the same copy. The sheet says three. The binder says one.
Your shop isn't the problem. Four tools each keep their own idea of what's in stock, and they never agree on a Friday night. The fix has a name, even if few stores use it: a game store operating system.
What is a game store operating system?
A game store operating system is the single system of record a store runs on. It holds the stock count, and it builds the storefront, customer requests, staff picking and data imports on top of that one count, so every job in the shop reads the same number instead of its own copy.
The name comes from the phone in your pocket. Apps on a phone share one set of contacts and one camera roll. Nobody retypes their contacts into each app. A store works the same way when its tools share one count of what's on the shelf.
That's the practical test. If you can remove the shared count and every other tool keeps working on its own copy, you don't have an operating system. You have a bundle, and a bundle drifts apart on a busy Friday.
Why do spreadsheets, a register and three apps stop working?
They stop working when a second and third person start touching stock. Each tool holds its own copy of the count, and every copy needs a person to keep it honest. With one owner, the owner is that person. With two to four staff, nobody is.
A one-person shop runs on memory, and that's fine. Hire someone and that knowledge walks out the door at closing. The spreadsheet is accurate the day you build it. The register knows what sold but not which binder a card lives in. The Company page tells this story from the owner's side.
What jobs should a game store operating system do?
Five. It should hold the stock, show it to customers, take their requests, guide staff to the cards and move data in and out. Each job reads the same count. A system that does four of the five on a separate copy is a fifth spreadsheet.
| Job | The question it answers | What breaks without one count |
|---|---|---|
| Stock | What do we have, and in which finish? | The sheet and shelf disagree by Tuesday |
| Storefront | What can a customer see and ask for right now? | You list cards you sold an hour ago |
| Requests | Who has asked for which exact copy? | Two people are promised the last one |
| Picking | Where is each card, and was it found? | Five trips to the binders for one order |
| Data in and out | How does stock get in? | Retyping, and lasting typos |
Why does one source of truth for stock matter?
Because a count that two tools update will eventually disagree, and a disagreement at the counter costs a sale or a customer. One source of truth means one place changes the number, and everything else reads it. For the count itself, see our guide to TCG inventory management. For the shelves and boxes it describes, see trading card storage for game stores.
The cleanest way to hold the count is three numbers. On hand is every copy physically in the shop. Held is every copy promised to a customer who hasn't picked up yet. Available is on hand minus held. Work that last number out every time someone looks and never store it, and nobody sells the same card twice.
Take a card with three on hand and two held. Available is one. The kiosk shows one, and nobody has to check the back. Oskii's counter kiosk searches live stock this way, and customers can browse from their phone by scanning its QR code.
The hold is the heart of pickup. A customer sends a request, the system holds the exact copies, and staff get a pick list with the bin on every line. Nothing is charged until the customer pays at your counter. The full step-by-step is in pickup requests for card shops.
What is it not, and how do you choose one?
It isn't automatically a point of sale. The category describes where the count lives and who reads it. Oskii is not a point of sale and doesn't take payments. It hands the total and the SKU list back to the register you already own. Some all-in-one systems also run events and take payments. Those are fair things to want, and Oskii isn't that kind of all-in-one.
Also check the catalogue first. Oskii covers Magic: The Gathering only today, with card data and daily market estimates from Scryfall. A system that can't hold a game you stock sends that game back to a spreadsheet.
To choose, ask to see the answers, not hear them, and use your own export in the demo. Our fair checklist for choosing game store software has all ten questions and a comparison of tool types.
Questions people ask
- What is a game store operating system?
- A game store operating system is the single system of record a store runs on. It holds the stock count, and the storefront, customer requests, staff picking and data imports all read that one count instead of keeping their own copies.
- How is it different from a POS?
- A point of sale takes payments and prints receipts. An operating system owns the stock count and the work built on it, such as customer search and picking. Some products do both. Oskii doesn't take payments or replace a register. It hands back the total and the SKUs to key into yours.
- How hard is it to switch software?
- It depends on where your data lives now. In Oskii you export a binder from ManaBox, upload the CSV and review a dry run before anything changes, and held cards are always kept. Oskii also imports the CSV CrystalCommerce generates. Support can help if an import looks off.
Where Oskii fits
At Oskii, we're obsessed with organization, and we love our local game store. So we built one honest count for local game stores that sell Magic singles. It gives you a kiosk customers search, holds on the exact copy, a pick list on your staff's phones and ManaBox imports that never drop a hold.
It's onboarding stores by invitation from the waitlist. You can read how a shop day runs on the retail page, or start from the home page and join the waitlist there.