E-commerce
September 2, 2026
Are you wondering how to manage recurring customer inquiries about the time required to prepare their order before shipping? The core issue lies in the frequent confusion between the "in preparation" status and the actual delivery, which triggers a wave of unnecessary support requests.
By clearly distinguishing the internal logistics phase from transit, you transform customer stress into an opportunity for trust. A clear policy and targeted response macros allow you to defuse anxieties starting on Day 0 without overloading your team.
So how do you structure your approach to handle these requests effectively? On the agenda:
Why do customers confuse preparation with delivery, and how can you avoid this trap?
What types of lead time requests should you map out for a tailored response?
How do you write a transparent and reassuring "PREP-TIME" policy?
What workflows and macros should you use to standardize support responses?
How does data analysis help you adjust your lead time promises?
Let's get started.
Summary
Why do questions about preparation times overwhelm support?
Inquiries regarding preparation times often saturate customer service because they stem from a deep confusion on the buyer's part. When the order status remains "unshipped" or "in preparation" after a few days, the customer interprets this state as a delivery delay and not as a necessary logistical step.
This lack of awareness leads to urgent tracking requests, often classified as WISMO (Where Is My Order), when it is simply a standard preparation time. If the brand does not communicate clearly about this internal phase, each unshipped ticket is treated as a critical delay.
It is crucial to understand that the customer often sees the "processing" status as an anomaly or a broken promise, especially if express delivery is promised. Without an explicit policy distinguishing preparation from transit, each inquiry receives a corrective response that does not resolve the fundamental confusion.
The causes of saturation
The customer equates "unshipped" with "not delivered." The preparation time is seen as unacceptable downtime.
"24h" promises are misunderstood: dispatch within 24 hours does not imply next-day delivery.
The weekend factor is often forgotten: an order placed on Friday evening is logically in preparation only from Monday to Friday.
Volume peaks like Black Friday create additional delays unanticipated by the customer, generating a massive flow of inquiries.
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
How does preparation fundamentally differ from delivery and MTO?
To answer questions correctly, we must strictly distinguish four logistical phases and their distinct support responses. The preparation phase (#395) corresponds to the period from when the order is paid until the creation of the delivery slip, without the package being in transit.
The transit phase begins when the carrier collects the package to deliver it to the customer, a step whose delays depend on the chosen shipping method. Make-To-Order (MTO) production involves a craft or workshop process that precedes preparation, thereby extending the overall deadline.
The fundamental distinction
Preparation: The store prepares the package. The status is "in preparation" or "not shipped". The response is based on internal lead times.
Delivery: The package is with the carrier. The status becomes "shipped". This is where delivery tracking applies.
MTO: Manufacturing in the workshop before preparation. Confusion often arises because the customer sees a very long delay without understanding the manufacturing phase.
Pre-order: The product has not yet been launched. The response should point to a specific pre-order policy, distinct from standard stock.
Your site must visually separate "Shipped within X days" and "Delivered within Y days" on the product page (PDP). This allows the customer to correctly anticipate the overall timeline. Support, however, only intervenes in the first phase when the status remains "not shipped".
How to correctly interpret Shopify statuses to avoid errors?
The correct interpretation of Shopify statuses is essential for guiding the customer without error. The "unfulfilled" status simply indicates that the order has been paid but the shipping label has not yet been generated or printed.
However, a "partially fulfilled" status can cause confusion if it is a split shipment to accommodate stock. A "fulfilled" status means that the hand-off to the carrier is complete: the package is now in transit and the customer must use the tracking number to follow their delivery.
Key Statuses
Unfulfilled: Preparation is underway or pending. This is the playground for preparation delay support.
Partially fulfilled: The package has been split (for example, a missing item) to be sent earlier. This requires an explanation regarding the split shipment.
Fulfilled: The order has left the warehouse. Any further questions fall under the carrier and transit times.
Cancelled: Preparation did not take place, often due to fraud or customer cancellation prior to shipping.
It is imperative not to promise 24-hour shipping if your warehouse operates under a 48-hour SLA. Support must validate the actual status in the database before reassuring the customer about a specific timeframe.
What is the crucial distinction between the preparation cut-off and the express cut-off?
The distinction between the preparation cut-off and the express cut-off is frequently a source of errors in customer communications. The preparation cut-off, often set at 2:00 PM, determines whether an order will be prepared the same day for shipment the following business day.
The express cut-off concerns the carrier and determines a delivery on D+1 or D+2 after shipment. These two timeframes are cumulative and not interchangeable. Confusing these two thresholds in a response macro leads to incorrect promises regarding the arrival date.
Management of Thresholds
Preparation Cut-off: If the order is placed before 2:00 PM, it is ready the same business day. Otherwise, it is pushed to the next day.
Express Cut-off: Requires specific shipping to guarantee fast arrival. This depends on the chosen logistics operator.
Sum of Delays: The total delivery time perceived by the customer is the sum of the preparation time and the transit time, not just one or the other.
What types of tickets regarding preparation times do you need to map?
To handle these requests effectively, you must map the twelve main typologies of tickets related to preparation times. Each scenario requires a specific response to avoid systematically sending the same generic message.
The typologies to remember
Preparation within standards: The customer inquires before the promised deadline. Reassuring and confirming response.
SLA breach: The order exceeds the announced time frame. Requires an apology, an explanation, and potentially a commercial gesture.
Cut-off not respected: Order placed too late to be shipped today. Explain the time rule clearly.
Weekly void: Order placed on Friday or Saturday, logical waiting until Monday. Remind of the working business days.
Volume spike: Announced extended delays (e.g., Black Friday). Confirm that the extension is temporary and expected.
How to structure data integration for automated sorting?
Data integration is the key to effective triage. Each ticket must be analyzed based on the order ID, the creation date, the current preparation status, and specific tags related to deadlines or personalization.
Input Data
"prep_sla_ok" Tag: Indicates that the order is on time. Allows for a standard response.
"prep_peak" Tag: Indicates a current slowdown. Requires informing the customer of the exceptional period.
Personalization data: If the order contains engravings or messages, this adds days to the lead time. This information must be tagged.
Clock and time zone: Compare the order creation time with warehouse hours to check the cut-off.
What is the eight-rule method for writing an effective PREP-TIME policy?
Writing the "PREP-TIME" policy must follow eight strict rules to be effective. It documents the SLA between the paid order and shipping, serving as a single reference for the entire team.
The 8 rules of the policy
Standard SLA: Clearly define that preparation takes 1 to 2 business days for standard stock.
Daily Cut-off: Specify the cut-off time (e.g., 2:00 PM) for same-day shipping.
Business days: Explicitly state that weekends do not count, except for announced exceptions.
Customization: Indicate the additional processing times (1 to 3 days) for engraving or packaging options.
What key elements should be included in your pre-order and MTO communication?
Communication on MTO and pre-orders
For made-to-order (MTO) or pre-ordered products, any confusion with standard stock must be avoided. Order tags must link to separate policies (#288 for MTO and #187 for pre-orders).
On the product page, the promise must be split: "Shipped within X days" (preparation phase) and "Delivered within Y days" (transit phase). The confirmation email must explicitly repeat the preparation SLA so the customer does not expect immediate delivery.
How to apply the PREP-FLOW to process requests systematically?
The PREP-FLOW flow structures the response to tickets in a systematic way. It consists of a series of logical steps that the agent must follow to verify the situation before responding.
Steps of the flow
Status check: Confirm whether the package is "shipped" or "not shipped". If shipped, the question falls outside of this scope.
Date comparison: Check if the current date exceeds the promised date (SLA) in the system.
Reason identification: Determine whether it is a volume peak, a customization, or a simple oversight.
Drafting the response: Use a macro adapted to the scenario (e.g., "prep_sla_exceeded") while personalizing it with the customer's ID.
How can the analysis of WISMO tickets reveal preparation opportunities?
WISMO Ticket Analysis
The analysis of tracking inquiries (WISMO) between D+0 and D+2 often reveals that customers confuse preparation and transit. It is estimated that 8 to 18% of these inquiries are actually questions about preparation times.
By identifying this signal, you can adjust your macro-responses to systematically include an explanatory section on preparation. This significantly reduces reopening rates and improves first contact resolution (FCR) without any extra effort.
How does Qstomy help reduce doubts about preparation times and optimize conversion?
Qstomy acts as a dedicated Shopify AI agent that guides the shopper to the precise answer regarding their preparation time. Unlike traditional tools, Qstomy does not just answer; it directs the customer to the right tracking, account, and policy information.
By integrating a contextual understanding of inventory and warehouse lead times, Qstomy can provide immediate reassurance about actual timelines. This helps reduce the number of open tickets, while increasing confidence in the order.
Key Strengths of Qstomy
Contextual Awareness: Qstomy can distinguish between a standard preparation time and a high volume peak thanks to real-time data.
Clear Promise: The AI agent communicates "shipped within X days" lead times smoothly, without technical jargon.
Proactive Resolution: Qstomy can anticipate doubts and provide explanations before the customer even asks the question.
Optimized Conversion: By reassuring on lead times, the AI promotes sales closure and reduces shopping cart abandonment.
What checklist should you adopt to finalize your preparation lead time management?
Final Checklist
To validate your strategy, make sure you have: A written "PREP-TIME" policy published on the site with cutoff times. Distinct response macros for each typology (SLA OK, SLA exceeded, Peak, Personalization). Support team training on the difference between "shipped" and "delivery". Integration of pre-order and MTO tags in the ticketing system. Activation of Qstomy to automate these responses with precision.
To go further: How to manage customer questions about waiting time before a human agent - Qstomy, How to manage customer questions about order preparation times - Qstomy, How to manage customer questions about "in preparation" status - Qstomy, How to manage customer questions about captured payments but order not created - Qstomy, How to manage customer questions about orders awaiting payment - Qstomy, Reduce "where is my order?" on Shopify with truly clear tracking - Qstomy, AI Chatbot for preparation times: inform based on stock, warehouse, and volume - Qstomy.
Enzo
September 2, 2026
