A Count That Writes Nothing
A stocktake in our system does not change your stock. It raises adjustments that somebody has to approve. That one decision is the difference between a count that tells you the truth and a count that quietly becomes the truth.
Most inventory systems treat a stocktake as a correction. You count, the system writes the counted figure over the book figure, and the difference disappears into a variance report nobody reads.
Ours refuses to do that, and the refusal is the best design decision in the module.
What actually happens when a count finds a difference
The variance does not write to stock. It raises a pending adjustment — a check-in or a check-out for the difference, sitting in the same approval queue as every other adjustment, subject to the same value threshold and the same separation of duties.
The session itself carries a status saying it is waiting on those adjustments, and only when they are settled does the stock move and the session complete.
The consequence is worth stating plainly: a counter cannot change stock. They can report what they counted. Somebody else decides whether that becomes the record. In a business where the person counting is also the person who could benefit from the count, that is not a nicety.
A count is evidence, not an instruction. Everything good in this module follows from that one sentence.
The other three things that follow from it
- The blind count is genuinely enforced. The counter is not shown the expected figure, and this is a lock rather than a convention. It is worth contrasting with the till: the blind cash count at the point of sale is a discipline that can be worked around, and we say so. The inventory one cannot.
- A disputed line is recounted, not overwritten. Lines carry a recount-requested status with the person who asked and their reason, and it writes an audit event. Approval refuses to change an already-approved line and tells you to request a recount instead — so the second number never quietly replaces the first.
- A session cannot be closed while anything is unresolved. Lines still submitted or awaiting a recount block the close. There is no way to finish a count by ignoring the awkward part of it.
Why this matters in a small-team retail or distribution business
Jamaican trading operations are frequently run by a small number of people who each do several jobs. The storekeeper counts. The same storekeeper receives. Often the same storekeeper is trusted completely and has been for fifteen years, which is exactly the situation in which nobody wants to design a control and everybody should.
The value of the pending-adjustment design in that setting is not suspicion. It is that it makes a second pair of eyes cheap. Nobody has to supervise the count. Somebody has to approve a short list afterwards, which takes minutes, and the list is exactly the set of things worth looking at.
It also protects the counter. A count that cannot be altered later by anybody, and a variance that was approved by a named person on a named date, is a record that defends the person who did the work.
Where it stops
Counting, layer by layer
Capture
Plans, sessions, per-person assignments, an enforced blind count, and barcode scanning against items and locations.
Dispute
Per-line recount requests with a reason and an audit event, and a session that will not close over an unresolved line.
Authorisation
Variances become pending adjustments under the normal approval threshold and separation of duties.
Scheduling
A plan has a frequency field. Nothing reads it — no session is ever created automatically, so every count starts with a person remembering.
Measurement
Variance is captured on every line and nothing aggregates it. There is no accuracy percentage, no trend, and no score by counter or by location.
Prioritisation
ABC analysis exists and is well built; nothing carries its result onto the count plan, so what to count more often is decided by hand.
Read the shape rather than the rows. The transactional half of counting is finished and careful. Everything about deciding WHEN and measuring HOW WELL is missing, and that is the half that turns counting into a programme rather than an event.
There is one more boundary worth naming because it catches people in food and beverage distribution particularly. Quantities are whole numbers and there is no unit of measure, so a count is a count of whatever unit your catalogue happens to use, and nobody can record two-thirds of a drum.
Four questions that tell you whether counting is a control or a formality
Does a count write to stock directly?
A good answer sounds like
No — it raises something somebody approves.
What it actually means
A count that writes directly means the person counting can set the record. Whether that matters depends entirely on who counts.
Is the blind count enforced or recommended?
A good answer sounds like
Enforced, and demonstrated by trying to see the figure.
What it actually means
The word "blind" appears in almost every product in this category. The lock does not.
What happens to a line somebody disputes?
A good answer sounds like
A recount with a reason, not an edit.
What it actually means
If the answer is that a supervisor edits the number, the original count is gone and so is the reason it was questioned.
What is my count accuracy this quarter?
A good answer sounds like
A percentage, by site and by counter.
What it actually means
Ours cannot answer this. The data is captured line by line; nothing aggregates it. Worth asking everywhere, because it is a common absence dressed as a variance report.
What AWRA OpsHub does today
- Count plans, sessions and per-person assignments, with an enforced blind count.
- Per-line statuses including recount requests carrying the requester and a reason, with audit events, and a session that cannot close while lines are unresolved.
- Variances raised as pending adjustments under the standard approval threshold and separation of duties, with a session status reflecting the wait and a write-back on settlement.
- Variance rules, and barcode scanning against items and locations during a count.
- Full history of who counted what, when, and what happened to it.
What it does not do
- Scheduling. A plan's frequency is stored, validated and read by nothing — no count is ever created automatically.
- A count accuracy measure of any kind: no percentage, no trend, no score by counter or location.
- Any write-back of ABC class onto a count plan, so counting frequency is prioritised by hand.
- Fractional quantities or units of measure — every count is in whole units of whatever your catalogue means.
Not ours, by choice
- The pending-adjustment design is the strongest thing in the inventory module and we would put it against anybody's. This page exists partly to say so.
- The missing half is scheduling and measurement, which is what turns counting from an annual event into a programme. Both are real absences and neither undermines the transactional design.
- Nothing here is Jamaican. It is what a count is worth in a small team; Jamaica is where our reader is most likely to be running one.
What is not built for Jamaica today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in Jamaica. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax rate that follows the class of supply, dated rate changes, a Jamaican payroll engine, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
A rate that knows what you are selling
The General Consumption Tax has a standard rate, a higher rate on telephone services and handsets, and a reduced effective rate in tourism. Our per-organization rate table can express a country, a region and a city — three columns of geography — and nothing about the class of supply, so a business outside the standard rate carries one correct default and sets the rest by hand on each line. The build is a dimension this data model does not have, and it is worth knowing it is not a Jamaican special case: the same missing column is what sub-national rates would need elsewhere, so it gets built once. Alongside it, rates that start on a date, for the tourism change announced for April 2027 and every one after it.
Banks, payments and counters that share a ledger
Statement feeds and local payment rails into the Payments Register, with retail counters, contract sales and invoicing posting to one set of books rather than three that get reconciled monthly.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
A Jamaican payroll engine with income tax tables, NIS and NHT computed on live employee records, producing the schedules in the layout the authority expects.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedDesign the count, not the counter
Who counts, who approves, how often, and which lines get counted more than once a year. Four decisions, one meeting, and the system supports all four once you have made them.
Plan the programmeFrequently asked questions
Who should approve count variances?
Not the counter, and the system will enforce that above your value threshold. Below it, the enforcement is your role design rather than the product, so set the threshold low enough that anything worth arguing about reaches a second person.
Can I count part of a warehouse?
Yes — sessions can be scoped and lines assigned to named people, which is what makes a rolling cycle count workable. What is missing is anything that decides for you which part to count, so the rotation is yours to design.
If nothing schedules a count, how do people run cycle counts?
By diary. Pick a day of the week, assign a slice, and make it somebody's standing job. The plan's frequency field records your intention and will not act on it, so treat it as documentation rather than as a commitment the system has made.
