{{ scopeLabel }}
{{ userInitials }} {{ userName }}
{{ homeEyebrow }}

{{ homeTitle }}

{{ homeSub }}

{{ nextTitle }} {{ nextSub }}
{{ a.title }} {{ a.body }}
Nothing is waiting on you.
Every demand this branch raised has moved on.
{{ s.label }}
{{ s.value }}
{{ s.sub }}
On its way here Approved and issued, or on order — not yet received.
Demand Route Coming from Lines Expected Where it is
{{ d.no }} {{ d.route }} {{ d.source }} {{ d.lines }} {{ d.expected }} {{ d.status }}
Nothing is on its way to this branch.
What is running low
Not yet — nothing counts branch stock A branch's holding is only known once the warehouse can issue stock against a demand. Until store issue is live, this panel would be guessing, so it shows nothing rather than a number somebody might order against.

Raise a demand

Route each line, and the demand splits itself: one document per destination. The branch never talks to a supplier — the route does.

What the branch needs A line with no quantity is not demanded.
Item Unit Quantity Route Goes to
{{ r.name }} {{ r.code }} {{ r.uom }} {{ r.dest }}
No items match that filter.
Direct supplier One demand goes to one destination — every direct line on this demand goes to the same supplier.
{{ supplierHelp }}
The date the kitchen needs it, not a promise from anybody.
What submitting creates
{{ splitHeadline }}
{{ c.badge }} {{ c.count }}
{{ c.dest }}
{{ c.note }}
Nothing demanded yet. Put a quantity against an item and its route decides which document it lands on.
Before this can be submitted
{{ c.mark }} {{ c.label }} {{ c.value }}
{{ listEyebrow }}

{{ listTitle }}

{{ listSub }}

Demand City / branch Raised Route Destination Lines Needed by Where it is Actions
{{ d.no }} {{ d.roundNote }} {{ d.branch }} {{ d.city }} {{ d.raised }} {{ d.raisedBy }} {{ d.route }} {{ d.dest }} {{ d.lines }} {{ d.needed }} {{ d.status }}
Nothing here with that status.

{{ detail.no }}

{{ detail.status }} {{ detail.route }}

{{ detail.subline }}

{{ detail.objectionTitle }} “{{ detail.objectionReason }}” {{ detail.objectionMeta }}
{{ s.label }}
{{ s.value }}
{{ s.sub }}
Lines {{ detail.linesNote }}
# Item Unit Demanded Issued / ordered State
{{ l.n }} {{ l.name }} {{ l.code }} {{ l.uom }} {{ l.qty }} {{ l.fulfilled }} {{ l.state }}
{{ detail.linesFooter }}
The trail {{ detail.trailNote }}
{{ t.title }} {{ t.meta }} “{{ t.quote }}”
Who can see this
{{ v.who }} {{ v.what }}
{{ scopeLabel }}

Receiving

Count what actually arrived. Short and damaged are recorded against the line, never rounded away — the document that follows is priced on what was accepted.

Direct from a supplier Delivered to the branch, never touching the warehouse. {{ receiveBadge }}
Order Supplier From demand Lines Expected Actions
{{ r.order }} {{ r.supplier }} {{ r.demand }} {{ r.lines }} {{ r.expected }}
{{ receiveTitle }} Count at the door, not afterwards
{{ userName }}
Item Ordered Accepted Damaged Reason State
{{ l.name }} {{ l.code }} · {{ l.uom }} {{ l.ordered }} {{ l.state }}
{{ receiveNote }}
From the city warehouse
Nothing to receive from the warehouse yet A warehouse receipt is counted against a store issue — the warehouse's own document saying what left its floor. Until the warehouse can issue against an approved demand, there is nothing here to count, and a blank line for somebody to fill in would be an invitation to invent stock.
{{ scopeLabel }}

{{ move.title }}

{{ move.sub }}

{{ move.sheetTitle }} {{ move.sheetSub }}
Item Quantity Reason Cost per unit Cost
{{ r.name }} {{ r.code }} · {{ r.uom }} {{ r.unitCost }} {{ r.cost }}
{{ move.costProvenance }}
{{ move.summaryTitle }}
{{ move.summarySub }}
{{ t.label }} {{ t.value }}
{{ move.blocker }}
{{ move.postedTitle }}
{{ p.title }} {{ p.meta }} {{ p.cost }}
{{ move.nonePostedNote }}
{{ scopeLabel }}

Cost of the day

