Fell & Sell Shop Pricing Guide
Read demand arrows and customer mood colors, then use a controlled pricing test to raise profit without losing reliable feedback.
Direct answer
Check the demand arrow first, set one price, and let customer mood colors plus completed sales grade the result. Change the tag in small steps and keep the latest successful sale as your next baseline.
Quick answer
- Green, yellow, and red demand arrows mean high, average, and low demand.
- Red customer faces mean too expensive, yellow means acceptable, and green means too cheap.
- Change one price at a time so the next customer cycle stays useful.
- Retest after prestige or decoration bonuses change the shop context.
Read the Pricing Signals at a Glance
Fell & Sell gives you two separate color systems. The demand arrow describes the market for that good. The face over a customer describes that shopper's reaction to the price currently on the tag. Read the arrow before setting a test price, then use faces and completed sales to judge the result.
| Signal | Meaning | Pricing response |
|---|---|---|
| Green demand arrow | High demand | Test above the average range, then watch customer reactions |
| Yellow demand arrow | Average demand | Start around the average range and let the next sales cycle confirm it |
| Red demand arrow | Low demand | Begin lower and require a completed sale before raising the tag |
| Red customer face | Price is too high | Lower the price by one small step |
| Yellow customer face | Price is acceptable | Hold the tag as a working baseline |
| Green customer face | Price is too low | Raise the price by one small step on the next test |
If you have not yet built a repeatable supply and sales cycle, complete the beginner route from dungeon loot to the first sale before optimizing every item.
Turn the Signals into a Price Decision
Treat the demand arrow as your starting condition and the customer face as your result. A green arrow gives you room to test upward, but it does not guarantee that any high price will sell. A red face still tells you to lower the current tag. With a red demand arrow, begin conservatively and make the item prove that customers will buy it.
Use this decision order each time:
- Read the item's current demand arrow.
- Check the most recent successful price in purchase history.
- Set one test price that fits both signals.
- Open sales and watch more than one customer reaction when possible.
- Confirm whether a purchase actually completes.
Customer mood alone can mislead when it comes from one shopper. Repeated reactions plus a completed purchase give you a stronger baseline for the next cycle.
Run a Controlled Pricing Test
Treat each customer cycle as a controlled price test. Keep the item and shop context steady, change one tag, and let the next reactions show whether the adjustment helped.
- Check the item's green, yellow, or red demand arrow before editing its tag.
- Choose one displayed item and move its price by one small step.
- Reopen sales without changing that same item's price again.
- Watch the customer face colors and wait for an actual purchase result.
- Review purchase history and keep the latest successful price as the next baseline.
Customer price reactions in an early Fell & Sell shop
This current launch-build playthrough shows the red, yellow, and green customer faces, then demonstrates a one-step price adjustment during the first shop cycle.
Know When the Test Worked
A test succeeds when it produces a clear next action, even if the first price was wrong.
| Observed result | What it tells you | Next move |
|---|---|---|
| Red faces and no completed sale | The current tag is too high for this test | Lower one step and reopen sales |
| Yellow faces and a completed sale | The tag is a useful working price | Keep it as the next baseline |
| Green faces and a completed sale | The item sold with room to test higher | Raise one step during the next cycle |
| Mixed faces with at least one sale | The current price is plausible, but the signal is noisy | Hold the price and observe another cycle |
| Demand color changes between cycles | The market condition has changed | Read the new arrow before comparing results |
Do not grade the test from smiles alone. Check that the item sold, then use purchase history to anchor the next adjustment.
Retest After the Shop Context Changes
Supply, demand, shop prestige, and decoration bonuses all matter to pricing decisions. Current material does not verify a single multiplier that converts prestige or a bonus into an exact safe price. After either factor changes, rerun the same small-step test and let current demand plus customer response establish the new baseline.
Use the decoration bonus decision process to choose a shop effect for a real bottleneck, then return to this pricing loop to verify what customers accept.
Fix a Pricing Test That Gives No Clear Answer
| Symptom | Likely cause | Smallest useful recovery |
|---|---|---|
| Reactions are mixed | One shopper is being treated as the whole market | Hold the tag and collect another reaction plus a completed sale |
| The item stops selling after a change | The step moved above the accepted range | Return to the last successful price, then test a smaller increase |
| A prior price no longer behaves the same | Demand or shop context changed | Read the current arrow and start a fresh cycle from the last sale |
| Many tags changed at once | The result no longer identifies which change mattered | Pick one item, restore its last successful price, and test it alone |
| A green face appears but profit still feels weak | The item may be priced too low | Raise one small step and confirm another completed sale |
The safest reset point is the most recent price that produced a completed purchase. It preserves an observed result and keeps the next change reversible.
What the Signals Do Not Prove
The color meanings, controlled adjustments, purchase history, and shop factors are supported by current launch-build material. A universal item-by-item formula is not. Demand can change, and prestige or decoration bonuses can alter the selling context, so a copied price table can become stale even when it worked in another cycle.
Use the signals to discover a live price in your save. Keep exact numbers tied to recent completed sales, and retest whenever the demand arrow or shop context changes.
Frequently Asked Questions
Was this helpful?
Continue reading
These related Fell & Sell pages answer the next questions around this topic.