DEV Community

mengyu2022-sudo
mengyu2022-sudo

Posted on

Asking Muse to add delivery and takeaway info to your shop's site

I'm not a developer. I'm someone who likes looking into interesting services and writing up what I find, in my own words.

Some shops deliver, some do takeaway, some do both — and customers usually find out by phoning to ask. This time I want to walk through asking a personal AI agent, Muse, to put the delivery and takeaway details on the company site, so the answer is there before anyone has to call. The tool underneath is Sakupa.

Start with what's already decided

Delivery details are facts the shop has already settled, not things for Muse to invent. Before asking, I gather four things:

  • The delivery area — which neighborhoods or streets it covers
  • The delivery and takeaway hours
  • Any fee or minimum order
  • How to order — by phone, or a link to an ordering page

The point is to hand over what's already decided. The area, the hours, the fee: the shop decided those. Passing them exactly keeps the page honest — nothing gets added that the shop never promised.

The flow in chat

With Sakupa connected to Muse, I say something like: "Please add a delivery and takeaway page." Then I pass the four things along, and I name the page clearly — for example, "Delivery and takeaway" — so Muse knows where it goes.

Then Sakupa's usual flow kicks in. analyze reads the current state of the site, a preview is shown for confirmation, and only then does anything run. That's the two-step check. On a delivery page, the preview is where I check two things: that the area names are right, and that the fee and minimum order match what the shop decided. A wrong fee on a public page is exactly the kind of mistake worth catching with my own eyes before it goes live.

Once confirmed, deploy publishes it. If the area or the fee changes, I ask again the same way, and the preview-and-confirm step runs again each time.

When the area changes, say what changed

Delivery areas change: a new neighborhood gets added, or a far one gets dropped. When that happens, I tell Muse exactly what changed — "Please add this neighborhood to the delivery area" — and pass the new list.

One habit that helps: when I ask for the change, I say whether the old area stays or goes. "Add this street, keep the rest" is clearer than "update the delivery area." Saying what changes and what stays the same keeps the edit small, and the preview easier to check.

How pricing works

A site starts with a 30-day free preview. After that, only the sites you keep are billed, from ¥200 a month, one contract per site. Adding a delivery page doesn't add a separate charge.

Payment goes through a Stripe-hosted page only. The design doesn't hand your card number to the AI.

Wrapping up

  • A delivery page starts from what's already decided: the area, the hours, the fee, and how to order
  • The facts come from the shop, not from the AI — nothing gets invented
  • Before publishing, the preview is where I check the area names and the fee
  • When the area changes, say what changed and what stays the same

I'm not a developer of Sakupa. I put this together from the public information on its official site and official manual. For the latest pricing and feature details, please check the official pages as of the day you read this.

References

Top comments (0)