Written by DROPS.ST.
Show delivery costs as soon as you can calculate them, and explain any conditions before customers commit time to checkout. When the exact cost needs a location, say what information is needed and why. DROPS delivery rules, configurable fields and connected checkout give shop owners a place to make those conditions part of the order instead of a separate support conversation.
Put the answer at the decision point
Customers do not need every delivery rule on every product card. They need enough information to decide whether continuing makes sense. A product page can show the delivery policy and minimum. The cart can show the applicable calculation once the required location and basket information are available. Checkout should confirm the final selection and total.
Avoid vague promises such as “fast delivery” when the relevant question is whether the customer’s address is served. State the actual area, charge and timing basis. If fulfilment is subject to shop acceptance, make that understandable before payment.
Use location-based delivery guidance to define the service boundary. The copy on the page should match the configured rule, including the inconvenient edge cases.
Write one coherent explanation across the shop
Here is an illustrative delivery arrangement: standard delivery costs 6 currency units within the stated service area, with no delivery charge on eligible baskets of 60 or more. These are example values, not DROPS pricing or a suggested universal promotion.
| Place | Example wording | What the customer learns |
|---|---|---|
| Product information | “Delivery is available in our listed service area. Standard delivery is 6; eligible orders of 60 or more qualify for free delivery.” | The cost and threshold before building a basket |
| Cart before location is known | “Enter your delivery area to check availability and the delivery charge.” | Why location information is requested |
| Eligible cart of 48 | “Products: 48. Delivery: 6. Total before any separately applicable tax: 54.” | The actual effect on this basket |
| Final review | “Delivery to your selected address: 6.” | Which fulfilment choice the total includes |
Choose the actual currency label and tax presentation for your shop. Do not leave an example’s “currency units” wording on a live checkout.
Explain thresholds without creating another surprise
If free delivery depends on the total after discounts, say so. In the example, a basket of 62 with a discount of 5 becomes 57. Whether it still qualifies depends on the real rule. The promotion, cart and final total must tell the same story.
Also explain which items or service areas are excluded when that matters. A large headline advertising free delivery cannot repair a hidden exclusion introduced at the last step.
DROPS keeps product selection and order details in one shop flow, so the team can review a customer’s chosen fulfilment method alongside the order. That context helps resolve “Why was I charged delivery?” with a specific answer instead of a generic policy link.
Ask for only the location detail the calculation needs
An early service-area check may need less information than dispatch. Decide what is necessary for the actual rule and use the shop’s supported fields accordingly. Do not request a full address simply to answer a broad availability question unless that precision is needed.
Try three baskets in the demo: below a threshold, at the threshold and after a discount. Then change the fulfilment choice or delivery area and inspect the explanation. The goal is a customer who understands the total before reaching for their wallet.
For the final price breakdown, use the checkout acceptance guide to check what appears in the order record as well as on screen.
Delivery should help close the sale, not reopen the negotiation. Explore how DROPS connects delivery choices, checkout and orders and give customers the cost while they can still make an informed choice.