Square POS

Connect Square POS to Stash so supported Square catalog, location, and closed-order data can feed your inventory workflow. Keep selling in Square while Stash handles mapped stock deductions, purchasing, suppliers, counts, forecasting, and location-level inventory.

Once connected, Square locations are mapped to Stash shops and POS products are synced. Products that should move stock need an explicit Stash mapping. For recipe, bundle, or component-based products, Blueprints define what inventory should be deducted when the linked Square product sells.

Stash starts processing orders created after the POS connection is established. Historical Square orders are not backfilled into inventory.

Square remains the system your team uses at checkout. Stash pulls newly closed orders on a scheduled sync, approximately every 15 minutes.

• Closed Square orders are picked up by Stash after the connection is live.
• Location mappings route each Square location to the correct Stash shop.
• Product mappings and Blueprints determine which inventory items or components should move.
• Inventory transactions are recorded in Stash with a reference to the originating POS order.
• Low-stock notifications and planning views update from the resulting inventory position.

Physical counts are still necessary for waste, breakage, theft, receiving differences, and other inventory movements a POS cannot observe. Refunds and voids do not automatically reverse a prior Stash stock deduction. Square modifiers are also not currently exposed in the order feed Stash receives, so modifier-level deductions require special handling.

1. Create or sign in to your Stash workspace.
2. Set up the Stash locations that correspond to your Square locations.
3. Open Integrations in Stash and connect your Square account.
4. Map each Square location to the correct Stash shop.
5. Sync the Square product catalog.
6. Link the Square products that should move inventory to the appropriate Stash inventory item or Blueprint.
7. Check units and pack-size information so component deductions can be converted correctly.
8. Run a real or test sale, close the order in Square, and allow up to roughly 15 minutes for the next Stash sync.
9. Review the POS sync log and inventory transaction history to confirm the expected deduction.

For a clean launch, finish location and product mappings before normal sales start flowing. Orders processed before a required mapping exists are not retroactively deducted later. If your Square workflow depends heavily on modifiers, review the current Square modifier limitation in the POS sync guide before going live.