The pieces. What each one does.

Your current site is generic, slow to update, and doesn’t look like your store. Updating it takes a webmaster, or just doesn’t happen, and a part-time staffer can’t safely touch it without breaking something. Or you have a site you’re happy with, and every tool you look at wants you to throw it away.

Two ways in, and you can switch between them. Let us be the website: the kinds of pages a game store actually publishes, a Magic page with formats under it, beginner guides, store policies, a homepage that doesn’t look like a template, all edited in plain language, with drafts that go live only when you say so. Or keep the website you have and switch to a portal: we serve just the customer pages for the pieces you use, events, pre-orders, store credit, the cards you’re hunting, in your branding, at an address like play.yourshop.com. You paste a few links into your own menu and footer. Nothing to design, and we never need access to your site.

• Starter pages and content already written for the games you sell
• Pre-built page layouts: landing, store policies, beginner guide
• Edit in plain language, with no theme files, no shortcodes, no webmaster
• Your logo, your colors, and your own domain, not a template with your name on it
• Drafts stay private until you publish; preview the whole site first
• Already have a website? Run a portal beside it instead: your site links to our customer pages, and nothing of yours is touched
• Switch between a full website and a portal any time; nothing is deleted either way
• More than one shop? Each location gets its own page with hours, address and a map, and the footer lists them all

Open play on a whiteboard. Tournaments on a manufacturer site. Paint nights on Facebook. Leagues in a spreadsheet. Your customers don’t know where to look.

One calendar. Customers sign up online, and pay by card through your own storefront if you charge for a seat, or out of the store credit they already have with you. You see who’s coming, take the money online or at the counter, and check them in at the door. Recurring events recur. One-offs stay one-offs.

• One-time and recurring events: leagues, FNM, paint nights
• Customer signup with capacity limits when you want them
• Paid seats: card through your storefront, at the counter, or from their store credit
• Sign someone up yourself, including a walk-in after the event has started
• Refund a registration straight from the roster, with no digging through the POS
• Check people in at the door, from the admin or the phone, and undo it if you mis-tap
• Each event is held at one of your locations, and customers can filter the calendar by location

You write the same FNM announcement three times: once on your site, once in Discord, once for the email list. Half of them go out late or not at all.

Write the post once. Pick where it goes. One click sends it everywhere. New event in the calendar? Same again, broadcast to all your channels. The mailing list lives here too, so you’re not exporting a spreadsheet into a third tool every time you want to send something.

• Cross-post to website, Discord, and email at once
• Schedule for later, or send right now
• Your mailing list lives here: build lists, and customers manage their own opt-out
• Email leaves from your own mail server, so it arrives from your domain
• New events broadcast automatically, with no double-typing

Tournament prizes get tracked as gift cards, sticky notes, or a spreadsheet on one staffer’s laptop. Trade-in credit goes missing. Refunds get awkward.

A real ledger. Issue credit for prizes, trade-ins, and refunds in one place. When a customer wants to spend it, it comes back through your register the way that register already works: as a coupon, a gift card, or a discount, depending on which POS you run. The numbers add up at the end of the month.

• Tournament prizes, trade-ins, refunds, all in one ledger
• On Wix, a single-use code the customer applies at checkout; on Square, a discount the clerk applies at the register
• No storefront connected, or a POS we don’t talk to yet? Issue credit and redeem it by hand, with a receipt number if you want one
• Split a single purchase across cash + credit + gift card automatically
• Customers check their own balance from your site or from Discord
• Every change tracked, so disputes have an answer
• One balance per customer, good at every location; each transaction records which shop it happened at

A spreadsheet, a stack of POS receipts, and a calendar reminder to pay people out. Disputes are a headache. Reconciliation is worse.

A real list of consignors and what they brought in. Sales from your storefront land against the right consignor on their own. The commission math happens when you prepare the payout, not the moment a sale lands, so a refund three weeks later doesn’t leave you chasing money you already handed over. Payouts go out as cash or as store credit, with optional caps so a consignor’s credit balance never gets out of hand.

• Consignors, intake records, and per-item mappings
• Sales from your connected storefront land on the right consignor, with no double-entry
• Needs a connected Wix or Square storefront: what a consignor is owed is worked out from the sales it reports
• Nothing is owed until you prepare a payout, so late refunds sort themselves out
• Payouts as cash or store credit, with a per-consignor cap
• Full ledger view for reporting and dispute resolution

Three regulars have each asked you to keep an eye out for the same card. One told a staffer who no longer works Saturdays. When a copy finally comes in on a trade, nobody remembers who wanted it or what they’d pay.

Signed-in customers search the card catalog, pick the exact printing, say which conditions they’ll take and what they’ll pay, and send you the request. Staff can file one at the counter too, for the regular who would rather just tell you. You approve what’s worth chasing. Approved cards become one wanted list your whole staff can see, your public site can show off, and Discord hears about.

• Customers pick the exact printing and the conditions they’ll accept
• Or file the request for them at the counter, from the admin or the phone
• One shared want list across your staff, your public site, and your Discord
• Claim a copy for a customer when one comes in; mark it sold at pickup
• Customers are emailed on every status change, plus a reminder to come collect
• Per-printing price lookups, a request cap, and a ban list when someone abuses it

