From Corner Shop to Regional Chain: Building Your Own Grocery App

Your neighbourhood customer reaches for their phone before dinner, and even though the item is sitting on your shelf, the order goes to a quick-commerce app instead. Deciding to build a grocery app is really deciding to move your shelf stock, your weighted products and your delivery capacity onto the phone the right way. Get the design wrong and cancellations and refunds eat the revenue it brings in. This page covers the technical scope of grocery projects, the integrations involved, and the items that determine cost.

How many separate apps does this need?

  • 01

    Customer App (iOS + Android)

    Aisle-based catalogue, weighted items with gram selection, delivery slot booking, substitution preferences, cash-on-delivery and online payment, one-tap reordering from favourites.

  • 02

    Picker (Store Staff) App

    Pick list sorted by aisle order, barcode and weight scanning, substitution suggestions for out-of-stock items, multi-order batch picking and bagging confirmation.

  • 03

    Courier / Delivery App

    Slot-based routing, address and door notes, proof-of-delivery photo, cash and card collection at the door, chilled-item alerts, live delivery notifications to the customer.

  • 04

    Web Admin Panel

    Catalogue and price management, stock thresholds, slot and courier capacity planning, promotion setup, cancellation and refund tracking, per-branch sales and picking reports.

What the app includes

  • Scanning the weight barcode writes the actual grammage into the basket
  • Splitting meal-card-eligible items into a separate payment within one basket (meal cards are a common Turkish food benefit valid only on food items)
  • Digital tab ledger (“veresiye”, the Turkish neighbourhood store credit book) with balance and collection records
  • Per-branch pricing, stock and delivery zone definitions
  • Bakery and deli items ordered against preparation time windows
  • A discount shelf for items approaching their expiry date
  • Click-and-collect arrival notification and in-store handover point
  • Bagging confirmation separating chilled, dry and chemical goods
  • Partial refunds: photo-backed claim on a spoiled item and line-level deduction
  • Picker shift handover with transfer of a half-finished order
  • Wholesale price lists and account-based ordering for cafés and small traders
  • Shelf count screen: physical stock entry and variance report

State of the sector

Quick-commerce apps and the chains' own apps have moved neighbourhood shopping habits onto the phone. For a regional grocer, the issue is not competing with chains on price; it is keeping that basket when the customer places the order on their phone. A grocer without an app hands the ready-made evening basket and the weekly shop to the platforms or to the competitor down the street, and on a marketplace loses commission, customer data and price control alike. A grocer with its own app keeps the customer list, the delivery capacity and the promotion calendar in its own hands, and turns proximity to the neighbourhood into fast delivery.

Metrics that matter here

  • Order fill rate — How many of the ordered lines are delivered complete; stock sync and the substitution flow raise this figure directly.
  • Basket picking time (minutes per order) — An aisle-sorted pick list and barcode verification increase how many orders the same staff can pick in a day.
  • Delivery slot utilisation — Shows how much of the capacity opened for couriers and chilled goods actually sells; it drives slot planning and delivery fees.
  • Monthly repeat order rate — Grocery profit comes from frequency; favourites lists and one-tap reordering feed this number.

Common mistakes in this sector

  • Opening the entire catalogue in the app at once Tens of thousands of lines rarely have correct images, weights and product information ready. A catalogue with missing images and wrong units destroys trust. The right approach is to start with the few thousand best-selling lines and grow catalogue quality step by step.
  • Syncing stock overnight When sales going through the till during the day are not reflected, customers order items you no longer have and the picker enters a cancellation. Critical lines need minute-level sync and a cut-off threshold that removes them from sale. Without it, the cancellation rate climbs fast in the first months.
  • Leaving the picker screen to a later phase If the customer app ships and picking is run off a paper list, errors and picking time both rise, and order status never reaches the customer live. The picker app should be planned as part of the first release, alongside the customer app.
  • Thinking about delivery fees and minimum basket later Without a rule engine driven by distance, slot and basket value, small orders lose money. Zone-based delivery fees, a minimum basket value and a free-delivery threshold all belong in the first release.