What this branch consumed, day by day. A monthly figure arrives too late to act on — by the time it is wrong, thirty days of it are already wrong.

{{ s.label }}
{{ s.value }}
{{ s.sub }}
Fourteen days Click a day to read it. A closed day keeps the cost it had. {{ trendRange }}
{{ noDayTitle }} {{ noDayBody }}
{{ breakdownTitle }} Each line at the cost it carried when it moved.
Item Where it went Quantity Cost per unit Cost
{{ b.name }} {{ b.code }} {{ b.where }} {{ b.qty }} {{ b.unitCost }} {{ b.cost }}
Consumed on {{ chosenDayLabel }} {{ dayTotal }}
Cost comes from the stock ledger — the moving average at the moment each issue was made. It is never re-priced at today's rate and never typed in.
Branch expenses Money spent that is not stock.
{{ billNote }}
{{ expenseBlocker }}
{{ e.title }} {{ e.meta }} {{ e.amount }}
{{ c.name }} {{ c.amount }}
Expenses this month {{ expensesMtd }}
Expenses are kept apart from consumption — one is what the branch bought, the other is what it used. Adding them together would double-count the day a purchase is also consumed.
Admin · every branch

Expense setup

The heads a branch can spend against. Set up once here for the whole group — a branch typing its own head is how the same cost gets reported twice under two names.

Expense heads Retiring a head hides it from new expenses; the ones already recorded keep it.
Code Head Group Bill Used State Actions
{{ h.code }} {{ h.name }} {{ h.group }} {{ h.billLabel }} {{ h.used }} {{ h.stateLabel }}
Add a head
{{ setup.headBlocker }}
Gulberg Outlet · Lahore

Inter-branch

When Gulberg pays for another branch — or another branch pays for Gulberg — it is recorded here, signed by the manager, and posted by Finance in both branches' books. Finance settles the balances by bank.

{{ t.label }} {{ t.value }} {{ t.sub }}
Record one
{{ ibPreview }}
{{ ibMsg }}
Head office reads inter-branch balances here; the branches record them and Finance posts them.
Who owes whom
{{ n.text }} {{ n.amount }}
Square with every branch.
Gulberg's inter-branch log
{{ r.no }}{{ r.tag }} {{ r.what }} {{ r.sub }} {{ r.waitNote }} {{ r.amount }}
Finance view across all branches →
{{ scopeLabel }}

What the branch costs

Two kinds of money leave a branch: stock it consumed, and bills it paid. They are counted separately and never added into one figure by accident.

{{ s.label }}
{{ s.value }}
{{ s.sub }}
Day by day The number above a column is what the kitchen consumed that day. Stock consumed Bills paid
{{ d.value }} {{ d.label }}
The two bars sit side by side rather than stacked — one is stock the kitchen used, the other is cash the branch paid out, and a single total of the two would say neither.
Where it went {{ periodLabel }}
{{ r.label }} {{ r.value }}
{{ r.note }}
No profit figure, and no margin Nothing in this system records what the branch sold, so there is no revenue to set these costs against. A profit line would have to invent the half it does not have. It arrives when sales do.
What the branch owes is not here either An expense marked “on account” is money not yet paid, but a payable balance belongs to Finance and Finance is later. The expense is on the record; the balance is not being guessed at.
{{ scopeLabel }}

Branch stock

This is movement, not a balance A stock figure needs both halves. The branch's outward movements are recorded below because the branch records them itself. What came IN is not: there is no opening count anybody signed for, and the warehouse cannot yet issue against a demand. Subtracting the half we have from a half we do not have would produce a number, and the number would be wrong.
{{ s.label }}
{{ s.value }}
{{ s.sub }}
What has moved, by item Every movement this branch has posted, at the cost it carried. {{ stockRange }}
Item Came in To the kitchen Wasted Total out Cost of what went out On hand
{{ r.name }} {{ r.code }} · {{ r.uom }} {{ r.inValue }} {{ r.issued }} {{ r.wasted }} {{ r.out }} {{ r.cost }} {{ r.onHand }}
Cost of everything that left this branch {{ stockOutTotal }}
The On hand column stays empty on purpose. It fills the day the warehouse can issue against a demand and an opening count has been taken — not before.
{{ soon.eyebrow }}

{{ soon.title }}

{{ soon.headline }} {{ soon.body }}
{{ soon.listTitle }}
{{ w.n }} {{ w.title }} {{ w.note }}
{{ soon.footer }}