True recipe gain equals dish value minus the value of all inputs. Then test whether the gain per machine-hour and per crop tile beats your next-best use.
Dish sale price alone is a poor profit metric. A recipe competes with selling ingredients, using processors for another product, and reserving food for stamina, buffs, quests, and relationships.
Calculate the complete input chain
Include raw crops, fish, animal products, and intermediates such as flour, fillets, sugar, rice, juice, and sauces.
- Use the value of every consumed ingredient.
- Count multiple processing stages.
- Exclude ingredients already protected for trials or festivals.
Measure throughput, not one sale
A high-margin dish can lose to a simpler recipe when its stations remain blocked or its ingredients arrive irregularly.
- Compare gain per occupied machine-hour.
- Match crop harvest timing to processor capacity.
- Avoid building surplus that cannot be cooked before the next harvest.
Keep utility food outside the sale batch
Stamina, health, and profession buffs often return more value through extra work than through direct sale.
- Create a labeled recovery-food reserve.
- Carry specialized buffs only on matching routes.
- Do not sell the last food needed for a boss or King-fish session.
Run one stable line before diversifying
A small repeatable menu is easier to supply, store, and evaluate than many incomplete recipes.
- Choose one dependable crop-based recipe.
- Add one animal or fish recipe only when supply is stable.
- Recalculate after balance patches change prices or yields.
Assign a shadow price to homegrown ingredients
A crop or fish is not free merely because you gathered it yourself. Give every ingredient a shadow price equal to its best realistic alternative use: direct sale, another recipe, bait, feed, a request, or progress toward a trial. Use that value when comparing dishes. If an ingredient is scarce or seasonal, raise its internal cost further until the protected reserve is complete. This prevents complex recipes from appearing profitable only because farm labor and valuable inputs were counted as zero. The calculation does not need perfect market modeling; it needs consistency across candidates. Revisit shadow prices when a profession unlock changes processing options, because the same wheat, fish, milk, or vegetable may suddenly support a more valuable production chain than it did last week.
- For each core ingredient, record direct sale value, strongest current alternative recipe, and any protected progression use, then choose the highest realistic opportunity cost, then update the ingredient ledger.
- Treat seasonal scarcity as a constraint by pricing only true surplus for sale cooking, never the seed, quest, festival, or emergency-food reserve, then update the ingredient ledger.
- Recalculate after new machines or recipes unlock, since an unchanged raw item can gain a better use without any change to its displayed sale value.
Run a controlled test batch before scaling
Before converting a harvest into a new money recipe, produce one complete test batch from raw input to sold dish. Record the quantity of each ingredient consumed, every machine occupied, waiting time between stages, final output, and when coins actually become available. Include failed assumptions, such as a missing appliance, locked recipe, or intermediate shared with bait. Then compare the batch with selling the same inputs or processing them through the current dependable line. Scale only if the new workflow improves the goal that matters: margin, cash speed, use of surplus, or reduced labor. A test batch limits losses from misleading sale prices and reveals whether the kitchen can repeat the recipe consistently rather than completing it once from accumulated storage.
- Start with enough ingredients for one end-to-end batch and keep all unrelated stock outside the test boxes so consumption remains easy to count, then update the test batch.
- Measure player touchpoints as well as machine time; frequent transfers, travel, or appliance changes can make a nominally strong margin impractical at scale, then update the test batch.
- Repeat the batch only after confirming ingredient replacement, since a recipe supplied by old storage is not yet a sustainable weekly production line, then update the test batch.
Protect working capital from long ingredient chains
Multi-stage cooking can lock value in flour, juice, fillets, sauces, and unfinished dishes for days while seeds, blueprints, or transport still require coins. Set a working-capital ceiling: the maximum raw value allowed inside sale-cooking queues before the next cash need. When the ceiling is reached, finish and sell existing batches before starting another chain. Keep a separate coin reserve for progression purchases so a profitable kitchen does not delay an important unlock. Favor shorter recipes when cash is urgently needed, even if their theoretical margin is lower. Longer chains become safer after crop supply, appliances, and storage are stable. This cash-flow rule distinguishes being profitable on paper from having spendable coins at the moment a profession or seasonal opportunity demands them.
- List upcoming seed, blueprint, bag, and travel purchases, then ring-fence those coins before buying ingredients or dedicating scarce crops to a long sale chain, then revise the cash plan.
- Count all unfinished intermediates against the cooking ceiling because they cannot fund tomorrow's purchase until the final dish is completed and sold, then revise the cash plan.
- When cash falls below the reserve, pause new complex batches and clear the shortest finishable line first rather than adding more high-margin work in progress.
Use a stop rule for bottleneck ingredients
Every sale recipe needs a rule that ends production before it consumes the island's last flexible ingredient. Identify the ingredient hardest to replace, then set three levels: protected reserve, routine cooking allocation, and optional surplus. Stop the sale line when stock reaches the protected reserve, even if other inputs and machines remain idle. If several dishes share that bottleneck, allocate complete batches to the recipe with the best current objective, not automatically the highest displayed price. The stop rule should also trigger when processors, storage, or harvest timing can no longer replenish the ingredient before the next planned batch. This keeps profit cooking reversible and leaves room for buffs, bait, gifts, quests, and newly unlocked recipes that may value the same material more highly.
- Choose one bottleneck per recipe based on replacement difficulty, not quantity used, and set its protected floor before moving any stock into kitchen storage, then update the stop rule.
- Post the stop quantity beside the relevant appliance or input box so refilling remains rule-based when several harvested stacks arrive at once, then update the stop rule.
- Review the floor after seasonal transitions and profession unlocks, increasing it when a new critical use appears and releasing surplus when that obligation is complete.
Frequently asked questions
Is the highest sale-price dish the best money maker?
Not necessarily. Subtract ingredient value and consider machine time, supply reliability, and the utility value of the food.
How many recipes should I produce for sale?
Start with one stable product line, then add another only when its ingredients and machines do not compete with the first.