E-commerce
July 1, 2026
"What is included in the Standard version?" "Can I change the finish after ordering?" "The representative is talking about the configurator when I bought a fixed configuration." Three tickets where a poorly explained pre-configured product generates incorrect expectations, modification disputes, and confusion with incompatible options #483.
The e-commerce pre-configured products support covers included fixed options, SKU shipped according to the chosen variant, modification limits, and comparison vs. full configurator. Distinct from dynamic configurator #482: here, it is a product already configured with variants or fixed options on the PDP.
This guide #683 covers policy PRECFG-SUP, flow PC-1 to PC-8, and matrix PRECFG-MAP. Pair of the future CS bot PRECFG (#684).
Summary
Why do pre-configured products generate support tickets?
The brand sells a Standard gaming PC, a 2-seater Fixed model sofa, or a pre-assembled Phase 1 skincare routine. The customer chooses a limited variant on the PDP, not a full configurator. Without a SOP, the agent improvises on the included content, promises post-order modifications, or redirects to configurator #482 even though the SKU is a fixed map.
Five typical pre-configuration frictions
Vague inclusions: customer does not know the fixed map options
SKU received: which variant is shipped in the order map
Modification requested: changing an option after purchase map
Vs configurator: difference between Standard vs Custom map
Return exchange: preconfigured variant return policy map
Baymard reminds us that a multi-option product without clarification on what is included drives an additional 12% to 18% of abandonment (Baymard, PDP 2025).
PRECFG #683 vs configurator #482, INCOMPAT #483, bundle #97 and bot #684
Five contents, five distinct configuration models.
Quick matrix
#683 PRECFG: fixed options included SKU limited variant explain
Bot config #482: dynamic configurator guidance customer choice
INCOMPAT #483: blocked options impossible combo configurator
Bundle #97: help choice pack vs single pre-purchase distinct fixed
#684 PRECFGbot: bot explain included editable handoff
#482 = customer composes options. #683 = fixed config chosen from limited PDP variants.
Which pre_cfg_* typologies should be classified?
Eight pre-configured product ticket scenarios.
Eight pre_cfg typologies
pre_cfg_whats_included: what fixed options are included map
pre_cfg_whats_fixed: what is not modifiable map
pre_cfg_which_sku: shipped variant SKU order map
pre_cfg_vs_custom: difference vs full configurator map
pre_cfg_compare_variants: Standard vs Premium diff map
pre_cfg_change_request: modify option post-order map
pre_cfg_post_order_edit: edit possible before shipping map
pre_cfg_return_exchange: return exchange variant policy map
Tags: pre_cfg, preconfigured, fixed_config. ORDER-API-CITE: sku variant order lookup.
How to structure the PRECFG-MAP matrix?
The PRECFG-MAP matrix documents each pre-configured product for agents and future bot #684.
PRECFG-MAP Columns
precfg_program_id: preconfig map program identifier
preconfigured_skus: Standard Premium variant SKUs map
fixed_options_copy: included fixed options map
variant_options_available: limited PDP choices map
whats_included_copy: customer included content map
whats_not_modifiable_copy: non-modifiable map
sku_assignment_rules: chosen variant shipped SKU map
compare_to_custom_copy: vs custom configurator map
change_policy_post_order: post-purchase modification map
return_policy_preconfigured: variant return / exchange map
incompat483_reroute_policy: custom combo → #483 map
customer_communication_copy: fixed config statement map
Sync PDP variant comparison table, product spec sheet included, helpdesk macros, and dashboard pre_cfg_sku_clarity_rate.
PRECFG-SUP policy in six rules
Six pre-configured product support rules.
PRECFG-MAP-GROUNDED: includes fixed options from map only
ORDER-API-CITE: sku variant order API before which_sku respond
INCLUDED-CITE: whats_included_copy fixed_options cite map only
NO-MODIFY-PROMISE: whats_not_modifiable change_policy map before edit promise
CFGBOT482-REROUTE: dynamic configurator → #482 CFGBOT distinct fixed
INCOMPAT483-REROUTE: blocked custom combo → #483 INCOMPAT distinct fixed
Flow PRECFG PC-1 to PC-8
Eight-step pre-configured product agent flow.
PC-1 Intake: pre_cfg_* intent + sku variant question order_ref
PC-2 PRECFG-MAP: included fixed compare change return reroutes
PC-3 Order lookup: email order API preconfigured_skus variant
PC-4 Classify: included fixed sku compare change edit return
PC-5 Policy triage: INCLUDED NO-MODIFY CFGBOT INCOMPAT reroute
PC-6 Respond: macro PRECFG grounded map customer_communication_copy
PC-7 Execute: ops edit exception return exchange escalate product
PC-8 Close: tag pre_cfg_resolved variant_sku clarity Y/N
SLA: pre_cfg_whats_included answered with whats_included_copy INCLUDED-CITE in one interaction.
Essential PRECFG macros
Four pre-configuration macro agents.
PRECFG-INCLUDED-01
« Variant [preconfigured_skus map] : included [whats_included_copy map]. Fixed options [fixed_options_copy map]. [customer_communication_copy map]. INCLUDED-CITE map only. »
PRECFG-FIXED-01
« Non-modifiable : [whats_not_modifiable_copy map]. Post-order modification : [change_policy_post_order map]. NO-MODIFY-PROMISE. [If custom-made : compare_to_custom_copy map CFGBOT482-REROUTE.] »
PRECFG-SKU-01
« Order [order_ref API] : variant [chosen variant] SKU [sku_assignment_rules map]. ORDER-API-CITE. [If comparing Standard Premium : variant_options_available map.] »
PRECFG-RETURN-01
« Return exchange preconfigured variant : [return_policy_preconfigured map]. Exchange to another variant [variant_options_available map] subject to stock. »
Edge cases: CFG error #481, MANPERS #597, PRODUPD #671 and color #449
Five cases outside the standard pre-configuration macro.
Post-order config error: #481 CFG-FLOW edit pre-fabrication distinct fixed PDP
Manual customization: #597 MANPERS human validation distinct fixed options
Variant product revision: #671 PRODUPD version SKU distinct fixed choice
Pending rendering color: #449 COLOR fixed variant distinct included
Customer wants custom combo: INCOMPAT483-REROUTE #483 or CFGBOT482 configurator
Preconfig = limited fixed SKU. Configurator #482 = customer composes. Error #481 = incorrect config passed to ops.
Essential pre_cfg KPIs
Five PRECFG steering metrics.
pre_cfg_sku_clarity_rate: which_sku responded ORDER-CITE / pre_cfg_which_sku
pre_cfg_included_cite_rate: INCLUDED-CITE / pre_cfg_whats_included
pre_cfg_modify_misroute_rate: edit promise out of policy / total target 0
pre_cfg_cfgbot_misroute_rate: routed #482 on landline / total low target
pre_cfg_return_exchange_rate: variant return / preconfig sales
Target: pre_cfg_included_cite_rate greater than 95% and pre_cfg_modify_misroute_rate 0.
PRECFG anti-patterns
Five common errors in pre-configuration support.
Invented included: INCLUDED-CITE whats_included_copy map only
Promise modification: NO-MODIFY-PROMISE change_policy_post_order map
Confusing configurator #482: CFGBOT482-REROUTE fixed distinct dynamic
Confusing INCOMPAT #483: combo blocked distinct fixed variant chosen
SKU without order lookup: ORDER-API-CITE sku_assignment_rules map
PRECFG with Qstomy
Qstomy on Shopify: detect pre_cfg intent, PRECFG-MAP RAG grounded, order variant SKU lookup, INCLUDED FIXED cite, handoff #684 bot explain tier 1 edit escalate.
Pipeline: #684 bot included compare tier 1 → #683 agents edit return CFG481 INCOMPAT483 escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
PRECFG Checklist (8 steps)
PRECFG-MAP v1: included fixed compare change return reroutes
Policy PRECFG-SUP: 6 rules INCLUDED NO-MODIFY reroutes
8 typologies pre_cfg_*: tags helpdesk preconfigured
4 macros PRECFG-*: INCLUDED FIXED SKU RETURN
PDP variant table: whats_included compare Standard Premium sync
Order variant metafield: sku_assignment_rules API agents
Agent training 30 min: PRECFG vs #482 vs #483 vs #97
KPI Dashboard: pre_cfg_* section 9 included_cite
FAQ
Difference with configurator #482?
#482 = customer composes dynamic options. #683 = limited fixed variant chosen on PDP.
Modify after order?
PRECFG-FIXED-01 change_policy_post_order map. Exception → PC-7 ops or #481 CFG.
Which SKU received?
PRECFG-SKU-01 sku_assignment_rules map ORDER-API-CITE.
Relation with #684 bot?
#684 = bot explain included editable tier 1. #683 = agents edit return escalate.
Going further
Config error (#481)
This week: index PRECFG-MAP active variants, PDP table included audit, PRECFG-INCLUDED-01 agent macro test.
Enzo
July 1, 2026
