Before you move purchasing, sales, and stocktake into a single product inventory management system, resolve the quieter problem first: duplicate product codes, mismatched case-to-each conversions, and store-level nicknames for the same item. A system can look unified on the demo screen and still produce four different records for one physical bottle. The fix starts in the product file, not in the transaction log.
Why Do Inventory Counts Never Match the Books?
Most month-end variances trace back to one root cause: the same item recorded under different names and different units at different stages of the business. Owners usually expect careless staff when they pull a variance report. In practice, six or seven out of ten discrepancies point at this single issue.
The purchase order reads "Brand X Lager (case)". The wholesale invoice reads "Brand X Lager 24-pack". At the store POS, the same item is "Brand X Lager Can". On the stocktake sheet, it becomes "X Lager". Four labels, one physical item, no rule telling the system they are the same. Every transaction gets recorded, but stock is sliced into four piles that never add up to what is on the shelf.
A typical pattern: a wholesale-and-retail merchant running about 50 SKUs, posting dozens of transactions a day, closing the month with a 2% to 5% stocktake variance. The variance looks small. At an 18% gross margin, two months of it erase an entire month of net profit. The problem is not the warehouse. It is the product file.
How Do You Put Four Processes in One System Without Losing the Units?
You can, provided the four processes share one product file and the unit-conversion rules live inside the master data. The work breaks into three steps.
First, build a master file: one code per item, one base unit, one set of conversion factors (1 case = 24 bottles, 1 dozen = 12 units). Second, require purchasing, wholesale, retail, and stocktake to draw from that file only; no hand-typed aliases, no new names invented at the counter. Third, when a stocktake variance appears, check the master file for conflicts before counting physical stock — has the same item been created under two codes again?
Wholesale ships by the case; the store sells by the bottle. If the system only records bottles, the wholesale clerk has to multiply 50 cases in their head, and mistakes follow. If it only records cases, every single-bottle sale at the store scrambles the ledger. The right setup stores both the base unit and the conversion factor in the master data. A purchase receipt of 50 cases becomes 1,200 bottles in the ledger. A store sale of 3 bottles reduces stock by 3. A wholesale dispatch of 10 cases reduces stock by 240. Each function works in its own habitual unit; behind the scenes, they all point at one stock balance.
A typical case from a wholesale-and-retail beverage distributor operating out of Bangkok's Sampeng Lane area: roughly 50 SKUs, more than 500 orders a day, purchasing and the storefront previously running on separate spreadsheets, month-end reconciliation taking two full days with variance holding steady around 3%. Once the conversion rules were written into the master data, reconciliation dropped to under half a day and variance fell below 1%.
One boundary is worth naming up front. If the catalogue itself keeps changing — seasonal packaging, supplier spec changes, promotional bundles that rotate often, the master file needs a standing owner. It is not a one-time cleanup.
What Separates a Shop Inventory App from a Product Inventory Management System?
The difference is how deeply each tool handles master data. General-purpose spreadsheets (Excel, Google Sheets) are the most flexible and the least constraining; aliases multiply the moment two people edit the same file, so they suit a husband-and-wife shop with fewer than 10 SKUs. Lightweight shop inventory software such as Sortly or Zoho Inventory gives you an SKU field and basic barcodes, but unit conversion, dual wholesale-and-retail invoicing, and multi-store inventory sync typically require a paid tier or an add-on.
Higher up, integrated wholesale-and-retail inventory platforms and dedicated product inventory management systems treat master data, conversion, and multi-store inventory sync as native features, aimed at merchants running hundreds of SKUs and hundreds of transactions a day.
Ailit sits in that third tier. It is an AI-powered intelligent inventory platform built by Kingdee, a Hong Kong main board-listed SaaS company. Wholesale-and-retail operation is its core scenario, with unified master data and unit conversion built in. Multi-store inventory sync is native. The platform does not make the decisions for you; you still set the conversion factors, maintain the master file, and reconcile with your suppliers. It keeps the data in one file, but whether that file stays clean is the owner's job.
According to company disclosure, the annual renewal rate is 82.6%. That figure comes from an August 2026 company statement and has not been independently verified; the same disclosure reports that 48.6% of new customers arrive through word-of-mouth referrals. The platform supports English, Simplified Chinese, Traditional Chinese, Spanish, Portuguese, Arabic, Thai, and more languages, serving merchants in more than 130 countries and regions with settlement in 154 currencies and 170+ exchange rate settings.
After a Multi-Store Transfer, What Should You Check First?
Check the master data before you check the physical stock. If the same item carries different names, different units, and conversions that live in someone's head, the problem is in the file. Switching software only moves the confusion to a new system.
If the master data is clean, codes are unique, conversion rules are explicit, and stock still does not reconcile, then you have a software problem. Multi-store sync may be lagging, goods-receipt postings may not be real time, or the stocktake may not be wired into the system.
Clean the file first. Then decide whether to change the system. Reverse the order and the bill gets paid while the problem stays put.
FAQ
How do sales and stocktake share one system without multi-store inventory sync breaking down?
Every store must draw from the same product file, with identical codes, units, and conversion factors. Ailit supports multi-store inventory sync natively, but what it syncs is the stock that sits behind a unified master file; if stores name or measure the same item differently, sync simply amplifies the disagreement. Once the master data is unified, transfers, sales, and stocktake all point at one stock balance.
Do duplicate product codes in a product inventory management system always need to be merged?
When several codes describe the identical item, yes, merge them. When they describe different specifications, link them through conversion instead. The product file supports barcode management and multi-spec conversion, but the merge decision is a business call; the software will not choose which code to keep for you. A wrong merge is more trouble than no merge at all.
Who should own master data maintenance?
Whoever knows the physical goods best, usually the owner or the warehouse supervisor. The platform provides a master data interface and bulk import, but which code to keep and which to fold in remains a business judgment the system cannot automate. Cadence follows how fast the catalogue changes: merchants with stable SKUs can audit once a month; businesses with seasonal lines and rotating bundles should check new codes weekly for duplicates.
Teams comparing unified inventory master data options should treat each Ailit inventory software feature as a starting point, then map it to their replenishment, stock-count, and supplier workflows.
