A mobile app for manufacturers: dealer orders and paperless shop-floor work.

A plant rarely needs an app for mass consumers. It needs something else: dealers ordering from the current price list in a minute, service engineers closing a job with photos, and section supervisors recording output and defects right at the machine. These are the apps we build — with 1C exchange.

Pricefrom ₸2,500,000Timelinefrom 8 weeksAsk a question
Manufacturing
Sign-in and role sele…
Catalog with partner …
Cart and checkout
Pay with Kaspi
Reminder: tomorrow at 10:00

An app for a manufacturer is almost always a work tool, not a storefront. Three typical scenarios: a dealer app for regular orders, a service app for installing and maintaining equipment at customer sites, and an internal app for the workshop and warehouse. Each has an audience of tens or hundreds of people, and it pays off through saved time and fewer errors, not through downloads.

A dealer app replaces calls and Excel: a catalog with partner prices, stock, reorders, shipment status, documents and reconciliation. A service app covers the job list, checklists, before and after photos, customer signature and a completion certificate. An internal app handles barcode and QR scanning, raw material receipt, output by work area, quality checks, and offline work where the workshop has no signal.

We build natively (Swift, Kotlin) or with Flutter — the choice depends on scanner and offline requirements and budget. For small teams a PWA is often enough: it opens in a phone browser or on a handheld data terminal.

What it needs

What a manufacturer's app can do.

Dealer catalog and prices

Items from 1C with individual prices, discounts and warehouse stock. Dealers see exactly what they can order.

Ordering and reorders

A cart, one-tap repeat of a previous order, item comments, statuses from confirmation to shipment with push notifications.

Documents and reconciliation

Invoices, waybills, reconciliation statements and e-invoices from 1C in one section, plus the partner's debt and shipment limit.

Service visits

A list of installation and maintenance jobs, route, work checklist, photos, the customer's on-screen signature and an automatic completion certificate.

Shop-floor scanning

Barcodes and QR codes on batches, raw materials and finished goods: receipt, transfers, output, stock-taking from a phone camera or handheld terminal.

Quality control

QC checklists per operation, defect photos, defect reason, batch hold and supervisor notification.

Offline mode

Works without a connection in the workshop and on site, syncs when the network is back without losing data.

Roles and access

Dealer, manager, engineer, supervisor, storekeeper and executive each see their own screens and data; sign-in by phone number or corporate account.

App screens

Main screens.

  • Sign-in and role selection
  • Catalog with partner prices and stock
  • Cart and checkout
  • My orders and shipment statuses
  • Documents, reconciliation and balance
  • Service requests and job card
  • Scanner: receipt, transfer, output
  • QC checklists and defect logging
  • Notifications
  • Executive dashboard
Integrations
1C: Manufacturing, ERP, Trade ManagementBitrix24 / amoCRME-invoicing system via 1CBarcode scanners and handheld terminalsPush notifications2GIS maps and routesKaspi Pay for prepayment
When you do not need an app

An honest alternative for a smaller plant.

If you have fewer than twenty dealers and they order once a month, a store app will not pay off: a dealer portal on the website with the same functions — catalog, prices, ordering, documents — is enough. That starts at ₸1,500,000 as part of a website.

For a workshop and warehouse with a small team, a PWA works — a web app that opens on a phone or handheld terminal without publishing to the App Store or Google Play. From ₸1,200,000.

A native iOS and Android app makes sense when there are hundreds of users, and you need reliable offline mode, a fast scanner or Bluetooth equipment. Then it is from ₸2,500,000 and 8 weeks or more.

Connection to the books

An app is useless without 1C exchange.

Prices, stock, orders, shipments and documents live in 1C, and the app should take them from there rather than from a separate database. So the work starts with a review of your accounting setup: which configuration, whether it is modified, how items and attributes are kept, whether HTTP services exist or an intermediate server is needed.

The typical setup is our own backend between 1C and the app: it caches the catalog, accepts orders and scans, passes them to 1C on schedule or instantly, and keeps working if 1C is unavailable. This keeps the app fast and spares the accounting system from requests by hundreds of users.

We allow 1–2 weeks at the start of the project for this review and the exchange design — cheaper than reworking the integration after launch.

Price and timeline

What drives the price of an app.

A PWA for the workshop, warehouse or dealers starts at ₸1,200,000. A native or Flutter app for iOS and Android with a backend and 1C exchange starts at ₸2,500,000, from 8 weeks. A multi-role app (dealers, service, workshop) with offline mode and handheld terminal support is estimated after a review.

The price goes up with: the number of roles and scenarios, offline mode, integration with scanners and equipment, the complexity of 1C exchange, executive reports. Base prices are on the mobile apps page.

Questions

The short version.

How much does an app for a manufacturer cost?

A PWA starts at ₸1,200,000, an iOS and Android app with 1C exchange at ₸2,500,000. A multi-role app with offline mode and handheld terminals is estimated after reviewing your accounting setup.

Native or Flutter?

We build natively (Swift, Kotlin) or with Flutter. Flutter is cheaper when the interface is the same on both platforms; native development is justified for heavy scanner, camera and Bluetooth use and complex offline scenarios.

Will the app run on handheld data terminals?

Yes, most modern terminals run Android, and an Android app or PWA runs on them with the hardware scanner. We agree on terminal models in advance.

Does an internal app need to be published in the stores?

Not necessarily. An internal app can be distributed through managed installation on Android and closed testing, or Apple Business Manager on iOS, and a PWA needs no stores at all.

How long does development take?

A PWA takes from 5–6 weeks, an iOS and Android app from 8 weeks, of which 1–2 weeks go to reviewing 1C and designing the exchange. We launch with a first group of users and expand based on feedback.

Discuss a project

Considering an app for dealers or the workshop? Describe the process — we will tell you whether you need it and what it costs.

Tell us who will use the app, how many people, which 1C you use and what is currently done on paper or by phone. We will reply with options and an estimate within 1–2 business days.

We reply during working hours, usually within a couple of hours.
Chat on WhatsAppChat on Telegram