Economy

Introduction

Profit in TCG Card Shop Simulator is a markup problem before it is anything else. Customers do not buy at a fixed price; the chance of a sale falls as you push your price above the market value the TCG Price app reports, and community testing suggests a sale becomes effectively impossible somewhere past a 60 percent markup. That single curve shapes almost every decision in the game, from how you price a fresh case of booster boxes to whether it is worth holding a card until an event pushes its category up. This hub covers the markup-to-buy-chance relationship in practical bands, the fixed costs that drain your account every day whether you sell anything or not, the difference between sealed product margin and single-card margin, and how to time big sales around the price swings that events create so you sell into the spike instead of competing with it.

Markup vs Buy Chance (community data)

Profit Levers

Core Mechanics

The economy runs on one published relationship and a handful of fixed costs. The buy chance curve is the relationship: at market value a customer is very likely to buy, and the probability falls steadily as your price climbs above it, with community testing putting the practical floor somewhere past a 60 percent markup. That curve is why matching the market instead of beating it is usually the higher-revenue choice, because a lower margin on a completed sale beats a high margin on a customer who walks out. Against that revenue sit the bills: electricity charges per real minute, and every checkout counter carries a flat daily fee whether it is used or not. Expansion adds permanent cost, since extra floor space raises the standing electricity rate. On top of the baseline there is the manipulation layer. Hosting an event at a play table pushes one category of product up while pulling another down, so a shop that stocks ahead of an event can sell into the spike, and a shop that does not can watch its own inventory get cheaper.

Advantages

Understanding the buy-chance curve converts pricing from a feeling into a decision. Once you know that a sale is very likely at market value and increasingly unlikely as you push above it, the question changes from how much can I charge to how much total revenue does this shelf produce per day, and the answer is usually a moderate markup on completed sales rather than a steep markup on customers who leave. The fixed-cost layer gives you a concrete break-even target to aim at, since electricity and per-counter fees are known quantities that have to be covered before anything is profit. The event system adds a genuinely strategic layer on top: because each event lifts one category and depresses another, you can plan a stock position days ahead and sell into a predictable spike instead of reacting to one. Even the customer population is exploitable, since wealthier shoppers carry more money and tolerate higher prices, so a shop that keeps its review score high attracts the buyers who can actually afford its best stock.

Challenges

The economy's constraints are mostly about information and cash flow rather than about difficulty. Market values move, and a price you set an in-game day ago can already be stale, which means the TCG Price app is something you have to keep checking rather than consult once. Fixed costs are unrelenting: electricity accrues per real minute and every counter charges a flat daily fee, so a slow day is not neutral, it is a loss, and expansion makes the baseline worse by adding permanent per-minute cost. There is also a hard ceiling on what pricing alone can achieve, since pushing past a certain markup does not raise revenue at all, it simply converts sales into browsing. The event manipulation layer is powerful but has its own cost: events charge a daily fee, they require stock ahead of time, and they push a category down as well as up, so running the wrong event against the wrong inventory actively reduces the value of the product already on your shelves. Finally, most of the precise numbers in this hub come from community testing rather than the developer, so treat them as directional.

Frequently Asked Questions

Quick Tips