Stock take software that will not scan your shelf and will not close the difference for you — no barcode, no RFID, no cycle-count scheduler, no automatic variance write-off
A count produces a number. The ledger produces another. The difference between them has to go somewhere, and where it goes is the entire question. NoxOrigin holds the adjustment as a record with a stated reason and a named owner. What is not here is a barcode-scanner integration, RFID, a cycle-count scheduling engine, or any automatic variance write-off — and the reason is not that they are unfinished. An adjustment that silently closes a variance hides the cause, and a variance written off by a rule hides it faster. Stock movement, purchasing and warehouses live in Commerce, and the stock take is the moment a person compares the shelf against that ledger on purpose.
Three products this name covers, and the one thing you get instead
A warehouse counting system, a stock control system, and a variance discipline. The first two are not in NoxOrigin in any form. The third is what the record gives you in their place, and it is worth being precise about the difference, because it is much smaller than the first two and genuinely useful.
The scanner and the tag
There is no barcode-scanner integration, no RFID integration, no device pairing, no scan-to-count mode and no scanner file import. A count in NoxOrigin is a number a person entered after looking at a shelf. That is a real limitation and it is better to have it stated here than discovered during your first stock take, because a count of forty thousand lines entered by hand is a different product from a scanned one.
The count scheduler
There is no cycle-count scheduling engine, no ABC classification, no rolling cadence, no count-due date and no count assignment queue. Nothing decides for you which line gets counted next, and nothing reminds you that a line is due. The reason is not that the feature is unfinished: which items deserve a count depends on value, velocity and risk, and encoding that judgement into a rule makes it look objective while it is not.
The automatic write-off
There is no automatic variance write-off, no tolerance band, no rounding of small differences and no rule that clears anything under a configured amount. This is the absence the rest of this page is built on. A variance closed without a reason is a loss that has stopped being visible, and a variance closed by a rule is the same loss repeated on a cadence nobody chose.
What there is instead: an expected figure, a counted figure, a difference, a reason and a name
The ledger quantity for the variant at the location, the quantity a person counted, the arithmetic difference between them, a stated reason, and the person who accepted the adjustment. Five things, held as records, so that the same cause can be recognised in the next count instead of being absorbed into a balance. That is a smaller product than a warehouse system and a different one, and it is the part that makes the next count more informative than the last.
A count routine where the difference has to be explained before it is accepted
Six steps. Step five is the one that separates this from a stock control product: the ledger moves because a named person accepted a stated reason, not because the system decided the difference was small enough to absorb.
Decide who counts and who signs, and write both names down
A count is an estimate made by a person, and a variance is a disagreement between two figures. If the person who counted is also the person who accepts the difference, there is no control in the record at all. Naming both is the cheapest control in this whole page and the only one that costs nothing to implement.
Freeze the movement you are counting against, and record that you did
Counting a shelf while the counter is selling from it produces a number that was never true at any moment. There is no freeze switch in NoxOrigin: stopping the counter, closing a till, or working to a location nobody is selling from is a decision a person makes and tells the team. Record what was stopped and when, because an unrecorded freeze is indistinguishable from an unrecorded sale.
Enter the counted quantity against the variant and the location
The count attaches to the same variant and stock location the ledger already holds, which is what makes the comparison possible at all. Where a unit of measure differs between the label and the system — a pack, a dozen, a kilogram — the conversion is a decision somebody makes once at setup. An unconverted unit of measure is the most common reason a variance appears on a line nobody touched.
Read the difference before you decide what it is
The count gives you an expected quantity, a counted quantity and a difference between them, and the difference has at least three ordinary causes: a movement that was never recorded, a receipt that arrived short, or goods that left without a document. It can also be an overage, which is just as informative — a receiving error or an unrecorded return both look like that. The arithmetic comes before the explanation, and the explanation is a person’s.
Record the variance with a reason and a named owner, and let the ledger move
This is the step the whole page is arguing for. The ledger quantity becomes the counted quantity because somebody accepted the difference and said why. Netting several lines into one adjustment is the tempting shortcut and it destroys the information: two lines with two different causes become one line with no cause, and the next count cannot do anything with it.
Read the repeated reason at the next count, and act on the cause
A cause that appears on every count is not a variance, it is a process, and the process is the thing to fix. The record is what makes that visible, because the same reason written down twice is findable and a mystery absorbed into a balance is not. This is also where purchasing and receiving enter, and those are Commerce records rather than things this page covers.
Two lines, 500 units, and a difference that nets down to one
Every figure in this section is constructed for this page so the arithmetic can be checked by hand. It is not a NoxOrigin result, not a customer’s record, and not a benchmark. The 18% GST appears only so the addition can be verified; it is not a tax position, and NoxOrigin does not file GST returns or any other statutory return. Nothing here is a shrinkage percentage, an inventory accuracy rate or an average variance, and this page publishes none of those.
The purchase, on a constructed unit cost of ₹25
500 units at 500 × 25 = ₹12,500. GST at 18% is 12,500 × 0.18 = ₹2,250, so the invoice total is 12,500 + 2,250 = ₹14,750. That invoice is a Commerce record, and it is not the same record as the payment for it — paid is a projection of allocations rather than a stored flag.
What the ledger believes is on the shelf
380 units of that line were sold at the counter, so the ledger holds 500 − 380 = 120 units. That figure is not a claim about the shelf. It is a record of what was received and what was invoiced, added together, and it is exactly as wrong as those two records are wrong.
The count, and the shortage nobody can explain yet
A person counts the shelf and finds 114 units. The variance is 120 − 114 = 6 units short, and at the same constructed ₹25 that is 6 × 25 = ₹150 of stock value the ledger claimed and the shelf does not have. At this point nobody knows whether it is a receiving error, an unrecorded movement, or goods that left without a document.
The overage on the next line, which is just as informative
The second line holds 60 on the ledger and 65 on the shelf, so the variance is 65 − 60 = 5 units over, worth 5 × 25 = ₹125. An overage is not the good news it feels like. It is an unrecorded receipt, a wrong unit conversion, or a return that was never documented — three causes, exactly as many as the shortage, and no cheaper to find.
What netting the two lines would have cost you
6 short and 5 over is a net 6 − 5 = 1 unit, or 1 × 25 = ₹25. That single figure is the reason a variance discipline exists. Netting replaced two different problems on two different lines with one number, discarded both causes, and left a ₹25 adjustment that explains nothing and cannot be learned from at the next count.
The two causes that were hiding inside the six
Four units were mis-picked at the counter and never recorded as a sale, and two units were damaged and discarded. 4 + 2 = 6, so the shortage is fully accounted for — and the mis-pick is a training and process problem while the damage is a handling problem. Written off as one line labelled shortage, both become the same loss forever, and neither gets fixed.
What the same cause costs across a year of counts
Four counts a year, the same 6 units short each time, is 6 × 4 = 24 units, which is 24 × 25 = ₹600 a year of value the ledger never had. This is a constructed illustration of a repeated cause rather than an estimate of your shrinkage, and it is the number a write-off rule would have absorbed silently. The rate at which it recurs is the diagnosis.
The supplier credit note, and the part that is your accountant’s
If the short delivery is the supplier’s fault, the credit note is 6 × 25 = ₹150 taxable, with GST at 18% of 150 × 0.18 = ₹27, so the credit total is 150 + 27 = ₹177. Checked the other way: 12,500 − 150 = 12,350, GST on that is 12,350 × 0.18 = ₹2,223, giving 12,350 + 2,223 = ₹14,573, and 14,750 − 177 = ₹14,573 — the same figure twice. How that correction should be treated in your books is a question for your chartered accountant, not a feature of this page.
The figure this page will not give you
There is no shrinkage percentage, no inventory accuracy rate, no average variance per line, no count accuracy benchmark and no count-frequency recommendation anywhere on this page. Each one would be a ratio against a chosen denominator, and the denominator is chosen after the result is known. Two quite different accuracy rates can describe the same stockroom in the same year depending on which lines and which periods were counted, which is why we will not print one here and let you assume yours would resemble it.
What was asked for, and the honest answer
If the first five rows apply to you, stop here and buy a warehouse management system. The rest is what NoxOrigin does with a difference somebody has explained.
| What a buyer asks for | In NoxOrigin |
|---|---|
| Count by scanning a barcode | No. There is no barcode-scanner integration, no RFID integration, no scan-to-count mode and no scan file import. A count is entered by the person who counted. |
| Schedule rolling or ABC cycle counts | No. No cycle-count scheduler, no classification, no count-due date and no assignment queue. The cadence is a written decision of yours. |
| Clear small variances automatically | No. There is no automatic variance write-off, no tolerance band and no rounding rule. An adjustment needs a stated reason and a named owner. |
| Diagnose why stock is missing | No. The record holds the expected figure, the counted figure, the difference, the reason and the owner. Finding the cause is a person’s work; the record only makes it answerable next time. |
| Report shrinkage against a target | No. There is no shrinkage percentage, no accuracy rate and no target to measure against, and this page publishes none. A ratio chosen after the result is known is an argument, not a measurement. |
| Hold stock movement, purchasing and warehouses | Yes, in Commerce. Variants, units, locations, receiving, transfers, returns, sales-linked deduction and low-stock comparison are all Commerce records. |
| Compare the shelf against the ledger on demand | Yes. An expected quantity, a counted quantity, the difference and an adjustable ledger figure, with the reason and the person who accepted it held on the record. |
| Separate a short delivery from an internal loss | Yes, as a person’s decision. A supplier short-delivery becomes a credit note against that purchase; an internal loss has no document that explains it, which is why the reason field is the control. |
| Handle a scope change attached to a stock arrangement | As a new quote on the same project. There is no change-request record, no milestone or deliverable record, no contract editor and no e-signature, and the first quote is never overwritten. |
| Post the variance to the statutory books | No. NoxOrigin does not file GST returns or any other statutory return and does not determine how a write-off or a correction should be treated. That is your chartered accountant’s call. |
Where this is the wrong tool
Stock take software is judged by what it refuses to imply. The list below is the set of things a reader is most likely to assume are present because the page title sounds like they are.
If you need to scan a shelf, this is the wrong product
No barcode-scanner integration, no RFID, no scan-to-count mode and no imported scan file. Buy the warehouse product where the hardware is the record. This page is worth thirty seconds to you if that sentence applies, and we would rather you spend the rest of your evaluation on the right tool.
Nothing here decides what to count next
No cycle-count scheduler, no ABC classification, no count-due date and no assignment queue. The cadence is a written rule of yours, held as a decision, and the system holds the results.
Nothing here closes a difference without a name attached
No automatic variance write-off, no tolerance band, no rounding and no rule that clears small differences. The system that can make a variance disappear on its own is making a different problem disappear, and the same cause returns next quarter as a new loss.
This is not a tax product and it does not post to your books
NoxOrigin does not file GST returns or any other statutory return, does not run a stock ledger to the statutory standard, and does not determine how a short delivery, a damaged receipt or a write-off should be treated. That belongs to your chartered accountant. The 18% used on this page is arithmetic, present so the example can be verified by hand.
Merge is a setup decision, and nothing merges automatically
Duplicate detection flags candidate pairs and a person reviews them. Two records for one customer or one variant split the counted, invoiced and collected figures exactly as thoroughly as they split the record, so the merge policy has to be agreed at setup rather than assumed to be running.
Shift close and day-end reconciliation are assisted-setup maturity
They are not switches you flip in an afternoon. A counter that has not been reconciled through that conversation is producing new numbers rather than correct ones, and the /day-end-business-reporting-software page is the same boundary seen from the cash side.
An invoice and a payment are different records, and paid is a projection
Money received reduces nothing until a person allocates it to an invoice. Paid is derived from allocations rather than stored as a flag, which is why a large received-but-unallocated amount is worth chasing on the day it lands, and why an outstanding figure from an unmanaged allocation queue cannot be trusted.
Run counts and accepted differences on the plan that matches your customer count
Growth is ₹1,600/month or ₹15,000/year, includes a 30-day trial, 10 users, 50 active projects, and 10,000 contacts. Say this plainly rather than let it be assumed: these are NoxOrigin platform plans. NoxCRM, Nox-Billings and Nox-Tickets are scoped custom deployments, quoted and priced separately against your own configuration, and the platform plan price never applies to any of them. Stock, purchasing and warehouses are Commerce work, so if what you need is a scan-driven count or a rolling count programme, say so in the conversation — that is a different product conversation, not a plan question.
Stock take questions, answered before you buy
Does NoxOrigin integrate with a barcode scanner?
No. There is no barcode-scanner integration, no RFID integration, no hardware pairing, no scan-to-count mode and no scanned-file import. A stock take is counted by a person and entered by that person. The count is a number a human put on the system, and the record cannot claim more authority than the person who counted. If scanning a shelf is the reason you are reading this page, a warehouse management product is the correct category, and no plan on this site adds the hardware integration to you.
Does it schedule cycle counts?
No. There is no cycle-count scheduler, no ABC classification, no rolling count cadence, no next-count-due date and no count assignment queue. Nothing in NoxOrigin will tell you that a particular item is due for a count, because the rule that decides which item is due is a judgement about risk and value that a person makes. What the record does give you is that the count you did, the count the ledger expected, the reason for the difference, and the name of the person who accepted it are all readable afterwards.
Will it write off the variance automatically?
No, and this is the single most important refusal on this page. There is no automatic variance write-off, no tolerance threshold, no small-difference rule and no rule that absorbs anything below a configured amount. An adjustment that silently closes a variance hides the cause, and a variance written off by a rule hides it faster and at scale. Recording the difference with a named owner is the control. Any system which can make the difference disappear on its own is solving a different problem, and the cause will reappear in the next count as a new surprise.
Where do stock movement, purchasing and warehouses actually live?
In Commerce, not in a stock-take tool and not in the billing counter by accident. Variants, units, stock locations, receiving, sales-linked deduction, returns, transfers between locations, low-stock comparison and purchasing are all Commerce records. The stock take and its adjustment is the moment a person compares the shelf against that ledger and puts the difference somewhere on purpose. The /inventory-billing-software page covers the billing-counter side of the same ledger and /stock-reorder-and-low-stock-software covers the reorder comparison.
My stock keeps going missing. Can this find out why?
It can hold the evidence and stop the question from being unanswerable next time, but it cannot diagnose the cause for you. A variance of six units and a variance of one thousand units look identical in structure: an expected figure, a counted figure, a difference, a reason and an owner. The reason is the only diagnostic input in the system, and it has to be a person writing it. This page publishes no shrinkage percentage, no inventory accuracy rate and no benchmark for either, because each of those is a number about somebody else's stock and not yours.
Is this included in the platform plan price?
The plan prices on this page are NoxOrigin platform plans. NoxCRM, Nox-Billings and Nox-Tickets are scoped custom deployments, quoted and priced separately against your own configuration, and the platform plan price never applies to any of them. The stock area, purchasing, warehouses and low-stock signals are Commerce work, so if your requirement is a stock-take and variance routine, say so in the conversation rather than assuming a plan price covers it.
What about a scope change or a contract attached to a stock item?
There is no change-request record, no milestone record and no deliverable record, no contract editor and no e-signature anywhere in NoxOrigin. If a stock arrangement is a scope change on a project, it is a new quote on the same project with its own lines and total, and the original quote is never overwritten. Stock quantity itself is a Commerce record and does not need a contract to exist for the number to be right.
Can it link a stock item to a purchase, an invoice and a payment?
A purchase in Commerce produces an invoice, and an invoice and a payment are different records: paid is a projection of allocations rather than a stored flag, so money received without an allocation has not reduced anything yet. What links a stock variance to money is a person’s decision about whether the cause is a supplier short-delivery, in which case it is a credit note against that supplier and a question for your chartered accountant about how it is treated, or an internal loss, in which case no document fixes it and only the reason does. NoxOrigin does not file GST returns or any other statutory return.
Tell us whether you need to scan the shelf.
If you do, we will say so before you spend any more of your time here, because NoxOrigin has no barcode integration, no RFID, no cycle-count scheduler and no automatic variance write-off, and no plan on this site changes that. What it does have is the discipline the difference actually needs: an expected figure, a counted figure, a stated reason, and a person’s name against it — so that the cause of the last count is still readable at the next one.