A release is coming and the reservations live on a sheet taped to the counter. Deposits are in a notebook. The distributor cuts your allocation the week of release and you spend an evening working out who gets what, then apologizing to the people who don’t.

Set the release up with its items, prices and limits, and open pre-orders. Staff reserve for customers at the counter, or customers reserve themselves on your site and follow it under My pre-orders. Take deposits at the counter or hold them from store credit. If the shipment comes in short, enter what you got and it proposes a split, first come first served or spread it out, that you can adjust by hand before anyone hears a word. Everyone not filled waits in order for a freed unit. Mark it arrived, work the pickup list, settle every deposit, and see how the release went.

• Releases with items, prices, per-customer limits and your own pre-order policy
• Reservations at the counter, or by the customer on your website or portal
• Deposits taken at the counter or held from store credit, every one settled with a recorded outcome
• Short shipment? A proposed split you can adjust by hand, and an ordered waitlist for freed units
• Pickup list with collect-by dates, overdue tracking, and a reminder email before the deadline
• Customers are emailed on every change; nothing is ever released or cancelled by a timer
• Your POS still rings up the sale; this keeps the list around it, no storefront needed
• Customers choose which location to pick up at, and the pickup list filters by it

The same regular is a website login, a Discord name, a line in the store-credit spreadsheet, and a stack of POS receipts. Four records, four half-answers, and no way to see what someone is actually worth to your store.

Every module writes to the same customer record. Open one person and see their events, their purchases, their credit, their bounties, and their history on one page. Records only get linked on proof: a verified email, or a link the customer completed themselves. Anything weaker waits for a staff member to say yes.

• One customer page: registrations, purchases, store credit, bounties, activity
• Bring the customers you already have across from Wix or Square in one import, previewed before anything is written
• Customers link their own Discord with a one-time code sent to their email
• Merge duplicates by hand; nothing is ever auto-merged on a guess
• Suggested matches queue up for staff review instead of linking silently

Month end means an export from the POS, an export from the spreadsheet, and squinting at both to work out what actually happened, with no way to tell whether you’re looking at all of it.

A sales summary pulled from every storefront you have connected, over whatever range you pick. When one number needs explaining, open the order behind it and read it end to end. And a sync page that says plainly whether anything failed to come through, rather than leaving you to notice a gap in December.

• Sales summary across every connected storefront
• Split by location, with each storefront’s locations matched to yours
• Open a single order end to end when a number needs explaining
• Sync status per storefront: where it’s up to, last error, rows brought in

Most software either bolts AI onto everything at once or leaves it out entirely. You end up either fighting a feature you never asked for, or wondering what you’re missing out on with no way to try a piece of it.

Every AI-assisted feature is a switch, and every switch starts off. Want help getting GameStoreOS product knowledge without reading a manual? Turn that on. Want help drafting your website, an announcement, or setting up an event? Turn that on. Want a natural-language assistant that answers questions and can act on your say-so, on a desktop or out loud on the phone? Turn that on too. Leave everything off and the product behaves exactly like it would without any of it. All of it draws on one thing: your store profile, the narrative that says what your store is and how it talks, so anything written for you sounds like your store and not a template. A guided interview builds that profile for you if you’d rather answer questions than write prose.

• Product knowledge: ask how something works and get pointed straight to it
• Drafting help for your website, announcements, and event setup
• A natural-language assistant, on desktop or the phone: ask a question about your own store, or have it act, like signing someone up for tonight’s event, each one shown on a confirm card before anything happens
• Every feature is its own switch, off by default; turn on only what you want
• One store profile grounds everything AI writes, with a guided interview if you want help building it

The admin is a desktop site, and the desk is not where the work happens. Checking people in means walking to the back office between rounds, or a printed roster and a pen, and a re-typing job at closing.

A phone app built for standing up, not sitting down. Pick tonight’s event, work the roster, check people in at the door, file a card request for the regular who would rather just tell you, and reserve the next set for them before they walk out. Staff see only the tabs their role can actually use, so whoever is covering Saturday isn’t looking at four things they can’t touch.

• Events: pick the night, work the roster, check people in, and undo a check-in
• Add a walk-in after the event has already started
• Bounties: the wanted list in your pocket, and file a request for a customer at the counter
• Pre-orders: look up what a customer has reserved, reserve something for them, and pull up a release’s pickup list
• Ask a question out loud and get an answer back
• Pick the location you’re working at once; the counter screens start there
• The tab bar shows only what that person’s role can use

Generic tools ship with hundreds of integrations that are nobody’s priority. Yours half-works.

A small set of connections to the tools you actually use, built and maintained for game stores specifically, not as one of a thousand options. Run more than one storefront and you can connect them all, with one marked as the main one. We pick the next integration based on what stores actually ask for, not what looks good on a logo grid.

• Wix: order sync, store-credit redemption as coupons and gift cards
• Square: order sync, store-credit redemption at the register
• Discord: event and announcement posts out, and a bot your customers can ask about their credit
• Connect several storefronts at once; you pick which one is primary
• Shopify and Crystal Commerce on the roadmap