Regulation and compliance

Price labelling is mandatory in food retail: the in-app price must match the shelf label, and for discounted items the pre-discount price must be shown as well. Online selling falls under Turkey's distance selling rules, so a pre-contractual information form, a distance sales agreement and an e-Arşiv (electronic archive invoice) flow must be in place, and the withdrawal-right exemption for perishable food must be stated explicitly. Alcohol and tobacco cannot be sold online and must be filtered out of the catalogue. Customer addresses, phone numbers and order history are personal data under KVKK (Turkey's data protection law, aligned with GDPR): a privacy notice, explicit consent and defined retention periods are required, and food business registration details must be accessible from within the app.

The real challenges in this sector

  • The price of weighted items is not final at the time of order

    Minced meat, cheese, tomatoes: the customer asks for 500 grams, the scale weighs 540. The basket total and the amount actually charged do not match. The fix is to place a pre-authorisation at checkout and capture the real amount once picking is complete, define a tolerance range per product, and send the customer an approval request when the difference exceeds it. The e-Arşiv invoice (Turkey's electronic archive invoice) must also be issued for the final post-weighing amount.

  • Shelf stock and app stock drift apart

    Every item that goes through the till reduces stock, but a customer may have added that same item to their basket at that exact moment. A single till receipt leaves an order short. The design calls for stock reservation at order time, minute-level stock sync from the store's retail management system, and an automatic cut-off threshold that removes low-stock lines from sale. Asking customers for a substitution preference up front lowers the cancellation rate outright.

  • Picking time depends on store layout

    If the order list arrives in random order, staff walk needlessly between aisles. Every product needs an aisle-corridor-shelf code so the pick list can be sorted to match the store layout, with barcode scanning to prevent the wrong item being picked. A multi-pick mode that collects several orders in the same slot in a single walk increases orders picked per person and clears the evening peak queue.

  • Cold chain and delivery slot capacity

    Frozen goods, dairy and hot bakery items cannot share a bag, and the delivery window is not unlimited either. Slot capacity has to be calculated from courier headcount, the volume of chilled items in the basket and distance, and a full slot must close in the app. The picker should be told when an order needs a thermal bag; for delays, a perishable-goods alert and a refund flow must be ready to go.

  • Promotions and shelf labels diverge from the in-app price

    Buy two pay one, loyalty-card member pricing, per-kilogram discounts: these are rules that run at the till. If the app rebuilds the same rules in its own engine, the shelf label and the screen start to disagree, and that is grounds for a direct consumer complaint. Promotion rules must be pulled from a single source, and a price change must reach the label and the app at the same moment it is published.

Required integrations

  • Retail management system / ERP sync (Logo, Mikro, Netsis, Nebim) for products, prices, promotions and stock
  • e-Arşiv invoicing and a GİB (Turkish Revenue Administration) integrator; invoices issued for the final post-weighing amount
  • Virtual POS and payment infrastructure: iyzico, PayTR or Param (Turkish payment providers), Craftgate or a bank virtual POS, with pre-authorisation support
  • Meal cards (Multinet, Sodexo, Setcard, Ticket - Turkish meal-card providers) plus cash and mobile POS collection at the door
  • Scale and barcode infrastructure: weight-embedded barcode parsing, Digi / Bizerba label formats, GTIN matching
  • Maps and routing (Google Maps / HERE), SMS OTP provider and delivery status notifications

Who this page is for

  • A single-branch neighbourhood grocery or corner shop

    Starting with click-and-collect, two or three fixed delivery slots and a catalogue of the best-selling few thousand items is enough. The picker screen and the store-credit ledger genuinely cut daily work; back-office integration and courier routing can wait at this scale.

  • A regional grocery chain with five to fifteen branches

    The real issue is per-branch pricing, stock and delivery zones. Back-office integration and single-source promotion rules belong in the early phases; if the shelf label and the app price diverge, the complaint lands straight on the branch.

  • A newly launched online grocery or specialist deli

    With no physical shelf habits, catalogue, grammage and content data are built from scratch. Cold-chain packaging, delivery fee rules and a minimum basket must be defined in the first release; business account ordering pays off early with café and restaurant customers.

A phased plan that splits the budget

  1. 1

    Phase 1 — A selling core for a single branch 6-8 hafta

    A catalogue of the few thousand best-selling items, click-and-collect plus fixed delivery slots, the picker screen, card and cash-on-delivery payment, and a basic admin panel. The picker screen belongs in phase one; without it picking runs on paper and order status never reaches the customer. At this point the store can take and fulfil orders on its own.

  2. 2

    Phase 2 — Back-office integration and weighed goods 4-6 hafta

    Two-way product, price and stock flow with the store's back-office system; weight barcodes and pre-authorised payment for weighed goods; promotion rules pulled from a single source; e-Arşiv invoicing (Turkey's e-archive invoice format) and meal cards. This phase takes catalogue upkeep out of manual work, so it follows once order volume has settled.

  3. 3

    Phase 3 — Multi-branch, courier and loyalty 4-6 hafta

    Per-branch pricing, stock and delivery zones; courier routing with live delivery tracking for the customer; loyalty card matching, store credit and business account ordering; zone-based delivery fees and the returns flow. These items only pay off once there are several branches and steady courier traffic.

