E-commerce
July 1, 2026
A customer sometimes places two orders a few minutes or hours apart. They then wonder if the orders can be combined to save on shipping costs, receive a single package, or simplify tracking.
The chatbot can help, but only if preparation has not yet started and if logistics rules allow it. It must explain the conditions, limitations, and what can be done without promising an impossible combination.
This guide shows how to manage order combination with an AI chatbot, in a way that is clear for the customer and realistic for operations.
Summary
Why do customers want to group their orders?
The need is simple: the customer realizes they forgot a product, places a second order, and then wishes to avoid two separate deliveries. They may also want to reduce their environmental impact, limit fees, or receive everything at the same time.
On the shop side, grouping orders can be useful, but it depends on the preparation status, the warehouse, the carrier, the products, and sometimes the country of delivery.
The chatbot must verify feasibility before leading the customer to believe that two orders can always become a single package.
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 conditions should be checked?
The bot must verify both order numbers, the address, the preparation status, the warehouse, the carrier, the products, the shipping times, and the payment method.
If an order is already prepared, shipped, or handed over to the carrier, consolidation is often no longer possible. The chatbot must then explain the limitation without giving the impression that the brand is refusing for its own convenience.
How do you explain the time window?
Grouping orders is generally an urgent action. The earlier the customer requests it, the higher the chances are. The bot can say: "I will check if both orders can still be modified before preparation."
This formulation helps the customer understand that the timeframe is not arbitrary. Once preparation has started, the team cannot always interrupt the logistics flow.
It also avoids a common frustration: the customer thinks they requested it fast enough, while the order has already moved to an automated preparation queue.
What can be said about the delivery fees?
If orders are grouped, the customer can request a refund for one of the delivery fees. The chatbot must not promise it automatically. It must check the store's policy.
A cautious response would be: "If grouping is possible, our team will also check if a delivery fee adjustment applies." This phrasing remains useful without creating a financial promise.
What should be done if regrouping is impossible?
The bot must explain why: preparation has already started, carrier has already been notified, products shipped from different warehouses, or incompatible logistics rules.
It can then propose an alternative: track the packages separately, cancel an order if it is still modifiable, or contact support if the customer placed the second order by mistake.
Which flow to follow?
The flow must quickly verify feasibility.
Collect both order numbers and the customer email.
Verify that the addresses, warehouses, and carriers are compatible.
Read the preparation status of each order.
Explain whether merging is possible, uncertain, or impossible.
Forward to support if a manual action needs to be attempted.
Which messages should be used?
For a possible request: "The orders still seem to be pending preparation. I am forwarding the request to check if they can be grouped together."
For a request that is too late: "One of the orders is already in preparation or has been handed over to the carrier, which often prevents combining them."
For fees: "If the grouping is confirmed, the team will check if an adjustment of the delivery fees is planned."
When to transfer?
Transfer is necessary as soon as a grouping is technically possible but requires logistical intervention, or if the customer requests a refund of fees, a partial cancellation, or an urgent modification.
The bot must transmit both orders, the address, statuses, carriers, products, and the time of the request.
Which KPIs should be monitored?
Track merge requests, successful merges, late merge requests, fee refunds, and tickets related to duplicate orders.
This data helps determine whether the checkout, confirmation page, or emails should better offer adding a product before shipping.
Which mistakes should be avoided?
Avoid promising a consolidation without checking the status, guaranteeing a shipping refund, or ignoring warehouse constraints.
The bot must be fast, but accurate. An unfulfilled consolidation promise creates more frustration than two well-explained separate packages.
How can Qstomy help?
Qstomy can detect nearby orders, check statuses, and forward grouping requests with full context.
The chatbot helps the customer act quickly without creating unrealistic logistical promises.
Explore AI support or request a demo.
COMBINEBOT Checklist (8 steps)
Sync COMBINE-MAP #497: RAG + eligibility API
Policy COMBINEBOT-SUP: 6 NO-AUTO-MERGE rules
8 intents bot_combine_*: flow CMB-1 to CMB-8
4 templates TPL-COMBINE-*: OFFER LATE ADDR PENDING
Trigger 2nd order webhook: proactive offer window
Ops ticket integration: auto merge request on accept
6 scenario tests: proactive, request, late, addr, decline, handoff
KPI Dashboard: combine_bot_* section 9
FAQ
Difference #497?
#497 = agents execute merge and refund. #498 = bot proposes and opens ops ticket.
Does the bot merge in Shopify?
No. Ops ticket with order IDs. Manual execution or merge app.
Aggressive proactive?
One offer per pair 48 h. Decline = suppress 7 days.
Going further
This week: activate 2nd command unfulfilled trigger, test eligible vs late, measure combine_bot_accept_rate.
Enzo
July 1, 2026
