Product and Order nodes
Let visitors pick products earlier in a flow with the Product node, then review and place the order later with the Order node.
The Product node and the Order node split ordering into two parts, so a visitor can choose products at one point in a conversation and place the order later, after other questions or choices.
Both nodes need Commerce turned on for your chatbot, and they work the same on your website, WhatsApp, and Instagram.
What each node does
- Product — lets the visitor pick one catalog product and adds it, with a quantity you set, to the order building up on their path. It never places the order on its own. Add several Product nodes along a flow to build up a multi-item order.
- Order — reviews the products picked up so far, resolves the customer details, and places the order once the visitor confirms.
When to use them
Use a Product node plus an Order node when you want products chosen before the order is placed — for example, let the visitor pick a main item early, ask a few more questions or offer an add-on, then review and place everything at the end.
Each product the visitor picks along the way is added to the same order. If the same product is picked more than once, the quantities are added together into a single line. A branch the visitor does not take never adds its products.
Set up a Product node
Add the Product node
In the node library, choose Product. Its edit panel is titled Add products.
Attach products
Search your catalog by product name or SKU and select Add on each product this node should offer. You can attach up to 50 products to one Product node. Set each product's quantity with the plus and minus buttons; a quantity can be any whole number from 1 to 9,999. Your chosen items stay pinned under Products this node adds.
The visitor is shown these products and picks one. That product is added to the order at the quantity you set, then the flow moves on.
Connect the next step
Under Next step, route the node to the next question, another node, or an ending. A Product node leads to exactly one next step. Your changes save automatically as you edit — there is no Save button.
A Product node must have at least one attached product. While it has none, the editor shows a reminder and the flow will not publish until you attach one, but your other edits are still saved.
Set up an Order node
Add the Order node
In the node library, choose Order. Its edit panel is titled Place the order.
Map the customer details
Under Customer details, connect the answers your flow collected to the order fields. Name and delivery address are required; email, phone, and notes are optional, so a visitor can leave a phone number instead of an email. Collect each detail earlier with an Ask for input node and give it a Key, then pick that Key here. Any email or phone you collect is still checked for a valid format before the order is placed.
If a required detail is unset or points to a Key that no longer exists, the editor shows which mapping to fix. Your changes save automatically as you edit, and the flow will not publish until every required detail is mapped.
The visitor always reviews the order first
Every order is reviewed before it is placed — there is nothing to switch on or off. When the visitor reaches this node they see a summary of the products, shipping, the total including shipping, and the details you collected, then place the order with a Confirm button (or Cancel to stop). The order is only created after they confirm. Shipping and tax come from Commerce → Settings.
Write an optional confirmation message
Leave Confirmation message blank to show the full order review automatically, or type your own message up to 500 characters. Drop in {orderId}, {orderTotal}, or {orderSummary} to include the order number, total, or full item review, plus any answer Key you saved such as {name}. A message longer than 500 characters is rejected with a note showing the limit.
Connect the next step
Under Next step, choose where the flow goes after the order. Your changes save automatically as you edit — there is no Save button.
Build and publish
Create, connect, validate, preview, and publish a flow.
Guided Flows overview
How guided flows work across the widget, WhatsApp, and Instagram.
Troubleshooting
- The order says the cart is empty. The visitor reached the Order node without picking any product, and the Order node has none of its own. Make sure a Product node always comes before the Order node on every path, or attach products directly to the order. The editor flags an Order node that could be reached with an empty cart before you publish.
- The flow will not publish. Check for highlighted issues: turn Commerce on, attach at least one product to every Product node, map the required name and delivery address on each Order node, and connect every node to a next step or ending. Fix each highlighted node, then publish again.
- The order was not placed even though the visitor confirmed. A detail may be missing or invalid. An order needs a name and delivery address, and any email or phone collected must be valid (an email must look like a real address, a phone must be a real number). Ask for the detail again with a clear example.
- The price or currency changed during review. If a product's price or currency changes between the moment the visitor sees the review and the moment they confirm, the order is not placed and the products stay in the cart. Ask the visitor to review the updated total and confirm again.
- The order total looks off. The total shown in the review is the product subtotal plus the shipping and tax from Commerce → Settings. Update those figures there to change what visitors are charged; every product uses your single store currency.
- A product is hidden, inactive, or out of stock. The order is blocked safely so nothing invalid is placed. Swap or remove the unavailable product, or restock and reactivate it in Products, then try again. The product picker also flags a hidden or sold-out product while you build the flow.
- Commerce is turned off. While Commerce is off, an Order node cannot place a new order. Turn Commerce back on to resume ordering.
- A confirmation shows
{orderId}or another placeholder as plain text. The placeholder was misspelled. Use the exact spellings{orderId},{orderTotal},{orderSummary}, or a saved answer Key like{name}. Unknown placeholders are left as-is so you can spot the typo. - The visitor picked or confirmed twice. The order is created only once. A repeated tap or a refreshed page does not create a duplicate order.