E-commerce
July 1, 2026
“I ordered with a custom logo, and no one contacted me to validate it.” “My file was rejected without explanation.” “Can I change the text before you start production?” Three tickets where poorly managed manual customization blocks the order and creates pre-production anxiety.
The e-commerce manual customization support covers incomplete submission, human validation status, pre-approval modification, file rejection, and ops review delay. Distinct from failed customization (#417) and auto-validation bot (#418): here, human intervention is mandatory before manufacturing.
This guide #597 covers policy MANPERS-SUP, flow MP-1 to MP-8, and matrix MANPERS-MAP. Completes automated customization. Pairs with the future customer service MANPERS bot (#598).
Summary
Why does manual personalization generate tickets?
Some orders require human validation: logo upload, complex text, custom requests outside the configurator. The customer pays and then waits for an invisible green light. Without a clear review status, each day without news becomes a ticket.
Five typical manual validation frictions
Incomplete submission: missing logo file or incorrect format
Vague review status: pending validation for X days
Pre-approval modification: changing logo text before production
Rejection without guidance: file rejected due to DPI or unclear copyright
Post-approval delay: validated but production not scaled up yet
Shopify notes that line item properties and customization apps carry personal data, but human validation remains outside the automated checkout (Shopify, order properties 2026). Without MANPERS-MAP, agents promise lead times or accept changes outside the ops workflow.
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
MANPERS #597 vs failed custom #417, validation bot #418, CFGERR #481 and bot #598
Five contents, five distinct customization moments.
Quick matrix
#597 MANPERS: human validation pre-production submission rejection modification
Failed Perso #417: incident post-delivery remake dispute
Bot validation #418: tier 1 bot auto-validation pre-purchase
CFGERR #481: config correction post-order before manufacturing
#598 MANPERSbot: bot status review file collection handoff
#418 = auto validation checkout. #597 = human ops review mandatory before starting production.
Which typologies of manpers_* to classify?
Eight manual personalization ticket scenarios.
Eight manpers typologies
manpers_submit_incomplete : missing info file incomplete submission
manpers_review_status : status of human validation delay
manpers_change_request : modify logo text before approval
manpers_rejected : personalization rejected due to policy
manpers_approved_delay : approved but production not started
manpers_file_format : incorrect format vector DPI required
manpers_complex_quote : custom request human quote required
manpers_cancel_pre_approval : cancel before validation completed
Tags: manpers, manual_perso, human_review. MANPERS-MAP-GROUNDED: review_sla rejection_rules from map only.
How to structure the MANPERS-MAP matrix?
The MANPERS-MAP matrix documents each manual customization type for agents and future bot #598.
MANPERS-MAP Columns
perso_type_id: logo_upload custom_text complex_design
review_required: yes always human ops design
review_sla_hours: validation team SLA working hours map
file_requirements: format DPI vector PNG min size
rejection_rules: copyright blurry forbidden text reasons
change_window_policy: modification allowed before approved status
approval_notification: proof email customer portal flow
escalation_ops: contact design ops queue
production_hold_tag: Shopify tag hold until approved
Sync Notion review queue, Shopify order tags, proof email flow and design ops sheet. Audit: review_sla displayed PDP checkout confirmation.
MANPERS-SUP policy in six rules
Six rules support manual personalization.
MANPERS-MAP-GROUNDED: sla rejection change from map only
REVIEW-STATUS-VERIFY: lookup queue ops before cite status
NO-APPROVE-AGENT: agent does not approve personalization outside ops design
CHANGE-WINDOW-SCOPE: modification according to change_window_policy map
REJECTION-CITE-RULES: rejection cite rejection_rules file_requirements map
POST-DELIVERY-REROUTE: failed personalization received → #417 PERSO-FLOW
Flow MANPERS MP-1 to MP-8
Flow agent eight steps manual personalization.
MP-1 Intake: manpers_* intent + order_ref text file
MP-2 Type lookup: MANPERS-MAP perso_type review sla rules
MP-3 Order verify: Shopify properties tags hold status
MP-4 Queue check: ops review queue status pending approved rejected
MP-5 Classify: incomplete status change rejected delay cancel
MP-6 Respond: macro MANPERS grounded map
MP-7 Execute: request file change escalate ops cancel hold release
MP-8 Close: tag manpers_resolved perso_type_id
SLA: manpers_review_status answered with real queue status in one interaction.
Essential MANPERS macros
Four manual validation agent macros.
MANPERS-STATUS-01
« Order [order_ref] personalization [perso_type_id]: status [pending review / approved / rejected / production started]. [If pending: delay [review_sla_hours map] business hours since submission.] [If approved: production launched within [production_sla].] Ops queue: [escalation_ops if delayed.] »
MANPERS-FILE-01
« Personalization file [order_ref]: [incomplete / rejected / OK]. [If rejected: cause [rejection_rules map].] Requirements: [file_requirements map DPI format]. Sent: [upload_url map email ops]. »
MANPERS-CHANGE-01
« Modification [order_ref]: [authorized / rejected]. [If authorized: change_window_policy map procedure.] [If already approved: production launched contact [escalation_ops].] New file text: [upload_url]. »
MANPERS-REJECT-01
« Personalization [order_ref] rejected: [rejection_rules map cause]. [If correctable: resubmit compliant file [file_requirements].] [If not correctable: alternatives [standard SKU / refund policy].] Resubmission deadline: [review_sla_hours]. »
Edge cases: MTO, engraving, order edit, and failed personalization
Five cases outside of standard manual macro-validation.
Made-to-order delay: MTO #288 production timeline distinct review
Post-delivery engraving dispute: POST-DELIVERY-REROUTE #489 ENGR-FLOW
Pre-manufacturing config error: CFGERR #481 correction config
Auto checkout validation: bot #418 reroute no human review
Failed personalization received: #417 PERSO-FLOW remake post-delivery
Pre-prod human review ≠ post-delivery failed personalization dispute. Reroute #417 if product already shipped.
Essential manpower KPIs
Five MANPERS steering metrics.
manpers_ticket_rate: manpers_* tickets / review_required orders
manpers_review_sla_rate: reviews within review_sla_hours map
manpers_first_submission_rate: OK files without resubmission
manpers_rejection_rate: manpers_rejected / total submissions
manpers_change_request_rate: pre-approval modifications / total
Target: manpers_review_sla_rate greater than 90% with file_requirements visible PDP checkout.
MANPERS anti-patterns
Five common manual validation errors.
Invented agent status: REVIEW-STATUS-VERIFY queue ops first
Direct agent approval: NO-APPROVE-AGENT ops design only
Out-of-window modification: CHANGE-WINDOW-SCOPE map policy
Rejection without cited rules: REJECTION-CITE-RULES file_requirements
Missed personal confusion: POST-DELIVERY-REROUTE #417 if shipped
MANPERS with Qstomy
Qstomy on Shopify: detect manpers intent, MANPERS-MAP RAG sla cite, order tag hold lookup, handoff #598 bot tier 1 status review collect file.
Pipeline: #598 bot status file requirements → #597 change escalate ops cancel release production.
Explore AI support and request a demo.
Checklist, FAQ and going further
MANPERS Checklist (8 steps)
MANPERS-MAP v1: review_sla file_requirements rejection change
Policy MANPERS-SUP: 6 REVIEW-STATUS-VERIFY rules
8 manpers_* typologies: helpdesk tags
4 MANPERS-* macros: STATUS FILE CHANGE REJECT
Production hold tag: Shopify hold until approved test
Upload portal URL: file_requirements PDP checkout visible
Agent training 30 min: MANPERS vs #417 vs #418
KPI Dashboard: manpers_* section 9
FAQ
Difference with bot #418?
#418 = auto pre-purchase checkout validation. #597 = mandatory human ops review post-order.
What is the status of my validation?
MANPERS-STATUS-01 REVIEW-STATUS-VERIFY ops queue.
Why was the file rejected?
MANPERS-REJECT-01 rejection_rules file_requirements map.
Is Bot #598 enough?
Tier 1 review status file requirements. Change approve reject → agents #597 ops.
Go further
This week: publish active MANPERS-MAP types, test Shopify hold tag, measure manpers_review_sla_rate.
Enzo
July 1, 2026
