Skip to main content

Why my Blueprint isn't deducting stock

Sales coming through but stock not moving? Work through this checklist — most issues are linking, unit setup, or sync-related.

Written by Jake
Updated today

Why my Blueprint isn't deducting stock

If your POS is showing sales but your Stash inventory isn't moving, one of a handful of things is usually wrong. Work through this checklist in order — most cases are resolved within the first three checks.

Quick checklist (90% of cases)

  1. Is the Blueprint linked to the POS product?

  2. Is the POS connection active and synced?

  3. Are the Blueprint's components valid (no warnings on the deduction preview)?

  4. Is the Blueprint at the same shop as the POS product?

  5. Has a sale actually happened since you linked it?

Walking through each one

1. Is the Blueprint linked to the POS product?

This is the most common cause. A Blueprint that exists but isn't linked to a POS product does nothing on sale.

Check: Open Products. Find the POS product that's being sold. Look at the Blueprint column — does it show the linked Blueprint's name, or a dash?

Fix: Click the product, set the Blueprint, save. See Linking a Blueprint to a POS product.

2. Is the POS connection active and synced?

If the connection is broken, sales aren't reaching Stash at all.

Check: Open Integrations. Each shop should show its POS connection in green/healthy state, with a recent Last synced timestamp.

Fix: If the connection looks broken, click Resync. If that fails, disconnect and reconnect the POS. See Connecting your POS to Stash.

3. Are the Blueprint's components valid?

Even with a perfect link, deduction will fail silently if the math can't work — for example, if a component uses Gram but the inventory item is stored in Bag with no Each Bag contains filled in.

Check: Open the Blueprint. Look at each component row's deduction preview. Any warning ("Cannot convert," "Set content info," "Insufficient stock") means that component won't deduct.

Fix:

4. Is the Blueprint at the same shop as the POS product?

Blueprints are scoped to a single shop. If the POS sale happens at Le Koffee Marais but the Blueprint exists at Le Koffee Bastille, they won't connect.

Check: Open both the Blueprint and the POS product. Compare the shop names.

Fix: Either create a Blueprint at the correct shop, or move the POS product mapping. The cleanest fix is usually to have one Blueprint per shop.

5. Has a sale actually happened since you linked it?

Stash doesn't backfill historical sales. If you linked the Blueprint after the sales happened, those past sales won't retroactively deduct.

Check: Make a real test sale through your POS. Wait 1–2 minutes for the webhook to land. Re-check the inventory item's stock.

Less common causes

POS location not mapped to a Stash shop

If you have multiple POS locations and one isn't mapped to a Stash shop, sales from that POS location have nowhere to land.

Check: Open Integrations and look at the location mapping section for your POS connection. All POS locations should map to a Stash shop. See Mapping POS locations to Stash shops.

The POS sale was for a product that exists in your POS catalog but never synced to Stash

If you added a product to your POS recently and haven't run a sync, Stash doesn't know about it. The sale comes in but Stash can't find a matching product.

Check: Open Integrations. Click Sync now on the POS connection.

The Blueprint's "Makes" value is too high

If your Blueprint Makes 100 but you meant Makes 1, deductions are 100x smaller than they should be — so small you might not notice.

Check: Open the Blueprint. Look at the Makes value. For most products it should be 1.

The cron job that calculates consumption hasn't run yet

Some Stash metrics update on a recurring schedule. If you just made a test sale, give it a minute or two before assuming nothing happened.

If none of the above fixes it

Get in touch via the chat icon. Send the POS product name, the Blueprint name, the shop, and the timestamp of a test sale. We'll trace it end-to-end and tell you exactly where it broke.

Related articles

Did this answer your question?