Typical scope and timeline

A typical grocery project covers an iOS and Android customer app, a picker app, a courier delivery app and a web admin panel. Catalogue and stock sync, the weighted-product flow, slot-based delivery, payment and e-Arşiv invoicing integration, promotion management and notification infrastructure are all in scope. UI/UX design, store listing assets, ASO, testing and the App Store and Google Play release process are included as well. Final scope and budget are agreed after a scoping call.

Estimated timeline: 10-16 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Connecting to the store's back-office system If a connector for a common back-office system exists, setup takes days; for an unlisted or older version it often cannot connect at all and the catalogue is keyed in by hand. A middleware layer can be written for an older version with no web service, or data read straight from its database; in return the integration is a separate effort line and takes time to test.
Weighed goods and grammage workflow Most off-the-shelf packages sell by unit; they offer a fixed pattern for grammage selection and the post-weighing price difference, with tolerance and approval steps usually not editable. Tolerance ranges are defined per product group, your scale label format is parsed, and the approval notification and invoicing flow follow your own checkout habits.
Monthly subscription and commission vs one-off investment The entry barrier is low and store-compliance updates plus server upkeep are included; in return, per-order commission and per-branch fees grow as volume does. Development is paid up front; after that only hosting, payment commission and maintenance remain. Unit cost falls as orders grow, but responsibility for updates sits with you and your supplier.
Ownership of catalogue and customer data Data sits in the provider's system; CSV export is usually possible, but order history, promotion rules and customer segments often move over incomplete. The database sits on your own server or cloud account, KVKK (Turkey's personal data protection law) retention periods and privacy notices follow your own processes, and the data stays with you if you change supplier.

Sector glossary

Weight barcode (embedded-weight EAN)
The barcode printed by the scale label: alongside the product code it carries the weighed grammage or amount. The app parses it and replaces the estimated weight in the basket with the real one.
Substitution
The similar item offered when an ordered product is not on the shelf. In grocery the rule is usually brand- or size-based, and the customer flags “substitution allowed” at order time.
Click and collect (“gel-al”)
The customer orders in the app and picks the bags up in store. With no courier cost it is the lowest-risk fulfilment model for a first release; notifications fire when the order is ready and when the customer arrives.
Shrinkage / spoilage (“fire”)
Goods written off before sale through spoilage, weight loss, breakage or expiry. It runs high in produce and deli, and is managed in the app through disabling items for sale, a discount shelf and count-variance reports.
FEFO (first expired, first out)
The rule that the closest-dated stock ships first. On the picker screen it says which batch to take from the shelf; sending short-dated stock to an online customer is one of the most common complaint triggers.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →