How to choose a delivery system and delivery time windows for a supermarket

How to choose a delivery system and delivery time windows for a supermarket

For the customer, choosing a delivery time window is a simple action. Behind it lies a complex promise: the store team has to finish picking and packing in time, a suitable vehicle has to be available, and the driver has to reach the address within the window shown at checkout. When one of these parts is not coordinated with the others, even an easy-to-use system can cause delays and unnecessary costs.

That is why choosing a delivery system for a supermarket should start with understanding your operations, not just with a list of features. This guide will help you define requirements, compare vendors, and test in a pilot whether the solution fits your stores, your customers, and your growth plans.

Start by mapping the process and capacity

Before approaching vendors, document the order's journey from the website to the customer's home. Identify who is involved at each stage: the e-commerce site, the store or warehouse, pickers, packers, the call center, drivers, and courier companies. That way you can identify delays, double data entry, and gaps in the overall picture.

Collect data from a representative period and, where possible, from peak periods too. Focus on the following areas:

• Orders and demand: The number of orders by day, hour, store, and delivery zone, along with changes during holidays and promotions.

• Picking and packing: Work times, the number of staff, and the differences between small and large orders.

• Distribution: Driver and vehicle availability, vehicle capacity, driving distances, and delivery time at each stop.

• Products: Variable-weight products, missing items, and products that require different transport conditions.

• Service: Delays, cancellations, repeat deliveries, and customer inquiries about arrival times.

The mapping will also help you decide which tasks the system will perform and which will remain in other tools. For example, a system may show time windows and plan routes but rely on another system for inventory management and picking. Ask the vendor to clarify where responsibility is handed off at each stage.

Managing delivery time windows: the promise to the customer versus reality on the ground

An open delivery window is not just a slot on a list. To keep the promise, you need to coordinate picking and packing capacity, driver and vehicle availability, the delivery zone, and the time each drop-off takes. A limit of ten orders per window, for example, may suit small carts, but not necessarily large orders or products that require different cooling conditions.

Check whether you can set rules by store, zone, and time, define order cut-off times, and adjust capacity for busy periods. Also find out what happens if a store closes early, a driver is unavailable, or a vehicle is out of service: can future windows be reduced, and who is authorized to make the change?

How does the system handle simultaneous selections?

Overselling can occur when several customers try to choose the last slot in the same window. Ask for a demonstration of the capacity allocation mechanism, not just of the availability screen. The key question is how double commitments are prevented, even if different components of the system are not updated at the same moment.

• At what stage is the slot reserved: when the window is selected, when payment begins, or only after the order is confirmed?

• How long is the reservation valid, and what happens if the customer abandons checkout?

• How do cancellations, address changes, or switching to another window affect capacity?

• What does the customer see if the window they chose is no longer available when the order is confirmed?

• Can a manager block a window or change its capacity, and is the change logged?

Test the behavior in a real scenario or in a test environment with several users. Make sure the customer service team also sees clear information about confirmed orders, temporary reservations, and slots that have been freed up.

Route planning and coordination between the store and the courier

A delivery coordination system should help not only with receiving the order but also with carrying it out. Route planning is affected by customer addresses, traffic, service time at each stop, vehicle capacity, and the time windows that were promised. Check which data is actually taken into account and which requires manual entry.

Ask to see what happens when a driver is running late, a customer cancels, or an order is added. Can the route be re-planned? Does the system flag commitments that may be at risk? Also check who approves the change and how the information reaches the store, the driver, and the customer.

If you combine an in-house fleet with courier companies, find out how orders are allocated to each party and which status updates are received from each company. Also check how a failed delivery is handled: recording the reason, arranging another attempt, and the implications for the products and the delivery cost.

Adapting to food: picking, substitutions, and transport conditions

Scheduling deliveries for grocery stores is different from shipping a uniform shelf product. A single cart may include heavy items, frozen products, fresh produce, and products weighed during picking. Check how the order details pass between systems and whether they help the team prepare in time.

Present the vendor with a scenario in which a product is missing and a substitute is needed. Check how the team records the substitution, how the customer is informed of the change, and how the order and billing details are updated in the relevant systems. Also ask how weight and price differences after picking are handled.

For temperature-sensitive products, examine the support for documenting transport conditions, separating products with different requirements, and handling exceptions. Software alone does not guarantee proper transport: the equipment, procedures, and training must also be adapted to the type of product, the manufacturer's instructions, and applicable law. A specific professional review is especially important when several delivery parties are involved.

Integrations: what actually connects to your existing systems?

Connecting to the e-commerce site, the ordering system, the POS, inventory, and courier companies can reduce double data entry and gaps between the order and its fulfillment. However, a claim that an integration exists is not enough. Find out what data is transferred, in which direction, how often, and who is responsible for maintaining the connection.

