Let your dealers order from a screen that shows their own price, not from WhatsApp

In wholesale, most of the day goes into writing up orders: the dealer calls, the case quantity gets debated, someone checks which version of the price list applies, and the order is keyed into the ERP by hand. Every step in that chain leaves room for error. A B2B ordering app lets the dealer see their own net price and account balance and push the order straight into your system.

How many separate apps does this need?

  • 01

    Dealer Ordering App (iOS + Android)

    An ordering app where each dealer signs in against their own price list, account balance and payment terms; catalogue, case-multiple cart, reorder from a past order, and order status tracking.

  • 02

    Field Sales Rep App

    An app the field rep uses to visit dealers on their route, enter orders with no connection, record collections and leave shelf/stock notes; the queue syncs as soon as connectivity returns.

  • 03

    Web Admin Panel

    The panel where price lists, discount tiers, promotion rules, credit limits, the order approval queue, the dispatch-day calendar and ERP mappings are managed; per-dealer sales and receivables reports live here too.

What the app includes

  • Rebuild a cart from a past order with one tap
  • Bulk entry screen: type product code and quantity, line after line
  • Case-multiple check that flags quantities outside full cases
  • Dealer-specific net price with the discount breakdown under each line
  • Account statement, due-date calendar and open cheque list
  • Credit-limit overrun sends the order to a sales manager approval queue
  • Free-goods promotions added to the cart as zero-priced lines
  • Delivery date picked from the region's shipping-day calendar
  • Short-supply notice per line with an equivalent-product suggestion
  • Field rep route list with visit close-out that works offline
  • Cash and cheque collection recorded in the field with a receipt photo
  • Dispatch note and carrier tracking number attached to the order detail

State of the sector

In wholesale and dealer sales, ordering still runs largely on phone calls, WhatsApp and the field rep's notebook. In that setup, taking orders depends on people: orders come in as long as sales staff are reachable during working hours, and anything that arrives in the evening or at the weekend waits until the next day. Misheard case quantities and lines priced off an outdated list come back as returns and invoice corrections. When large suppliers give their dealers their own ordering app, how easily a brand can be reordered becomes part of the competition for shelf space. A supplier without an app simply is not on the dealer's screen.

Metrics that matter here

  • Share of orders placed through the app — As more orders come through the app instead of phone calls and WhatsApp, the burden of writing up orders falls away from sales staff.
  • Order line error and return rate — Because case multiples, pricing and stock are checked in the cart, fewer lines go through with the wrong quantity or an outdated price.
  • Active dealers and reorder frequency — Frequently bought items and reorder-from-history shortcuts make it easier for dealers to keep ordering regularly without gaps.
  • Overdue receivables balance — Because limit and payment term checks run at the moment of ordering, open-account shipments to risky dealers are prevented.

Common mistakes in this sector

  • Calculating the price on the device When discount logic is buried inside the app, a dealer who has not taken the update keeps ordering at the old price after the rules change. Pricing must be calculated on the server, and the amount shown in the cart locked to the order record.
  • Copying retail cart logic Quantity steppers, single-product cards and an “add to cart” flow do not work in wholesale. A dealer enters 60-80 lines in one sitting; without fast list entry, barcode add and reorder from history, the app gets abandoned.
  • Showing stock without allocating it If the stock shown on screen is not reserved, several dealers order the same batch and shipments come up short. Allocation must happen at confirmation, and any line that cannot be filled must be flagged clearly to the dealer.
  • Leaving the field rep app for later If the field team carries on with the old method, part of your orders stays outside the system and the sales picture in the panel is incomplete. The field flow should be covered in the first release, at minimum with offline order entry.

Regulation and compliance

Because a dealer order is a commercial transaction, dispatch and invoicing fall under GİB (Turkish Revenue Administration) regulations: if you are registered for e-Fatura and e-Arşiv (Turkey's mandatory e-invoicing system), invoices for orders coming out of the app must be issued through an integrator, and if you fall under e-İrsaliye, the dispatch waybill must be produced electronically too. Tax ID verification when opening a dealer account can be done through the GİB taxpayer lookup. Under KVKK (Turkey's data protection law, aligned with GDPR), even though the dealer is a legal entity, the contact person's name, phone number and location data are personal data; for the location records collected in the field rep app you need a privacy notice, a defined retention period and defined access rights.

The real challenges in this sector

  • Every dealer sees a different price

    In wholesale there is no single list price: the list depends on the dealer group, discounts depend on the product group, contracted customers get product-specific fixed prices, and volume tiers add another discount on top. The app must not calculate the price on the device; it should run through a single pricing engine on the server and write the source of the price into the cart as well. Otherwise the dealer sees one price and the invoice shows another.

  • Credit limit and overdue balance checks

    If a dealer trading on open account has hit their limit or has an overdue cheque, the order needs to be stopped in the cart. Limits change in the ERP in real time; if the app trusts a cached balance, risky orders get through. The right approach is a fresh balance query to the ERP at cart confirmation, and if the answer is slow, moving the order into an “awaiting approval” queue for the sales manager rather than rejecting it.

  • Case multiples, minimum order values and free-goods rules

    Products are sold by case, pack or pallet, not by unit; you cannot order 7 units out of a 12-piece case. On top of that there are region-specific minimum order values and free-goods promotions of the “buy 10 cases, get 1 free” kind. These rules have to be shown clearly the moment items go into the cart, not fixed by hand at the warehouse after the order is submitted.

  • Two-way stock and order sync with the ERP

    If the stock, account and price data on the Logo, Netsis, Mikro or Nebim side drifts from what the app shows, three dealers will order the same last 20 cases. Rather than full stock sync, stock should be allocated at order confirmation, the dealer should be told which lines could only be partly filled, and the order sent to the ERP should carry an identity that prevents duplicate records on retry.

  • Offline field work and conflict resolution

    The field rep takes orders in a warehouse basement, an industrial estate or a village market where there is no signal. The catalogue, dealer-specific prices and limits have to be stored on the device, and the order created locally and held in a queue. If the price changed before sync, or the dealer placed the same order through their own app, the conflict must not be silently overwritten; the rep should get a confirmation screen showing the difference.

