Managing Stock Across Two Kitchens (or Any Split Location)
16 April 2026 · 8 min read
You start baking at home. Everything is in one place: the cupboards, the fridge, the freezer. You know roughly what you have. It works.
Then demand grows and you hire a commercial kitchen one or two days a week. Now your flour is in two places. Your vanilla extract is definitely at home - or was it the unit? The labels you ordered went to the house, but you need them tonight at the kitchen.
This is a very common situation for food producers, and it creates stock problems that are genuinely hard to manage with the tools most people reach for first.
Why two locations breaks simple systems
A single spreadsheet - or even a single physical notepad - works reasonably well when everything is in one place. You can glance at the shelf, count what’s there, and update the number. It’s not perfect, but the friction is low.
Split locations break this entirely.
You’re no longer checking one shelf - you’re trying to hold a mental model of two separate locations, often updated at different times by the same person. The spreadsheet on your phone at home doesn’t reflect what you left at the kitchen this morning. The notes you made at the unit last Thursday are accurate for then, not now.
The most common failure modes:
Phantom stock. You think you have enough chilli flakes to make your next batch. What you actually have is an empty jar at home and a half-full one at the unit. You don’t discover this until you’re mid-recipe at the wrong location.
Double ordering. You order more brown sugar because you can’t remember if you left any at the unit. You had plenty. Now you have too much in the wrong place and a slightly trimmer bank account.
Wrong-location ingredients at production time. This is the one that really costs you. You’ve booked the kitchen for four hours on Saturday morning. You arrive and realise the key ingredient is at home, forty minutes away. You either improvise, cancel the booking, or do a frustrated round trip.
Split batch confusion. You start a product at home (prep work) and finish it at the unit (cooking, packaging). Keeping track of which raw materials moved where - and when - becomes a genuine challenge.
What you actually need to track
Before thinking about tools, it helps to be clear about what information you need.
Per location:
- What ingredients/materials do I currently have here?
- What quantities?
Across both:
- What do I have in total?
- What’s low enough to trigger a reorder?
- What can I make this week, given what I have across both sites?
In transit (the awkward third state):
- What have I moved or am about to move from one location to the other?
That last point is underappreciated. When you’re carrying a box of packaging from home to the unit, those items are temporarily in neither the home stock count nor the unit stock count. If you update your records when things arrive rather than when they leave, you’ll always have a gap.
The “bag-and-note” approach (low-tech but effective)
Before reaching for software, there’s a practical low-tech system some food producers find works well for small operations.
Keep a printed or handwritten stock list for each location. When you move anything from one location to another, you write it down immediately - what moved, how much, and in which direction. You update both lists before you forget.
A simple physical notebook at each location, used consistently, is more reliable than a spreadsheet updated from memory. The notebook is always there. The laptop is not always open.
This works up to a point. It struggles when:
- You’re moving things frequently
- Multiple people are sometimes at both locations
- You need to quickly check “can I make this order?” without visiting both sites first
What software needs to do (and what most doesn’t)
Most basic inventory apps are designed for a single stock location. They’ll track what you have, let you adjust quantities, and tell you when something’s low. They’re not built for the “this item exists across two places and the total matters, but the breakdown also matters” problem.
What you actually need from a two-location setup:
Location-aware stock records. Not just “I have 5kg of oats” but “I have 3kg at home and 2kg at the unit.”
Transfers as a first-class operation. Moving stock from one location to another should be a specific action in the system - not a manual adjustment at both ends. When you log a transfer, both locations should update simultaneously.
Total-aware reorder alerts. A “low stock” alert should be based on the combined total, not per-location. If your reorder point for vanilla extract is one bottle, the alert should fire when you have less than one bottle across both locations - not fire separately for each location that drops below the threshold.
Production that draws from a specified location. When you log that you made 20 jars of chutney, the system should deduct from the location where you actually made it, not just from your total.
Practical habits that help, whatever system you use
A few practices that make multi-location stock management more manageable:
Set a weekly reconciliation time. Pick one moment per week - Sunday evening, Monday morning - where you check both locations against your records. Not a full count every time, just a quick sanity check on the items most likely to drift. It takes five minutes and prevents the accumulated errors that turn into a crisis.
Use named bags or containers for transfers. When you’re moving things from home to the unit, put them in a designated bag (or box, or cool bag). The physical act of putting things into the bag prompts you to log the transfer, rather than just carrying loose items and forgetting half of them.
Order to a single location wherever possible. If most of your production happens at the rented unit, try to have supplies delivered there directly rather than at home, even if it means collecting from a neighbour or having deliveries held. One fewer transfer to track.
Don’t split batches unnecessarily. If you can do all the prep for a product at one location and all the production at another, that’s easier to track than mixing it up. Moving partially-made product adds a layer of complexity that usually isn’t worth it.
Track packaging separately from ingredients. Labels, jars, lids, and boxes tend to move differently to ingredients - they’re usually bought in bulk, stored at one location, and brought to production in batches. Keeping them on a separate stock list (or at least mentally categorising them differently) reduces confusion.
When to add a second location formally vs. keep it casual
Not every business that uses a rented kitchen needs formal two-location stock tracking. If you use the unit infrequently, always move the same set of supplies back and forth, and run relatively few product lines, a simple checklist system may be all you need.
Formal location tracking starts to pay off when:
- You use the unit regularly (once a week or more)
- You leave a permanent stock of supplies at the unit
- You have more than around 20-30 distinct ingredients/materials
- You start making production decisions remotely (“can I make that order this week?”) and need an accurate picture without visiting both sites
The cost of getting this wrong scales with the volume you’re producing. A phantom stock error that costs one wasted journey or one delayed order is annoying when you’re making 50 jars a month. When you’re making 500, it starts to hurt.
A note on future growth
Many food producers eventually move to a single production location - either dropping the home kitchen entirely (producing only at the unit) or, if they grow significantly, transitioning to a dedicated space of their own.
If that’s a possibility for you, it’s worth choosing a stock management approach that handles the transition. Moving from a two-location to a single-location setup should be straightforward - you shouldn’t have to rebuild your product and supplier records from scratch. Similarly, if you eventually move to a third location, your system should handle that without requiring a different approach.
The producers who handle location changes most smoothly are usually the ones who set up clean, location-aware records early - even when it felt like unnecessary complexity at the time.