StoreSync blog

Coffee Shop Inventory Transfers: A Two-Shop Log

Track coffee shop inventory transfers between your Square shops with a copyable two-sided log: sender and receiver checks, one unit per item, no phantom purchases.

By Jared · 2026-11-16 · 9 min read

The way to track coffee shop inventory transfers between locations is one log with one transfer ID per move, where the sending shop records what left and the receiving shop separately records what arrived. Keep those two numbers apart, use one unit for every item, and leave any gap open until someone investigates it. That is the whole system, and it works on paper or in a spreadsheet.

Most owners with two to five Square shops already move oat milk, beans and syrups between locations when one shop runs short before a delivery. The problem is that the move leaves no trace. One shop's count drops, the other's rises, and the difference shows up weeks later as unexplained food cost variance or a vendor purchase nobody made. The log below fixes that without new software.

How should a coffee shop track inventory transfers between locations?

Treat every transfer as a two-sided transaction: one record, two signatures. The sender writes down what actually left the shop. The receiver, separately, writes down what actually arrived. Nobody edits the other person's number.

That is the core of inter-store transfer best practice. A few rules make it hold up:

If you run a commissary or prep kitchen that feeds your storefronts, the same log applies. The commissary is simply the sender on most lines.

You don't need transfer software to start. Multi-location tools such as MarketMan, Craftable and Restaurant365 are built around purchasing, invoices and food cost across units, and they can make sense at scale. For two to five shops, a disciplined log is the cheaper first step, and it teaches you what you'd want from software later.

The blank two-shop transfer log (copy and paste)

Paste this into a spreadsheet, one row per item per transfer. Columns before the divider are filled by the sender, columns after it by the receiver.

Transfer ID Date/time sent From shop To shop Item Unit Qty requested Qty sent Sender initials Date/time received Qty received Condition (OK / damaged / short) Receiver initials Difference (received minus sent) Status Notes / resolution
T-0001 Sent / Received / Open
T-0002
T-0003

Three notes on using it:

Print a paper copy for each shop's back counter if staff aren't at a computer when the milk arrives. Someone enters it into the spreadsheet the same day.

A hypothetical example: moving oat milk and beans from Shop A to Shop B

This is a made-up example to show the mechanics. Shop B ran low on oat milk and house beans before Thursday's delivery, so Shop A sends some over.

T-0001, Shop A to Shop B. The Shop B lead requests 6 cartons of oat milk and 4 bags of house blend. The Shop A lead packs and records:

The Shop A lead initials and writes the send time. Status: Sent.

When the driver arrives, the Shop B lead opens the box and counts without looking at the sender's numbers first. They find 5 cartons of oat milk, one with a dented seal, and 4 bags of beans.

The beans close out as Received. The oat milk line stays Open. Nobody changes the sent quantity from 6 to 5, and nobody plugs Shop B's count to make it look clean. The note reads: "6 sent, 5 arrived, one carton dented. Checking with Shop A whether a carton stayed behind."

That open line is the system working. The next section explains why.

Sender and receiver checks, and one unit for every item

Each side checks independently, and every item gets exactly one unit that both shops use. These two controls prevent most transfer disputes.

Sender check. Before the box leaves: count the item, confirm the unit, note the condition, write the quantity sent. Do it at the moment of packing, not afterward from memory.

Receiver check. On arrival: count the item, check the seal and the date, compare condition, write the quantity received. Count first, then compare to the sender's number. If you read the sent quantity before counting, you'll tend to see what you expect.

One unit per item. Pick the unit once and use it at both shops. Oat milk is cartons, not cases at one shop and quarts at the other. Beans are 12 oz bags, not pounds on one sheet and bags on another. Syrup is bottles. Pastries are each.

Mixed units are the quiet cause of transfer errors. A sender writes "1 case" and a receiver writes "12," and the log shows a phantom difference of 11. Put a short unit list at the top of the spreadsheet and treat it as law.

The same discipline pays off when you count. If your transfer units match your count units, a transfer never has to be converted before it touches your numbers. If you're still tightening your count process, see coffee shop inventory management.

In-transit stock and discrepancies: leave them open, don't plug the count

Leave a discrepancy open and unresolved until you know why it happened. Don't adjust a count just to make the two shops agree.

Plugging is tempting. Shop A says 6, Shop B says 5, and the fastest fix is to edit one number. But that erases the only evidence you have. If cartons are going missing between shops, or one location consistently over-packs, the pattern only shows up if the original disagreement stays on the page.