• Which integrations exist and are working today, and which require development or customization?

• Are order changes, cancellations, substitutions, and delivery statuses also transferred?

• What happens when a message fails or arrives twice? Is there logging, alerting, and a way to recover?

• Who diagnoses a fault that spans the system vendor, the e-commerce site, and the delivery company?

• Can orders, performance data, and settings be exported at the end of the contract, and in what format?

Ask for technical documentation and a demonstration of a sync failure. For example, an order that was confirmed on the website but never reached the delivery system should be visible so it can be handled, not disappear between systems. Define in advance who receives the alert and what the workflow is until it is resolved.

Customer experience, privacy, and compliance

Test the ordering process in Hebrew and on mobile: Are the time windows clear? Is the delivery fee shown before the purchase is completed? Does the customer understand what to do if a change is needed? Make sure that confirmation, delay, and change notifications also arrive through the appropriate channel and show consistent information.

Examine the accessibility of the digital service and whether it meets the requirements that apply to the business. For distance selling, also check the information provided to the consumer about price, delivery, and cancellation. Don't assume the same cancellation rules apply to every food product or every transaction; we recommend getting legal advice suited to your circumstances.

The system may process addresses, phone numbers, order details, and driver locations. Ask the vendor to explain role-based permissions, encryption, backup, activity logging, data deletion, and security incident handling. Also review the contract terms with vendors that process data and how responsibility is divided between them and the business. This checklist does not replace a review of the obligations that apply to you.

How do you compare price and total cost?

Supermarket delivery management software may look cost-effective based on the subscription fee alone, but the actual cost also depends on the volume of use and the accompanying services. Ask each vendor for a detailed proposal based on the same order volume and the same number of stores and drivers.

• Setup, configuration, training, and data migration fees.

• A fixed subscription and variable payment per order, per driver, or by another component.

• Development and maintenance of integrations, including connections to courier companies.

• The cost of customer notifications, support, customizations, and future changes.

• Commitment terms, possible price increases, contract termination, and data export.

Compare at least two scenarios: normal activity, and a peak or growth period. That way you can see how the cost changes as the number of orders rises, rather than relying only on the entry price. Alongside the price, review the service level agreement (SLA): support hours, how faults are reported, the agreed response times, and each party's responsibilities.

Demo and pilot: how to test before you expand

Instead of settling for a demonstration of a single successful order, prepare scenarios based on your own operations. Ask the vendor to show unusual load, two customers competing for the last slot in a window, a missing product, a late driver, a repeat delivery, and an integration failure. Involve store, customer service, IT, and logistics representatives in the review: each of them may spot different problems.

After the initial screening, run a pilot in a store or a defined delivery zone. Set the length of the trial, the comparison group or baseline data, the areas of responsibility, and the conditions for expansion in advance. It is best to include busy hours as well, not just quiet days.

Success metrics to define in advance

• On-time delivery: The number of orders delivered within the promised window out of all orders delivered. Define how the delivery time is measured and what happens if the window was changed with the customer's agreement.

• Cancellations and repeat deliveries: Measure these separately, so the on-time delivery metric does not hide orders that were not completed on the first attempt.

• Cost per order: Compare the relevant costs before and during the pilot, using the same calculation method.

• Capacity utilization: Check how much of the defined capacity was used, alongside the actual workload and service quality.

• Customer and staff experience: Track inquiries, reasons for delays, and feedback from employees and customers.

For example, if 90 out of 100 delivered orders arrived within the promised window, the on-time delivery rate under this definition is 90%. Canceled orders are not included in the denominator in this example, so their number should be reported separately. Consistent measurement matters more than comparing percentages calculated in different ways.

Decision checklist before signing

The most suitable system is the one that connects the promise made at checkout with the business's ability to deliver. Before choosing, make sure the vendor has demonstrated reliable capacity allocation, exception handling, and the relevant integrations; that the price quote includes the expected cost components; and that the service agreement and data export terms are clear.

Finally, compare the pilot results with the goals you set. If the team can handle the orders, customers receive clear information, and the metrics indicate a fit with your business needs, you can make a better-informed decision about expanding.

Frequently asked questions

What should you check in a supermarket delivery system?

Check capacity and delivery time window management, route planning, integration with existing systems, data security, and total cost. Also examine how well it fits food products and your picking and delivery processes.

How do you reduce overselling of delivery time windows?

Check how the system allocates capacity when several customers choose the same window, when the reservation expires, and how cancellations or changes return capacity to availability. Ask for a demonstration of the process under load.

Which costs should you consider when comparing systems?

In addition to the subscription, check setup fees, payment per order or per driver, integrations, notifications, support, and future changes. Compare proposals based on the expected order volume and on growth and seasonality scenarios.