Selling Vegetables Online: What Your Product Page Should Tell Customers So They Still Buy When Food Safety News Breaks

Think about your regular vegetable seller at the morning market. She remembers that your family likes young morning glory tips, she knows you come by every Saturday, and on a day when the greens from one farm don't look good, she tells you straight: "Take the ones from the other farm today, this batch isn't great." So you buy from her every time, without standing there turning over every bunch.

That kind of trust doesn't come from having the cheapest prices in the market. It comes from two small things: she knows where her stock comes from, and she remembers who bought what.

In late October 2026, a story went around that Thailand's National Food Institute had found Listeria in raw enoki mushrooms. If you go back to the source, the National Food Institute's article on pathogens in raw enoki mushrooms says it collected 5 samples of raw enoki from 4 brands on sale in Bangkok, and found Listeria monocytogenes in all 5. The institute's article list gives the publication date as 19 April 2024. So this round of news was an older result being shared again, and 5 samples are far too few to say how widespread contamination in the market really is.

But if you sell vegetables or mushrooms online, the customers typing into your chat that day don't care about sample sizes. They just want to know, "Where does this shop's stock come from, and what about the pack I bought yesterday?" In this article I'll walk through how your product pages and your back office can answer those two questions. For food safety itself, please treat the National Food Institute and the Thai FDA as the authority. We're a web team, not food safety experts.

Answer these 3 questions first. It takes under 3 minutes

Say tomorrow there's news about something your shop sells. It doesn't have to be mushrooms. It could be salad greens, bean sprouts or cut fruit. Answer yourself honestly.

Question one. If a customer asks which farm their batch came from and what day it arrived at your shop, can you answer within five minutes, or do you have to dig through delivery slips in a box?

Question two. If you wanted to message only the customers who bought that product in the past week, do you know who they are and how to reach them?

Question three. When a new customer who just saw the news visits your shop for the first time, what will they find on the product page that makes them confident enough to order?

If you can answer all three, your shop is better prepared than most. If you're stuck on even one, the rest of this article was written for you.

A good product page does the regular seller's job

At a market stall, customers can ask the seller on the spot. On a web page, they can only read what you've written. So the product page has to answer the questions customers will ask before they ask them.

Say where it comes from, clearly enough to check

"Fresh from the farm" sounds nice, but a customer can't check anything with it. Try the actual province or farm name you buy from instead. If it's imported, say the country of origin. If the farm holds a standard like GAP or Organic Thailand, include that too. You already have this information on your delivery slips. You've just never put it on the web page.

Show the date received or the lot number

Fresh produce changes batch every few days. Showing the date it arrived at your shop, or the lot number currently on sale, helps customers in two ways. They know how fresh it is, and if a particular batch ever has a problem, you and your customers are speaking the same language. Nobody has to guess which batch "the one I bought early in the month" was.

Give storage and cooking guidance, and point to the source

Some products people like to eat raw or only blanch for a moment, and enoki in a shabu pot is a good example. The product page is the best place to tell customers how to store it and that it should be cooked before eating. But take the temperature and time figures from the agency that issued the advice, and link to the original. Don't write numbers from memory. Even the news reports about enoki this time quoted a temperature that didn't match the National Food Institute's own page.

Say how you'll contact customers if there's a problem

A short line such as "If any batch has a problem, we will notify every customer who ordered that batch by LINE and email on the same day" tells customers someone is looking after them. But only write it if your back office can actually do it, which brings us to the part customers never see.

The part customers can't see, but matters most on the day of the news

A market seller remembers customers from memory. An online shop with dozens of orders a day can't do that. What replaces memory is linking three things together at the moment you pack: the order number, which lot each item in that order came from, and the contact channel the customer has agreed you can use.

When those three live together, on the day you need to send a notice, you just search "who received lot 1027" and get the list in seconds. You message only that group, without announcing it across your whole page and alarming customers who aren't affected.

When those three are scattered, with orders in chat, delivery slips in a box and customer lists on each admin's phone, answering that one question can take all day. And by then the news has moved faster than you.

This doesn't need to be complicated. For a small shop, just having a field where the packer picks the lot number when confirming shipment is enough to start building up the data.

What should the customer message look like?

Many shops know they should notify customers, but when the day comes they sit typing for ages, afraid of saying the wrong thing. They worry about frightening customers more than necessary, and they worry about looking like they're hiding something. It's much better to prepare a message template on a day when nothing is happening.

A good message usually covers four things in a few lines. It opens by saying clearly which product, which lot and which delivery date it's about, so customers can compare with what's in their fridge right away. Then it says what happened, based on what the shop actually knows at that point. If you don't know yet, say you don't know yet and are checking. Next comes what the shop will do, such as a refund or sending a replacement from a new batch. It closes by pointing to the advice of the relevant authority, instead of the shop writing its own health advice.

An opening line you could use: "To customers who ordered enoki mushrooms from lot 1027, delivered on 27 October, we wanted to let you know first." That one sentence tells customers immediately that this message really concerns them, and customers who didn't get a message don't need to worry. It's only possible because the shop linked lots to orders from the start.

An example from a real recall notice

To see why lot information matters, look at a notice from the United States. On 14 May 2026, the US Food and Drug Administration (FDA) published a recall of 150-gram enoki mushroom packs from HH Fresh Trading, 120 cases distributed to wholesalers in Texas and Florida, after a Florida Health Department lab found Listeria monocytogenes. The notice said no illnesses had been reported.

