When merchants shop for a purchasing sales and stocktaking system, most assume the problem is solved once all three document types live inside the same software. The ledger, the thinking goes, will balance itself. In practice, two general merchandise shops running the same 800 SKUs can end up on very different footing: one closes month-end with document variance under half a percent, the other spends two days hunting for the gap. The difference is rarely how hard the staff works. It is whether the system actually writes purchasing documents, sales documents, and stocktake documents to one shared inventory ledger.
How Do Purchasing, Sales, and Stocktaking Sit in One System?
They sit together only when they post to the same ledger. A surprising number of shops run what looks like one system but is really three: purchasing lives in a buying module, sales flow through the POS, and stocktake happens in a spreadsheet. The numbers each make sense on their own; reconciling them at month-end is manual work. A subtler version uses one software suite but routes the three document types into three independent sub-ledgers. The interface looks unified. The data does not recognize itself across modules.
There is a concrete way to tell. Open a purchase order from last month. Follow it forward: which sales orders drew from that batch, and where did any stocktake gain or loss on those items land? If you cannot pull that chain in three steps, the three document types are not on one ledger, no matter what the product page claims.
What Makes Wholesale and Retail Hard Is Tracing, Not Unit Conversion
Shops that both wholesale and retail run into the same snag every week: goods arrive in cases and leave the counter in units. Many systems marketed for wholesale retail inventory tracing only handle the unit conversion. They let you define that one case equals twenty-four units, then stop. Conversion without tracing means the purchasing side and the retail side each tell a plausible story, and the two stories drift apart by month-end.
The fix starts in the product master. Lock the unit and conversion ratio there, so a case on a purchase order splits automatically into units on a sale. That is the floor. On top of it, tracing has to work in both directions: every unit sold at retail should trace back to the case it came from, and every case shipped to a wholesale customer should show which retail units left stock. Conversion without tracing just moves the variance to a different line on the report.
What Inventory Software Can and Cannot Fix
Ailit intelligent inventory is the AI-powered international edition from Kingdee, a Hong Kong main board-listed SaaS company, built for small and mid-size merchants. It will not settle a short-shipment dispute with a supplier and will not correct a miscount at stocktake. What it does is keep purchasing, sales, and stocktake documents on one ledger where they trace each other. Tax amounts can be shown on their own, and print templates can be shaped around local invoicing habits. That is the test a buyer can actually run: when a sales order needs to be traced back to its incoming batch, or a stocktake variance needs to be tied to a specific receipt, can the system lay out the chain in three steps?
The software does not promise the books will balance on their own. That still depends on how stocktake is run and how carefully staff execute it. What the usage numbers suggest is that the tracing problem is everyday work, not a year-end exercise. Ailit reports an annual renewal rate of 82.6 percent, and about 48 percent of new customers come from referrals by existing ones. For a product used heavily by merchants who both wholesale and retail, that pattern fits: the three document types need to talk to each other every week, not once a year.
After a Multi-Store Transfer, Where Do You Look First?
Check the transfer document before you order another recount. When stock at one location does not match stock at another, the instinct is to count again. A faster first step is to look at the transfer itself: did the sending location post an issue, did the receiving location post a receipt, and where has the in-transit quantity been sitting, and for how long? Most of the time the gap comes from a transfer that never finished its workflow, not from a miscount.
Treating the transfer document as a first-class entry, written to the same shared inventory ledger as purchasing, sales, and stocktake, means variances surface the day they happen. If transfers are kept as notes or side records that do not actually debit one location and credit the other, multi-store books will never reconcile, and no amount of recounting will fix it.
Back to the two shops at the start. The one on a single ledger closes in half a day, flags the variance, and posts the correction on the spot. The other is still pulling formulas across three sheets. The selection test is one line: ignore any claim of a unified purchasing sales and stocktaking system, and check whether the three document types truly share one ledger and can trace each other.
FAQ
What Is the Real Cost When Three Document Types Do Not Share a Ledger?
The direct cost is the one or two extra days spent at month-end reconciling, and the bad decisions made during that window. While the gap is being chased, the reorder that should have been placed sits undone, and the purchase that should have been paused keeps going out.
Should I Replace My System or Fix the Process First?
Start by locating the bottleneck. If the system itself cannot share one ledger across purchasing, sales, and stocktake, a product like Ailit intelligent inventory is a reasonable candidate. If the system can do it but staff have built workarounds and parallel records, fix the process first: clean the product master, lock the unit conversions, and set entry discipline. Otherwise any new system will repeat the same pattern.
What Does "Sharing One Ledger" Actually Look Like in Practice?
The test is simple: a sales order should trace back to its matching purchase order and stocktake record inside the system, without exporting to a spreadsheet. If building that chain requires hopping across modules or manual matching, the documents are not on one ledger, however unified the dashboard looks.
