Skip to content
DT Nova

How to build a grocery delivery app: picking, slots, payments and the rules

If you are working out how to build a grocery delivery app, start with what makes it different: it looks like food delivery from the outside and is a different problem inside. A restaurant order is a few dishes cooked to order. A grocery order can be dozens of items picked from shelves, some weighed, some out of stock, some chilled or frozen, delivered in a slot the customer booked days ahead. This guide explains the apps a grocery service needs, the parts that decide whether customers come back, the payment and food information rules, and a checklist to scope the build.

It is written for grocers, food retailers and start-ups planning online ordering with delivery or click and collect. If you deliver from restaurants or dark kitchens, read our guide on how to build a food delivery app; for prescriptions and pharmacy goods, the guide on how to build a medicine delivery app.

The short version

  • The product catalogue is the biggest job: thousands of items, each with prices, stock, photos and the food information the law requires.
  • Picking and substitutions decide customer satisfaction more than the customer app's design.
  • Weighed items need an authorise-then-capture payment flow, because the final price is known only after picking.
  • Delivery slots are a capacity problem: pickers, vehicles and cold storage, not just times on a calendar.
  • Start with one store or warehouse and a limited area, measure missing items and late deliveries, then grow.

The apps a grocery service needs

PartUsed byWhat it does
Customer app and web shopCustomersSearch, browse, favourites and previous orders, basket, slot booking, payment, substitution preferences, order tracking, refunds
Picking appStore or warehouse staffPick lists in walking order, barcode scanning, weights, substitutions with customer approval, packing by temperature zone
Driver appDriversRoute for the slot, delivery confirmation, age checks where needed, returns of rejected items
Operations consoleYour teamCatalogue and prices, slot capacity, promotions, customer service, refunds, reports
IntegrationsSystemsPoint of sale or ERP for stock and prices, product data feeds, payment provider, routing

Online shopping is now ordinary for most people. Eurostat's e-commerce statistics for individuals (data extracted February 2026, read 11 November 2026) report that 78% of EU internet users aged 16 to 74 bought or ordered goods or services online in 2025, and that the problem online buyers reported most often was delivery slower than expected, named by 20%. For groceries, where a missed slot means a missed dinner, that is the number to design against.

The product catalogue

A supermarket range runs to thousands of items, and every one needs a name, photos, a price, stock, a category, and the food information the law requires. That data rarely sits in one clean place: prices and stock come from the point of sale or ERP, product details from suppliers, and photos from anywhere. Most products carry a GS1 barcode number (GTIN), which is the natural key to join the sources; GS1 describes its Global Data Synchronisation Network as the world's largest product data network, and many brand owners publish their product data through it (GS1, read 11 November 2026).

The food information rules make the catalogue a legal matter as well as a sales one. For prepacked foods sold at a distance, Article 14 of Regulation (EU) No 1169/2011 (read 11 November 2026) requires the mandatory food information, except the minimum durability or use-by date, to be available before the purchase is concluded, on the material supporting the distance sale or through other clearly identified means without extra cost, and all mandatory particulars to be available at the moment of delivery. Ingredients, allergens, nutrition, net quantity and the other particulars therefore belong on every product page, and they must change when the supplier changes the recipe. The build needs a way to see which products lack required data, and to keep them off sale until it is filled in.

Picking and substitutions

The picking app is where a grocery service wins or loses customers. A good one gives the picker a list sorted in the order the shelves are walked, confirms each item by scanning its barcode, records the weight of weighed items, and splits the order into ambient, chilled and frozen bags so each goes to the right place in the van.

When an item is missing, the picker needs a decision fast. The customer sets a preference per item or per order: no substitute, the app's suggestion, or a specific alternative. The picking app proposes a substitute by brand, size and price, the customer can approve or reject it in the app before the order leaves, and the receipt shows clearly what was replaced. Missing and substituted items are the main quality measure, reported per store, per category and per picker, so the cause can be fixed: a stock count that is wrong, a product that is always short, or a list in the wrong order.

Weighed items and payments

Fruit, vegetables, meat, cheese and deli items are sold by weight, so the final price is not known when the customer pays. The usual pattern is to authorise the card for the estimated total plus a margin when the order is placed and capture the real amount after picking. Card authorisations do not last forever: Stripe's documentation on placing a hold on a payment method (read 11 November 2026) gives a validity window of seven days for customer-initiated online card payments with Visa, Mastercard, American Express and Discover, and states that an extended authorisation can be requested for some eligible payments. A slot booked more than a few days ahead therefore needs the authorisation made closer to the slot, or a fresh one, and the app should tell the customer when the card will be charged.