What's worth noticing is how the notice tells consumers whether their product is affected. It gives a product code but no lot number, and what consumers can do is take the product back to where they bought it for a refund. That means the only people who will realise are the ones who happen to see the notice and still have the bag to check the code.

Now picture an online shop that sold that same batch. If the shop had linked orders to lots, it would know immediately who received it and could contact them before they had to find the news themselves. That's the regular market seller, online.

"I already sell fine through LINE and my page"

That genuinely works, and I'm not arguing with it. Plenty of online vegetable shops grew entirely from chat. Customers are used to it, admins reply quickly, and sales close well.

What chat wasn't designed to do is structured searching back through history. If all your orders live in chat, a question like "who ordered mushrooms this month" means someone reading through every conversation, and the more admins you have, the harder it gets. A shop website with its own ordering system doesn't replace chat. It keeps the data chat can't keep for you. Customers can still message you just as before. The order simply ends up in a system you can search. If you want to judge whether your shop has reached the point where it needs a system, our team wrote about the signs your business has outgrown Excel and LINE, which is worth a look.

What a website can't do, said plainly

A website doesn't make vegetables any cleaner. Food safety comes from growing, harvesting, transport and keeping the right temperature the whole way. That's the work of the farm and the shop, under the standards of the agencies responsible.

A website can only help with two things: telling customers honestly where the produce comes from and how to handle it, and helping the shop reach affected customers quickly when there's a problem. If a shop talks about its website as if it makes the product safe, that's an overclaim, and smart customers will feel it.

Labelling, permits and the rules for selling food online are set by the Thai FDA. If you're not sure what your products require, asking the Thai FDA directly will get you the most reliable answer.

Why starting early pays off

Lot data is only valuable if it was recorded before the day you need it. If you start linking orders to lots today, in three months you'll have three months of searchable history. If you start on the day the news breaks, you'll have zero days.

Trust builds up over time too. A customer who has received a message from your shop saying "your batch came from this farm and arrived on this date", even on days when nothing happened, will remember that you care. On the day there's news, they'll ask you before they stop buying.

The minimum version a small shop should have

If you're not ready to invest much, these three things are enough to start: product pages that show the origin, date received, and storage and cooking guidance with links to the relevant agency; a lot-number field in your order management that the packer fills in every time; and a list of customers who have agreed to receive messages, which you can pull by lot.

With those three, you can already answer all three questions from the start of this article. Add the rest as your shop grows.

Real tools you can use alongside your site

Thailand already has a traceability system. The National Bureau of Agricultural Commodity and Food Standards (ACFS) runs QR Trace on Cloud, which lets farmers, farmer groups, community enterprises, cooperatives and businesses record where their products come from and create a QR code for the packaging. It covers fruit and vegetables, rice, eggs, fisheries, livestock and processed products. According to an ACFS press release from April 2023, the training it ran was for producers certified under GAP, Organic Thailand or GMP. The release doesn't say what the current sign-up conditions or costs are, so check with ACFS directly.

If the farm you buy from already uses this system, your product page can simply include the link or the QR image for that batch. Customers then see information from the source, without having to take the shop's word alone.

And for the side where something has already gone wrong, the US FDA recall notice described above is a public document anyone can read. Read it once and you'll see what information a shop should have on hand.

A 5-step plan you can start this week

1. Open the latest delivery slips for your 5 best-selling products and note the farm or source, province, and any standard the farm holds.

2. Add origin, date received and storage guidance to those 5 product pages, with a link to cooking advice from the agency that issued it.

3. Set up a simple lot-number format, such as the date received followed by a farm code, and have the packer fill it in for every order.

4. At checkout, ask customers how they agree to be contacted about the products they bought, and store that with the order.

5. Do one rehearsal: search for who received last week's lot, and time how many minutes it takes.

How to tell whether it's working

The first number to watch is how long it takes to answer "who received this lot" in the step 5 rehearsal. If it takes half an hour the first time and under a minute the following month, the system is working.

Another number that tells you a lot is chat questions. Count how many times a week customers ask about origin or freshness. Once the information is on your product pages, those questions should drop, because customers find the answer before they message you.

Repeat-purchase rate takes months to show and has many other factors mixed in, so don't draw conclusions from a single month. If you want that trust to be visible on your site too, our article on showing customer reviews on your website covers where to place them so they actually help close the sale.

Back to the regular vegetable stall

That seller has no complicated system at all. She simply knows where her stock comes from, remembers who bought what, and tells customers straight when something isn't right. An online shop can do the same. It just needs the web page and the back office to remember for you.

If you already sell fresh produce and want to see how having your own website differs from selling through chat alone, start with the pros and cons of a website for online stores.

If you'd like an ordering system that links product lots to customers from the moment you pack, take a look at what TumWebSME's back-office system service can do, then message us and tell us about your shop. We'll help you work out where a shop your size should start.

Follow TumWebSME

Follow our tips on building websites and online marketing here:

• Facebook: TumWebSME รับทำเว็บไซต์ธุรกิจ

• Instagram: @tumwebsme

• TikTok: @tumwebsme

• YouTube: TumWebSME

Contact us for services

• 088-983-9386 (Khun Ploy)

• 099-856-3198 (Khun Saennan)