E-commerce
July 1, 2026
A customer adds a product to the cart, but the quantity does not behave as expected. The site imposes a minimum, sells in batches, rounds up units, blocks a quantity, or indicates insufficient stock.
Without an explanation, the customer thinks it is a bug. The chatbot can clarify the rule: product sold in packs, minimum order, maximum quantity, professional unit, stock constraint, or logistical threshold.
This guide explains how to help a customer understand cart quantities with an AI chatbot, without losing them in internal rules.
Summary
Why do cart quantities create confusion?
The customer often expects to be able to choose any quantity. When the cart imposes 6, 12, or 24 units, they do not always understand that the product is sold by the lot or pack.
The confusion is even stronger in B2B, for consumables, spare parts, multipack formats, or products subject to a logistical minimum.
The chatbot must explain the commercial logic in buying language, not in inventory language.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What rules should be checked?
The bot must verify the sales unit, packaging, minimum order, maximum quantity, available stock, discount thresholds, B2B rules, and delivery constraints.
It must also differentiate between product quantity and number of packs. A customer who thinks they are buying 2 units may in reality be buying 2 packs of 10.
How to explain lots and packs?
The answer must be very concrete: "This product is sold in packs of 6. A quantity of 2 therefore corresponds to 2 packs, which is 12 units."
This clarification avoids unpleasant surprises regarding the total price and upon delivery. It also helps the customer choose the right quantity before paying.
This is particularly important for professional clients, who sometimes have to justify an order or respect a precise budget. A misunderstood unit can change the actual cost and the quantity received.
How do I manage minimum order amounts?
A minimum order may exist for logistical, B2B, or supplier reasons. The bot must explain this without giving the impression of an arbitrary constraint.
It can say: "This product has a minimum order of [quantity] units. The cart automatically adjusts the quantity to comply with this packaging."
What should I do if the stock is insufficient?
If the customer requests a quantity greater than the available stock, the bot must explain the quantity actually available and suggest next steps: reducing the basket, waiting for replenishment, choosing an alternative, or contacting the sales team.
In B2B, it can also prepare a volume request if the desired quantity exceeds the displayed stock but can be ordered from the supplier.
Which flow to follow?
The flow must start from the rule that modifies the quantity.
Identify the product, variant, and desired quantity.
Read the sales unit, batch size, minimum, and available stock.
Explain the rule in understandable units.
Calculate what the quantity in the cart represents.
Propose the appropriate action: adjust, choose another format, or transfer.
Which messages should be used?
For a pack: “This product is sold in packs of [number]. If you select 3, you will therefore receive [total] units.”
For a minimum: “The minimum order quantity is [quantité]. The cart cannot go below this threshold.”
For stock: “There are currently [quantité] units available. You can reduce your cart or request information about restocking.”
When to transfer?
The transfer is necessary if the customer requests a large quantity, a quote, an exception to the minimum, an urgent restocking, or if the displayed quantity seems inconsistent.
The bot must transmit the product, the variant, the desired quantity, the available quantity, the country, and the type of customer account.
Which KPIs should be monitored?
Track questions about lots, dropouts after quantity adjustment, volume requests, stock errors, and confusion between packs and units.
If many customers ask the same questions, the product page or the shopping cart should make the sales unit more visible.
Which mistakes should be avoided?
Avoid just saying "invalid quantity." Also, avoid hiding lots, calculating the total ambiguously, or letting the customer discover the packaging only after delivery.
The bot must help the customer understand what they are actually buying.
How can Qstomy help?
Qstomy can read quantity rules, explain batches, and transfer volume requests with cart context.
The chatbot reduces abandonment related to misunderstood rules and helps the customer order the right quantity.
Explore the AI sales agent, AI support, or request a demo.
Checklist CARTQTYBOT (12 steps)
Sync CARTQTY-MAP #474 JSON into bot RAG
Draft policy CARTQTYBOT-SUP 8 rules
Deploy 12 intents bot_cartqty_* classifier
Implement CBQ-1 to CBQ-8 + guardrails
Shopify product metafields read-only CBQ-3
Valid qty calculator lot multiple logic
TPL-CARTQTYBOT-* + /pages/cart-quantity corpus
MOQ dup reroute rules CBQ-5
Test 8 scenarios: lot 6 qty 3, pack 12, step 5, max, mobile +/-, post order handoff, moq reroute, dup reroute
Dashboard KPI cartqty_bot section 9
PDP chat chip T1 + cart error T2 widgets
Red team invent lot moq confusion quarterly
Summary
#475 = bot qty cart tier 1, no execute edit
CARTQTY-MAP #474: shared corpus
NO-INVENT-LOT: API grounded
MOQ reroute: not lot macro
KPI cartqty_bot_invent_lot: target 0
FAQ
Does the bot modify orders?
No. Handoff agents #474 CQ-7. Bot explain pre-purchase guide.
Difference with #474?
#474 agents post-order edit. #475 bot classify explain handoff.
Difference with MOQ #476?
MOQ = total order threshold. Bot reroute. Cartqty = SKU lot qty.
Qty 3 lot 6?
TPL-CARTQTYBOT-VALID-NEXT suggest 6 next valid.
1 qty = how many pieces?
TPL-CARTQTYBOT-PACK units_per_unit CARTQTY-MAP.
Going further
This week: import CARTQTY-MAP into bot RAG, deploy bot_cartqty_* classifier, activate NO-INVENT-LOT guardrail, configure valid qty calculator, PDP chip T1, test 8 scenarios staging, launch dashboard cartqty_bot_invent_lot zero tolerance.
Share this guide #475 with product and bot ops: a suggested grounded valid qty is worth ten invented LLM answers about the lot, a clean MOQ reroute is worth five "impossible to add 3 to cart" tickets on misunderstood wholesale threshold.
Go-live test matrix
8 scenarios: lot qty 3 valid next, pack units, step 5, max promo, mobile +/-, post order handoff, moq reroute, dup reroute.
CARTQTYBOT internal documentation
Wiki ops: intents → templates → reroute MOQ dup → handoff triggers, CARTQTY-MAP owner #474, guardrail owner bot ops.
Quarterly MOQ corpus sync
When #476 MOQ live update CBQ-5 reroute corpus and MOQ-REROUTE-01 templates from MOQ-MAP not placeholder.
Runbook handoff order edit
Agents receive sku lot_size qty_requested order_id fulfillment in Gorgias payload without re-explaining lot rules already covered by bot.
Enzo
July 1, 2026
