Prepare a product shortlist for a customer
Bring together a few relevant catalog choices for a store employee to verify.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Keep product information organized so a customer can browse categories, review item details, and collect possible choices in a cart. Treat availability and prices as information to verify, not a purchase commitment; have staff confirm any order details and approve the exact payment link and customer message before sharing them.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Help customers review products and organize possible selections, requiring staff approval before any purchase link or customer commitment.”
Clear tasks, with review where it matters.
Helps customers browse a product collection, compare details, and organize items they may want to buy.
Product information, stock, prices, and payment terms can change, and a cart is not an order. Keep catalog details current, verify the exact items and total with the store, protect customer details, and require an authorized person to approve the payment link, message, and recipient before sharing them.
Select an illustrative task to explore its proposed role. No workflow runs here.
Have a store owner verify product names, descriptions, categories, prices, and availability before customers rely on them.
Present clear item details and let the customer explore categories or request more information.
Keep chosen items and quantities visible for review without implying that stock is reserved or an order is placed.
Have an authorized person confirm item availability, quantities, price, and any applicable purchase terms.
Require staff to approve the exact total, payment destination, customer message, and recipient before sending a payment link.
Have a store owner verify product names, descriptions, categories, prices, and availability before customers rely on them.
These are planning notes for the concept, not instructions for a currently available template.
Choose the fields customers need and assign an owner to keep prices, stock, and descriptions current.
Explain that selections are not orders and specify when an item may be considered reserved.
Limit access to customer selections and retain only what the store needs for follow-up.
Name who verifies order totals and terms and who approves each payment link and customer message.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation