← WhatsApp Business Automation
0/15 complete

Module 04 · Sales Automation

Building a Product Catalog Flow Inside WhatsApp

20 minfocused lesson5practical steps4grounded questions3source links
Open lesson + course map

On this lesson

Course outline

A catalog flow helps a customer find and request an eligible product. It does not replace product truth, inventory, pricing, tax, delivery, refund, or commerce-policy controls. WhatsApp states that businesses remain responsible for their transactions and that catalog commerce must follow Meta commerce policy and applicable law.

After this lesson, you can design a catalog flow backed by authoritative product data and a reviewable order summary.

// concept

Create the Product Contract

For every sellable item store:

// prompt — copy me11 lines
product_id
approved_title
current_description
price_pkr
tax_and_delivery_rule
availability_state
eligible_locations
image_rights_owner
variant_options
return_or_cancellation_link
last_verified_at

The commerce system or governed catalog is authoritative. The chatbot retrieves values; it does not generate price or availability. Mark unknown, limited, preorder, made-to-order, or out-of-stock states explicitly.

Before listing an item, check WhatsApp’s current business messaging and commerce restrictions. Do not attempt to sell prohibited or restricted goods through a clever category name.

// concept

Design Browse-to-Request States

// prompt — copy me2 lines
CATEGORY → PRODUCT → VARIANT → QUANTITY → LOCATION → SUMMARY → REQUEST
                 ↘ unavailable → alternative or human

At SUMMARY show product ID, variant, quantity, subtotal, delivery/tax status, fulfillment estimate, and policies. Use REQUEST ORDER if inventory or payment still needs verification. Use CONFIRM ORDER only when the underlying system actually reserves or creates the order.

Keep a back/edit route. If price changes between browse and confirmation, show the new price and require fresh confirmation.

// worked_example

Worked Example

A Sialkot sports-goods seller offers custom footballs. The customer selects Training Ball, size 5, quantity 10, and Lahore delivery. The catalog returns a sample subtotal of PKR 35,000, while customization and delivery are pending quotation. The flow cannot display PKR 35,000 as the final total.

The summary says:

// prompt — copy me5 lines
10 × Training Ball TB-05: PKR 35,000
Logo customization: pending artwork review
Delivery to Lahore: pending quotation
Final total: not confirmed
Action: REQUEST QUOTE / EDIT / HUMAN

The request reaches an agent with product IDs and the customer-approved summary. The agent verifies artwork rights, production capacity, delivery, total, deposit, and terms. The order system creates the final reference.

// failure_cases

Failure Cases to Diagnose

7 cases to diagnose

  • AI invents features from the product image

    use approved catalog fields only.

  • Old price cached in the bot

    re-fetch before confirmation and version the quote.

  • Unavailable variant appears orderable

    validate variant combinations server-side.

  • Delivery hidden until after confirmation

    disclose rule or pending amount clearly.

  • Image copied without rights

    record permission or ownership.

  • Catalog contains restricted goods

    remove them and review policy eligibility.

  • Chat message becomes the only order record

    create a durable order or quotation reference.

// pakistan_angle

Pakistan Angle

Show PKR with separators and state whether tax, delivery, customization, and COD charges are included. For imported goods, do not promise customs, warranty, or delivery outcomes without current supplier and legal evidence. For handmade products, distinguish sample imagery from the exact delivered item.

Address handling should collect only fulfillment needs: recipient name, reachable phone, city, area, street/location detail, and landmark when required. Show it back for confirmation and restrict access. Do not request a CNIC image for ordinary catalog browsing or COD merely because it might reduce fake orders.

// hands_on

Hands-On Exercise

5 steps

  1. Build product contracts for five sample items.

  2. Verify policy eligibility and image rights.

  3. Draw category-to-request states with edit and unavailable branches.

  4. Create a summary that separates known and pending amounts.

  5. Test price change, stock change, invalid variant, and unsupported city.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

3 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

  1. 1 / 4 · diagnose

    Your work shows this failure mode: “AI invents features from the product image.” What does the lesson tell you to do about it?