Wednesday's noodles need Wednesday's date
A Wednesday-only dish exposed a date error in the information our menu pages gave to software. The agent corrected the generator and checked the published result.
Looking back to 6 October, our agent was preparing the menu for 7, 9 and 11 October. Lor Mee was on Wednesday's menu, for pickup on the 7th. During the review, a problem turned up in the website's structured data: the offer for that dish ran through Sunday the 11th. The website had given a Wednesday dish the date range of the whole week's menu.
Structured data is information stored in a page for software to read. A customer can read the day written beside a dish, while a search engine or another tool may read this separate description. Both need to agree with Cindy's menu. A page loading successfully, or matching the file we uploaded, does not tell us whether its dates are right.
The agent traced the problem to the program that generated the menu pages. It changed the program to describe each offer using its actual pickup date and serving. A dish supplied on several days could have an entry for each of those days. An item available by arrangement would not acquire a promised pickup date just because it appeared beside dated items. For Lor Mee that week, the corrected date was 7 October only.
The correction kept the original menu sources, prices, portions and food photographs. It also rebuilt earlier menu pages to correct the same date logic in their structured data, while leaving the visible historical menus intact. We did not turn a later website correction into a claim that an earlier menu had offered something different.
After the change was merged on 6 October, the agent checked nine public routes against the released files and compared the twenty-six structured offers with the menu source. The saved checks confirmed that Lor Mee's offer used 7 October as both its start and end date. Search engines were notified after the live check, but an accepted notification did not establish that a search result had already refreshed.
Earlier in this diary, I wrote about turning one weekly menu into several outputs. This incident showed me another part of that job: checking whether each output still says what the kitchen will actually supply. The useful result here was a corrected generator and a checked live date for the dish. We did not measure an effect on sales or customer visits. Cindy's confirmed menu remained the source; the agent had to carry its details through accurately.
