Use this article after your recipes are already clean and your Square sales data is flowing.

Review Square Mapping, run a dry-run sync from Inventory, then check the depletion result before you allow write mode.

Quick facts

Start here

Square depletion in this phase is recipe-based, not full packaging inventory.
Dry-run mode lets you test without writing inventory movements.
Unmapped Square items can create suggestion rows for review.
Nested recipe depletion can be enabled, but you should review the preview carefully before turning it on.

Before mapping starts

Make sure the recipe you want to deplete already exists and has the right yield and units.
Decide whether one sale should deplete the parent recipe only or also deplete subrecipes.
Use a short sync window at first so the test result is easier to review.

Start with a dry-run Square sync so you can inspect what would happen before inventory movements are written.

Use a narrow date range for the first test.
If the totals look strange, stop there and fix the mapping before you write anything.

Use the suggestion queue to speed up review, but approve only the mappings that truly match the sellable item.
Turn on nested depletion only when the child-recipe math is understood and the preview looks right.

Approve the right recipe match for each Square item key, then set the quantity per sale that should be depleted.

Common reasons depletion looks wrong

The Square item is unmapped or mapped to the wrong recipe.

The recipe yield or unit setup is wrong.

Nested depletion was enabled before the child-recipe math was reviewed.

Run another sync in write mode only after the dry-run result looks reasonable.
Check a few known sales and confirm the depletion rows match the quantity you expected.
If inventory looks too low or too high, review missing mappings, wrong quantity-per-sale values, stale recipe yields, or incorrect nested depletion settings.