Groceries are physical goods, so payment runs through your payment provider, not the app stores' in-app purchase systems. In the United States, a grocery service that wants to accept SNAP benefits online must be authorised for it; the USDA's SNAP online purchasing pages (read 11 November 2026) list the participating states and retailers and explain how a store applies. Loyalty programmes, coupons and member prices are usually already in the point of sale, and the app should use the same rules rather than a second copy.

Delivery slots and capacity

A delivery slot is a promise that a picker, a vehicle, a driver and space in cold storage will all be available. Slot capacity should be calculated from those limits: how many orders the store can pick per hour, how many stops a van can make in the slot window, and how long chilled goods can wait. When a slot fills, it closes. Popular slots can carry a different delivery fee, and a reserved slot should expire if the order is not completed. Click and collect uses the same planning with a pickup point instead of a van.

Routing turns the slot's orders into a driver's route. For a small service, ordering stops by area is enough; for larger ones, a routing engine plans the vans for each wave of slots. The driver app confirms each delivery, records items the customer refused, and checks age at the door for restricted products such as alcohol where national law requires it.

Returns, refunds and the right of withdrawal

EU consumer law gives a 14-day right of withdrawal for most distance sales, but Article 16 of the Consumer Rights Directive 2011/83/EU (read 11 November 2026) lists exceptions that cover much of a grocery basket, among them goods liable to deteriorate or expire rapidly, and sealed goods not suitable for return for health protection or hygiene reasons once unsealed after delivery. The legal rule is only the floor: customers expect a refund for a damaged, missing or short-dated item, and the app should let them report it with a photo in a few taps. Refunds go back to the original payment, with a record your customer service team can see. Your advisers confirm the wording of the terms; the software applies them consistently.

Build checklist

  • Service model: delivery, click and collect or both; from stores, a warehouse or both.
  • Catalogue sources: point of sale or ERP for price and stock, supplier or GS1 data for product details, a process for missing food information.
  • Picking: walking order, barcode scanning, weights, substitution rules and customer approval, temperature zones.
  • Payments: authorise and capture for weighed items, authorisation timing for slots booked ahead, refunds, any benefit programmes.
  • Slots: capacity rules for picking, vehicles and cold storage, fees, reservation expiry.
  • Delivery: routing, proof of delivery, age checks, refused items.
  • Couriers: if drivers are platform workers, the EU platform work rules in our food delivery guide apply.
  • Measures: missing items, substitution acceptance, late deliveries, repeat orders.

How DT Nova helps

This guide is the background. When you are ready to build, our on-demand app development and app development pages describe the service. We build the customer app and web shop, the picking and driver apps and the operations console as one system on one backend, integrated with your point of sale or ERP and your payment provider. We usually start with one store or warehouse, a limited delivery area and the catalogue cleaned up, and grow once missing items and late deliveries are under control. See e-commerce app development for the customer app, on-demand app development for the delivery side, and inventory management software for stock. The code is yours, and the system is hosted in an EU region as standard.

Questions people ask

How is grocery delivery app development different from food delivery?

A restaurant order is a few dishes cooked to order; a grocery order is often forty or more items picked from shelves, some weighed, some out of stock, some chilled or frozen, delivered in a booked time slot. That adds a product catalogue with thousands of items, a picking app, substitution rules, variable prices for weighed goods, slot capacity and temperature handling that restaurant apps do not need.

How do you charge for items sold by weight?

The usual pattern is to authorise the card for the estimated total plus a margin when the order is placed, and capture the final amount after picking, when the real weights are known. Card authorisations expire: Stripe's documentation, for example, gives seven days for most customer-initiated online card payments, so slots booked further ahead need a later authorisation or a fresh one.

What food information must a grocery app show?

In the EU, for prepacked foods sold at a distance, the mandatory food information other than the best-before or use-by date must be available before the purchase is concluded, and all mandatory particulars must be available at delivery (Regulation (EU) No 1169/2011, Article 14). In practice that means ingredients, allergens, nutrition and the other required particulars on every product page.

Can customers return groceries?

EU consumer law gives a 14-day right of withdrawal for most distance sales, but Article 16 of the Consumer Rights Directive excludes goods that are liable to deteriorate or expire rapidly, and sealed goods unsuitable for return for health or hygiene reasons once unsealed. Most grocery services still offer refunds for damaged or missing items, which the app should handle in a few taps.

Should a grocery delivery app be one app or several?

Several connected parts: a customer app and web shop, a picking app for store or warehouse staff, a driver app, and a console for your team to manage the catalogue, slots, substitutions and refunds. They share one backend, so stock, orders and prices are the same everywhere.

Sources