In September, a shop owner posted about a late night on Reddit's r/smallbusiness. Their in-store point-of-sale (POS) system was "pretty legacy", and the vendor had finally opened a way to grab "non secured emails" from a mailbox. They had put the job off for two months. Then: "last night I stayed up for a couple of hours with Claude and low and behold it wrote a small plugin." By the next day they had "automated away hours and hours of manual typing!"
That's one owner's word, and they already run WooCommerce stores. Our answer: you can connect a POS system to an online store yourself, using an AI assistant, when the job runs one way, between two systems, and nothing breaks if it runs late. Live stock across Shopee, Lazada and the counter needs a team.
The Malaysian version: the same sale, typed twice
Illustrative: one counter sale, three screens.
Picture a shop selling at the counter and on Shopee. Each counter sale gets keyed into Shopee stock and the accountant's spreadsheet by hand. It's what the part-timer does after 9pm.
The Reddit owner assumed the fix meant a developer bill: "You realize developers would charge me thousands to set this up." We suspect that belief keeps many shops retyping.
Why this one worked
As we read it, the job passed all three tests. Data left the old POS by email, and the post mentions nothing going back in. It joined just two systems. And records that arrive an hour late are annoying, not costly.
It's an odd thing for a software house to write, but a job like that is DIY work now, if you're at home in your store's back end. Like the Hokkaido farmer who built his own farm tools, you decide what to build and the AI writes the code.
Paste this into Claude or ChatGPT and fill in the brackets:
My staff copy [sales] from my cashier system [name] into [Shopee / my web store] by hand.
The cashier system can export [email / CSV / not sure].
Ask me questions until you understand the job. Then tell me if I can automate it
myself, the simplest way, and what could go wrong. No code until I agree.
Test on a copy of your data, and keep typing by hand until the numbers match.
When connecting a POS system to an online store gets hard
| The job | Try it yourself? |
|---|---|
| Copy counter sales into one store or spreadsheet | Yes. One way, two systems, fine if late |
| Same stock on Shopee, Lazada and the counter | No. Late updates sell what you don't have |
| Payments or LHDN e-invoices | No. Errors cost money or compliance |
| A POS with no export at all | Usually no. Getting data out is the job |
| Customer names, phones, addresses | Get help. PDPA applies |
Syncing your POS stock with Shopee, Lazada and your online store is harder than it looks. Each sale must reach every channel fast, and two buyers can grab the last item at once.
Customer data is the quiet trap. Since 1 June 2025, Malaysia's amended PDPA requires businesses to report a personal data breach likely to cause significant harm to the Personal Data Protection Commissioner, within 72 hours under its guideline. Leave phone numbers out of your first script.
That harder work is what we take on. For one distributor, we built a prototype that reads WhatsApp orders, prices each line against a daily feed from their back-office system, and sends any below-list price to a person for approval. It's a prototype with no results to quote yet, but that's the harder job: money on the line, and a person who signs off.
What to do this week
List every place your staff type the same data twice. Pick one that runs one way, between two systems, and does no harm if late. Try that one yourself.
Anything that looks like the table's bottom four rows is custom software work we do. Send us your list and we'll say honestly which ones you can do yourself.
This is general information, not legal advice.
