Editing or deleting a Blueprint

You can update any field on a Blueprint or Modifier Blueprint at any time, or delete one entirely. Changes apply to all future POS sales. Past sales are never retroactively recalculated — once a deduction is written, it stays.

This article applies to both Blueprints (base products) and Modifier Blueprints (oat milk, extra shot, gift wrap, etc.). The mechanics are the same — only the fields differ slightly.

Who can do this

Only Admins can edit or delete Blueprints. Members can view them.

Editing

From the sidebar, open Blueprints.
Pick the right tab — Blueprints or Modifier Blueprints.
Click the row you want to edit.
Click Edit.
Change any field — name, description, location, POS product link, Makes, components ("What this uses"). For Modifier Blueprints, you can also edit the swap ("What this swaps out").
Watch the deduction preview on each component row to confirm the math still works after your changes.
Click Save.

Changes take effect immediately for future sales. The next POS sale that triggers this will use the updated recipe.

Pausing temporarily

If you need to stop a Blueprint or Modifier Blueprint from deducting for a while — testing a new recipe, a seasonal item out of rotation, a component temporarily unavailable — the cleanest approach is to unlink the POS product:

Open it.
Click Edit.
Clear the POS Product field (or set it to none).
Save.

With no POS product linked, sales of that product will be skipped (logged as "no blueprint") and no inventory will move. When you're ready to resume, edit it and set the POS Product back. Future sales from that point on will deduct as normal.

What you can change without breaking things

✅ Name and description — cosmetic, no impact on deductions
✅ Components — add, remove, or change quantities at any time
✅ Makes — changing the yield rescales all future deductions per the formula component_quantity × (sold_qty ÷ Makes)
✅ POS product link — re-link to a different POS product. See Linking a Blueprint to a POS product.
✅ Swap (Modifier Blueprints only) — set, unset, or change the item that gets added back when this Modifier Blueprint fires

What changes are riskier

Changing the location (shop)

Each Blueprint or Modifier Blueprint is tied to one shop, because its components live at that shop. If you change the location, the existing components may not exist at the new location — Stash will warn you and may unselect them. The POS Product link will also need to be re-set, because it's scoped to the shop.

The cleaner approach: create a new one at the new shop with components from that shop. Don't move an existing one across shops.

Removing a component that's already deducting on sales

Future sales will stop deducting that component. Past deductions are preserved in transaction history. This is fine if you've genuinely changed the recipe — just be aware.

Past sales are never recalculated

This is a hard rule. If you change a recipe today, every sale before today keeps its original deduction. Stash never goes back and "fixes" historical data — that would corrupt your audit trail and confuse end-of-month reports.

If you've been operating with the wrong recipe and your stock numbers are off, the fix is a manual stock adjustment with a note explaining the correction — not editing the Blueprint and hoping the past changes too. See Adjusting stock quantity manually.

Converting between Blueprint and Modifier Blueprint

If you created the wrong type — built a Blueprint when you meant a Modifier Blueprint, or vice versa — you can convert between them without losing your work.

Open the Blueprint or Modifier Blueprint.
Click the menu (⋯).
Choose Convert to Modifier Blueprint (or Convert to Blueprint).
Confirm.

Components, name, location, and POS product link are preserved. Going from Modifier Blueprint to Blueprint will clear the swap configuration ("What this swaps out") after a confirmation prompt — Blueprints don't have a swap field. Going the other way leaves the swap empty until you set one.

Deleting

Open the Blueprint or Modifier Blueprint.
Click the menu (⋯) and choose Delete.
Confirm.

Deletion is permanent. The Blueprint disappears from the list. Any POS product that was linked to it becomes unlinked — sales of that POS product stop deducting components.

What happens to past sales when you delete a Blueprint?

Nothing. All past inventory transactions are preserved with their original references. Your audit trail and historical timeline stay intact. Only future sales of the linked POS product stop deducting.

This is the same principle as editing: Stash never rewrites history. Delete is a forward-looking action.

What if I just want to pause, not delete?

Unlink the POS Product field instead of deleting (see Pausing temporarily above). The Blueprint stays in the list with all its components and recipe intact, ready to be re-linked when needed. Deletion is for Blueprints you're sure you'll never use again.