Pan Innovation House is a Gaziantep-based software company that builds ERP-connected iOS and Android apps for warehouse, quality and maintenance teams in the factory and for sales and service teams in the field. We design iOS and Android applications around your needs, build them with offline mode and push notification infrastructure, and manage the App Store and Google Play release process; approval decisions rest with the stores.
Prepared by Pan Innovation House, a software company based in Gaziantep, Türkiye · Last reviewed:
A mobile app is your business's digital arm reaching the field, the sales team and the customer. What sets it apart from an off-the-shelf app is that it is built around your process: a warehouse worker counting stock, a dealer placing an order, a customer booking an appointment — each works within screens designed for their own flow, inside their own permission boundaries. Where template solutions strain, custom development fits the software to your workflow instead of forcing your workflow into the software.
The concrete case for a custom mobile app is control and continuity. An app that talks directly to your production tracking, ERP, CRM or accounting system; that keeps working in the field without internet and syncs data when the connection returns; that stores your data without opening it to third parties — you only get that with a purpose-built design. Ready-made apps go so far; as the business grows, every constraint you cannot customise turns into cost.
Pan Innovation House works from its Gaziantep headquarters and its London office; we know the field realities of production-heavy sectors such as carpets, machinery, textiles and food. We design apps API-first and deliver iteratively; deliveries go through a review step before they go live. The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. After launch, the maintenance scope and response times are defined in the contract.
For teams counting stock in the warehouse, walking quality control rounds, logging machine maintenance or tracking deliveries. Field apps with photo and barcode support that work offline in production areas where the internet is weak.
For carpet, textile and machinery exporters: mobile apps where field salespeople and dealers place orders from their phones, see stock and prices, and track order status. Sales carry on without being tied to a desktop.
For SMEs and brands that want to move processes such as loyalty, appointments, order tracking or service requests onto the customer's phone. Apps that announce campaigns via push notifications and open a direct channel to the customer.
For executives who want production, sales and finance data on their phones. Enterprise apps fed by your ERP or BI system, delivering instant summaries and approval flows on mobile.
We build both platforms from one codebase with React Native and Expo, adding native modules (Swift, Kotlin) where performance or device hardware demands it. One development effort, two stores.
Data entry continues in the field without internet and syncs with the server when the connection returns. Local storage, conflict handling and queue logic keep the field working when the connection drops.
Instant push notification infrastructure for order confirmations, stock alerts, campaign announcements or service reminders. Notification flows that bring users back into the app and inform them on time.
Barcode and QR scanning with the camera, GPS location, photo capture, file upload and biometric sign-in. Device features that meet the field's real needs.
API connections to your ERP, CRM, production tracking (MES) or accounting system. The mobile app is not an isolated island — it becomes part of your existing software ecosystem.
JWT-based authentication, role and permission boundaries and secure token storage. Every user sees only the data and screens they are authorised for.
App Store and Google Play submission, review handling and release management. After launch, over-the-air (OTA) updates let us ship some interface and JavaScript-level fixes without a new store review; native code changes need a new version and store approval.
Not every field, warehouse or dealer team needs an app published in the stores. The tables below set out four common routes, what the project covers and what it does not, what you receive at handover, and what drives time and cost.
The choice mostly depends on whether users must work offline, how much they rely on device features such as the camera, barcode scanning or location, how many users there are and how often data moves to and from the ERP.
| Route | Enough when | Where it struggles | Cost structure |
|---|---|---|---|
| Mobile-friendly web panel or PWA | Users are mostly online; filling in forms, viewing lists and entering orders is enough. | Long periods offline, background location and some device features are limited in the browser; on iOS, notifications and installation behave differently from a native app. | One code base; no store process. |
| The mobile app of your ERP or other packaged software | The app from the software you already use does the job; few extra fields or flows are needed. | Business-specific field flows, offline working and custom screens depend on the product, and per-user licences may apply. Ask the software vendor. | User licence or subscription. |
| Low-code app platform | Simple data-capture and approval screens; you want a pilot quickly. | It can hit limits with complex business rules, heavy use and deep ERP links; the app lives inside the platform and is hard to move elsewhere. | Subscription per user or per use. |
| A custom iOS and Android app | Teams work offline in the field and need device features such as barcode, camera and location, plus regular sync with the ERP. | Design, testing on real devices and store processes take time, and the approval decision lies with Apple and Google. Maintenance is needed as operating systems update. | A project fee and a maintenance agreement. |
Scope is written down for every project during discovery. The split below shows the boundaries that most often get blurred in enterprise mobile projects.
| Area | In the project | Out of scope or agreed separately |
|---|---|---|
| App and back end | Screens, user roles, offline working and sync, notification infrastructure, the server side and an admin panel. | Users' phones and tablets, and mobile device management (MDM) software for company devices, are separate items. |
| Store publishing | Preparing the App Store and Google Play submissions and managing the release process. | We recommend opening the developer accounts in your name; account fees are yours and the approval decision lies with the stores. |
| ERP and other systems | Moving the data the app needs to and from the ERP, CRM or accounting software in the direction set during discovery. | Licence and API fees of the connected systems are between you and their vendors. |
| Consumer apps | This page covers enterprise apps for field, warehouse and dealer teams. | Consumer apps such as e-commerce, booking and ordering are covered separately on our mobile app development page. |
Handover covers the working app and the pieces you need to keep it running.
| Deliverable | What it is for |
|---|---|
| A clickable prototype | Lets you confirm the flow with field users before development starts. |
| iOS and Android releases | Published after passing a closed test group. |
| Admin panel and server side | User, permission and content management; the infrastructure that runs sync and notifications. |
| Source code | The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. |
A firm figure is given in writing after discovery. These factors set the quote most.
| Factor | Why it matters |
|---|---|
| Number of screens and roles | Every role needs its own permissions and every screen its own tests. |
| Offline working | Capturing data without a connection and syncing later requires conflict rules. |
| Device features | Barcode, camera, location or an external device connection are each separate development and testing work. |
| Direction of integration | Only reading from the ERP and writing records back to it are different workloads. |
| Range of devices and versions | The operating-system versions and device models to support set the testing effort. |
If these are ready, the first call is concrete; we can fill any gaps together during discovery. The first 30-minute call is free; the scope of an on-site discovery, and its fee if any, is agreed in writing during that call.
We get to know the field, sales or customer-side process first-hand, pinning down user roles, screens and integration points. This stage is the foundation for setting cost and timeline realistically.
We present the flow and screen designs as a clickable prototype. Before anyone in the field uses the app, we validate the logic and ergonomics together.
We build the app piece by piece, in working releases. With an API-first architecture, backend and mobile progress in parallel; you see every release on test devices and give feedback.
Testing on real devices, a closed test group and store submission. We manage the App Store and Google Play release process; approval decisions rest with the stores. Deliveries go through a review step before they go live.
Post-launch monitoring, bug fixing and new feature development. Fast intervention with OTA updates where the change allows it, and support under the maintenance scope defined in the contract. The source code we write is handed over to you as defined in the contract.
A firm figure only emerges after discovery; the number of screens, role structure, offline requirements and integration scope drive the cost. Rather than quoting an estimate up front, we clarify the scope and present a transparent proposal and timeline.
Yes. The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. The app's repository, store accounts and infrastructure are handed over to you; if you later want to work with another team, you can continue from that handover.
On most projects we build both platforms from one codebase with React Native and Expo, which cuts both time and cost. Where high performance or specific hardware is required, we add native modules.
When needed, yes. For field conditions with weak or no connectivity we design offline operation: data is stored on the device and syncs with the server when the connection returns.
Yes. We design the app API-first and integrate it with your existing ERP, CRM, production tracking or accounting system so data flows from a single source.
Yes. We carry on with maintenance, bug fixing and new feature development under the maintenance scope defined in the contract. With Expo OTA updates we can ship some interface and JavaScript-level changes without a new store review; native code or permission changes need a new version and store approval, and OTA use is itself subject to store rules.
The first step in having a mobile app built is a discovery exercise that clarifies who will use the app, for what work and through which screens. At this stage we work out user roles, screens and the systems to connect to, such as the ERP or CRM; cost and timeline are also set realistically here. We then show the flow in a clickable prototype and move on to development once the logic and usability have been validated with users in the field.
We listen to what you need and tell you whether custom development or an off-the-shelf product fits better. The first 30-minute call is free; the scope of an on-site discovery, and its fee if any, is agreed in writing during that call.
Desktop applications that keep going even when the internet drops, connect directly to barcodes and local hardware, and run fast on the shop floor and in the office. For Windows and macOS, with the source code we write handed over to you.
Details →Web applications that are installable, work offline and meet the Core Web Vitals thresholds. Measured speed, a solid technical SEO foundation and an experience developed specifically for your brand.
Details →Custom API and integration development that gets your ERP, CRM, marketplace, e-invoice and production systems talking to each other, with a two-way, secure and traceable data flow.
Details →We set up electronic data interchange with retail chains and major buyers alongside your ERP. We turn incoming orders into your records, your shipments into dispatch advices and your invoices into the message the buyer expects; a faulty message lands in a queue, gets corrected and is sent again.
Details →We build the cloud infrastructure that keeps your software stable, secure and scalable: an automated, observable and reversible flow from code change to production release.
Details →ERP software designed around your processes, bringing your entire operation — from production to finance — onto a single backbone. Where the off-the-shelf package falls short, we build a system that fits your factory exactly.
Details →
