Inventory Guide

Square Inventory for Restaurants: What It Can Track

Square can support restaurant inventory at several levels: standard item inventory, ingredient and recipe tracking in eligible Square for Restaurants plans, and deeper restaurant inventory workflows through Square Restaurant Inventory by MarketMan. The right setup depends on whether you only need sellable-item counts or a full ingredient, purchasing, waste, food-cost and multi-location operating system.

What restaurant inventory actually needs to track

Restaurant inventory usually includes more than the items visible on the menu:

  • raw ingredients
  • prepared ingredients
  • packaged beverages
  • alcohol where applicable
  • retail products
  • disposables and packaging
  • cleaning and operational supplies

The complexity comes from converting purchases into recipes, recipes into menu items, and sales into ingredient consumption.

Standard Square inventory vs ingredient inventory

WorkflowBest for
Standard Square item inventoryDiscrete sellable products such as bottled drinks, packaged products and merchandise
Square RecipesConnecting supported menu items with ingredient usage and food-cost calculations
Square Restaurant Inventory by MarketManDeeper ingredient tracking, purchasing, menu costing and restaurant inventory analysis

How Square Recipes works

Square's current ingredient-cost tracking lets eligible Square for Restaurants users add ingredients, attach recipes to menu items, and track ingredient stock and food cost.

When a recipe-linked menu item is sold, supported ingredient quantities can decrease and Square can calculate COGS and profit margin using ingredient unit costs.

Current Square Recipes limitations

Square currently documents several important limitations for the recipe feature. These include:

  • no batch prep or recipes-of-recipes
  • modifiers do not currently decrement ingredient stock through recipes
  • recipes are not supported on items with multiple variations in the documented beta workflow
  • the feature is limited to supported prepared food and beverage item types

Because Square describes this as a beta capability, restaurants should verify the latest product behavior before redesigning their entire inventory process around it.

Why batch prep matters

Many restaurants do not consume every raw ingredient directly from the final recipe.

For example:

  1. flour, water and yeast become dough
  2. dough becomes pizza portions
  3. pizza portions become menu items

If the inventory system cannot model recipes of recipes or prepared sub-recipes, the restaurant may need a separate operational process for batch production.

How modifiers complicate restaurant inventory

Modifiers are common in restaurants: extra cheese, additional protein, alternative milk, sauces, toppings and substitutions.

If modifiers do not drive ingredient consumption in the chosen recipe workflow, actual ingredient usage can diverge from theoretical usage even when base recipes are correct.

Restaurants with heavy modifier usage should test real orders before assuming ingredient depletion will match physical consumption.

Square Restaurant Inventory by MarketMan

Square also documents Square Restaurant Inventory by MarketMan for eligible restaurant plans. Square describes it as a connected restaurant inventory solution with:

  • real-time ingredient tracking
  • purchase-order workflows
  • menu costing
  • analytics
  • inventory and product variance reporting

This is a third-party integration connected with Square POS rather than the same thing as standard Square item inventory.

Restaurant purchasing and receiving

Inventory accuracy starts when the delivery arrives.

A strong receiving workflow should:

  1. compare the delivery with the purchase order
  2. count or weigh what physically arrived
  3. record shortages, substitutions and damaged goods
  4. capture the correct unit cost
  5. use consistent units of measure
  6. put perishable stock away using the restaurant's rotation policy

See inventory receiving.

Units of measure are a major source of error

A restaurant may buy beef by the case, receive it by weight, portion it in grams, and sell it inside a menu item.

If purchasing, receiving, recipes and physical counts use inconsistent units, the inventory system can look wrong even when every employee followed the screen correctly.

Define conversions before automating ingredient depletion.

Theoretical vs actual ingredient usage

Recipe-based inventory calculates what ingredients should have been used based on sales. Physical counts show what was actually used.

The difference can reveal:

  • overportioning
  • waste
  • spoilage
  • theft
  • recipe errors
  • unrecorded staff meals
  • modifier usage
  • receiving errors

This variance is often more useful than simply knowing the current stock number.

Waste and spoilage

Restaurants lose inventory for reasons other than sales. Waste must be recorded separately if the business wants trustworthy food-cost and replenishment data.

Useful waste categories can include:

  • spoilage
  • production waste
  • overproduction
  • customer returns
  • staff meals
  • samples and promotions
  • damage

Square has expanded inventory-adjustment reason support, including additional built-in and custom reasons in current inventory history workflows.

Physical counts still matter

Recipe depletion is theoretical. Physical counts verify reality.

Count high-value, high-variance and perishable ingredients more often than stable low-risk supplies.

Use the difference between theoretical and physical inventory as an investigation signal rather than immediately overwriting the system.

See cycle counting and inventory variance.

Multi-location restaurant inventory

Multiple restaurants add several planning questions:

  • which location is running low
  • which location has excess inventory
  • whether inventory should be transferred
  • which supplier serves each location
  • how food cost differs by location
  • whether one restaurant has abnormal waste

Companywide totals can hide these operational problems, so review stock, waste, purchasing and variance by location.

Where Square can be enough

Square may be enough when:

  • the restaurant primarily needs POS-linked item tracking
  • recipe complexity is relatively simple
  • the current Square recipe capabilities match the menu structure
  • purchasing and supplier workflows are straightforward
  • one or a small number of locations are manageable

Where restaurants may need a deeper inventory layer

Consider a more specialized inventory workflow when:

  • batch prep is central to operations
  • recipes and sub-recipes are complex
  • modifier usage materially affects food cost
  • multiple vendors and price changes require active management
  • waste and variance need tighter analysis
  • several locations share purchasing and stock
  • forecasting demand and purchase quantities is a priority

Square restaurant inventory vs Stash

Square is the POS and transaction system. Stash is positioned around broader inventory planning for growing physical businesses.

Stash for Square inventory management connects supported Square data with stock, purchasing, suppliers, forecasting, transfers and multi-location workflows.

For restaurants, the best fit depends on whether the main problem is recipe-level food costing, general stock control, or purchasing and replenishment across the wider business.

Frequently asked questions

Can Square track restaurant ingredients?

Yes. Square currently documents ingredient tracking through Square Recipes for eligible restaurant plans and through Square Restaurant Inventory by MarketMan for deeper restaurant inventory workflows.

Does Square deduct ingredients when a menu item sells?

In supported Square Recipes workflows, selling a recipe-linked menu item can decrement tracked ingredients and calculate COGS from ingredient unit costs.

Can Square track modifiers as recipe ingredients?

Square's current recipe documentation says modifiers do not track ingredient inventory or costs in that beta workflow.

Can Square handle batch recipes?

Square currently documents a limitation around batch prep and recipes of recipes in Square Recipes. Restaurants with complex prep should verify whether another workflow is needed.

What is Square Restaurant Inventory?

It is a restaurant inventory solution powered by MarketMan and connected with Square POS, offering ingredient tracking, purchasing, menu costing and analytics for eligible users.

When should a restaurant use Stash with Square?

When purchasing, forecasting, supplier management, transfers and multi-location replenishment are becoming the main inventory challenges around the Square sales data.

Next steps

Map your inventory workflow before choosing the tool: identify sellable products, raw ingredients, prep items, modifiers, waste, suppliers and locations. Then test whether Square's current recipe and inventory capabilities match that operating model before adding another inventory layer.

Turn better inventory decisions into a better operating system

Stash connects inventory tracking, forecasting, purchasing, suppliers, and multi-location visibility so growing physical businesses can act on the numbers with less manual work.

Start free trial