Handle gaps this way:

  1. Keep both numbers. Sent stays what the sender wrote. Received stays what the receiver wrote.

  2. Mark the line Open. Add a plain note: what you suspect, who is checking.

  3. Assign one person. Usually the lead at the sending shop, since they can check what is physically left.

  4. Resolve within a day. Damaged in transit, miscounted at packing, or left behind. Write the cause in the notes column.

  5. Adjust only after it's explained, and write the adjustment as its own line referencing the transfer ID.

In-transit stock works the same way. Anything marked Sent but not yet Received belongs to neither shop's usable count. If a transfer sits in Sent for more than a day, that's a flag by itself. Someone should call.

A weekly glance at your Open lines tells you which items and which routes cause trouble. Track the count of open lines and their dollar value, and you'll know quickly whether this is a one-off or a habit. Unexplained shrink from sloppy moves also feeds your waste log, so keep the two separate: a transfer difference is a logistics question, waste is a spoilage question.

Keep a transfer from becoming a vendor purchase

An internal transfer is not a purchase, and it must never be booked as one. The stock already belongs to you. It only changed shelves.

Here is how the mistake happens. Shop B receives six cartons of oat milk with no paperwork. The manager sees product on the counter, assumes a vendor delivery, and enters it as received against the dairy supplier. Now Shop B's count is up, the vendor's spend is overstated, and Shop A's count is quietly wrong because nothing was subtracted.

The transfer ID is your guard against this. Use these habits:

That last point matters because inflated vendor spend at one shop and missing stock at another both distort your percentages. If you review them weekly, the food cost variance worksheet is where a mishandled transfer would surface, as variance you can't explain.

Where transfers meet counts, par levels and food cost (and where StoreSync fits)

Transfers touch three other routines: your counts, your par levels and your food cost. Keeping the log clean keeps all three trustworthy.

Counts. Do your regular count with transfers settled. A count taken while product is in transit, or while a transfer is Open, won't match your records at either shop. Close out or note open transfers before counting.

Par levels. If Shop B keeps borrowing oat milk from Shop A, the real problem is Shop B's par. The log shows you which items move most often and in which direction. Use that to reset ordering, with the par level worksheet as a starting point. The goal is fewer transfers, not better transfers.

Food cost. Because transfers carry cost at the same unit price, they shouldn't move your food cost percentage at all. If they do, something was booked wrong.

Where StoreSync fits. StoreSync is operations software for Square coffee and restaurant shops that puts inventory and recipe costing in one login, so the counts you trust and the recipe costs you rely on sit together rather than in separate apps and spreadsheets. The transfer log stays your control for moving stock between shops. StoreSync is where the verified inventory and the recipe costing live once the stock is counted. It syncs with Square, and one shop is $146 a month billed annually, with each additional shop at $50 a month and setup included.

That pairing is the point. A log tells you what moved. Verified inventory and costed recipes tell you what it means for your margins.

Start with the log, then put your counts and recipe costs in one place

Coffee shop inventory transfers stay clean when every move has one ID, two independent counts, one unit per item, and an open line for anything that doesn't match. Run the log for two weeks and you'll see which items travel, which routes leak, and which pars are the real problem. When you want your counts and recipe costing in one login for all your Square shops, book a demo at getstoresync.com/demo.

Common questions

How do you track inventory transfers between coffee shop locations?

Use one log with a unique transfer ID per move. The sending shop records what left, the receiving shop independently records what arrived, and any difference stays open until explained. Use the same unit for every item at both shops. A spreadsheet or printed sheet is enough for two to five locations.

What is the best inventory management software for a coffee shop?

It depends on your size. Multi-unit tools like MarketMan, Craftable and Restaurant365 focus on purchasing and food cost. For Square coffee shops with one to five locations, StoreSync combines inventory and recipe costing in one login and syncs with Square, so counts and costs are not split across separate apps.

How should you handle a transfer where the received count doesn't match?

Leave it open. Keep the sender's quantity and the receiver's quantity as written, note the difference and the likely cause, and assign one person to resolve it within a day. Adjust counts only after the cause is known, as a separate line tied to the transfer ID.

How do you stop a transfer from being booked as a vendor purchase?

Require a transfer ID before anyone counts in product that has no vendor invoice. Check vendor deliveries against invoices and transfers against the log, never one for the other. Carry the original unit cost across so your food cost percentage does not shift because stock moved between shops.