Last reviewed June 2026, the anxiety-reduction case and the PrestaShop placement points (product page, cart, checkout delivery step, order confirmation) below are current; out of the box PrestaShop still shows no product-page delivery estimate, only a static per-carrier Transit time string at checkout.
There is a quiet, anxious window in every online order: the gap between "Pay now" and "It arrived." During that window the customer has handed over money and received nothing tangible in return, just a confirmation screen and a hope. The single most effective thing a PrestaShop store can do to shrink that anxiety is to answer one question before they ever click Pay: when will this turn up? Not "3 to 5 business days", an actual date. "Arrives Tuesday 7 to Thursday 9 October." That one line of copy does more to calm a nervous buyer than any trust badge, review widget, or money-back banner you could bolt on.
This post is specifically about the customer-anxiety side of delivery dates: why a concrete date soothes the exact fear that makes people hesitate or email support, where on a PrestaShop store the date has to appear to actually do that job, and how to wire it up. The separate, more operational question, how to calculate a realistic estimate, build in buffers, and not over-promise, is its own discipline, covered in setting realistic expectations for customers. Here we assume you'll get the number roughly right and focus on making it work for the customer's nerves.
What the anxiety actually is, and why "3-5 business days" makes it worse
Purchase anxiety isn't vague. It's a specific loss-of-control feeling that hits the instant money leaves the customer's account. The product is now somewhere between your stockroom and their door, and they have zero visibility into that journey. Their brain fills the silence with worst-case stories: it's lost, it's stuck, it won't come before the birthday, the store is a scam.
The cruel part is that the most common "delivery information" on the web actively feeds that anxiety. "Ships in 3-5 business days" forces the customer to do mental arithmetic, and people are bad at it. They have to know today's date, count forward, remember which days are weekends, guess whether "business days" includes the day they ordered, and account for the bank holiday they half-remember is coming. Most don't bother; they just feel uncertain. A computed date range removes the maths entirely. "Tuesday to Thursday next week" is a thing a human can picture and plan around. That shift (from a span the customer has to decode into a date they can see) is the whole game.
A concrete delivery date earns its place because it does five things at once:
- It replaces a worst-case story with a plan. "It'll be here Thursday" is something you can arrange your week around; "3-5 days" is something you worry about.
- It pre-empts the "where is my order?" email. If the page said Tuesday-to-Thursday, the customer won't be drafting a panicked message on Monday. Your support inbox feels this immediately.
- It signals competence. A store that can name a date is a store that clearly knows where its parcels are. That reads as "these people have their logistics handled," which is exactly the reassurance a nervous first-time buyer needs.
- It turns the deadline into a reason to buy. "Arrives before Christmas" or "here in time for the party" can be the deciding line on a gift purchase, anxiety flipped into urgency.
- It removes a silent abandonment cause. Uncertainty about when is a documented reason carts get left behind; a visible date closes that exit door.
Where the date has to appear in PrestaShop to actually calm anyone
A delivery date only reduces anxiety if the customer sees it at the moment the anxiety strikes, and in a default PrestaShop store, that's almost never where the information naturally lives. Out of the box, PrestaShop has no product-page or cart delivery estimate at all; the only delivery-time signal is the static Transit time text you can set per carrier under Shipping → Carriers (the General settings tab, "Transit time" field), and that only surfaces deep in the checkout once a carrier is chosen. By then the most anxious moment. The decision to buy, has already passed. So placement is the real work. Four points matter, in order of impact:
The product page (this is where the sale is won or lost)
The biggest anxiety-reduction happens before the add-to-cart click, not after. A customer weighing whether to buy is the most nervous customer you have, and a date sitting right beside the price and the add-to-cart button answers their unspoken question at the exact second they're asking it. In PrestaShop terms this means rendering the estimate on the product controller, near the product-add-to-cart block in product.tpl, high on the page, impossible to scroll past. A date buried in the footer or a tab does nothing; the whole point is that it's in the buyer's eyeline while they hesitate.
The cart page
Once items are in the cart (the cart controller / shopping-cart.tpl), the estimate should recompute for the order as a whole. Driven by the slowest item if a customer has mixed a same-day-dispatch product with a made-to-order one. Showing a date here keeps the reassurance present while the customer is deciding whether to proceed, rather than letting the silence creep back in.
Checkout, the moment a carrier is selected
At the delivery step (CheckoutDeliveryStep on the order controller), the date should update the instant the customer picks a shipping method, so "Express. Arrives Wednesday" sits next to "Standard. Arrives next Monday." This is where the date stops being just reassurance and starts doing conversion work. See the cost-perception note further down.
Order confirmation page and email
The order-confirmation controller and the order_conf mail template are the customer's reference point for the entire anxious waiting window. A confirmation that ends with "Estimated delivery: Tuesday 7 – Thursday 9 October" is the line they'll re-open the email to check. Leaving it off here is the most common own-goal: you reassured them right up to the purchase, then went silent at the exact moment they're most invested.
Doing it without editing your theme: the Estimated Delivery Date module
You can hard-code transit times into carriers and hand-edit templates, but you'll be maintaining theme overrides forever and you still won't get a computed, holiday-aware date in front of the buyer on the product page. That's the gap our Estimated Delivery Date module exists to close. So what does it actually do for the anxiety problem? It puts a real, calculated date in every one of the four placements above, product page included, from your back office, with no theme surgery and no developer invoice, so it survives your next PrestaShop upgrade.
The date it shows isn't a static guess; it's assembled from the inputs that make an estimate believable:
- Preparation time. How long your team needs to pick, pack and hand off, set globally or overridden per product for the made-to-order items that genuinely take longer.
- Carrier transit time, each carrier and method carries its own window, so standard post and express courier show different, honest dates.
- Cut-off time, a configurable daily deadline ("order before 2pm and it ships today") so the date reflects reality instead of optimism.
- Non-working days. Weekends and country-specific public holidays are skipped in the count, which is exactly the maths customers get wrong in their heads.
- Destination, a domestic parcel and a cross-border one quote different dates, because they genuinely arrive at different times.
The benefit framing is the point: the customer feels a calm, specific promise at every step; you feel a quieter support inbox and a setup you did from the admin panel, not a code branch you have to babysit through upgrades. Getting the inputs right (how conservative to be, how to handle backorders, how much buffer to build in) is the expectation-setting craft we cover separately in setting realistic expectations for customers; the module gives you the dials, that guide tells you where to set them.
How the date quietly justifies your shipping prices
Anxiety isn't only about timing, it's also about feeling ripped off. A customer staring at "Express: €8.90" with no context has every reason to resent it. Put a date beside it, "Express: €8.90, arrives Wednesday" against "Standard: free, arrives next Monday", and the premium suddenly has a visible, purchasable benefit attached. The customer isn't paying more for nothing; they're paying to compress four anxious waiting days into one. The date converts an abstract surcharge into a concrete choice, which is why it belongs on the checkout delivery step specifically. How you structure those price tiers in the first place is a different decision, weighed up in free vs flat rate vs calculated and when free shipping actually makes sense.
The peak-season trap: when a confident date becomes a liability
The one time a delivery date can increase anxiety instead of reducing it is when it goes stale. During Black Friday, Christmas and Easter, carrier networks congest and transit times stretch, and a date computed from your normal settings will quietly start lying. The fix is to treat the peak window as a deliberate adjustment, not an afterthought:
- Pad carrier transit by a day or two for the duration of the rush, so the displayed date stays achievable.
- Make the cut-off message the loudest thing on the store. "Order by 18 December for delivery before Christmas" is, for a few weeks, the single most reassuring line you can show, it converts the customer's deadline anxiety into a clear instruction.
- Raise preparation time if your own packing desk is the bottleneck, an honest extra day beats a broken promise that generates a support ticket and a one-star review.
The principle is the same one that runs through this whole post: a date only reduces anxiety while it stays true. The moment it can't be trusted, it does the opposite.
What the anxious customer is really asking
Strip away everything and a nervous buyer wants answers to three questions, in this order:
- When will it arrive?, a specific date range they can picture, never a span they have to count out.
- Can I get it faster?, express options shown with their own dates, so the choice is concrete.
- Can I follow it?, the promise that once it ships, they won't be in the dark. That hand-off from estimate to live tracking is what carries the reassurance through the actual waiting window, and we cover it in tracking numbers and delivery notifications.
Answer those three clearly and you defuse the large majority of post-purchase support contacts before they're ever sent, not by adding more features, but by removing the uncertainty that was generating the questions. The carrier setup that feeds accurate transit times into all of this is its own job, walked through in setting up carrier modules in PrestaShop, and the wider plan of which carriers and speeds to even offer is mapped in shipping strategy for small stores. But the date itself, visible, specific, honest, in front of the buyer before they pay, is the cheapest anxiety reducer in your whole store.
Frequently asked questions
Why does a date calm anxiety better than "3 to 5 business days"?
Because "3 to 5 business days" makes the customer do the work. They have to know today's date, count forward, remember which days are weekends, and account for any holiday, and most people don't bother, they just feel uncertain. A computed date removes the arithmetic entirely: "arrives Tuesday to Thursday next week" is something a human can picture and plan a week around. You're not giving them more information, you're giving them information they don't have to decode.
Does PrestaShop show a delivery date out of the box?
No. A default PrestaShop store has no product-page or cart delivery estimate at all. The only delivery-time signal is the static Transit time text you set per carrier under Shipping → Carriers, and it only appears deep in checkout after a carrier is chosen. Well past the most anxious moment, which is the decision to buy. Putting a real date earlier, on the product page, is the gap a delivery-date feature fills.
Where does the date matter most for reducing anxiety?
The product page, next to the price and add-to-cart button. That's where a hesitating buyer is most nervous and most likely to leave, so a date there answers the unspoken "when will it turn up?" at the exact second they're asking it. The cart, checkout delivery step, and order-confirmation email each reinforce it, but if you can only place it in one spot, the product page is the one that moves the sale.
Won't a delivery date backfire during Black Friday or Christmas?
It can, but only if you let it go stale. During peak season carrier networks congest and transit times stretch, so a date computed from your normal settings starts quietly lying. The fix is to pad transit by a day or two for the duration, raise your preparation time if your own packing desk is the bottleneck, and make the cutoff message ("order by 18 December for delivery before Christmas") the loudest line on the store. A date only reduces anxiety while it stays true; the moment it can't be trusted it does the opposite.
Where does the Estimated Delivery Date module display the date?
On the product page, under the add-to-cart button, via the displayProductAdditionalInfo hook, the highest-anxiety spot, and the one a default PrestaShop store leaves empty, with no theme editing. It's driven from the back office by your processing days, a daily cutoff hour, a weekend skip, and the date format, so the calculated day appears in the buyer's eyeline while they're still deciding. Set those inputs to numbers you can actually hit and the reassurance stays honest.
