Is importing Excel into SQL or AutoCount the best way?
Excel import is good for one big batch with fixed columns, such as opening balances. For daily orders it still needs someone to build the Excel first, so the typing has only moved. A better fix is to take the order where it arrives, on WhatsApp, and check it once before it is recorded.
Where Excel import works
Opening balances, a price list, or a month of identical rows. The columns are fixed, the codes match, and you run it once.
Where it stops helping
Orders arrive on WhatsApp in different shapes. Someone reads each one, finds the customer and item codes, and types them into a sheet. One wrong code and the import fails or books the wrong item.
Take the order at the source
If the order is read when it arrives, matched to your customer and items, and shown to the approver as a preview, the sheet step disappears. The approver checks one preview instead of a hundred cells.
How Lucco does it
Lucco Boss does this today for its own invoices: you say it on WhatsApp, check the preview and reply 1. Writing the same orders into SQL Account or AutoCount is being built for wholesale and factories, with the first 1 to 2 companies installed from mid December. Want to see the order to receipt flow? WhatsApp 011-2922 2627 and send: Try invoicing. It takes 30 seconds, the demo data is made up and it clears itself after 24 hours.
Questions bosses ask
Do I have to stop using Excel?
No. Keep Excel for what it does well. The aim is that nobody types each WhatsApp order into it.
Is the SQL and AutoCount link live?
Not yet. Orders and invoices on WhatsApp work in Lucco Boss today, and the link into your software is being built.
Updated · Lucco Technology
