I'm not a developer of Sakupa. I'm someone who likes looking into services I find interesting, and I write up what I learn from the official site and the official manual.
Some dishes sell out. When one does, the menu page should say so — before a customer walks in expecting it. This post walks through asking Muse, a personal AI agent, to add a sold-out notice to a menu page, using Sakupa.
What to decide before asking
A sold-out notice is a small change, but it still helps to decide three things before asking:
- Which item is sold out
- How long the notice stays up
- What the notice says
Which item is sold out sounds obvious, but a menu can list the same dish in two places — the lunch menu and the dinner menu, for example. Name the exact place: "the seasonal fish set on the lunch menu" leaves less room for guessing than "the fish set."
How long the notice stays up matters because a sold-out notice is temporary. Some dishes come back tomorrow; some come back next season. Decide whether the notice should stay until you ask again, or come down on a certain date. "Keep it up until I say otherwise" is a clear instruction.
What the notice says is short: "Sold out for today" or "Sold out until next week." One line is enough. It does not need a reason, and it does not need an apology. A customer reading the menu only needs to know the dish is not available right now.
The chat flow
With Sakupa connected to Muse, ask for the notice and hand over the three decisions together. Give the words exactly as they should read, and name the page: "Add 'Sold out for today' next to the seasonal fish set on the lunch menu page" leaves less room for guessing than "mark something sold out."
Then Sakupa's usual flow runs: analyze reads the current state of the site, and a preview with a confirmation step comes before anything is executed. For a sold-out notice, the preview is where you check three things:
- The notice is next to the right dish
- The words read exactly as decided — no added reason, no extra promise
- Nothing else on the menu changed
A sold-out notice sits right next to a price and a dish name, so a small slip matters. The wrong dish marked sold out turns away a customer who wanted it; the right dish left unmarked disappoints one who came for it. Checking with your own eyes before publishing is the point of the preview.
Once confirmed, deploy publishes the change. When the dish is back, ask again the same way to take the notice down, and the same preview-and-confirm flow runs again.
Keeping it honest
A sold-out notice works best when it stays simple. Three things help:
- One line, next to the dish: the notice belongs with the item it describes, not at the top of the page
- A date when there is one: "Sold out until next week" is more useful than "Sold out" with no end in sight
- Take it down when the dish returns: a notice left up after the dish is back is worse than no notice at all
The notice is temporary by nature. Deciding how it comes down, at the same time as deciding how it goes up, keeps the menu honest.
Pricing
A site starts with a 30-day free preview. After that, only the sites you keep are on a paid plan, starting at ¥200 a month, contracted per site. Adding a sold-out notice costs nothing extra.
Payments go through a Stripe-hosted page only. The design does not hand your card number to the AI.
Summary
- A sold-out notice is a decided fact: which item, how long it stays up, and what it says
- Name the exact place on the menu, and give the words exactly as they should read
- In the preview, check the notice is next to the right dish, the words are as decided, and nothing else changed
- Keep it to one line next to the dish, with a date when there is one
- Decide how the notice comes down at the same time as how it goes up
I'm not a developer of Sakupa. I put this together from the official site and the official manual. Please check the official information for current pricing and features.
Links
- Sakupa official site: https://sakupa.com
- Sakupa official manual: https://sakupa.com/manual
- @sakupa/mcp (npm): https://www.npmjs.com/package/@sakupa/mcp
Top comments (0)