A reliable Square item library uses one clear item record, separate variations for quantities that must be tracked independently, unique SKUs, consistent categories, and explicit location and channel assignments. Catalog structure determines whether inventory and reporting can be trusted.
An item is the product or service customers recognize. A variation is a separately sold version of that item. Use variations for sizes, colors, package quantities, or other versions that need their own price, SKU, or inventory quantity.
Example: “House Coffee Beans” is the item. “250 g,” “500 g,” and “1 kg” are variations. If each package has a different barcode and quantity, each needs its own variation and SKU.
A SKU is an internal identifier, not a product description. Keep it unique, stable, and easy to scan or search. A practical structure may combine a short category, product, and variation code, such as COF-HSE-500G. Do not encode details likely to change, such as price.
Categories should support merchandising, reporting, counting, or menu organization. Avoid both extremes: one generic “Products” category and dozens of one-item categories. A coffee shop might use Coffee beans, Milk and alternatives, Syrups, Packaged food, Merchandise, and Supplies, while keeping sellable menu organization distinct where needed.
Square allows items to be assigned to specific locations and sales channels. An item available at two stores can still have a separate quantity at each. Online visibility, fulfillment, and location availability should be tested rather than inferred from the item name.
Square's current create and edit items guide explains the live Dashboard controls.
The buying, counting, and selling unit may differ. A restaurant may buy a case, count bottles, and sell portions. Basic item inventory works best when the tracked unit matches the actual sellable unit. Ingredient or recipe workflows are more appropriate when one menu sale consumes several component units.
Square can handle the POS inventory action described above. Businesses that need a dedicated workflow for forecasting, purchasing, physical counts, ingredient-level tracking, or multi-location inventory can also connect Square with Stash for Square inventory management, which explains the combined workflow and when a dedicated inventory layer may make sense without replacing Square at checkout.
The item is the parent product or service; variations are separately configured versions that can carry their own price, SKU, and stock quantity.
It is strongly recommended for inventory operations. Unique SKUs reduce ambiguity in imports, receiving, counting, reporting, and integrations.
Yes. Assign the item to the relevant locations, then maintain and verify each location's quantity separately.
Usually not. Ingredients are components with different units and depletion logic. Use an appropriate recipe or connected ingredient-inventory workflow.
Last reviewed: August 8, 2026. Square menus, plan names, feature availability, and regional interfaces can change; confirm the current workflow in Square's official documentation.
Stash connects inventory tracking, forecasting, purchasing, suppliers, and multi-location visibility so growing physical businesses can act on the numbers with less manual work.