Inventory

Warehouses & transfers — multiple stocks in multiple places

A central warehouse with several branches? A commissary kitchen and operating outlets? The system tracks parallel balances for every location and moves stock through a clear send-and-receive cycle.

Why separate warehouses?

A warehouse per location

A central store, a commissary, any number of sales branches — each with an independent balance.

Request-and-approve transfer cycle

A branch requests quantities from central, an approver signs off, then the send-and-receive happens.

Step-by-step transfer tracking

Left central, in transit, arrived at branch, accepted — every step is timestamped and tied to a user.

Return surplus stock

A branch received too much? Return the surplus to central using the same cycle.

Branch-warehouse mapping

Each branch is mapped to one or more warehouses, and recipe deductions on sales come from there automatically.

Live stock per warehouse

Search any item and see its quantity across every warehouse and branch in one screen.

Transfer cycle

From transfer request to final receipt

A transfer starts with a request from the receiving branch (a transfer order). The approver accepts or declines. On acceptance, the sending warehouse picks the goods, deducts from its balance, and marks them sent. The receiver records what actually arrived — any gap is logged as loss or damage, not as phantom stock.

  • Transfer orders with states: open, accepted, declined, closed
  • Actual transfer states: sent, received, returned
  • Log shortages or damage at the moment of receipt

Warehouse setup

Model your stock map the way you actually operate

A single-branch restaurant may need one warehouse. A ten-branch chain may need a central, a commissary, and one per branch. The model is flexible — set up what fits, and reorganize later.

  • Any number of warehouses per business
  • A branch can draw from more than one warehouse
  • Linked to branch settings in /back-office/branches

Tied to recipes

The cashier sells, the recipe deducts from the right warehouse

When a dish sells at the cashier, the system identifies the warehouse mapped to that branch and deducts the recipe ingredients from it. You do not think about which stock feeds which branch — the mapping is set once and applies to every ticket forever.

  • Auto-deduction on every sale
  • Tied to recipes at /inventory/recipes

Ready to organize multi-location stock?

No transfer chaos, no phantom stock, no mystery losses. Every movement documented.

Start Free Trial

Just one intro call. No spam, ever.

  • 14-day free trial
  • No credit card required
  • Cancel anytime
FAQ

Common questions

Answers about warehouses and inter-branch transfers.

Yes. The system supports multiple warehouses, and each branch can be mapped to a primary warehouse while still pulling from others when needed.

Open a transfer (create → accept/decline → close), then send and receive (or return) until the transfer closes.

Receive the actual quantity; the difference is logged automatically with an optional reason (damaged, missing) and shows up in your loss report.

Yes. Weighted-average cost moves with the transferred quantity, so margin reports at the receiving branch stay accurate.

Yes, with permission. You can grant a branch visibility into other warehouses' stock to help with order planning.