E-commerce
July 1, 2026
"What is this €2.99 service fee?" "Why pay extra when delivery is already charged?" "No one asked for gift wrapping, why is it checked?" Three tickets where an ill-explained service fee fuels cart abandonment, chargebacks, and post-purchase disputes.
The e-commerce service fee support covers platform fees, order processing, checkout options, and minimum order surcharges. Distinct from handling #410 and shipping #204: here, it is about service fees or order options, not transport or warehouse preparation.
This guide #715 covers policy SVCFEE-SUP, flow SF-1 to SF-8, and matrix SVCFEE-MAP. Pair of CSU of the future bot SVCFEE (#716).
Summary
Why do service fees generate tickets?
The brand adds checkout service fees, small cart surcharges, or a gift wrap option checked by default. The client sees a distinct "service fee", "processing fee", or "premium packaging" line separate from shipping. They confuse this with delivery or handling, contest it post-purchase, or abandon checkout.
Five typical service fee frictions
Misunderstood utility: what is this map fee used for
Shipping and handling confusion: perceived triple billing map
Option checked by default: gift wrap insurance opt-out map
Small cart surprise: minimum order fee below threshold map
Fee-only refund: post-purchase refund request map
Baymard estimates that 48% of cart abandonments are linked to unexpected perceived additional costs (Baymard, Cart Abandonment 2026). Without SVCFEE-MAP, support and checkout diverge on what each fee line covers.
SVCFEE #715 vs handling #410, port #204, bot #411 and bot #716
Six contents, six distinct checkout fee types.
Quick Matrix
#715 SVCFEE: checkout option service fee, calculated utility, opt-out
Handling #410: oversize fragile warehouse preparation, separate service
Shipping #204: carrier shipping rate, separate service fee
Fee Bot #411: global cart breakdown, separate playbook customer service
Hidden Fees #291: ops view abandonment, separate service typology
#716 SVCFEEbot: bot to explain calculation purpose, tier 1 alternatives
#410 = warehouse handling. #715 = platform service fee or order option, transparency and customer service agents.
Which svcfee_* typologies should be classified?
Eight service fee ticket scenarios.
Eight svcfee typologies
svcfee_why_charged : what is the purpose of this fee map
svcfee_vs_shipping : difference between shipping, service, and handling map
svcfee_checkout_surprise : discovered at shopping cart map
svcfee_opt_out : remove gift wrap / insurance option map
svcfee_small_order : surcharge below minimum order value map
svcfee_refund_request : refund fee only post-purchase map
svcfee_pdp_missing : fee not displayed on product detail page map
svcfee_waive_request : request to waive fee as a goodwill gesture map
Tags: svcfee, service_fee, checkout_fee. PURPOSE-CITE: purpose_explanation_copy map only.
How to structure the SVCFEE-MAP matrix?
The SVCFEE-MAP matrix documents each service fee for agents and future bot #716.
SVCFEE-MAP Columns
svcfee_program_id: service fee map identifier
fee_type: platform processing gift_wrap insurance small_order map
amount_rule: flat pct threshold map
trigger_rule: order subtotal option selected default_on map
purpose_explanation_copy: what this fee map is used for
opt_out_path: uncheck portal checkout steps map
refund_policy: refundable Y/N conditions map
pdp_display_copy: product page badge map
customer_communication_copy: macro checkout email map
bot_intent_map: bot_svcfee_* #716 mapping
Sync Shopify checkout extensions, apps fee line item and helpdesk macros. Legal audit if default_on option.
SVCFEE-SUP policy in six rules
Six rules support service fee.
SVCFEE-MAP-GROUNDED : amount purpose opt-out from map only
PURPOSE-CITE : purpose_explanation_copy cite map verbatim
FEE-BREAKDOWN : distinguish between service port #204 handling #410
OPT-OUT-CITE : opt_out_path cite if svcfee_opt_out map
REFUND-POLICY-CITE : refund_policy cite map only
HAND410-LINK : handling → #410 HANDLING distinct service fee
SVCFEE flow SF-1 to SF-8
Service fee agent flow eight steps.
SF-1 Intake: svcfee_* intent + order_ref cart screenshot
SF-2 SVCFEE-MAP: fee_type amount purpose opt-out refund
SF-3 Order lookup: Shopify order line items fee breakdown verify
SF-4 Classify: why vs_shipping opt_out refund waive surprise
SF-5 Triage: PURPOSE FEE-BREAKDOWN OPT-OUT REFUND HAND410
SF-6 Respond: macro SVCFEE grounded customer_communication_copy
SF-7 Execute: refund exception waive ops redirect #410
SF-8 Close: tag svcfee_resolved purpose_cited refund Y/N
SLA: svcfee_why_charged answered with PURPOSE-CITE purpose_explanation_copy in one interaction.
Essential SVCFEE macros
Four service fee macro agents.
SVCFEE-PURPOSE-01
"Fee [svcfee_program_id map] [amount_rule map]: [purpose_explanation_copy map verbatim.] Distinct from shipping and handling. PURPOSE-CITE."
SVCFEE-BREAKDOWN-01
"Order [order_ref]: Products [subtotal] € · Shipping [shipping] € · Handling [handling si map] € · Service [service fee map] € · Total [total] €. FEE-BREAKDOWN."
SVCFEE-OPT-01
"Remove [fee_type map]: [opt_out_path map checkout steps.] Before payment only if order not shipped. OPT-OUT-CITE."
SVCFEE-REFUND-01
"Fee refund: [refund_policy map.] [If eligible agent exception: conditions.] REFUND-POLICY-CITE."
Edge cases: handling, storage, assembly, and bot #411
Five cases outside the standard macro service fee.
Warehouse handling: HAND410-LINK #410 handling oversize fragile
Refundable deposit fee: #412 DEP distinct fee service non-refundable
Delivery assembly: #290 bulky assembly fee distinct platform service
Breakdown checkout bot: #411 bot cart reroute if pre-purchase
Checkout taxes: #758 taxes distinct service fee option
Triple line shipping + handling + service = SVCFEE-BREAKDOWN-01 itemized mandatory.
Essential service fee KPIs
Five SVCFEE management metrics.
svcfee_purpose_cite_rate: PURPOSE-CITE / total svcfee_why_charged
svcfee_breakdown_cite_rate: FEE-BREAKDOWN / svcfee_vs_shipping surprise
svcfee_refund_rate: refund fee only / total svcfee tickets
svcfee_checkout_surprise_rate: surprise / orders with active service fee
svcfee_waive_rate: waive agent exception / svcfee_waive_request
Target: svcfee_purpose_cite_rate greater than 95% and svcfee_checkout_surprise_rate decreasing post-PDP badge.
SVCFEE anti-patterns
Five common service charge support errors.
Confusing port and service: FEE-BREAKDOWN itemized map
Invented utility: PURPOSE-CITE purpose_explanation_copy map only
Promising refund outside policy: REFUND-POLICY-CITE map
Ignoring opt-out: OPT-OUT-CITE opt_out_path map
Rerouting handling as service: HAND410-LINK #410 distinct
SVCFEE with Qstomy
Qstomy on Shopify: detect svcfee intent, SVCFEE-MAP RAG grounded, purpose breakdown cite, opt-out guide, handoff #716 bot tier 1.
Pipeline: #716 bot explain service fee tier 1 → #715 agents refund exception redirect #410.
Explore AI Support and request a demo.
Checklist, FAQ and going further
SVCFEE Checklist (8 steps)
SVCFEE-MAP v1 : fee types amount purpose opt-out refund
Policy SVCFEE-SUP : 6 rules PURPOSE FEE-BREAKDOWN OPT-OUT
8 typologies svcfee_* : tags helpdesk service_fee checkout
4 macros SVCFEE-* : PURPOSE BREAKDOWN OPT REFUND
Checkout disclosure : fee visible before payment default_off audit
Page /pages/fees : table service vs port vs handling
Agent training 30 min : SVCFEE vs #410 vs #204 vs #411
Dashboard KPI : svcfee_* section 9 purpose_cite surprise
FAQ
Difference oversize handling #410?
#410 = warehouse preparation oversize. #715 = platform service fee or order option.
Difference bot #411?
#411 = bot breakdown global cart pre-checkout. #715 = playbook CS agents service fee post-purchase.
Refund the fee alone?
SVCFEE-REFUND-01 refund_policy REFUND-POLICY-CITE map.
Relation to #716 bot?
#716 = bot explain calculation utility tier 1. #715 = agents refund exception waive redirect #410.
Going further
This week: index SVCFEE-MAP active fees checkout, sync PDP badge purpose_explanation_copy, test macro SVCFEE-BREAKDOWN-01 agents triple line.
Enzo
July 1, 2026
