How to Implement Barcode and QR Code Scanning in a Nigerian Inventory App

Nigerian wholesalers, retailers, and logistics operators increasingly need digital inventory management that works with existing product barcodes. Adding scanning capability to your inventory app removes the need for manual data entry, reduces stock errors, and speeds up stocktaking and dispatch workflows significantly.

This guide covers choosing the right scanning library, integrating the camera, handling different barcode formats, managing errors, and connecting scan results to your inventory database.

Common Myths vs. Facts About Barcode Scanning in Nigerian Apps

Step 1: Choose a Scanning Library for Your Platform

Your choice of scanning library depends on your app's platform. For React Native apps, the two most reliable options in 2026 are expo-barcode-scanner for Expo-managed projects and Vision Camera with the vision-camera-code-scanner plugin for bare React Native. Vision Camera is faster and more accurate on low-end Android devices, which are common among Nigerian warehouse staff, making it the better choice for production inventory apps.

For Flutter apps, use mobile_scanner, which is actively maintained and supports all major barcode formats. For Android-native apps, Google's ML Kit Barcode Scanning API provides fast, on-device decoding with no network requirement and strong performance on mid-range Tecno and Infinix devices common in Nigerian business environments.

Step 2: Request and Handle Camera Permissions

You must request camera permission from the user before activating the scanner. In React Native with Expo, request this on the screen where the scanner appears:

import { Camera } from 'expo-camera';

const [hasPermission, setHasPermission] = useState(null);

useEffect(() => {
  (async () => {
    const { status } = await Camera.requestCameraPermissionsAsync();
    setHasPermission(status === 'granted');
  })();
}, []);

if (hasPermission === null) return <View />;
if (hasPermission === false) return (
  <Text>Camera access is required to scan barcodes. 
  Please enable it in your device settings.</Text>
);

If the user denies permission, show a clear message explaining why camera access is needed and link them to their device settings. Never silently fail on a permission denial, as this leaves users confused about why the scanner is not working.

Step 3: Build the Scanner Component

Create a full-screen scanner view with a visible scanning area indicator. Nigerian users who are new to barcode scanning need visual guidance to align the product barcode with the camera. A translucent overlay with a highlighted scan box in the centre communicates this clearly without instructions.

import { BarCodeScanner } from 'expo-barcode-scanner';

function InventoryScanner({ onScanComplete }) {
  const [scanned, setScanned] = useState(false);

  const handleBarCodeScanned = ({ type, data }) => {
    if (scanned) return;
    setScanned(true);
    onScanComplete({ type, data });
  };

  return (
    <BarCodeScanner
      onBarCodeScanned={handleBarCodeScanned}
      barCodeTypes={[
        BarCodeScanner.Constants.BarCodeType.ean13,
        BarCodeScanner.Constants.BarCodeType.ean8,
        BarCodeScanner.Constants.BarCodeType.qr,
        BarCodeScanner.Constants.BarCodeType.code128,
      ]}
      style={StyleSheet.absoluteFillObject}
    />
  );
}

The scanned flag prevents the same barcode from firing multiple lookup requests while the user holds the phone steady. Reset it after the lookup completes to allow the next scan.

Step 4: Look Up Scanned Codes in Your Inventory Database

When a scan completes, use the barcode value to query your local SQLite database first. If found, display the product details and let the user update quantity. If not found locally, query your remote API if connectivity is available. If still not found, prompt the user to add a new product or flag the item for review.

Design this lookup to complete in under 500 milliseconds on a local query. Nigerian warehouse staff scanning dozens of items in a stocktake session will abandon the app if each scan requires a two-second wait. A local database of your product catalogue makes the scanning workflow fast enough for real production use.

Step 5: Handle Errors and Edge Cases

Common scanning errors include blurry images from camera focus lag, damaged or partially covered barcodes, and barcodes printed at angles or on curved surfaces. Build a manual entry fallback that lets users type a barcode number when the camera cannot decode it. This fallback should be one tap away from the scanner screen, not buried in a menu.

Log failed scan attempts with the barcode image if possible. Reviewing failed scans after deployment tells you which product types or label conditions cause problems in your users' actual environments, and guides decisions about label reprinting or scanner UI adjustments.

Step 6: Integrate Scanning Into Your Inventory Workflow

Barcode scanning is most valuable when it is embedded directly into your key inventory workflows: receiving stock, fulfilling orders, conducting stocktakes, and processing returns. For each workflow, design the scan action to pre-populate the relevant form fields so the user only needs to confirm quantities and tap submit.

For offline environments, queue scan-triggered inventory updates in a local sync queue and process them when connectivity returns, using the conflict resolution approach described in your offline persistence implementation. A scan that updates inventory locally but fails to sync should show the user a pending status rather than silently recording the change as complete.

Frequently Asked Questions