Warehouse is a record of what is actually in store and what is moving: godowns, the stacks inside them, the quantity in each, and every truck that came in or went out.
It is built around the stack because that is the unit a godown is actually managed in. A stack has a crop, a variety, a lot number, a bag size and a count — and it sits on a pallet or on bare floor, is covered or is not, has been fumigated or has not, and was last inspected on some date or never.
Those storage-condition fields are not decoration. Ground contact is one of the single biggest causes of real spoilage, because moisture wicks straight into the bottom layer, and a stack that nobody has inspected for three weeks is the one that will be found spoiled. The dashboard surfaces inspections that are overdue rather than waiting to be asked.
Stock movements are recorded as real signed changes against a stack — a truck in, a truck out, or a manual correction after a physical recount — so the quantity on screen has an audit trail behind it rather than being a number somebody overwrote.
Everything exports as a PDF or a spreadsheet: every stack with its crop, lot, bags, tonnage, pallet type, protection status and last inspection date. That is the document a buyer, an auditor, a lender or an insurer asks for, and assembling it by hand from a register takes a day.
It is honest about the one thing it cannot do: it knows only what was entered. It cannot see the godown, and a stack that was quietly sold is still in the app until somebody says so.
How to use Warehouse
What it is. A live record of what is in store and what has moved: godowns, the stacks inside them, the quantity in each, their storage conditions, and every truck in or out — with overdue inspections surfaced rather than waiting to be asked for, and the whole thing exportable as the document a buyer, auditor, lender or insurer asks for.
When to open it. Continuously, once set up. The record is only worth having if it is current, and a warehouse record that is a week behind is a warehouse record that gets argued with.
Have ready.
The godowns, named.
The stacks in them: crop, variety, lot number, bag size, count.
Their storage conditions: pallet or bare floor, covered or not, fumigated or not, last inspection date.
Every movement as it happens.
Step by step.
Add the warehouse. Name it something people use.
Add each stack with its crop, variety, lot number, bag size and count. The lot number is what connects a stack to its paperwork.
Record the storage conditions honestly — especially whether the stack is on a pallet and whether it has been inspected.
Record every movement as it happens: a truck in, a truck out, or a manual correction after a physical recount.
Watch the overdue inspections. They are shown rather than hidden, because the stack nobody has looked at for three weeks is the one that will be found spoiled.
Export the PDF or the spreadsheet when somebody asks what is in store.
What it will not do. It knows only what was entered. It cannot see the godown, cannot weigh a stack, and a lot that was quietly sold is still in the system until somebody says so. The inspection list tells you what has not been looked at, not what is spoiled.
Every setting in Warehouse, explained
Warehouse / godown
The building. How to choose: The name people actually use for it. If it is wrong: Nothing miscalculates; the report becomes harder to read than the register it replaced.
Stack
The unit a godown is genuinely managed in — a crop, a variety, a lot, a bag size and a count. How to choose: One stack per lot. Two lots in one stack cannot be traced apart later, which defeats the lot number. If it is wrong: Traceability is lost at exactly the moment somebody asks where a particular consignment came from.
Lot number
What connects the physical stack to its invoice, its grading and its origin. How to choose: Copy it exactly from the paperwork. If it is wrong: A quality complaint that cannot be traced to a lot is a complaint against your whole godown.
Bag size and count
What the tonnage is computed from. How to choose: The filled weight, not the sack's nominal size. Stack Calculator does the arithmetic if you are counting a block. If it is wrong: Tonnage is out in proportion while the bag count stays right, which is why both are recorded.
Pallet or bare floor
Whether the stack sits on a pallet or on the floor. How to choose: Record it truthfully. Ground contact is one of the largest single causes of real spoilage — moisture wicks straight up into the bottom layer. If it is wrong: You lose the ability to explain why one stack spoiled and another did not, which is the only way the record improves your practice.
Covered / fumigated / last inspected
The protection state of the stack and when anybody last looked at it. How to choose: Update the inspection date every time somebody actually inspects, not when they walk past. If it is wrong: The overdue-inspection list is the most useful thing on the dashboard, and it is only as good as this date.
Stock movement
A signed change against a stack: in, out, or a correction after a recount. How to choose: Record it at the time. Record corrections as corrections rather than overwriting the number. If it is wrong: Overwriting a quantity destroys the audit trail, and an audit trail is the entire difference between this and a figure somebody typed.
A worked example
A godown with four stacks, one of which was last inspected nineteen days ago and sits on bare floor.
What goes in:
Four stacks entered with conditions
Movements recorded as they happened
What comes out:
Current quantity per stack, with the movements behind each figure.
That one stack surfaced as an overdue inspection.
Total tonnage in store, by crop.
An export listing every stack with crop, lot, bags, tonnage, pallet type, protection status and last inspection date.
The export is the point. That document — every stack with its lot, tonnage, storage condition and inspection date — is what a buyer, an auditor, a lender or an insurer asks for, and assembling it by hand from a register takes a day. Here it takes a press.
How to read what it gives you
Every quantity has movements behind it. A number with an audit trail can be defended; a number somebody overwrote cannot.
Overdue inspections are surfaced, not buried. Spoilage is found by looking, and stacks that are not looked at are the ones that spoil.
Storage-condition fields are not decoration. Ground contact, cover and fumigation status are the fields that predict which stack you will lose.
The export is the deliverable. Everything else on the screen exists to make that document true.
What usually goes wrong
Recording a physical recount by overwriting the quantity instead of entering a correction. The correction is the interesting part — it tells you how much you were out and how often.
Mixing two lots into one stack.
Updating the inspection date without inspecting.
Letting the record fall behind. A warehouse record that is a week stale is worse than none, because people trust it.
Questions people ask about Warehouse
How should I keep godown stock records?
By stack, not by total, and with every movement recorded as a signed change rather than by overwriting a number. The stack is the unit a godown is actually managed in — one crop, one lot, one bag size — and movements with an audit trail are the difference between a figure you can defend and one somebody typed.
Why does it matter whether a stack is on a pallet?
Because ground contact is one of the largest single causes of real storage loss. Moisture wicks up from the floor into the bottom layer and spoils it from underneath, where nobody sees it until the stack is moved. Recording it is what lets you explain afterwards why one stack was lost and another was not.
What document do buyers and lenders ask for?
Essentially the export this produces: every stack with its crop, lot number, bag count, tonnage, pallet type, protection status and last inspection date. Assembling that by hand from a register is a day's work, which is why it usually does not get done until somebody insists.
How often should stacks be inspected?
Often enough that a problem is found while it is still one stack. The dashboard surfaces what has gone longest without being looked at rather than prescribing an interval, because the right interval depends on the crop, the moisture and the season — but a stack nobody has checked for three weeks is reliably the one that turns out to be spoiled.
Can it tell me how much is actually in the godown?
It tells you what has been entered and what has moved, which is the best record anybody has short of a physical count. It cannot see the building. That is why corrections after a recount are recorded as corrections — the gap between the record and the count is itself information worth keeping.
Want to use Warehouse for real, right now? Open Warehouse in the Laisha app → Ten days free, no card. After that 10 US dollars a month, one price worldwide.