E-commerce

AI chatbot for cart quantities: explaining lots, units, and minimum order quantities

AI chatbot for cart quantities: explaining lots, units, and minimum order quantities

July 1, 2026

"The bot says pack of 4 while the spec sheet indicates 6." "The AI doesn't understand why I can't add 3 to the cart." "Transferred without explaining that 1 qty = 12 pieces." Three bot failures where the AI invents a pack rule, confuses wholesale MOQ and SKU qty, or routes an order edit without an order status.

An e-commerce cart quantity AI chatbot does not replace CARTQTY-FLOW agents (#474). It classifies bot_cartqty_* intents, lookups grounded CARTQTY-MAP SKU, explains lot increment unit pack max, guides PDP cart self-service, and hands off post-purchase order edits.

This guide #475 covers intents bot_cartqty_*, flow CARTQTYBOT, and KPI cartqty_bot. Distinct from the qty playbook (#474) and the future MOQ (#476): here, AI use case to explain cart minimum unit lots.

Summary

Why automate cart quantity support with a bot?

Qty questions arise on PDP, cart, and checkout when the customer hesitates before purchasing and a generic bot does not read CARTQTY-MAP.

Bot cartqty volume and opportunity

70 to 82% of cartqty_pre_purchase tickets are botifiable as tier 1 if CARTQTY-MAP is grounded and NO-INVENT-LOT guardrails are active.

Three risks of an uncalibrated qty bot

  • Invent lot size: LLM quotes pack of 4 without SKU API

  • MOQ confusion: € threshold confused with SKU pack

  • Wrong route dup: two orders processed for cart qty

Baymard notes that clear quantity feedback reduces mobile abandonment by 8 to 15% (Baymard, mobile 2025). Fin reminds to look up product before AI agent response (Fin, AI agents 2026).

Angle #475 vs neighboring content

  • CS qty #474: CARTQTY-FLOW agents. #475 = tier 1 explain bot.

  • MOQ #476: future wholesale order threshold. #475 = qty SKU pack reroute MOQ.

  • Duplicate #473: bot dup. #475 = qty one order.

  • Saved cart #438: restore cart bot. #475 = qty rules explain.

  • Fresh fees bot #411: checkout fees. #475 = qty not fees.

DTC Food & Beverage Example

38 cartqty tickets/month baseline #474. After CARTQTYBOT: cartqty_bot_auto_resolve 79%, cartqty_bot_invent_lot 0, cartqty_bot_csat 4.5/5.

Bot explains, does not execute edit

CARTQTYBOT-SUP: bot guides qty on PDP, hands off for order edit, #474 CQ-7 agents execute.

PDP pre-add cart peak

58% of cartqty bot sessions occur before add-to-cart: CARTQTYBOT T1 chip is critical at the conversion moment.

Cart drawer error hook

Cart validation error for lot multiple: trigger proactive T2 bot_cartqty_cannot_add_qty to reduce ticket lag.

Grocery category bot corpus

Preload drinks, diapers, canned foods in CARTQTY-MAP rows for highest cartqty_bot_session_rate categories.

How does CARTQTYBOT differ from CARTQTY #474 and MOQ #476?

Playbook human qty, bot MOQ wholesale future, and bot qty cart: three layers of bot conversion.

Bot → qty role matrix

  • #475 CARTQTYBOT: SKU lot increment explain guide

  • #474 CARTQTY-FLOW: agents post-order edit execute

  • #476 MOQ future: cart subtotal threshold wholesale

  • #438 SCART-BOT: saved cart restore

  • #473 DUPBOT: duplicate orders pair

Shared CARTQTY-MAP corpus

#474 defines CARTQTY-MAP JSON. #475 bot consumes: lot_size increment_step units_per_unit max_qty pdp_disclosure.

Four BOT-CARTQTY-TYPE flows

  • bot_cartqty_pdp_guide: how adjust qty lot explain

  • bot_cartqty_lot_block: cannot add 3 lot 6 explain

  • bot_cartqty_pack_units: 1 qty = N pieces clarify

  • bot_cartqty_post_order: ordered too much handoff edit

Promise #475

Policy CARTQTYBOT-SUP, 12 intents bot_cartqty_*, flow CARTQTYBOT CBQ-1 to CBQ-8, guardrails, handoff payload, KPI cartqty_bot_*.

Bot ops 30 minutes training

Module 1: lot vs MOQ vs dup. Module 2: guardrail red team check fake lot. Module 3: valid qty calculator demo. Quiz 90 % before prod.

Conversion widget placement A/B

PDP chip above vs below add-to-cart test cartqty_bot_pre_purchase_save 4 weeks.

Which bot_cartqty_* intents should be classified?

Twelve cart quantity bot intents before the CARTQTYBOT flow.

Twelve bot_cartqty intents

  • bot_cartqty_how_adjust: how to change cart quantity

  • bot_cartqty_lot_explain: why in slots of 6

  • bot_cartqty_cannot_add_qty: unable to add 3 blocked

  • bot_cartqty_pack_units: 1 = how many pieces

  • bot_cartqty_increment_step: steps of 5 10 only

  • bot_cartqty_max_limit: ceiling of 10 why

  • bot_cartqty_min_required: minimum 2 to add to cart

  • bot_cartqty_mobile_plusminus: +/- adds too much on mobile

  • bot_cartqty_moq_reroute: order threshold € blocked

  • bot_cartqty_post_order_wrong: ordered too many handoff

  • bot_cartqty_dup_reroute: two orders not qty

  • bot_cartqty_oos_at_qty: stock max available

Bot execution tier

Tier 1 auto: lot_explain, pack_units, increment_step, max_limit, min_required, mobile_plusminus, how_adjust.

Tier 2 handoff: post_order_wrong, moq_reroute explain + agent if needed.

Bot session fields

cartqty_intent, sku, qty_requested, lot_size, increment_step, units_per_unit, max_qty, order_id optional, pre_post_purchase flag.

Intent router qty keywords

"pack of", "by 6", "cart quantity", "impossible 3", "how many pieces" route CARTQTYBOT before generic cart macros.

Post-handoff bot silence

After order edit handoff CBQ-7: bot stops qty guidance during the same session to prevent contradictory steps.

How does the bot consume CARTQTY-MAP #474?

The bot reads CARTQTY-MAP #474 for grounded qty rules without inventing lot size.

Lookup CBQ-4 bot

  • sku → lot_size_min: mandatory multiple

  • increment_step: +/- step quoted

  • units_per_unit: pieces per qty

  • unit_label_fr: box carton pack lot

  • max_qty_cart: limit reason

  • pdp_disclosure: exact customer text

Product API CBQ-3

Shopify product variant metafields custom.lot_size sync CARTQTY-MAP verify before respond.

Collection fallback

SKU no row: collection inherit rules CBQ-4 collection CARTQTY-MAP not LLM default.

Valid qty calculator

bot_cartqty_cannot_add_qty: bot computes next valid qty 6 12 18 from grounded lot_size.

RAG /pages/cart-quantity

Corpus CARTQTY-* macros #474 + FAQ link every cartqty thread.

Stale CARTQTY-MAP alert

Bot RAG hash mismatch #474: block lot answers handoff until sync.

Multi-SKU cart session

Client asks qty rules product A in cart with B: CBQ-3 lookup SKU mentioned message context.

Market localized unit labels

CARTQTY-MAP market FR UK: bot responds unit_label_fr or EN per session locale same lot_size numbers.

How to write the CARTQTYBOT-SUP policy in eight rules?

The CARTQTYBOT-SUP bot qty policy structures explain grounded without invent lot or execute edit.

Eight CARTQTYBOT-SUP rules

  1. CARTQTY-MAP grounded only: lot step units from map API

  2. NO-INVENT-LOT: block lot size not in map

  3. MOQ-REROUTE: cart subtotal threshold → #476 not lot macro

  4. DUP-REROUTE: two orders keywords → #473 DUPBOT

  5. NO-EXECUTE-EDIT: post-order handoff agents CQ-7

  6. Compute valid qty: suggest next lot multiple not guess

  7. Handoff payload SKU rules: lot_size qty_requested order fulfillment

  8. /pages/cart-quantity link: once per cartqty thread

Bot prohibited actions

Waive lot policy bot. Promise order edit shipped. Invent units_per_unit. Confuse saved cart #438 qty stale as lot bug.

Pre vs post purchase gate

CBQ-2: no order_id pre-purchase guide only. order_id post → fulfillment check before edit promise.

Fulfillment gate post-order

CBQ-2 order API fulfillment_status null before edit handoff promise not TPL edit if shipped.

Collection inherit explain

CBQ-4 cite collection rule source when SKU inherits: transparency reduce invent_lot disputes.

How do I apply the CARTQTYBOT CBQ-1 to CBQ-8 flow?

The CARTQTYBOT CBQ-1 to CBQ-8 flow structures triage qty bot grounded maps.

Eight steps CBQ-1 to CBQ-8

  1. CBQ-1 Intent classify: bot_cartqty_* from message

  2. CBQ-2 Context gate: pre-purchase sku | post order_id email

  3. CBQ-3 SKU product lookup: variant metafields CARTQTY-MAP

  4. CBQ-4 Rules match: lot increment max units disclose

  5. CBQ-5 Reroute check: MOQ dup saved_cart branches

  6. CBQ-6 Respond tier 1: TPL-CARTQTYBOT-* grounded CBQ-4

  7. CBQ-7 Branch: close guide | handoff order edit | moq explain | product bug

  8. CBQ-8 Log: intent sku valid_qty_suggested handoff csat

CBQ-6 bot_cartqty_lot_explain

TPL-CARTQTYBOT-LOT: sold by [N], valid qty [N] [2N] [3N], 1 = [units_per_unit] [unit_label].

CBQ-6 bot_cartqty_pack_units

TPL-CARTQTYBOT-PACK: 1 quantity = 1 [box] of [12] pieces. For [24] pieces qty 2.

CBQ-7 bot_cartqty_post_order_wrong

Unfulfilled handoff order edit payload. Fulfilled return policy link #474 CARTQTY-POST-ORDER-01.

CBQ-6 bot_cartqty_mobile_plusminus

TPL-CARTQTYBOT-MOBILE: type qty manual, wait 1 s between +, debounce tip.

CBQ-2 SKU from URL context

PDP page context prefill sku reduce client re-type product name errors.

SLA bot tier 1 cartqty

CBQ-6 TPL response under 5 s. Post-order handoff ack under 10 s with ticket ref.

CBQ-5 saved cart branch

"Cart recovered qty locked": verify #438 restore then CARTQTY-MAP current rules not stale assume bug.

Which TPL-CARTQTYBOT-* templates and guardrails?

Eight cart quantity bot templates and NO-INVENT-LOT guardrails.

TPL-CARTQTYBOT-LOT

" [Product] sold in packs of [N]. Add [N], [2N] or [3N] to the cart. 1 pack = [units_per_unit] [units]. /pages/cart-quantity "

TPL-CARTQTYBOT-PACK

" 1 in cart = 1 [box] of [12] pieces. Total pieces = quantity × [12]. "

TPL-CARTQTYBOT-STEP

" Quantities by [5]: try [5], [10], [15]. + Button advances by [5]. "

TPL-CARTQTYBOT-MAX

" Maximum [10] per order ([stock/promo]). Reduce qty or contact pro order support. "

TPL-CARTQTYBOT-VALID-NEXT

" [3] impossible. Next valid qty: [6] (= [1] pack). "

TPL-CARTQTYBOT-MOBILE

" Mobile: enter the number directly. Wait 1 second between each +. "

Guardrail NO-INVENT-LOT-01

Block lot_size units_per_unit not matching CARTQTY-MAP API within session.

Guardrail MOQ-REROUTE-01

Checkout blocked subtotal MOQ keywords route moq explain not lot macro.

Touchpoints

  • PDP chat chip "Quantity and packs?" T1

  • Cart drawer qty error T2 proactive

  • /pages/cart-quantity T3 bot embed

  • Checkout block message T4 bot_cartqty_moq_reroute

TPL-CARTQTYBOT-HANDOFF

" Agent transfer for order modification #[X] qty [requested]. Not shipped: modification possible within [SLA]. "

Checkout summary qty bot

T4 checkout "2 packs = 12 units" confirm chip opens bot_cartqty_pack_units clarify last mile.

Which MOQ, dup, and subscription cases should be processed?

Special bot cartqty cases require immediate reroute or handoff.

MOQ checkout block

bot_cartqty_moq_reroute: "Order threshold [€500] not product qty. Add items or see #476 MOQ." Not TPL-CARTQTYBOT-LOT.

Dup two orders reroute

"Two identical orders": #473 DUPBOT not cartqty qty selector.

Subscription qty

Recurring portal edit distinct cart one-time bot_cartqty_how_adjust reroute.

Saved cart stale qty

#438 restore: re-verify CARTQTY-MAP rules may have changed.

Bundle SKU qty 1

Bundle flag CARTQTY-MAP: 1 qty = complete kit not single unit lot.

OOS partial stock

bot_cartqty_oos_at_qty: max [12] available not lot bug TPL-CARTQTYBOT-MAX stock reason.

Shared cart #444

Co-purchase qty conflict: route shared cart bot not CARTQTYBOT single buyer.

B2B case pack light

Case 24 explain lot. Full wholesale MOQ → #476 when live.

Promo max qty dynamic

CARTQTY-MAP promo_end_date: bot cites active flash limit not permanent max.

Mixed subscription cart future

#504 mixed cart: qty rules differ by line type, bot classifies subscription vs one-time separate.

Gift qty same rules

#205 gift buyer qty 2: same CARTQTY-MAP lot rules, no gift exception bot.

Which cartqty_bot KPIs should be measured?

The cart quantity bot KPIs link auto-resolve, zero inventory lot, and conversion save.

Eight key metrics

  • cartqty_bot_session_rate : bot_cartqty sessions / qty chats

  • cartqty_bot_auto_resolve : tier 1 closed / sessions

  • cartqty_bot_pre_purchase_save : checkout completed post bot guide / eligible

  • cartqty_bot_invent_lot : guardrail violations (target 0)

  • cartqty_bot_moq_reroute_accuracy : correct MOQ vs lot / moq intents

  • cartqty_bot_handoff_quality : payload complete / handoffs

  • cartqty_bot_valid_qty_accept : client adds suggested qty / sessions

  • cartqty_bot_csat : satisfaction post cartqty bot

DTC lots Benchmark

cartqty_bot_auto_resolve 75-85 %, invent_lot 0, pre_purchase_save uplift 8-15 %, cartqty_bot_csat > 4.3/5.

Conversion bot dashboard

Intent breakdown, PDP vs cart touchpoint, moq reroute rate, post_order handoff funnel.

cartqty_bot_abandon_delta

Measure checkout abandon rate sessions with bot_cartqty_lot_explain vs control SKU subset.

cartqty_bot_ticket_delta agents

Target 60-75 % cartqty tier 1 deflection post-CARTQTYBOT maintain handoff quality.

valid_qty_accept tracking

Pixel or cart API event client sets suggested qty within 5 min bot session measure calculator effectiveness.

Which cartqty bot anti-patterns should be avoided?

Twelve cart quantity bot anti-patterns to ban from production.

1. Invent lot size

NO-INVENT-LOT-01 block LLM guess.

2. MOQ as lot

MOQ-REROUTE-01 threshold € not SKU lot.

3. Execute order edit bot

Rule 5 handoff agents only.

4. Route dup as qty

Rule 4 DUP-REROUTE two orders.

5. Waive lot bot promise

Policy exception agents manager only.

6. Skip units_per_unit

TPL-CARTQTYBOT-PACK must cite count.

7. Blame client tone

Empathy + guide not "you should have read".

8. Ignore mobile context

bot_cartqty_mobile_plusminus branch touch UX.

9. Saved cart as lot bug

Restore #438 verify rules first.

10. Empty handoff post_order

Rule 7 payload sku qty order fulfillment.

11. Skip valid qty suggest

Rule 6 TPL-CARTQTYBOT-VALID-NEXT required.

12. Skip /pages/cart-quantity

Rule 8 link once.

13. Theme bug reproducible

+/- bug confirmed : product ticket escalate not repeat TPL-CARTQTYBOT-MOBILE only.

14. Compare two SKUs lot

Client asks product A lot 6 vs B lot 12 : CBQ-3 lookup both SKUs separate TPL each grounded.

How does Qstomy implement CARTQTYBOT?

Qstomy on Shopify runs CARTQTYBOT: bot_cartqty_* classifier, CARTQTY-MAP #474 lookup, product metafields API, valid qty calculator, MOQ dup reroute gates, handoff order edit payload.

Qstomy cartqty bot capabilities

  • cartqty_intent_classifier: 12 bot_cartqty intents

  • cartqty_map_bot_lookup: lot step units max

  • valid_qty_calculator: next lot multiple

  • invent_lot_guard: block ungrounded rules

  • moq_dup_rerouter: branch #476 #473

  • order_edit_handoff: post-order payload

Pipeline #475 #474 #476

#475 bot tier 1 qty explain. #474 agents post-order. #476 MOQ wholesale when live reroute.

Calculated DTC scenario

Food lots of 6, 38 cartqty tickets/month, invent lot uncalibrated bot baseline.

After CARTQTYBOT-SUP + Qstomy: cartqty_bot_auto_resolve 81%, cartqty_bot_invent_lot 0, cartqty_bot_pre_purchase_save +12%, cartqty_bot_csat 4.5/5.

Explore customer support and request a demo.

Conversion AI Governance

CBQ-8 logs feed AI governance (#124) monthly cartqty_bot guardrail audit.

Weekly cartqty bot guardrail audit

Sample 25 sessions regex lot_size not in map responses zero tolerance.

Cart validation webhook integration

Cart API reject invalid qty → webhook bot_cartqty_cannot_add_qty session with sku qty_requested prefilled.

PDP metafield sync monitor

Alert when Shopify metafield lot_size diverges from CARTQTY-MAP row: block bot responses SKU until ops reconcile single source truth.

What checklist is needed to deploy CARTQTYBOT?

Checklist CARTQTYBOT (12 steps)

  1. Sync CARTQTY-MAP #474 JSON into bot RAG

  2. Draft policy CARTQTYBOT-SUP 8 rules

  3. Deploy 12 intents bot_cartqty_* classifier

  4. Implement CBQ-1 to CBQ-8 + guardrails

  5. Shopify product metafields read-only CBQ-3

  6. Valid qty calculator lot multiple logic

  7. TPL-CARTQTYBOT-* + /pages/cart-quantity corpus

  8. MOQ dup reroute rules CBQ-5

  9. Test 8 scenarios: lot 6 qty 3, pack 12, step 5, max, mobile +/-, post order handoff, moq reroute, dup reroute

  10. Dashboard KPI cartqty_bot section 9

  11. PDP chat chip T1 + cart error T2 widgets

  12. 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

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

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.