Multi-location inventory management

Stash brings together item-level inventory, location-level stock, suppliers, purchase orders, receiving, stock transfers, reorder signals, POS-connected data, and an auditable inventory ledger. Available capabilities can depend on plan, permissions, integrations, and workspace configuration.

Teams can work with location-level inventory and move stock through transfers that progress from draft to in transit, partially received, received, or cancelled. Sent and received quantities remain explicit so stock in motion does not disappear into a spreadsheet.

An item can include quantity, unit, cost and selling price, minimum and maximum stock, reorder quantity, SKU, barcode, category, tags, supplier links, brand, status, storage fields, dimensions, weight, pack size, and images. Teams can choose which columns they need to see.

Quantity changes preserve the previous amount, new amount, time, and business context. Movement categories include restock, consumption, adjustment, transfer in or out, waste, stocktake, return, correction, and opening stock. Notes and reason codes can document what happened.

Yes. Stash stores supplier contacts and operational details such as lead time, buffer days, delivery days, and minimum order value. Items can be linked to primary, secondary, backup, preferred, or alternative suppliers.

Teams can create purchase orders for a supplier and destination, select items, quantities, currency, and an expected delivery date, then update the order as needed. Deliveries can be received in full or partially, and inventory is updated from the quantities recorded as received.

Connected POS catalog, location, and order data can be mapped to Stash inventory. When product-to-item or component-blueprint mappings are configured, processed sales can support inventory deductions. Physical counts are still needed for waste, breakage, theft, and other movements a POS cannot observe.

Each item can have a low-stock threshold, and Stash can surface low-stock, critical, and out-of-stock states together with reorder alerts. Replenishment inputs can include stock, sales or consumption data, supplier lead times, delivery schedules, and buffers; operators should review suggestions before ordering.

Yes. Organization roles and permissions control access to areas such as reports, settings, purchase orders, transfers, blueprints, and cost data. Inventory and purchasing activity can retain the user and business context needed for operational accountability.

Start with the locations, item catalog, quantities and units, suppliers, stock thresholds, and integration or mapping details relevant to your workflow. Setup time depends on item count, data quality, number of locations, and operational complexity.