Field guide

Pricing and demand

Run a one-variable price test with your own observations instead of treating a community table as a universal rule.

Set a clean baseline

Record the starting price, selected period, location, opening hours, and the traffic or sales measure you will compare.

Change one value

Keep the other conditions stable and record the same measure again. If hours, stock, staffing, or location also change, label the result as mixed evidence.

Use careful language

Sales can be higher in one test without proving that a price is best. Keep the save conditions and build context with the observation instead of turning it into a game-wide rule.

Ask the player to run a one-variable price test and keep the raw observations with the save and build context.

Open the optimizer