> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/ecommerce/how-to-collect-address-payment-and-other-details-from-user-after-you-receive-an-order.md).

# How To Collect Address, Payment and Other Details From User After You Receive An Order ?

#### Setting Up an Automated Order Management System

1. **Create a WhatsApp Bot Flow for New Orders**
   * Design a bot flow in WhatsApp that activates as soon as a new order is placed.
2. **Collect all the details** required like address,payment method,etc.
3. Create custom order fields if necessary to store additional information.
4. For online payment , generate payment link and send it to user.
5. Trigger a seperate automation flow to send a thankyou message with order details when the payment is received.
6. Handle failed payments by sending reminders or providing alternative options.#

{% embed url="<https://youtu.be/XWBI2RA-u4E>" %}

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocumentation.gitbook.io/user/ecommerce/how-to-collect-address-payment-and-other-details-from-user-after-you-receive-an-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.