> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/getting-started/address-collection.md).

# Address collection

### Overview

Address collection controls how customers provide delivery and checkout details.

The selected method sends collected details to [Order Management](/whatsapp-commerce/manage-orders/order-management.md). It also determines the customer checkout experience.

### Configure address collection

Follow these steps to select an address collection method.

#### Step 1: Open catalog settings

Go to **Ecommerce → Catalogs**. Select the required catalog, then click **Edit**.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2F3pgyoF34K2dl6s4nlaq8%2Fscreenshot-1172c07a.jpg?alt=media&amp;token=9bc1837f-093a-462a-8b6b-6aeebbb8917b" alt=""><figcaption></figcaption></figure>

#### Step 2: Choose an address collection method

Choose the option that fits your business requirements:

* **Quick Checkout** provides a complete, app-like checkout within WhatsApp.
* **Address only** collects structured address details through WhatsApp Flow.
* **Message by Message** collects each detail through a chatbot conversation.
* **India Checkout Flow** provides an interactive checkout experience without Meta Business Verification.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2FPcd6KAuip5HyWVsN2pTp%2Fimage.png?alt=media&amp;token=810e3752-f232-4b5f-914e-c43554a2913a" alt=""><figcaption></figcaption></figure>

### Address collection methods

#### Quick Checkout

Quick Checkout collects checkout details in one interactive WhatsApp experience. Customers avoid switching between several chat messages.

The checkout form adapts automatically to your configured delivery, payment, and order settings. You do not configure each form field manually.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2F5fA6fIqXAwwECuGqQ7MK%2Fimage.png?alt=media&amp;token=6809ce38-b957-4410-98bf-f23b35393ce7" alt=""><figcaption></figcaption></figure>

#### Customer experience

Depending on your configuration, customers can:

* Select, add, or edit a delivery address.
* Choose a delivery method, slot, and payment method.
* Review charges, discounts, and the order summary.

Before confirmation, customers can review products, quantities, prices, delivery details, taxes, discounts, and the final payable amount.

#### Dynamic configuration

The form reflects settings from delivery configuration, Order Management, payment methods, and delivery slots.

For example:

* Enabled delivery slots appear as a checkout selection.
* Choose which address fields to collect from customers.
* Disabled cash on delivery removes that payment option.
* Pickup-only orders hide delivery-specific fields.
* When address collection is disabled, customers can add order notes and choose available payment or delivery-slot options.

#### Automatic checkout chatbot

Quick Checkout uses a dedicated checkout chatbot automatically.

Configure the chatbot in **Order Management**. Use **Automatically add contacts to chatbot when an order is received based on order stage**. Then select the order stage that triggers checkout. The **Placed** stage is recommended.

Quick Checkout automatically applies its checkout chatbot. You cannot change it while this method is selected. Choose **Address only** to configure a different chatbot and flow.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2FloCzQRQ6oqIBOJYmown7%2Fimage.png?alt=media&amp;token=876515fb-1232-455e-8f11-88e22bb84657" alt=""><figcaption></figcaption></figure>

At the configured order stage, it temporarily replaces the standard chatbot. It launches the form, collects details, shows the summary, and completes checkout.

Use this option for businesses that need a modern checkout experience. It works well for retail, restaurants, grocery, pharmacy, and delivery-slot businesses.

#### WhatsApp Flow

WhatsApp Flow uses Meta’s native WhatsApp Flows feature for structured address collection.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2FPH9Fy6RflNjXua9JSTsf%2Fscreenshot-ebf9a65e.jpg?alt=media&amp;token=65813179-d422-45ed-b238-5a27a70877ab" alt=""><figcaption></figcaption></figure>

Customers enter delivery and contact details in a guided form within WhatsApp. This method focuses on address collection. It does not provide payment selection, delivery slots, or a complete order summary.

{% hint style="warning" %}
WhatsApp Flow requires Meta Business Verification. Unverified businesses cannot use this option.
{% endhint %}

Use this option when you need standardized address data and have completed Meta Business Verification.

To configure it, select **Address only**. Select an existing WhatsApp Flow, or click **Create preconfigured flow** to create a tailored flow.

#### Message by Message

Message by Message uses a conversational chatbot sequence. The chatbot requests each address detail separately, such as name, phone number, address, city, and postal code.

<figure><img src="https://2006641734-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpJoGenGxBt4nUMwDYga6%2Fuploads%2FoaGCdP5dZUtesQRPcthn%2Fimage.png?alt=media&amp;token=74b16567-0003-4c72-aaa9-fd4fa2647c26" alt=""><figcaption></figcaption></figure>

Use this option when WhatsApp Flows are unavailable or a conversational experience is preferred. It also supports businesses without Meta Business Verification.

This method requires more customer responses than a structured form. It remains the most compatible address-collection option.

#### India Checkout Flow

India Checkout Flow provides an interactive, flow-like checkout experience for Indian businesses.

It supports faster address collection and fewer conversational steps. Meta Business Verification is not required.

Use this option for India-only operations that need a richer checkout experience without Meta Business Verification.

### Related settings

Your address collection experience changes with these configurations:

* [Shop Setup](/whatsapp-commerce/logistics-integration/logistics-core-module/shop-setup.md)
* [Customize Delivery Methods](/whatsapp-commerce/logistics-integration/logistics-core-module/customize-delivery-methods.md)
* [Order Management](/whatsapp-commerce/manage-orders/order-management.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pickyassist.com/whatsapp-commerce/getting-started/address-collection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.