Mobile App for Goods Receiving with Barcode Scanning

When receiving goods at the warehouse, an operator spends 15 minutes manually entering 50 boxes. With our app, it takes 2 minutes. Replacing paper documents and manual entry with scanning and automatic verification against the Purchase Order (PO) — a real case we implemented at a warehouse with 100 daily receipts. Time savings: 8 hours of staff work daily, error reduction from 5% to 0.5%. The solution is a mobile app with a built-in barcode and Data Matrix scanner. Contact us to get a prototype in 2 days and evaluate acceleration at your warehouse.

How Automation with Scanner Speeds Up Receiving by 5x

Manual receiving leads to delays, input errors, and disputes with suppliers. A barcode scanner speeds up the process by 3–5 times: the operator no longer needs to enter SKUs and quantities by hand. Parsing GS1-128 allows extracting GTIN, lot number, expiry date, and quantity from a single barcode. According to GS1 General Specifications, this format supports up to 48 digits. For example, a pallet with SSCC provides all data about the boxes inside immediately. We integrated GS1-128 and Data Matrix, including Chestny Znak marking codes. Additionally, EAN-13, ITF-14, Code 128, and QR are supported — a full set for any supplier.

Scanning Data Matrix for Mandatory Marking

For goods subject to mandatory marking (Chestny Znak), Data Matrix is the only format meeting legal requirements. The app parses the cryptotail, checks the code online via the Chestny Znak API, and records the status — allowed for sale, blocked, or expired. This prevents acceptance of counterfeit goods and fines under Federal Law 54-FZ. Photo capture of defects at this stage allows documenting damage and attaching it to the discrepancy report TORG-2.

Verification Against Purchase Order: Workflow

The primary scenario: load the Purchase Order (PO) before receiving, scan incoming goods, and compare actuals with the plan in real time.

data class ReceivingLine(
    val poLineId: String,
    val sku: String,
    val gtin: String,
    val orderedQty: Double,
    val receivedQty: Double = 0.0,
    val lotNumber: String? = null,
    val expiryDate: LocalDate? = null,
    val status: LineStatus = LineStatus.PENDING
)

class ReceivingViewModel : ViewModel() {
    fun processScan(parsedBarcode: Map<String, String>) {
        val gtin = parsedBarcode["01"] ?: parsedBarcode["02"] ?: return
        val lot = parsedBarcode["10"]
        val expiry = parsedBarcode["17"]?.let { parseExpiry(it) }
        val qty = parsedBarcode["37"]?.toDoubleOrNull() ?: 1.0

        val line = findLineByGtin(gtin) ?: run {
            // товар не в PO — предупреждение, фиксируем как неожиданный
            recordUnexpectedItem(gtin, qty)
            return
        }

        val updated = line.copy(
            receivedQty = line.receivedQty + qty,
            lotNumber = lot ?: line.lotNumber,
            expiryDate = expiry ?: line.expiryDate,
            status = when {
                line.receivedQty + qty > line.orderedQty * 1.05 -> LineStatus.OVER_RECEIVED
                abs(line.receivedQty + qty - line.orderedQty) < 0.01 -> LineStatus.COMPLETED
                else -> LineStatus.IN_PROGRESS
            }
        )
        updateLine(updated)
    }
}

Over-receiving and under-receiving both require visual warnings. Color coding: green (within tolerance), yellow (minor discrepancy), red (significant overage or defect). Additionally, photos of damages are captured — each image is linked to the report line and stored in S3 with a time-limited URL. Delivery verification at this stage guarantees inventory accuracy.

What to Do When Discrepancies Occur?

If scanning reveals overages or shortages, the app prompts the operator to photograph the problematic item and generate a TORG-2 discrepancy report. The document can be sent to the supplier immediately via email. For warehouse inventory, this feature helps quickly identify systematic delivery errors.

How to Set Up GS1-128 Scanning: Step-by-Step Instructions

1. Connect the scanner to the device via Bluetooth.
2. Open the app and select "Receiving".
3. Point the camera at the GS1-128 barcode.
4. Verify the recognized data: GTIN, lot, expiry, quantity.
5. Confirm the receipt — data is automatically matched against the PO.

What's Included in Turnkey Development

Additionally, we provide: load testing, data migration from legacy systems, preparation of the app for publication in App Store and Google Play (including Code Signing certificates and Provisioning Profiles). Order turnkey development — get a ready solution with a warranty.

Receiving Speed Comparison

For a warehouse with 100 daily receipts, the savings are about 8 hours of staff labor. Savings from reduced fines and increased turnover can be significant. Automated receiving is 3–5 times faster and 10 times more accurate than manual.

Integration with Chestny Znak

The app automatically validates each Data Matrix code via the Chestny Znak API. If the code has already been withdrawn from circulation or counterfeited, the operator receives a warning. Upon completion of receiving, a report listing all verified codes is generated, reducing the risk of claims from regulatory authorities. This procedure can be configured to send automatically via email or direct push to WMS.

How to Get a Prototype in 2 Days?

Leave a request on our website — we will analyze your warehouse process, prepare a prototype of the app, and demonstrate it. Contact us to discuss integration and timelines.

Quality Guarantees

Every project undergoes code review, automated tests (UI + unit), and integration testing with real scanners. We use CI/CD (GitHub Actions) for build and publication to TestFlight/Google Play Console. Certified Apple and Google developers. Get a consultation — we will prepare a commercial proposal and prototype in 2 business days. Contact us to calculate timelines and cost individually.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.