The custom Fiori applications are web-based and run in any modern browser on Android, iOS or Windows devices — including ruggedised barcode scanners that have an integrated browser. The user opens the app, logs in with their SAP credentials and selects the transaction they need to perform. When they scan a barcode or QR code, the app reads the encoded data (material number, batch, serial number, storage location), pre-fills the relevant fields and prompts the user to confirm or adjust quantities. On confirmation, the app calls SAP OData services to post the transaction — the result appears in SAP immediately, with the user's ID and timestamp. The apps are designed for warehouse and shop floor use: large touch targets, minimal text input, clear error messages when something is wrong (wrong material scanned, quantity exceeds open order, batch not available in the scanned storage location). Offline mode is available for environments with intermittent Wi-Fi — transactions queue locally and sync when connectivity is restored.

We support all common barcode formats: 1D (Code 128, Code 39, EAN-13, EAN-8, ITF-14, GS1-128) and 2D (QR Code, Data Matrix, PDF417). The format used depends on your requirements — GS1-128 for supply chain standards compliance, QR for high data density (useful when you need to encode batch, expiry date, serial number and lot in one symbol), Code 128 for general warehouse use. Labels are printed from SAP using standard SAP output configuration (SAPScript, SmartForms or Adobe Forms) triggered by the relevant transaction — goods receipt, production order release, goods issue, packing. The label template is designed during implementation to include the data fields your operations need: material number, description, batch number, production date, expiry date, quantity, unit, plant, storage location, customer part number and any other field from the SAP document. Multiple label formats can coexist — a standard internal label for your warehouse, a customer-specific label for despatch, a compliance label for regulatory requirements — with the correct format selected automatically based on the transaction context.

Inventory errors in SAP environments typically come from three sources: manual transcription (writing down a batch number and typing it into SAP later — any step where a human copies data is a step where errors occur), time lag (updating SAP hours after the physical movement, during which SAP stock records do not reflect reality and decisions are made on stale data) and missing transactions (movements that happen on the floor and never get recorded in SAP at all, causing perpetual stock discrepancies). Barcode scanning eliminates all three: the scanner reads the data without transcription, the transaction posts the moment the scan happens and the process requires a scan to proceed — there is no "I'll do it later." The result is a SAP stock record that reflects the physical reality of your warehouse in real time, which means MRP plans on accurate data, picking lists reference accurate batch availability and cycle counts produce fewer discrepancies.

SAP delivers standard Fiori apps for warehouse transactions (goods movement, physical inventory) that work well for straightforward scenarios at the material level. Custom Fiori apps are warranted when: you need batch or serial number scanning as a mandatory step within the transaction (not an optional field), you have business-specific validation rules (only allow FEFO batch selection, warn if batch quantity is insufficient, cross-reference against a production order), you need to combine multiple SAP steps into one scan workflow (scan a pallet, confirm picking, update handling unit and trigger goods issue in one step), or the standard SAP Fiori app UI is not optimised for the screen size or device type your warehouse uses. Most real warehouses need custom apps — the standard apps are a starting point, not the end solution.

A single-transaction custom Fiori barcode app (for example, a goods receipt scanning app with batch and serial number capture) typically takes 4–6 weeks: requirements workshop, app design, development, SAP integration testing, user acceptance testing and deployment. A full warehouse scanning suite covering goods receipt, goods issue, transfer orders, production confirmation and physical inventory: 10–16 weeks. Label design and SAP output configuration is typically 2–3 weeks running in parallel with app development. The implementation can run alongside an SAP implementation project or as a standalone enhancement to an existing SAP environment. The biggest variable is the complexity of your business rules — a straightforward goods receipt scan with batch capture is fast; a workflow that involves multi-step validation, FEFO enforcement, cross-plant transfer rules and automatic goods issue to linked production orders takes longer to build and test correctly.