The verdict in three sentences
For 35 field sales reps taking orders from cafés, hotels and restaurants, a PWA (progressive web app) costs 40,000 to 70,000 EUR, against 70,000 to 120,000 EUR for native iOS and Android apps in Berlin. The deciding factor is not price but offline mode: in Brandenburg's rural dead zones, order entry must work without a network and sync later. A well-built PWA covers this need in most cases; native is mainly justified for heavy scanning, Bluetooth printing or an MDM-managed iPhone fleet.
PWA or native: what really changes for a beverage wholesaler
The sales director of a beverage wholesaler equipping 35 reps wants fast order entry, an up-to-date catalogue (over 1,500 SKUs, bottle deposits, customer-specific prices), each outlet's history and instant transfer to the ERP. Both technologies can do it, with concrete differences.
| Criterion (2026 situation) | PWA | Native iOS and Android app |
|---|---|---|
| Development budget | 40,000 to 70,000 EUR | 70,000 to 120,000 EUR |
| Delivery time | 3 to 4 months | 4 to 6 months |
| Developer accounts | None | Apple 99 USD a year, Google 25 USD once |
| Store publishing and review | None, instant updates | 1 to 3 days of Apple review per release |
| Offline mode (catalogue, orders) | Yes, via service worker and local storage | Yes, more robust on large volumes |
| Barcode scanning | Yes (camera), slower in bursts | Yes, fast, works with dedicated scanners |
| Bluetooth slip printing | Limited, especially on iPhone | Full |
| Annual maintenance | 15% of build | 18 to 20% of build (two platforms) |
Push notifications now work on iPhone for a PWA installed on the home screen (since iOS 16.4), which removes one of the old blockers. However, PWA local storage on Safari is still subject to stricter rules: plan regular syncing to avoid unused data being purged.
Decision matrix for 35 reps around Berlin
| Your situation | Recommended choice | Reason |
|---|---|---|
| Mixed Android and iPhone fleet, personal devices | PWA | Single codebase, no store |
| Under 50 users, orders of 10 to 40 lines | PWA | Performance more than sufficient |
| Scanning 200 items per visit in a customer warehouse | Native | Scan speed and list rendering |
| Printing delivery slips on a portable printer | Native | Full Bluetooth APIs |
| Routes in dead zones lasting over 4 hours | PWA or native, offline mandatory | Both work if designed from day one |
| Budget capped at 70,000 EUR | PWA | Native nearly doubles across two platforms |
| MDM-managed iPhone fleet and internal app | Native or PWA | MDM eases private native deployment |
Most regional wholesalers fall into the first four rows: a PWA with real offline mode is then the best balance of cost, time and maintainability.
3-year total cost and integrations
| 3-year item (35 reps) | PWA | Native iOS and Android |
|---|---|---|
| Initial development | 55,000 EUR | 98,000 EUR |
| ERP connector (items, prices, orders) | 10,000 EUR | 10,000 EUR |
| Maintenance (15% or 19% a year) | 24,750 EUR | 55,860 EUR |
| Hosting and APIs | 6,000 EUR | 6,000 EUR |
| Store accounts (Apple 3 years and Google) | 0 | About 320 EUR |
| 3-year total (estimate) | 95,750 EUR | 170,180 EUR |
The gap of about 74,000 EUR over 3 years should be weighed against your real needs. If no use case requires native, that money is better spent on features with direct value: order suggestions based on history, stock-out alerts or territory dashboards.
Mini case study
Jonas, sales director of a beverage wholesaler near Berlin, manages 35 reps who each make 12 visits a day. Today paper slips are re-keyed every evening, about 20 minutes per rep, with 3% entry errors.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
With an offline PWA at 55,000 EUR, re-keying disappears: 35 reps x 20 minutes x 220 days equals 2,570 hours a year, about 102,800 EUR at 40 EUR loaded per hour. Even counting half that gain, development is covered in under 13 months. Jonas keeps the native option for a phase 2 if Bluetooth printing becomes essential.
FAQ
Does a PWA really work without a network?
Yes, the catalogue, customer prices and orders are stored on the device and synced when the network returns. Plan 15 to 20% of the budget for reliable syncing with conflict handling.
Do we pay store fees for a PWA?
No, a PWA installs from the browser without the App Store or Google Play. Native requires 99 USD a year at Apple and 25 USD once at Google.
Can we start with a PWA and move to native later?
Yes, the API and back office stay the same; only the mobile interface is rewritten. That usually costs 40 to 60% of a native app built from the start.
How long does it take to equip 35 reps?
Allow 3 to 4 months for a PWA and 4 to 6 months for native, including a 2 to 3 week pilot with 5 reps before full rollout.
Wouldn't an off-the-shelf tool be cheaper?
Order-taking software costs 25 to 60 EUR per user per month, which is 31,500 to 75,600 EUR over 3 years for 35 reps. Custom makes sense if your pricing rules, deposits or ERP integrations are specific.
Let's scope your project. Tell us your number of reps, your ERP and your field constraints: we will recommend PWA or native with an indicative budget and schedule. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
