Do not start a large e-liquid batch because every input slot is available. Start it when you can name the recipe, verify every ingredient, identify the shelf or order that needs the output, and afford the next replacement order. Otherwise the mixer converts flexible cash and ingredients into a box that may occupy storage while a different flavor blocks a customer or shipment.
This guide is bounded to the released game checked on August 22, 2026. Official material establishes that crafted e-liquids reduce costs and can be sold in-store; retail gameplay shows the recipe/input/output transaction, customer flavor questions, tracked ingredients, and later mixer progression. Exact recipes, ingredient quantities, sale prices, unlock levels, and machine speeds must come from the current mixer and product panels.
Separate the customer’s flavor problem from the machine recipe
Customers can ask for a recommendation by flavor family. In the verified release footage, an advice prompt explicitly offers +10 REP for a correct answer and -10 REP for a wrong one. That is a product-identification test. It does not ask which recipe is cheapest or which box has the best margin.
When the prompt asks for Minty, Tropical, Sour, or another named family:
- Read the requested family exactly.
- Compare the full labels of the offered products; brand color and package art are not flavor evidence.
- Choose only when one option’s name or current product information supports the requested family.
- If the current client exposes a product detail panel, use it instead of interpreting an ambiguous marketing name.
Do not turn the visible examples into a permanent answer key. The recordings show products such as Frozen Apple, Lemon Shock, Sunshine Paradise, Raspberry Reactor, and Grape Plasma, but a product name alone does not prove every flavor tag, and later patches can change the pool. The safe rule is label-to-request matching in the current prompt.
Read the mixer from left to right
The mixer interface shown in the release playthrough has four useful regions: a recipe list, a selected recipe, input slots, and output. Treat each craft as a transaction across those regions.
- Select: choose the exact recipe required by shelf demand, an accepted order, or a tracked quest.
- Read: inspect all required inputs before moving inventory.
- Load: add the correct ingredient and quantity to each input slot.
- Recheck: confirm the selected recipe did not change while you moved items.
- Mix: start one controlled batch.
- Collect: verify the expected box appears in output and the ingredients actually decrement.
If the action is disabled, the earliest mismatch is usually more informative than the button. Check recipe selection, missing input, exact ingredient identity, quantity, machine state, and output capacity in that order. Loading extra ingredients before identifying the missing slot creates a second inventory problem.
Track ingredients before ordering another colorful box
The inventory UI provides a Track action and a dedicated Tracked Items panel. Use tracking for the bottleneck input, not every item in the building. One recipe should have one visible shortage list.
Before placing an ingredient order, compare:
- units already in machine input;
- units in general inventory or storage;
- units reserved for a different recipe or customer order;
- units already included in an unprepared delivery contract.
Then order only the missing amount plus a reserve you can justify with proven demand. The official store description promises cost reduction through mixing but does not publish a permanent ingredient-cost formula. Savings exist only when the output sells or completes a contract; overproduction can still lock cash in slow inventory.
Run one control batch before scaling
A control batch answers questions that a recipe name cannot: whether the current machine accepts the inputs, how the output is packaged, where it lands, and whether the destination recognizes it.
- Record the selected recipe and the count of each input.
- Make the smallest batch the current UI allows.
- Collect the output immediately so a full output slot cannot block the next test.
- Move one box to its intended shelf or order reserve.
- Observe one result: a sale, an accepted packaging-machine line, a quest increment, or an identified lack of demand.
Only then increase production. If the first box sells but the second does not, do not assume the recipe broke. Customer mix, shelf access, price, and existing inventory may have changed. Keep the next test to one variable.
Give every output a destination before pressing Mix
Use three destinations with different ownership rules:
| Destination | Proof it is needed | Protection rule |
|---|---|---|
| Walk-in shelf | Recent sale or repeated customer demand | Start with a small facing; do not fill storage from one sale. |
| Pickup/online order | Exact product appears in a named required-items list | Reserve it away from the open retail shelf. |
| Quest or experiment | The tracked objective or test names the action | Stop when the counter or test result reads back. |
If the output has no destination, leave the ingredients flexible. A later customer can ask for a different flavor, and an online order can require a specific product variant. Empty machine time is cheaper than a large wrong batch when storage is tight.
Price crafted stock from a completed sale
Visible product panels show current and retail prices, while the official description connects customer satisfaction and reputation to better store results. Do not calculate an “optimal” e-liquid markup from a single recorded screen. Instead, price one small batch and observe the complete path:
- The box is unpacked and placed on compatible equipment.
- A customer can physically reach it.
- The item is selected rather than only inspected.
- Checkout completes.
- Balance, shelf count, reputation, and any tracked counter change as expected.
If the item remains while neighboring products move, check price feedback and flavor demand before crafting more. If it sells out, confirm replacement ingredients remain affordable. A product that sells once but empties the ingredient budget is not yet a dependable line.
Use recipe coverage to find gaps, not to force every flavor onto a shelf
The checked gameplay later shows Mixer II and a recipe display reading 16/24. That is evidence of progression and a larger recipe catalogue in that recorded save. It is not evidence that every new game starts with the same count, that 24 is permanent, or that unlocking a recipe creates demand.
When a new recipe appears, classify it:
- Demand gap: it answers a flavor request or order your current range cannot serve.
- Supply alternative: it uses ingredients that are easier to replenish in your current shop.
- Coverage only: it is useful for a quest, experiment, or recipe catalogue but has no proven buyer yet.
Test demand-gap recipes first. Keep coverage-only output to the minimum that proves the action. A full recipe list is knowledge; it is not a stocking plan.
Scale toward crafting milestones without flooding storage
Steam’s current achievements include Mixing It Up for the first crafted e-liquid, Master Mixer for 640, and Liquid Legend for 1,920. Those counts confirm long-run crafting goals, but they do not specify the most profitable recipe or require the output to occupy your retail floor at once.
For a long crafting session, use a closed loop:
- Select a recipe with a proven destination.
- Set a batch ceiling from free storage and shelf/order demand.
- Mix, collect, and move output before the machine blocks.
- Sell or fulfill enough output to recover space and replacement cost.
- Check the achievement or quest counter at a known interval.
Stop when the destination fills, ingredients reach the protected reserve, the counter stops, or replacement stock would consume operating cash. The achievement is cumulative; there is no evidence that one enormous unsold batch is required.
Assign co-op roles around machine state
In co-op, one person should own the selected recipe until its batch is collected. A second can obtain ingredients, a third can stock outputs, and a fourth can cover customers or delivery. The mixer owner announces four things: recipe, missing input, batch state, and destination.
Do not let two players quick-move items into the same machine without confirming the selected recipe. A well-intended ingredient delivery can overwrite the clean test or consume stock reserved for another box. When output is collected, announce whether it is retail, pickup, or shipping stock before another player shelves it.
Recover a stalled production chain from the machine outward
| Failure signal | First check | Do not do yet |
|---|---|---|
| Recipe cannot be selected | Current machine tier, recipe unlock, and live quest/level state | Buy ingredients for an unavailable output. |
| Mix remains disabled | Every required input, exact identity, quantity, and output space | Load unrelated stock into empty slots. |
| Ingredients decrement but no usable box appears | Output slot, nearby floor, inventory, and machine state | Start another batch. |
| Crafted box will not satisfy an order | Full product label and order-required variant | Assume same flavor means same SKU. |
| Crafted stock does not sell | Shelf compatibility, path, price feedback, and observed demand | Scale the same recipe. |
| Craft counter does not move | Current game version and whether output collection completed | Consume an entire reserve chasing the counter. |
The launch received an achievement hotfix on August 16. If the product exists and sells but only the achievement is missing, update and retest one controlled craft. If the output itself is missing, preserve the mixer input/output screen and treat it as a production-state problem.
Watch a verified later-game mixer segment
KnuckleHead’s public EP2 page identifies the full game, channel, and Steam link, and its duration matches the supplied local file within one second. The segment below shows Mixer II, a visible recipe list, input/output handling, tracked items, storage, and customer-facing work in the same retail session. It is evidence for the interface and handoffs, not an official recipe table.
Route the output without confusing the three queues
For cash reserve, shelf testing, price readback, and day-close checks, use the Vape Store Miami Beginner Guide. For a crafted SKU committed to a pickup or shipping contract, follow the required-items comparison in the Vape Store Miami Orders Guide. A mixer output may feed either article’s queue, but it should belong to only one destination at a time.
Evidence boundary and official links
Steam’s official Vape Store Miami listing defines ingredient ordering, recipe use, shop sales, reputation stakes, co-op scope, and the production-room image. Release and hotfix timing comes from the developer announcement archive. The game’s global achievements provide the three current crafting milestone descriptions.
No readable official source in this set publishes every current recipe, ingredient ratio, unlock level, mixing time, wholesale price, or permanent best seller. This guide therefore teaches the repeatable readbacks that reveal those values in the current client instead of inventing a recipe sheet from partial footage.