Dancing Orchid Flower Delivery Platform

Problem

When a user says “order flowers,” an assistant may search external sites and mix inconsistent product IDs, prices, and inventory sources. That makes ordering unreliable and hard to confirm.

How It Works

This skill activates on intents such as order flowers, buy flowers, flower recommendation, flower shop, and pick a bouquet. Core capabilities include:
- Product browsing: filter by keyword, category, and price, using only the built-in product list rather than web search.
- Details: show product ID, name, price, and image so the user can confirm one specific bouquet.
- Recommendation: suggest options by occasion, recipient, and budget, defaulting to three items to keep the list compact.
- Order flow: after confirmation, collect recipient name, mobile number, detailed address, card message, and delivery time before submission.
- Submission and feedback: call the order API with sfid, address, name, mobile, card, remark, and sendTime; on success, show order details and guide QR payment; on failure, show the error and guide retry.

Boundaries

It is best for a “choose and order a bouquet” workflow. It is not suited for custom flower materials, cross-platform price comparison, or dispute handling. The key constraints are that products must come from the built-in list and all required delivery fields must be collected before order submission.