E-commerce

How to manage customer inquiries about pre-order availability by variant

How to manage customer inquiries about pre-order availability by variant

July 1, 2026

"I ordered size M on pre-order, but the site now shows S available immediately." "My color is delayed while the other is shipped." "Can I change my variant without canceling?" Three tickets where an ill-explained pre-order by variant creates confusion, delays, and chargebacks.

The pre-order variant availability support covers different ETAs by size, color or format, mixed pre-order plus in-stock inventory, variant changes, and split carts. This is distinct from global pre-order (#187): here, we deal with SKU variant granularity and heterogeneous lead times.

This guide #551 covers policy VARPRE-SUP, flows VP-1 to VP-8, and the matrix VARPRE-MAP. It completes pre-order and variants. Paired with customer service of the future VARPRE bot (#552).

Summary

Why does pre-ordering by variant generate tickets?

A product can have size S in stock and M on July pre-order. The customer reads "available" on the product page without seeing the selected variant. The agent quotes a global product date instead of the ETA of the ordered variant.

Five typical frictions

  • Variant ETA: M lead time ≠ L lead time on the same PDP

  • Mixed stock: one color ships now, another is pre-order

  • Variant change: swapping size/color before production

  • Split cart: line items with different fulfillment statuses

  • PDP display: pre-order badge missing on the affected variant

Shopify points out that availability is expressed at the variant level, not just the parent product (Shopify, variants 2026). Customer service must quote the ETA per ordered SKU.

VARPRE #551 vs pre-order #187, variants and bot #552

Five contents, five levels of stock granularity.

Quick matrix

#187 = general preorder policy. #551 = zoom stock ETA by variant and SKU change before ship.

Which varpre_* typologies should be classified?

Eight variant preorder ticket scenarios.

Eight varpre typologies

  1. varpre_eta_variant: when will my size/color be shipped

  2. varpre_stock_mixed: stock vs preorder variant of the same product

  3. varpre_swap_variant: change size/color before shipping

  4. varpre_cancel_one_line: cancel one variant and keep the others

  5. varpre_pdp_mismatch: site says available but preorder at checkout

  6. varpre_delay_one_variant: delay on one variant only

  7. varpre_split_shipment: one variant shipped, the other pending

  8. varpre_availability_check: which variant is available when

Tags: varpre, preorder_variant, variant_eta. VARPRE-MAP-GROUNDED: ETA from variant map, never parent product date.

How to structure the VARPRE-MAP matrix?

The VARPRE-MAP matrix documents availability by SKU variant for agents and future bot #552.

VARPRE-MAP Columns

  • variant_sku: size color size SKU

  • availability_type: in_stock preorder backorder sold_out

  • eta_ship_date: variant ISO shipping date

  • eta_window: week range of if uncertain

  • swap_allowed: yes no cutoff date

  • cancel_line_allowed: cancellation of single line policy

  • pdp_badge: PDP checkout variant badge text

  • bot_intent_map: bot_varpre_* #552 mapping

Sync PreProduct variant metafields or preorder app, dynamic PDP and helpdesk macros. Weekly audit of 5 preorder SKUs.

VARPRE-SUP six-rule policy

Six rules supporting pre-order variants.

  1. VARPRE-MAP-GROUNDED: ETA quotes ordered variant only

  2. NO-PARENT-ETA: never global product date if variant differs

  3. SWAP-CUTOFF: variant change before cutoff map

  4. SPLIT-TRANSPARENT: explicit status per line item

  5. DELAY-VARIANT-SCOPE: announced delay affects ordered variant only

  6. MIXED-STOCK-CLEAR: distinguish immediate stock vs preorder

Flow VARPRE VP-1 to VP-8

Flow agent eight steps pre-order variant.

  1. VP-1 Intake: varpre_* intent + order line variant

  2. VP-2 Line lookup: SKU variant ordered fulfillment status

  3. VP-3 VARPRE-MAP: availability eta swap cancel rules

  4. VP-4 Classify: eta swap delay split availability

  5. VP-5 Respond: macro VARPRE grounded variant SKU

  6. VP-6 Swap execute: SWAP-CUTOFF edit line if authorized

  7. VP-7 Split notify: partial tracking other lines

  8. VP-8 Close: tag varpre_resolved variant_sku

SLA: varpre_eta_variant answered with eta_ship_date map and pdp_badge in one interaction.

Essential VARPRE macros

Four macro agents.

VARPRE-ETA-01

"Variant [variant_label] SKU [sku]: preorder, estimated shipping [eta_ship_date]. Other variants: [availability_summary map]. Order #[order_num] status [fulfillment_line]."

VARPRE-SWAP-01

"Change to [new_variant]: [authorized before [swap_cutoff] / denied production started]. [If authorized: confirmed, new ETA [new_eta].] [If denied: line cancellation or wait according to policy #187]."

VARPRE-SPLIT-01

"Order #[order_num] partial shipment: [variant_shipped] shipped [tracking]. [variant_preorder] preorder, ship [eta_ship_date]. Two separate notifications."

VARPRE-DELAY-01

"Delay variant [variant_label]: new ETA [new_eta], reason [reason]. Other lines unaffected. Options: wait, swap if [swap_allowed], cancel line."

Edge cases: mixed cart, color, and made-to-order

Five cases outside the standard ETA macro.

Made-to-order variant: workshop production ETA, not product launch date. Distinct tag varpre vs mto.

Essential KPI variants

Five VARPRE steering metrics.

  • varpre_ticket_rate: variant tickets / preorder SKU orders

  • varpre_eta_accuracy: % variant ETA respected vs map

  • varpre_swap_success: variant changes before cutoff

  • varpre_pdp_mismatch_rate: display vs checkout tickets

  • varpre_split_clarity: partial variant shipment CSAT

Target: varpre_eta_accuracy higher than 90% on multi-variant preorder drop cohorts.

VARPRE anti-patterns

Five common mistakes.

  1. Parent product ETA: NO-PARENT-ETA

  2. Swap after cutoff: SWAP-CUTOFF

  3. Global order status: SPLIT-TRANSPARENT line item

  4. Unscoped variant delay: DELAY-VARIANT-SCOPE

  5. Confusing stock and preorder: MIXED-STOCK-CLEAR

VARPRE with Qstomy

Qstomy on Shopify: detect varpre intent, line item variant lookup, VARPRE-MAP RAG eta cite, split status by SKU, swap cutoff guardrail, handoff #552 bot tier 1.

Pipeline: #551 agents swap delay → #552 bot ETA variant tier 1.

Explore AI support and request a demo.

Checklist, FAQ and going further

VARPRE Checklist (8 steps)

  1. VARPRE-MAP v1: ETA swap badge by variant SKU

  2. VARPRE-SUP Policy: 6 NO-PARENT-ETA rules

  3. 8 varpre_* typologies: helpdesk tags

  4. 4 VARPRE-* macros: ETA SWAP SPLIT DELAY

  5. PDP variant badges: preorder vs dynamic in stock

  6. Agent sidebar line item: variant SKU eta fulfillment

  7. 30 min agent training: mixed stock scenario

  8. KPI Dashboard: varpre_* section 9

FAQ

Difference #187?
#187 = global preorder delay cancellation. #551 = ETA and swap by variant.

Change size on preorder?
VARPRE-SWAP-01 if SWAP-CUTOFF map allows.

One variant shipped, the other not?
VARPRE-SPLIT-01 status by line item.

Bot #552 sufficient?
Tier 1 ETA quotes. Swap delay execution u2192 agents #551.

Going further

This week: document VARPRE-MAP 10 top preorder SKUs, test VARPRE-ETA-01 size M scenario, measure varpre_pdp_mismatch_rate.

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.