Required integrations

  • Account, stock, price list and order transfer with Logo, Netsis, Mikro or Nebim ERP
  • e-Fatura / e-Arşiv (Turkey's mandatory e-invoicing system) and e-İrsaliye (electronic waybill) integrator, compliant with GİB (Turkish Revenue Administration) rules
  • Tax ID verification and dealer account opening via GİB taxpayer lookup
  • Bank virtual POS plus iyzico/PayTR (Turkish payment providers) for settling balances by card and taking payment outside open account
  • Dispatch waybill and tracking number matching with Yurtiçi, Aras, MNG or Sürat (Turkish courier companies)
  • SMS/OTP service for dealer contact sign-in and order approval notifications

Who this page is for

  • A regional food or beverage wholesaler with a field sales team

    The weight is in the field, so the rep app belongs in phase one: routes, offline ordering, collections and van stock. The dealer-facing app is layered on top, with shipping-day calendars and free-goods rules set up early.

  • A manufacturer or brand just opening its dealer network

    With few dealers the rule set is still simple. Phase one alone is enough: catalogue, dealer-group pricing, case-multiple cart and the panel. If the ERP is not settled yet, orders move by file export and the two-way integration is added as the network grows.

  • A single-warehouse spare parts or hardware distributor with a huge item list

    The problem is not field work but finding the right part among tens of thousands of item codes. Priority goes to OEM and cross-reference code search, filtering by vehicle or machine model, the code-and-quantity bulk entry screen and equivalent suggestions on short supply; the rep module can wait until last.

A phased plan that splits the budget

  1. 1

    Phase 1 — A core the dealer can order with, on its own 5-7 hafta

    Catalogue, dealer login, dealer-specific price list and discount tiers, case-multiple cart, reorder from history and order status tracking. The panel manages products, price lists and the order queue. Transfer to the ERP is one-way file or manual approval at this stage, so dealers can order from day one without waiting on integration work.

  2. 2

    Phase 2 — ERP link, credit risk and promotion rules 4-6 hafta

    Two-way link with the ERP (Logo, Netsis, Mikro, Nebim): stock, balances and prices pulled in, orders written back as order documents. Adds a live credit and due-date check at checkout, an approval queue for limit overruns, free-goods and quantity-tier promotions, the shipping-day calendar and short-supply notices. Building it after Phase 1 is live means the rules are shaped by real order traffic.

  3. 3

    Phase 3 — Field team, collections and document flow 4-5 hafta

    The field rep app arrives: route list, offline catalogue and prices, queued orders, a conflict screen when prices or limits changed, cash and cheque collection, shelf and competitor notes. Alongside it the e-dispatch-note integrator (Turkey's electronic waybill system), carrier tracking, card payment against the balance, and per-dealer sales and ageing reports. Field work comes last because offline conflict rules only settle once the head-office flow is stable.

Typical scope and timeline

Catalogue and dealer-specific pricing engine, credit limit and payment term checks, case-multiple cart and promotion rules, order approval flow, two-way ERP integration, offline ordering for field reps, admin panel and reports. Native iOS and Android, store release and QA included. e-İrsaliye (electronic waybill) and virtual POS are optional modules.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Connecting to the ERP you already run Packaged B2B portals ship connectors for common ERPs; on a standard setup stock and balance sync runs within days. A custom build writes the connector from scratch, which takes longer, but it can follow customised ERP fields, a second company code and warehouse-level stock logic exactly.
How deep the pricing rules can go Common rules such as dealer-group discounts and quantity tiers are settings in a packaged product; no developer needed to change them. Contract prices, cases where a product group and a dealer group overlap, and the order in which free goods combine with tier discounts only come out right when the rule engine is written to your logic.
Monthly per-dealer fees versus a one-off build With a handful of dealers a subscription is cheap and needs no upfront budget; maintenance and releases stay with the vendor. Per-user fees grow with dealer count and order volume; a custom build front-loads the cost, then leaves hosting and maintenance, and adding a dealer costs nothing extra.
Data ownership and who owns the store listing Some packaged services put dealers inside a shared app; setup is fast and order and account data is usually exportable. A custom app is published under your own developer account and name, the database sits on your servers, and changing supplier does not change the icon and login habit on the dealer's phone.

Sector glossary

Free goods (mal fazlası)
A discount paid in goods instead of money — buy ten cases, get one free. The free quantity shows as its own zero-priced line on the order and invoice, yet it still consumes real warehouse stock.
Case multiple and unit conversion
Selling in cases, packs or pallets rather than single units. You cannot order seven pieces from a twelve-piece case; the app must know the conversion between piece, case and pallet and suggest the nearest valid multiple in the cart.
Credit risk limit (cari risk limiti)
The ceiling of open-account exposure allowed for one dealer. It counts not only the outstanding balance but also cheques and notes in collection plus approved-but-unshipped orders; checkout is validated against that total.
Van sales versus pre-sales (sıcak/soğuk satış)
In van sales the rep carries stock on the vehicle and closes order and delivery in the same visit, so vehicle stock must decrement live in the app. In pre-sales the rep only takes the order and the warehouse ships it on the next shipping day.
Partial fulfilment and backorder
Shipping the part of the order that stock covers and leaving the rest open. Whether the short line is cancelled, rolled to the next shipment or swapped for an equivalent product has to be agreed as a rule with the dealer in advance.

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 →