Buy, grow or fish? Start with the ingredient.

Compare the same usable quantity

A cheap batch is not necessarily the cheapest usable serving. Divide cash cost by usable yield, then consider the time you choose to value. Enter all three in the source optimizer; leave unavailable methods out rather than pretending every ingredient can be grown or caught.

• Buy: record vendor, quantity, cost and destination inventory.
• Grow: record seeds, machinery, conditions and harvested usable yield.
• Fish: record catch, usable quantity and your own trip time.

Stock location matters

The Q&A describes personal, kitchen, greenhouse and home inventories. An item you own may still need to reach the kitchen before it can support service. Capture where purchases and harvested goods arrive before assuming inventory is shared.

Connect stock to the menu

Build a reverse list of dishes using the ingredient. A shortage then points to the part of the menu at risk. We prepare this relationship in the database schema; exact recipe mappings open only when the live build confirms them.

• Avoid importing complete ingredient counts from other wikis.
• Attach vendor and build context to every price.
• Keep observations separate when an event or relationship changes the price.