The Stock Card: Proving Why Your Stock Figure Is What It Is
This conversation happens in every repair shop, and it always ends the same way.
“Only two brake pads left? I could have sworn there were eight last week.” “Yes, I don’t understand it either.”
And then nobody can finish the sentence. Not because anyone is hiding anything — but because nowhere holds the story. All that is stored is today’s number, and today’s number can never explain itself.
The stock card holds the story.
Not merely a list of ups and downs. Every row carries a pointer to the transaction that caused it — a purchase, a purchase return, a sale, a sales return, a part used on a repair, a repair return, a stock-count adjustment, an inter-shop transfer, or goods written off as damaged. Nine different origins, and no row that came from nowhere.
So “why are there only two?” stops being an argument and becomes a search. You open the history, trace backwards, and the answer is usually boring: four went into Saturday’s repairs, two more sold over the counter on Monday.
What makes the stock card valuable is not the times everything agrees. It is the times it does not — because a discrepancy you can trace will tell you which part of your workflow is leaking. And that is far more useful than finding out who was careless.
Before you start
- Products registered and transactions recorded through the application rather than from memory.
Steps
-
First, understand how Arus Stok differs from a stock report
A stock report answers "how many are there now". Arus Stok — the stock movement screen — answers "why is it that many". The first is one number; the second is a sequence of events. When there is a discrepancy, only the second is any use.
-
Open Inventory → Arus Stok, then filter to one product
The first field to fill is not the date but Produk (product) — because the right way in is through the item causing trouble, not the whole shop. Only then narrow Tanggal Awal and Tanggal Akhir (start and end date). One item history is far easier to read than an ocean of transactions filtered afterwards.
Filter to one product before you read. -
Read the two columns that matter: in and out
Each row either adds or subtracts, never both. Total in minus total out must equal the current stock figure. If it does not, the arithmetic is not what is wrong — some transaction was never recorded.
These two columns decide everything. -
Notice the origin of each row — this is where the real value sits
Every movement carries a pointer to the transaction that caused it: a purchase, a purchase return, a sale, a sales return, a repair, a repair return, a stock-count adjustment, an inter-shop transfer, or damaged stock. You will never meet a row that came from nowhere.
The origin of each row — that is the real value here. -
Trace back to the original transaction whenever something looks odd
Finding an outgoing row you do not recognise, then opening the transaction behind it — that is the entire point of a stock card. Nine times in ten the answer turns out to be ordinary: a part used on a repair you had forgotten.
Trace back to the source transaction when something looks off. -
Learn the most common discrepancy: goods out with no transaction
If shelf stock is lower than the system, and the card shows no outgoing movement in that window, the cause is almost always the same — something was taken off the shelf without being recorded. Not theft; usually busyness.
-
Learn the opposite pattern: goods in with no purchase
Shelf stock higher than the system usually means goods arrived without the purchase being recorded, or a customer return that was never entered. This is more dangerous than it looks, because the cost price went unrecorded too — making your profit look larger than it is.
-
Treat a stock count as a correcting row, not as an eraser
When you adjust stock through a count, the adjustment itself is recorded as a movement row. Earlier history is not deleted. This matters: corrections that erase the trail make recurring patterns impossible to find.
An opname adds a correcting row; it never erases history. -
Spot-check the card against the shelf for high-value items
You do not need a full count every week. Take your five most expensive items and match system against shelf. If those five agree, the rest is usually fine. If one is off, that is where to dig.
Compare against the shelf for high-value items. -
Make this your first move, not your last
When somebody asks "why is stock short?", the correct reflex is to open the stock card — not to question a person. Questioning people invites defensiveness; opening the history invites an answer.
What you end up with
Every stock discrepancy can be traced back to the transaction that caused it, so you fix the leaking workflow rather than guessing who was at fault.
If something goes wrong
The stock card figure does not match the stock report
Check you are viewing the same shop and a date range covering the whole history. A card cut short by a date filter obviously will not add up to the current figure.
There is an outgoing row I do not recognise
Open the source transaction through the pointer on that row. Most often it turns out to be a part used on a repair, because repair usage deducts stock exactly like a sale.
Stock is negative but the goods are on the shelf
That means the outgoing movement was recorded before the incoming one — usually goods sold before the purchase was entered. Record the purchase with its correct date and the negative resolves itself.
I want to know who took the goods out
The stock card points at the transaction; the transaction carries the name of whoever entered it. For changes made afterwards, trace through the activity log instead.
The history is too long to read
Narrow it to the window between when the figure was still right and when it started being wrong. You almost always know those two dates, and narrowing cuts hundreds of rows down to a dozen.