How to Build a Shop and Vendor System

Shops and vendors—where players spend and earn currency on goods—are common across genres, and a good shop system handles the transactions cleanly while being data-driven enough that vendors and their stock are easy to author. It also intersects directly with your game's economy, so the prices and availability it defines carry real design weight.

Transactions, inventory, and currency, defined as data

A shop system handles the mechanics of buying and selling: a vendor has an inventory of goods with prices, the player has currency, and transactions exchange currency for goods (and often the reverse, selling goods for currency). Building this data-driven—vendors and their stock defined as data, with prices and quantities—means new vendors and changes to their inventories are authoring tasks rather than code changes, which matters because games often have many vendors with different stock that needs tuning. The system handles the transaction logic generically: checking the player can afford a purchase, transferring currency and goods, updating inventories. Representing vendors, stock, and prices as data keeps this flexible and tunable, letting designers populate the world with varied shops and adjust their economics without touching the transaction code.

The shop system is also where your economy lives, so prices and availability deserve real design attention. What vendors sell, what they pay, and what things cost are not just mechanical details—they're the levers of your game's economy, determining how players earn and spend, what's accessible when, and whether currency stays meaningful. A shop system that's mechanically correct but economically careless can break the game's balance, with prices that trivialize currency or availability that disrupts progression. This connects directly to economy design: the shop is a major source and sink of currency, so its prices and stock should be set with the overall economic balance in mind, controlling the flow of currency and the pacing of access. Treating the shop system as both a transaction mechanism (built cleanly and data-driven) and an economic lever (with prices and availability set deliberately for balance) is what makes it serve the game well, providing the buying and selling players expect while keeping the economy that the shop largely defines in healthy balance.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

A shop system handles transactions with data-driven vendors and stock—and defines your economy, so set prices and availability deliberately.