E-commerce
July 1, 2026
"I paid, why is my order blocked?" "My prescription is rejected without explanation." "Support is asking me for medical details in the chat." Three tickets where an ill-defined pre-validation flow blocks sales, violates privacy, or creates a refund dispute.
The e-commerce pre-validation support covers prescriptions, medical questionnaires, or operations approval before shipping. Distinct from regulated #119: here, purchase gate, document validation, status queue, not product claim.
This guide #609 covers policy PRESCVAL-SUP, flow PV-1 to PV-8, and matrix PRESCVAL-MAP. A new pre-sale compliance vertical. Future support pair with bot PRESCVAL (#610).
Summary
Why does pre-validation generate tickets?
The customer pays, then discovers that the order is pending validation. They do not know what to send, how long to wait, or why a pharmacist or an ops agent rejects their file. Support becomes an improvised medical relay.
Five typical frictions in prior validation
Opaque blocked order: paid without visible validation status
Unclear prescription upload: photo format, PDF, expiration delay
Rejection without a clear reason: rejection without a rejection_reasons map
SLA exceeded: validation_sla_hours exceeded without any updates
Sensitive data in chat: agent requests complete medical history
The GDPR treats health data as a sensitive category: minimal collection and clear purpose are mandatory (CNIL, health data 2026). Without PRESCVAL-MAP, agents approve prescriptions or promise shipping outside the validation queue.
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
PRESCVAL #609 vs regulated #119, complements #SUPP, age #543 and bot #610
Five contents, five distinct product compliance layers.
Quick Matrix
#609 PRESCVAL: prescription questionnaire pre-sale validation queue status
#119 REG: health claims disclaimers product advice
SUPP Supplements: advice on choosing non-prescription supplements
#610 PRESCVALbot: tier 1 bot inform without sensitive data
#119 = what we say about the product. #609 = gate before shipping prescription or map questionnaire.
Which prescval_* typologies should be classified?
Eight scenarios for pre-validation tickets.
Eight prescval typologies
prescval_how_it_works: customer does not understand pre-purchase validation flow
prescval_eligibility: product requires prescription or questionnaire
prescval_upload_submit: how to send prescription document
prescval_status_pending: order blocked pending validation status
prescval_approved_ship: validation OK when shipping
prescval_rejected: prescription rejected reason resubmission
prescval_expired_invalid: rx expired illegible out of scope
prescval_refund_cancel: refund if rejected or abandoned
Tags: prescval, rx_validation, pre_sale_gate. PRESCVAL-MAP-GROUNDED: validation status from queue only.
How to structure the PRESCVAL-MAP matrix?
The PRESCVAL-MAP matrix documents each SKU or category subject to prior validation for agents and future bot #610.
PRESCVAL-MAP Columns
sku_or_category: SKU or gate validation category
validation_type: prescription_required medical_questionnaire prior_approval
required_documents: rx_pdf photo questionnaire fields
validation_provider: in_house pharmacy partner third_party
validation_sla_hours: processing time for business days
rejection_reasons: list of authorized rejection motives for agents
resubmit_rules: new upload, max attempts window
order_hold_until_approved: Y/N shipment blocked
refund_if_rejected: refund policy if definitively rejected
privacy_notice_url: health data processing info
customer_copy: customer phrasing PDP checkout gate
escalate_compliance: Y handoff DPO legal pharmacist
Sync validation portal, Shopify order hold tag, secure upload URL and helpdesk macros. Audit: customer_copy visible on PDP before payment.
PRESCVAL-SUP policy in six rules
Six rules support prior validation.
PRESCVAL-MAP-GROUNDED : validation_type SLA documents from map only
VALIDATION-QUEUE-VERIFY : lookup queue before status approved rejected cite
NO-APPROVE-AGENT : agent never approves prescription pharmacist ops only
NO-MEDICAL-ADVICE : no diagnosis advice treatment refer to healthcare pro
PRIVACY-MIN-DATA : no medical history chat redirect upload secure
REG119-REROUTE : product efficacy claim → #119 REG distinct gate
Flow PRESCVAL PV-1 to PV-8
Flow agent eight-step prior validation.
PV-1 Intake: prescval_* intent + email order_ref SKU question
PV-2 SKU lookup: PRESCVAL-MAP validation_type documents SLA
PV-3 Queue verify: portal validation API file status
PV-4 Classify: how eligibility upload status reject refund
PV-5 Respond: macro PRESCVAL grounded map customer_copy
PV-6 Execute: resend upload link refund cancel escalate pharmacy
PV-7 Document: validation_id status note without copying rx chat
PV-8 Close: tag prescval_resolved sku_or_category
SLA: prescval_status_pending answered with actual queue status and validation_sla_hours map in one interaction.
Essential PRESCVAL macros
Four pre-validation agent macros.
PRESCVAL-EXPLAIN-01
"Product [SKU]: [customer_copy map]. Validation required: [validation_type]. Documents: [required_documents]. Deadline: [validation_sla_hours] working hours. Order on hold until approved: [order_hold_until_approved map]. Upload: [secure_upload_url]."
PRESCVAL-STATUS-01
"Order [order_ref] file [validation_id]: status [pending / in_review / approved / rejected queue API]. [If pending: processing within [validation_sla_hours] h.] [If approved: shipping [expected date].] [If rejected: PRESCVAL-REJECT-01.]"
PRESCVAL-REJECT-01
"File [validation_id] rejected: [rejection_reasons map exact reason]. [If resubmit_rules: resubmission possible before [deadline] via [upload_url].] [If refund_if_rejected: refund [policy map timeframe].] We are not healthcare professionals: consult your doctor if needed."
PRESCVAL-UPLOAD-01
"Prescription upload [order_ref]: [required_documents map photo PDF format]. Secure link: [upload_url]. [If privacy: [privacy_notice_url].] Do not share your complete medical data via chat: use the portal."
Edge cases: medical questionnaire, partner pharmacy, B2B, and returns
Five cases outside standard macro-validation.
Medical questionnaire only: medical_questionnaire without rx upload form map
Partner pharmacy dispute: escalate_compliance validation_provider handoff
B2B pro account: separate pro cart approval individual rx
Health product advice: REG119-REROUTE #119 disclaimers
Post-validation return: separate return policy pre-sale gate
Pre-sale validation ≠ product usage advice. Reroute #119 if the customer asks about treatment efficacy.
Essential prescval KPIs
Five PRESCVAL steering metrics.
prescval_ticket_rate: prescval_* tickets / gate SKU orders
prescval_status_sla_rate: % of status answered with actual queue
prescval_reject_resubmit_rate: rejected then resubmitted approved
prescval_refund_after_reject_rate: refund_if_rejected executed
prescval_privacy_violations: health data chat audit target 0
Target: prescval_privacy_violations 0 and prescval_status_sla_rate greater than 95% with API sync queue.
PRESCVAL Anti-patterns
Five common errors during pre-validation support.
Approve agent prescription: NO-APPROVE-AGENT pharmacist ops only
Invented status: VALIDATION-QUEUE-VERIFY queue first
Cat health data: PRIVACY-MIN-DATA upload secure redirect
Medical advice: NO-MEDICAL-ADVICE refer to doctor pharmacist
Rejection without map reason: rejection_reasons cite PRESCVAL-REJECT-01
PRESCVAL with Qstomy
Qstomy on Shopify: detect prescval intent, PRESCVAL-MAP RAG grounded, validation queue lookup, upload link cite, handoff #610 bot tier 1 privacy-safe.
Pipeline: #609 agents reject refund escalate pharmacy → #610 bot explain upload handoff.
Explore AI support and request a demo.
Checklist, FAQ and going further
PRESCVAL Checklist (8 steps)
PRESCVAL-MAP v1: SKUs gate validation_type SLA documents
PRESCVAL-SUP Policy: 6 NO-APPROVE-AGENT rules
8 prescval_* typologies: helpdesk tags
4 PRESCVAL-* macros: EXPLAIN STATUS REJECT UPLOAD
PDP checkout gate visible: customer_copy before payment
Secure upload portal: helpdesk API queue sync
Agent training 30 min: PRIVACY-MIN-DATA quiz
KPI Dashboard: prescval_* section 9
FAQ
Difference with regulated #119?
#119 = health claims product advice. #609 = prescription gate questionnaire before shipping.
Can an agent approve a prescription?
No. NO-APPROVE-AGENT. validation_provider queue decision.
Can a client send rx via chat?
No. PRIVACY-MIN-DATA redirect to secure PRESCVAL-UPLOAD-01.
Relationship with #610 bot?
#610 = tier 1 bot explain without sensitive data. #609 = agents reject refund escalate.
Going further
This week: index PRESCVAL-MAP gate SKUs, audit PDP checkout customer_copy, test macro PRESCVAL-STATUS-01 with API queue.
Enzo
July 1, 2026
