threefoldWORKSLet’s talk
Menu

WORKFLOW

Stock transfer between branches that never closes

Illustrative example Retail chains Restaurants

Branch A messages the group that it is out, branch B says it has extra, the owner types “ok”, and a week later six units are on nobody’s count because the slip is in a drawer and the transfer was never closed.

The workflow

One branch runs out of an item that another branch is holding too much of, the transfer between them is agreed in a chat thread and moved on a paper slip, and the stock leaves one count without ever reliably arriving on the other.

Illustrative example Branch transfer · closed

Transfer · TR-0419

Branch B to Branch A · 6 units
  1. Transfer proposedDone
    Branch A below minimum · Branch B above maximum · Monday 09:10
  2. Approved and dispatchedDone
    Approved by the owner in the branch thread · 09:34Slip TR-0419 to both branches · 6 units in transit
  3. Receipt confirmedDone
    Received at Branch A · 6 of 66 unitsClosedBoth counts updated · closed Tuesday 11:02
    Confirmed by both branches · slip photo and message read

The owner made the only decision in it.Every step on record

What happens today

Multi-branch chains count stock in spreadsheets, and count it infrequently. Monthly counts leave a thirty-day blind spot, as the accounting firm that works with Philippine restaurants puts it, and a transfer is the one movement of stock that changes two branches’ counts at once and belongs to neither.

The transfer itself lives in a chat: branch A posts that it is out; branch B posts that it has eight; the owner approves in the same thread, and a paper transfer slip goes with the units in the delivery van or the rider’s bag. Branch B deducts the units when they leave, or when someone remembers; branch A adds them when they arrive, or does not, because the slip turned up a day after the box. The point-of-sale vendors that sell to these chains list stock transfer, transfer alerts, and per-branch variance as features of their higher tiers, which says the need is common enough to sell to. It does not say how many chains have the feature switched on, and this story assumes most do not.

A transfer that never closes is not a rounding error. It is stock that one branch has written off and the other has not written on, and at the month-end count it shows up as shrinkage at branch B and a surplus at branch A — or, if branch A sold the units before counting, as sales of stock that branch never had. Either way the variance report points at the wrong branch.

What ordinary rules handle

Most of this is two stock positions, a threshold, and a clock, and we build it as ordinary rules, because ordinary rules are cheaper to run, easy to check, and behave the same way next month.

  • Watching each branch’s stock position for an item that is below its minimum at one branch while another branch holds more than its maximum, and proposing the transfer from the branch that can spare it.
  • Preparing the slip from the proposal: item, quantity, from, to, who approved, and a reference number that both branches quote back.
  • Holding the transfer open until both ends confirm — sent from B, received at A — and reminding each branch on a schedule until it does.
  • Flagging any transfer still open past the number of days the chain sets, and routing it to the operations manager with both branches’ current counts attached.

Where the assistant follows through

This is the part we call follow-through: the assistant checks the records, prepares the action, routes it, chases the reply, and raises what it cannot settle.

What rules cannot do is read “received na, kulang isa” in the branch thread and turn it into a receipt of five against a slip for six, or work out that the photo of the slip, folded and signed, is the confirmation branch A never typed. AI reads the message and the photo and makes that call, and it is a smaller part of the job than it sounds.

  1. The shortage becomes a draft transfer. The two stock positions are set side by side, the quantity is proposed, and the slip is drafted with a reference number. Draft, because nothing has moved yet.
  2. The proposal goes to the owner for approval. In the thread the branches already use, with both counts attached, so the answer is a word and not a phone call.
  3. Once approved, the slip goes to both branches and the units are posted as in transit. Branch B’s count comes down on dispatch and branch A’s does not go up until it confirms, so for the days in between the units are on the transfer, not lost.
  4. Receipt is confirmed on both sides, and chased. The receiving branch is asked in its own thread to confirm the quantity, and the slip photo or the message is read as the confirmation. A short receipt is flagged with the slip and both messages attached, so the next person to look at it is not re-doing the check.
  5. A transfer that never closes is escalated rather than absorbed. If neither branch has confirmed after the days the chain allows, the transfer goes to the operations manager as an open item with the two counts, not into the month-end variance as shrinkage at one branch and a surplus at the other.

Where a person decides

Moving stock between branches is the owner’s call — or the operations manager’s, once the owner has handed that down — and the assistant cannot take it. It proposes the transfer, prepares the slip, and stops there — not because a check failed, but because that is where the line was drawn when the workflow was built.

Stock moving is a decision. The approval stays on the record with the reference number, the two counts at the time, and the name of the person who gave it, and the transfer stays open until both branches have said so. A month later, the question “where did the six units go, and who agreed to move them” has an answer.

Where to start

Start with two branches and the ten items you transfer most — the ones the group chat is already about. One shortage, one proposal, one slip confirmed at both ends is enough to see how many transfers close on their own and how many were never going to.

Nobody at the branches has to learn anything new. They post to the same group they post to now, and the owner answers a message and approves.