Field notes from the Cambodian software ground.

What a scan actually changes, which symbology each item needs, why KHQR is not a product barcode, and what has to happen when the signal drops in the middle of a count.

Lot numbers, expiry dates and serial numbers are three different records answering three different questions. This is what each one has to hold, what a recall demands from them, and why the moment of goods receipt decides all of it.

Your stocktake came back wrong and nobody can say why. Counting a few lines at a time, all year, is how you get an answer while the pallet is still remembered.

A distributor counts one thing. A plant counts four, and one of them is not legally yours to sell yet. This is what changes in the stock model when the floor is a cutting room.

What a third-party warehouse needs that an owner-operated one does not: owner stamped on every movement, one record behind both the stock and the invoice, and an exit that is an export.

A stock migration is a cleaning job, not an import job. The import runs in an afternoon. What fills the calendar is deciding which of three rows is the real product, and explaining every difference between what a line cost and what was counted.

Half of these words reach a Cambodian business through an English system nobody translated, and the other half through whoever trained the last warehouse manager. When the two do not line up, a stock meeting spends twenty minutes agreeing what a word means before it can discuss a number.

A CRM records every touch on a deal as a dated row. What that means, the Monday a Telegram thread and an Excel sheet stop being enough, and how a sales team gets off the sheet.

In Cambodia the deal arrives in a chat, not on a form. What a bot or a Page inbox connection captures, why the phone number is the key, who owns the handle when a rep leaves, and what to ask a vendor.

Eight CRM tools, read off their own pages on one date and held to the seven questions a Cambodian sales team actually has.

A rep on a provincial route writes the visit in the customer's shop, signal or not. What the phone has to hold, what syncs each way, and what the office actually sees.

What a won deal carries into the order and the invoice, what the CRM never writes, and how a quote in dollars reaches a VAT return in riel.

A vendor-by-vendor read of what is actually sold in Cambodia, what it costs where anyone will say, and where each one is genuinely the right answer.

Cambodian shops price in dollars and give change in riel. Here is why, and what it demands of the software behind the counter.

Not the power. The signal. What a half-finished KHQR payment does to your sales record, and what to test before you buy.

Enterprise resource planning, explained for the Cambodian market: what an ERP system is, why local compliance changes the decision, which platforms fit, what they cost, and how to choose the right one, with links to every detail.

Human resource and payroll systems, judged against what Cambodian compliance actually demands: Tax on Salary, NSSF, seniority-payment indemnity, Labour Law leave, KHR/USD pay, and Khmer payslips. Which platforms fit, what they cost, and how to choose.

What GDT e-VAT is, who must file, how a system prepares the monthly return, what CamInvoice changes, and the pitfalls that catch Cambodian businesses off-guard.

What CamInvoice is, who needs it first, how the adapter works, what it costs, and the pitfalls that catch teams off-guard at go-live.

A 25-point self-assessment checklist for Cambodia SMBs to measure GDT readiness before an audit, a vendor selection, or an internal compliance review.

Why QuickBooks hits the wall for Cambodian SMBs, what a migration off it actually covers, and how to land the cutover without breaking GDT compliance.

Why Cambodian businesses are moving off Peachtree, what makes it harder than QuickBooks migrations, and how to get off it cleanly.

Source-code ownership, GDT compliance, escape clauses, hidden per-user fees: the contract traps that cost Cambodian SMBs millions of riel.

What a Cambodia ERP project actually takes: phase by phase, week by week, with the KH-specific delays that vendor timelines never include.