Insights · Order intake

How to get LINE orders into your ERP

Three ways to stop retyping LINE orders into SAP Business One, Odoo or your accounting software, with a person still checking.

To get LINE orders into your ERP without retyping, first move orders to a LINE Official Account your company controls, then either give regular customers a short order form or use an AI reader that proposes order lines for a person to approve, and finally create the approved order in the ERP through its supported interface.

Why orders arrive in chat in the first place

In Thailand, LINE is where business conversations already happen. A restaurant owner orders the same way they message a friend: a quick text between services, a photo of a handwritten list, sometimes a voice note. Asking them to log in to a portal usually fails, because the portal is slower than the chat and the customer does not see why they should change.

So the order arrives in one of three places: a salesperson's personal LINE, a shared group with the customer, or the company's LINE Official Account. From there, someone on the order desk reads it and types it into the ERP. That is the step to fix. The customer's habit is not.

What retyping actually costs

You do not need a study to see the cost; you need one honest morning at the order desk. Watch for:

  • Time: every order is read, interpreted and typed again, line by line.
  • Errors: "2 ลัง" becomes 2 units instead of 2 cases; a product nickname maps to the wrong code.
  • Lost orders: a message in a rep's personal chat is seen late, or not at all, when that rep is on leave.
  • No history: the original message and the ERP order are never linked, so a dispute means scrolling through chats.

Count those for a week, on your own orders. That count, not an industry average, is the business case.

Step 1: move orders to a channel the company owns

Before any technology, decide where orders should arrive. If customers send orders to reps' personal accounts, the company does not own the conversation, cannot see it when the rep is away, and cannot connect it to any system.

A LINE Official Account solves that. It is the business version of LINE: several staff can answer from it, and messages sent to it can be received by your own software through LINE's Messaging API. Messages in personal LINE accounts cannot be read by software in a supported way, and you should not try. Check LINE's current terms and message pricing for your plan before you design around it.

Step 2: choose one of three ways in

There is no single right answer. It depends on how many orders you get and how regular your customers are. Most distributors end up using two of these at once.

Option A: a standard order message or form

For regular customers who order the same products, send them a short order form (a link from the LINE Official Account) with their usual products already listed. They change quantities and send. The form writes a clean order straight into your system. It is cheap, very accurate and works well for repeat business. It fails for customers who will never open a form.

Option B: an AI reader with a person approving

For free-form messages, an AI model reads the message (Thai, English or both, plus product nicknames) and proposes order lines: customer, product, quantity, unit, delivery date. It matches products against your own product list. A person on the order desk sees the original message next to the proposed lines, corrects anything wrong, and approves. Only approved orders move on.

This keeps the customer's habit intact and removes most of the typing. It does not remove the person, and it should not: the person is what makes it safe. Test it on a sample of your real past messages before committing, and look at the cases it gets wrong, not only the ones it gets right.

Option C: an order tool that writes to the ERP

Whether the order came from a form or from the AI reader, it has to reach the ERP. That last step is an integration: the approved order is created in SAP Business One, Odoo or your accounting software through its supported interface (an API where there is one, or an import file where there is not). Do this once, properly, and every channel benefits.

Step 3: keep the link between message and order

Whichever route you choose, store the original message, the person who approved it and the ERP order number together. When a customer says "I ordered five, not three", you open the order and see their message beside it. This one design choice ends a surprising number of arguments.

Mistakes to avoid

  • Automating before standardising. If every customer uses a different word for the same product, write the product nicknames list first. The AI reader will use it too.
  • Letting AI write straight to the ERP. Always keep a person approving, at least until you have measured the error rate on your own orders for a good while.
  • Building on personal accounts. Anything built around a rep's personal LINE breaks the day that rep leaves.
  • Replacing the ERP to fix intake. Order intake is a problem in front of the ERP. A new ERP will receive the same messy messages.
  • Forgetting the data question. Know which AI provider reads your customers' messages, where the data goes and whether it is used for training. Ask before you sign.

A sensible first month

  1. Week 1: watch the order desk, count retyping and errors, and collect a sample of real messages.
  2. Week 2: set up or tidy the LINE Official Account and write the product nickname list.
  3. Weeks 3–4: try a form for your top regular customers, and test an AI reader on the sample of past messages, with a person approving.

At the end you know, on your own data, how much typing each option removes and how often it needs correcting. Then decide what to connect to the ERP.

Where this fits: this guide connects to AI implementation and ERP integration. Also see software for distributors and importers.

FAQ

Questions readers ask

Can software read orders from my sales reps' personal LINE chats?

Not in a supported way. Software can receive messages sent to a LINE Official Account through LINE's Messaging API. Personal accounts are not designed for that, and building on them breaks when a rep leaves.

Does AI understand Thai order messages?

Modern models handle Thai, English and mixed messages, but product nicknames and units are specific to your business. Test on your own past messages, and keep a person approving.

Do we need a new ERP to do this?

No. Order intake sits in front of the ERP. The approved order is created in the ERP you already run, through its API or an import file.

How long does it take to set up?

A form for regular customers can be live in a few weeks. An AI reader needs a test on your real messages first; plan for a diagnosis of one to two weeks before committing to a build.

Contact

Send us ten real LINE orders.

We'll show you what a form or an AI reader would do with them, and what it would get wrong, on a 30-minute call.

We reply within one working day, Bangkok time (GMT+7).

30 minutes, no deck.

Book a 30-min call