E-commerce
July 1, 2026
"Why can't I add this product to my cart?" "I ordered from the wrong store, what should I do?" "Two separate packages, why two shipping fees?" Three tickets where a poorly explained multi-store cart blocks a purchase or generates a delivery dispute.
The e-commerce multi-store cart support covers separate catalogs, shipping fees per store, stock availability, and the impossibility of merging carts. Distinct from Shopify Markets: here, we are talking about several distinct Shopify stores, not a single multi-country shop.
This guide #803 covers policy MSTRCART-SUP, flow MS-1 to MS-8, and matrix MSTRCART-MAP. Customer support pairing of the future: bot MSTRCART (#804).
Summary
Why do multi-store shopping carts generate tickets?
DTC Group: FR store, US store, separate outlet. Each Shopify has its own cart, shipping fees, stock. The customer mixes up URLs, expects a single package, or orders from the wrong catalog. The agent promises a cart merger which is impossible.
Five typical multi-store frictions
No cart merger: products from different stores incompatible map
Wrong store: order incorrect store URL map
Separate deliveries: split ship two shipping fees map
Stock per store: available store A but not store B map
Return to which store: CS routing store_id map
Each Shopify store is an independent checkout (Shopify, stores 2026). Without MSTRCART-MAP, agents confuse Markets and multi-store.
MSTRCART #803 vs Markets, marketplace, omnichannel POS and CARTCALC #801
Six contents, six distinct cart journeys.
Quick matrix
#803 MSTRCART: multi-store carts separate catalogs shipping availability
Shopify Markets: one shop countries distinct currencies separate stores
Marketplace: third-party sales channels distinct own shops
Omnichannel POS: POS online same inventory distinct multi-store
CARTCALC #801: total variance distinct calculation which store
#804 MSTRCARTbot: bot availability delivery by store tier 1
#803 = multiple Shopify stores. Markets = one shop, multiple countries.
Which mstrcart_* typologies should be classified?
Eight multi-store shopping cart ticket scenarios.
Eight mstrcart typologies
mstrcart_no_merge: impossible store cart merge map
mstrcart_wrong_store: order wrong store URL map
mstrcart_split_ship: separate deliveries multiple fees map
mstrcart_fee_diff: different shipping fees per store map
mstrcart_stock_scope: stock available store A not B map
mstrcart_url_confusion: which store to order from map
mstrcart_return_routing: return to which store CS map
mstrcart_account_scope: customer account valid on which store map
Tags: mstrcart, multi_store, cart_routing. STORE-ID-CITE: store_name store_url map only.
How to structure the MSTRCART-MAP matrix?
The MSTRCART-MAP matrix documents each shop for agents and future bot #804.
MSTRCART-MAP Columns
store_id: Shopify store identifier myshopify domain
store_name: public store name FR US outlet map
store_url: checkout store URL map
catalog_scope_copy: collections products this store only map
no_merge_cart_copy: cart merging impossibility map
split_ship_policy_copy: separate deliveries multi-order map
shipping_fee_by_store_copy: shipping fee policy by store map
stock_scope_copy: store's own inventory not shared map
return_store_routing_copy: after-sales service return store order map
account_scope_copy: customer account by store or SSO map
markets_reroute_copy: a distinct country shop multi-store map
bot_intent_map: bot_mstrcart_* #804 mapping
Sync ops sheet by store: shipping profiles, return address, helpdesk routing store_id tag.
MSTRCART-SUP policy in six rules
Six rules for multi-store basket support.
MSTRCART-MAP-GROUNDED: store response from map only
STORE-ID-CITE: store_name store_url cites each map response
NO-MERGE-CITE: no_merge_cart_copy cites if merge requested map
SPLIT-SHIP-CITE: split_ship_policy_copy if separate packages map
ORDER-LOOKUP-FIRST: verify order store_id before routing
MARKETS-REROUTE: one country shop → separate multi-store international guide
Flow MSTRCART MS-1 to MS-8
Flow agent eight steps multi-store cart.
MS-1 Intake: mstrcart_* intent + store_url order_ref product_url client_store_guess
MS-2 Store identify: store_id MSTRCART-MAP row from URL order shop domain
MS-3 Order lookup: Shopify order store_id verify catalog_scope stock
MS-4 Classify: no_merge wrong_store split_ship fee stock url return account
MS-5 Triage: STORE-ID NO-MERGE SPLIT-SHIP MARKETS CARTCALC return routing
MS-6 Respond: macro MSTRCART grounded store_name policy map
MS-7 Route action: redirect store_url cancel reorder return_store escalate ops
MS-8 Close: tag mstrcart_resolved store_id cited reroute Y/N
SLA: mstrcart_wrong_store answered STORE-ID-CITE + correct store_url in 15 min chat.
Essential MSTRCART macros
Four multi-store cart macro agents.
MSTRCART-STORE-01
"[store_name map] Store: [catalog_scope_copy map.] Order here: [store_url map.] STORE-ID-CITE."
MSTRCART-NOMERGE-01
"[no_merge_cart_copy map.] [store_A] and [store_B] products: two separate orders. Links: [store_url list map.] NO-MERGE-CITE."
MSTRCART-SPLITSHIP-01
"[split_ship_policy_copy map.] [shipping_fee_by_store_copy map.] Orders #[order_A] #[order_B] separate shipments. SPLIT-SHIP-CITE."
MSTRCART-RETURN-01
"Return order #[order_num] [store_name map] store: [return_store_routing_copy map.] Return address store_id [store_id map.]"
Edge cases: Account SSO, outlet, B2B, and total calculation
Five cases outside the standard multi-store macro.
Group SSO Account: account_scope_copy login cross-store map
Outlet different price: #247 distinct routing store catalogue
Total cart discrepancy: CARTCALC801-REROUTE breakdown by store
B2B pro store: pro catalogue distinct DTC store
Amazon Marketplace: third-party channel distinct from Shopify stores
Cart merge impossible = NO-MERGE-CITE. One Markets shop = MARKETS-REROUTE.
Essential mstrcart KPIs
Five MSTRCART steering metrics.
mstrcart_store_cite_rate: STORE-ID-CITE / total mstrcart tickets
mstrcart_wrong_store_recover: reorder correct store / total wrong_store
mstrcart_no_merge_ticket_rate: cart merge tickets / multi-store sales
mstrcart_markets_misroute: wrongly routed to Markets / total mstrcart target 0
mstrcart_first_response_sla: first response store identify min
Target: mstrcart_store_cite_rate 100% and mstrcart_markets_misroute 0.
MSTRCART anti-patterns
Five common mistakes with multi-store cart support.
Promising cart merging: NO-MERGE-CITE no_merge_cart_copy map
Confusing Markets with multi-store: MARKETS-REROUTE verify one shop vs several
Not citing the store: STORE-ID-CITE store_name store_url mandatory
Returning to the wrong store: return_store_routing_copy order store_id map
Assuming shared stock: stock_scope_copy own inventory store map
MSTRCART with Qstomy
Qstomy on Shopify: detect mstrcart intent, MSTRCART-MAP RAG grounded, store_id routing multi-shop, handoff #804 bot tier 1 or agents MS-7.
Pipeline: #804 bot available store tier 1 → #803 agents route return reorder.
Explore AI support and request a demo.
Checklist, FAQ and going further
MSTRCART Checklist (8 steps)
MSTRCART-MAP v1: one line per store_id catalog merge ship stock return account
Policy MSTRCART-SUP: 6 rules STORE-ID NO-MERGE SPLIT-SHIP LOOKUP MARKETS
8 typologies mstrcart_*: tags helpdesk multi_store store_id
4 macros MSTRCART-*: STORE NOMERGE SPLITSHIP RETURN
Helpdesk routing: store_id tag per boutique Gorgias views
Agent training 30 min: MSTRCART vs Markets one shop
Customer hub store picker: store_url links footer of each boutique
Dashboard KPI: mstrcart_* section 9 store_cite misroute sla
FAQ
Shopify Markets difference?
Markets = one shop multiple countries. #803 = multiple separate Shopify boutiques.
Merge two carts?
No. MSTRCART-NOMERGE-01 no_merge_cart_copy map. Two orders.
Two shipping fees?
MSTRCART-SPLITSHIP-01 split_ship_policy_copy shipping_fee_by_store_copy map.
Relation to #804 bot?
#804 = store delivery availability bot tier 1. #803 = agents routing return reorder.
Going further
Cart calculation (#801)
This week: index MSTRCART-MAP by store_id, sync multi_store helpdesk tags, test MSTRCART-NOMERGE-01 macro on scenario: FR + US boutique product merge impossible.
Enzo
July 1, 2026
