Show when an order is expected to leave the seller separately from when it may reach the customer. Preparation belongs to the seller's workflow; transit depends on shipping conditions. Combining both into a vague delivery label creates avoidable expectations.
If a product page says “within 24 hours,” the basket says “two working days” and the confirmation says “delivery tomorrow,” the customer cannot know which message applies. Fix the operational rule behind the text before rewriting individual pages.
Split the timeline into three stages
- Stock or sourcing: Is the item ready to ship or still to be obtained?
- Preparation: When will the order be picked and packed?
- Transit: What estimated interval applies after carrier handover?
Also define dispatch internally. Does it mean creating a label or physically handing over the parcel? A tracking number alone does not always prove carrier possession.
Make the conditions visible
- Working days versus calendar days.
- Any order cutoff time and relevant time zone.
- Different treatment for preorders or sourced items.
- Estimates that depend on address or region.
- Additional preparation for customized products.
No single duration fits every shop. Base wording on a measured preparation process rather than a narrow marketing promise the operation cannot consistently meet.
Use wording that separates the stages
For example: “Preparation: 1–2 working days. Estimated transit after dispatch depends on address and carrier.” These durations illustrate wording only; they are not verified terms for your shop. If a date is an estimate, label it clearly and explain known exceptions.
Check consistency across the journey
Compare the product page, basket, pre-payment summary and order confirmation. Explain what happens when one basket contains items with different preparation times. If separate parcels are planned, show their individual status rather than hiding everything behind one “completed” label.
Detect delays at the right stage
Compare planned and actual dispatch times. Track sourcing delays, packing queues and carrier handover separately so the team knows where to act. When updating a customer, avoid replacing one missed estimate with another unverified promise.
When discussing an e-commerce project with BE Soft, prepare examples of a normal order, an item awaiting supply and a delay. These scenarios make requirements for page information, notifications and administrative tracking concrete without assuming existing features.
