Mobile Supply Chain Apps & Offline Operations

Who this is for: Storeroom managers, inventory controllers, receiving clerks, maintenance supervisors, and supply chain leads evaluating or implementing the MAS 9 Maximo Mobile supply chain applications. Also relevant for migration teams moving from Maximo Anywhere to Maximo Mobile.

Estimated read time: 10 minutes

The Storeroom Problem That Mobile Solves

Here is a scene we have watched play out at dozens of customer sites: a storeroom clerk walks to the back shelf, pulls three bearing assemblies for a work order, walks back to the desk, logs into Maximo on a shared terminal, navigates to the Inventory Usage application, types in the item number, enters the quantity, fills in the charge information, and clicks Save. Total time for a simple issue transaction: four to six minutes — of which five seconds was the actual physical task of picking the parts.

Now multiply that by 80 transactions per shift. The clerk spends more time feeding the system than doing actual warehouse work.

MAS 9 changes this equation fundamentally. Maximo Mobile puts four dedicated supply chain applications directly into the storeroom clerk's hand — and into the receiving dock, the count team's scanner, and the field technician's pocket. The transactions that used to require a round trip to a desktop terminal now happen where the work happens, including when there is no network connection at all.

This is not a nice-to-have. For organizations running 24/7 operations with distributed storerooms, remote sites, or field crews that operate in areas without reliable connectivity, mobile supply chain is the difference between real-time inventory accuracy and a system that is always a shift behind reality.

Issues and Transfers Mobile

Target Users: Storeroom clerks, material handlers

The Issues and Transfers Mobile app is designed for the people who physically move inventory — pulling items from shelves, staging them for pickup, shipping them between storerooms, and recording every transaction in real time.

Core Capabilities

Stage Items for Issue. The app supports a staging workflow where the clerk picks items from storage and moves them to a designated staging area before final issue. This is critical in large storerooms where the person picking parts and the person handing them to the technician may be different people — or where parts are pre-staged for morning shift work orders the night before.

Issue Without Reservation. Not every issue follows the reservation-first workflow. The app allows direct issue of inventory without a prior reservation, covering unplanned demand, emergency repairs, and situations where the planner did not have time to create a formal reservation. The clerk selects the item, specifies the quantity, and assigns the charge destination — work order, GL account, or cost center.

View and Edit Charge Information. During the issue process, the clerk can modify GL accounts and cost centers. This handles the common real-world scenario where the cost allocation for a material issue needs to change at the point of transaction — the parts were planned for one work order but are actually being used on another, or the cost center was entered incorrectly on the original reservation.

Storeroom-to-Storeroom Transfer. The app supports transfers between any storerooms defined in the system. A satellite storeroom running low on a critical item can receive a transfer from the central warehouse, and the entire transaction — decrement from source, increment at destination, create the transfer record — happens from the mobile device. No desktop required.

Shipment Creation. For inter-storeroom transfers that involve physical shipping (not just a clerk walking parts from one room to another), the app creates shipment records that track the transfer through the logistics process. This is essential for organizations with geographically distributed storerooms where transfers move through a loading dock, a truck, and a receiving dock at the other end.

Tools Transfer. Tools have different tracking requirements than consumable inventory — they are issued and returned, not consumed. The app handles tool transfers with or without reservations, maintaining the custody chain that tool management requires.

Work Order Reference. Every issue can be linked to a work order, a material request, or an internal purchase order. This linkage is what drives accurate cost allocation and material usage tracking. The clerk does not need to remember or look up reference numbers — they scan or search and select.

Barcode Scanning. The app uses the device camera (or a connected Bluetooth scanner) to scan item barcodes for identification. Point the scanner at the shelf label or the item packaging, and the app looks up the item, displays the description, and populates the transaction form. This eliminates manual item number entry — and the transcription errors that come with it.

Offline Support. The entire Issues and Transfers workflow operates offline. The clerk can stage items, issue inventory, perform transfers, and scan barcodes without any network connection. When connectivity is restored, background sync pushes all transactions to the server automatically. We will cover the mechanics of offline operation in detail later in this post.

What This Means in Practice

A storeroom clerk working a night shift at a remote plant — no WiFi in the warehouse, cellular coverage spotty — can process every issue, transfer, and staging transaction during the entire shift. When they walk back to the office where the WiFi reaches, the device syncs automatically. By the time the morning planner opens the desktop application, every transaction from the night shift is already reflected in inventory balances. No backlog of paper tickets to enter. No morning data entry session. No discrepancies between what was physically issued and what the system shows.

Inventory Count Mobile

Target Users: Count personnel, inventory managers

Physical inventory counting is one of those processes where the gap between what the system says and what actually happens on the floor creates the most pain. The Inventory Count Mobile app closes that gap by putting the count process directly on the device that the count team carries through the storeroom.

Core Capabilities

Barcode-Driven Counting. The primary counting workflow is barcode-driven. The counter scans the bin label, the app shows what items should be in that bin, and the counter enters the physical quantity. Alternatively, the counter scans item barcodes directly to identify items. This scan-first approach eliminates the most common counting error: recording quantities against the wrong item or the wrong bin.

Cycle Count Execution. The app integrates with Maximo's count book and cycle count scheduling. When a cycle count is scheduled in Manage, the count assignments appear on the mobile device. The counter opens the assigned count, walks the storeroom in the sequence defined by the count book, and records each count. No printed count sheets. No manual transcription.

Multi-Bin Counting. For items stored across multiple bins or locations within a storeroom, the app supports counting across all bins in a single session. The counter does not need to close one bin and open another — the app presents all bin locations for the item and collects counts for each.

Blind Count Mode. This is a configuration option that hides the system's current balance from the counter. In blind count mode, the counter sees the item description and bin location but not the expected quantity. This prevents the natural human tendency to "confirm" what the system says rather than actually counting what is on the shelf. Organizations that take count accuracy seriously almost always enable blind count mode — it is the single most effective control for honest physical counts.

Photo Attachment. The counter can take photos during the counting process and attach them to the count record. This capability has several practical uses: documenting items that appear damaged, capturing bin conditions that explain discrepancies (water damage, spill contamination), providing visual evidence for high-value count adjustments, and recording shelf labels that have become illegible.

Count Approval Workflow. After counts are recorded, the app supports a configurable approval workflow. Counts that fall within an acceptable variance threshold may be auto-approved. Counts with significant discrepancies route to a supervisor for review before the system balance is adjusted. The specific thresholds and approval routing are configured in Manage.

Offline Counting. The physical counting process works entirely offline. Counters download their count assignments, walk the storeroom without network connectivity, enter all counts, and sync when finished. This is essential for large storerooms where WiFi coverage is incomplete, or for outdoor laydown yards where connectivity is unreliable.

The Online-Only Exception: Reconciliation

Count reconciliation is online only. This is an important limitation to understand and plan for. You can count offline — scan barcodes, enter quantities, attach photos, work through your entire count assignment without a network connection. But the reconciliation step, where counted quantities are compared against system balances and discrepancies are identified and resolved, requires an active connection to the server.

The reason is straightforward: reconciliation must compare your counted quantity against the current system balance, which may have changed since you downloaded your count assignment (another clerk may have issued items, a PO receipt may have arrived, a transfer may have posted). The server must be the source of truth for the comparison.

Practical implication: Plan your counting workflow so that the physical counting happens wherever it needs to happen (including offline), but the reconciliation review happens in an area with network connectivity — or back at a desk where the counter or supervisor can connect.

Receiving Mobile

Target Users: Receiving clerks, warehouse personnel

The Receiving Mobile app puts the PO receipt process directly on the receiving dock — exactly where it should happen. Instead of the traditional workflow where the receiving clerk signs a paper packing slip, stacks the boxes in the receiving area, and later walks to a terminal to enter the receipt, the clerk processes the receipt while looking at the physical delivery.

Core Capabilities

PO-Based Receiving. The app presents a scrollable list of open purchase orders awaiting receipt. The clerk selects the PO that matches the delivery sitting on the dock. This PO list includes visual indicators — vendor name, PO number, item descriptions — so the clerk can quickly identify the right PO without memorizing numbers.

Visual PO List. The PO list is not just a text dump. It includes visual indicators, item descriptions, and enough context for the receiving clerk to match the physical delivery to the correct PO. Scrolling, searching, and filtering are all supported. For receiving docks that handle dozens of deliveries per day, the ability to quickly find the right PO among hundreds of open orders is a meaningful time saver.

Quantity Entry. The clerk enters the received quantity, which can differ from the ordered quantity. Partial receipts, over-receipts (within tolerance), and short shipments are all handled. The app records the actual quantity received and the system calculates the variance from the ordered amount.

Item Image Verification. When the item master includes images, the app displays them during the receiving process. The clerk can visually compare the physical item on the dock against the image in the system. This addresses the surprisingly common problem of receiving the wrong item — especially for parts that look similar but have different specifications.

Rotating Asset Receipt. When receiving a rotating asset (an item that becomes an asset upon receipt — pumps, motors, instruments), the app creates the receipt in a "waiting for asset" status. This triggers the asset serialization process — the asset record gets created, the serial number gets assigned, and the item transitions from inventory to asset tracking. The mobile app handles the receipt side; the asset creation workflow continues on the server.

Real-Time Sync. When online, receipt data syncs to the server immediately. The moment the clerk taps "Complete Receipt" on the dock, the desktop Receiving application reflects the new receipt. Inventory balances update, PO status changes, and anyone watching the system sees the receipt in real time. This eliminates the delay between physical receipt and system visibility that plagues paper-based receiving processes.

Inspection on Receipt. For items that require inspection before acceptance (quality-critical parts, items from new vendors, regulated materials), the app supports an inspection workflow directly on the receiving dock. The clerk can record pass/fail inspection results on the mobile device, and failed inspections trigger the appropriate rejection and return-to-vendor workflow.

Check for Updates. The "Check for Updates" function pulls new POs to the local database for offline processing. When the receiving clerk starts a shift, they tap this button to download all current open POs. If new POs are created during the shift while the clerk is offline, they will not appear until the next update check. Plan accordingly for high-volume receiving operations.

Offline Receipt Processing. The entire receipt process works offline. The clerk downloads the open PO list, goes to the receiving dock (which may have no WiFi), processes multiple receipts, and syncs everything when they return to a connected area. For receiving docks in remote locations, outdoor laydown areas, or sites with unreliable connectivity, offline receiving is not optional — it is the only way the process works.

MAS 9.1 Receiving Enhancements

MAS 9.1 introduced four targeted improvements to the Receiving Mobile app based on feedback from the initial MAS 9.0 release:

Receiving Bin Updates. Clerks can now update receiving bins and additional attributes directly upon receipt. In 9.0, the bin assignment often required a second step in the desktop application. The 9.1 enhancement puts the bin update into the mobile receipt flow, eliminating the follow-up task.

Enhanced Item Identification. The 9.1 release displays additional information to help identify items, receipts, and PO data. This addresses feedback that the 9.0 interface sometimes did not show enough context for the clerk to confidently match a physical delivery to the correct PO line — especially for POs with multiple lines of similar items.

Performance Improvements. Data loading optimizations, enhanced sorting, filtering, and search performance were all improved in 9.1. For receiving operations that deal with hundreds of open POs, the 9.0 performance on initial load and search was a common complaint. The 9.1 improvements specifically target large-volume receiving environments.

Return Processing. The ability to process returns directly from the mobile receiving interface was added in 9.1. Previously, returns required the desktop Receiving application. Now the receiving clerk can initiate a return-to-vendor from the same mobile app where they processed the original receipt — a logical workflow that should have been there from the start.

Technician App Supply Chain Features

Target Users: Field technicians, maintenance workers

The Technician mobile app is primarily a work execution tool — it is where technicians view their assignments, record labor, log failures, and complete work orders. But it also includes supply chain features that are relevant to how field workers interact with the material supply process.

Material Request Creation

Technicians can create material requests directly from the field. Instead of calling the storeroom, walking back to a computer, or writing a part number on their hand and hoping they remember it at the end of the shift, the technician opens the work order on their device and creates a material request on the spot. The request flows to the storeroom for fulfillment.

Material Usage Recording

When the technician installs a part, they record the material usage on the work order directly from the field. This is the transaction that reduces inventory balance and charges the cost to the work order. Recording usage at the point of installation — not hours or days later at a desktop — is what makes inventory balances trustworthy.

Barcode Scanning

The Technician app includes the same barcode scanning capability as the storeroom apps. The technician scans the part, the app identifies it, and the material usage transaction is populated. No manual part number entry. No guessing whether the part number on the bin label matches what is in the system.

Planned Material View

Before starting a job, the technician can view the materials planned for the work order — what parts were specified by the planner, what quantities, and whether those materials have been reserved or issued. This gives the technician visibility into whether the job is material-ready before they drive to the site.

Material Availability Check

The technician can check available inventory before requesting materials. If the bearing they need is out of stock at the local storeroom but available at a regional warehouse, they see that information on their device. This avoids the frustration of requesting a part only to find out hours later that it is not available — and it gives the technician the information to make a decision about whether to wait for the part or use an alternative.

Offline Capabilities: How It Actually Works

Offline support is the feature that separates Maximo Mobile from a web browser pointed at a responsive URL. Every supply chain mobile app supports full offline work, but understanding how offline works — and where its boundaries are — is essential for planning your deployment.

Full Offline Work

All four supply chain-relevant apps — Technician, Issues and Transfers, Inventory Count, and Receiving — function without any network connectivity. The apps store a local database on the device that contains the data the user needs: work orders, inventory items, PO lines, count assignments, storeroom data. The user works against this local database, and all transactions are queued locally until sync occurs.

Configurable Sync Scope

Not every user needs every piece of data on their device. The sync scope is configurable — you choose which data downloads to the device based on the user's role, storeroom assignment, or other criteria. A receiving clerk only needs open POs for their storeroom, not every PO in the organization. A count team member only needs the count assignments for their scheduled count, not the entire item catalog. Keeping the sync scope tight improves sync speed and reduces device storage consumption.

Partial Data Refresh

After the initial download, subsequent sync operations only transfer changed records — not the entire dataset. If a clerk synced 500 PO lines this morning and 3 new POs were created since then, the next sync transfers 3 new records, not 503. This partial data refresh approach makes incremental sync fast even on slow cellular connections.

Conflict Resolution

What happens when a clerk processes a transaction offline, and while they were offline, someone else modified the same record on the server? Maximo Mobile includes automatic conflict resolution. The resolution logic depends on the transaction type — for most supply chain transactions, the offline transaction is applied and the server record is updated to reflect both changes. In cases where automatic resolution is not possible, the conflict is flagged for manual review.

Device Storage Management

The app provides tools to monitor and manage device storage capacity. Large sync scopes, photo attachments from counts, and accumulated transaction history all consume device storage. The storage management features let administrators and users see how much space is being used, what is consuming it, and when cleanup is needed.

Background Sync

When connectivity is restored, data syncs automatically in the background. The user does not need to manually trigger sync — the app detects connectivity and begins pushing queued transactions to the server and pulling new data to the device. This background sync means the user can continue working while sync happens. They do not need to sit and wait for an upload to complete before starting their next task.

What Changed from Maximo Anywhere: The Migration Path

For organizations currently running Maximo Anywhere (the 7.6-era mobile solution), the move to Maximo Mobile is not just a version upgrade — it is a platform replacement. Understanding the specific differences is critical for planning the migration.

Build and Deployment

Maximo Anywhere required a Mobile Application Framework (MAF) rebuild and redeployment for every configuration change. If you added a field to the mobile work order screen, you rebuilt the MAF application, generated a new APK (Android) or IPA (iOS), and distributed it to every device. This process could take hours and required a development environment with specific tooling.

Maximo Mobile uses server-side configuration only. Changes to the mobile application — adding fields, modifying layouts, adjusting business rules — are made through the MAF Configuration application in Manage and take effect when users next sync or log in. No device-side build. No APK/IPA distribution. No rebuild cycle.

Distribution

Maximo Anywhere relied on manual APK/IPA distribution — either through an enterprise mobile device management (MDM) platform or through sideloading. App updates required the same distribution cycle.

Maximo Mobile is distributed through the standard app stores (Apple App Store, Google Play Store, Microsoft Store). The app itself updates through normal app store mechanisms. The application configuration (which controls what users see and do) is entirely server-side.

Customization

Maximo Anywhere used XML configuration files and custom adapters for customization. If the standard mobile app did not do what you needed, you wrote an adapter in JavaScript, packaged it into the MAF build, and deployed it. These custom adapters were fragile — they could break with IBM updates and required mobile development expertise to maintain.

Maximo Mobile customization is done through the MAF Configuration application. This is a server-side configuration tool that controls field visibility, layout, business rules, and workflows for the mobile apps. The customization model is closer to configuring a Manage application than writing mobile code. For customizations that go beyond configuration, the Application Designer in Manage provides additional extension points.

Inspection Forms

Maximo Anywhere downloaded inspection forms per inspection — every time a technician opened an inspection, the form definition was downloaded from the server.

Maximo Mobile downloads inspection forms once at login. This is a significant performance improvement for organizations that use Maximo inspections heavily. Instead of repeated downloads for every inspection, the form definitions are cached on the device and only re-downloaded when the definitions change.

Platform Architecture

Maximo Anywhere was a hybrid web-based application — essentially a web app wrapped in a native container. This hybrid approach limited performance, offline capability, and device integration.

Maximo Mobile is a native application on iOS, Android, and Windows. Native applications have better performance, deeper device integration (camera, GPS, Bluetooth scanners, biometric authentication), and more robust offline storage.

Offline Capability

Maximo Anywhere had limited offline capability. Some transactions could be performed offline, but the scope was restricted, sync was less reliable, and conflict resolution was basic.

Maximo Mobile offers full offline with configurable sync scope, as described in the previous section. The offline capability is architecturally fundamental to the application, not bolted on as an afterthought.

Barcode Support

Maximo Anywhere had limited barcode support that often required additional configuration or third-party plugins.

Maximo Mobile includes built-in barcode scanning across all apps. The camera-based scanner works out of the box, and Bluetooth scanner pairing is supported for environments where camera scanning is impractical (bright sunlight, dirty lenses, very small barcodes).

Migration Planning Implications

The Anywhere-to-Mobile migration is not a lift-and-shift. The customization model is different (XML/adapters versus MAF Configuration), the deployment model is different (manual distribution versus app stores plus server config), and the offline model is different (limited versus full). Organizations should plan for:

  • Customization re-implementation. Any Anywhere customizations built with XML and custom adapters must be re-implemented in the MAF Configuration application. Some customizations may no longer be necessary because Mobile includes features that Anywhere lacked.
  • Testing cycle. The mobile user experience will change. Field testing with actual storeroom clerks, receiving personnel, and technicians is essential — not just functional testing in a lab.
  • Training. Even though the basic concepts are the same (scan, enter, save), the interface is different enough that users need training on the new app. Treat this as a new application rollout, not an upgrade.
  • Parallel operation period. Plan for a period where both Anywhere and Mobile are available. Cut over by storeroom or by role, not all at once.

Putting It Together: Which App for Which Role

Role — Primary App — Key Supply Chain Functions

Storeroom Clerk — Issues and Transfers Mobile — Stage items, issue with/without reservation, storeroom transfers, barcode scanning

Material Handler — Issues and Transfers Mobile — Shipment creation, tools transfer, work order-linked issues

Count Team — Inventory Count Mobile — Cycle count execution, barcode-driven counting, blind count, photo attachment

Inventory Manager — Inventory Count Mobile — Count reconciliation (online), approval workflow, multi-bin counting

Receiving Clerk — Receiving Mobile — PO-based receiving, quantity entry, inspection on receipt, rotating asset receipt

Warehouse Supervisor — Receiving Mobile — Return processing (9.1), receiving bin updates (9.1), enhanced item identification (9.1)

Field Technician — Technician App — Material request, usage recording, barcode scanning, availability check

Maintenance Planner — Desktop Manage — Planned material view (referenced by technician app), reservations, count book management

Offline Readiness Checklist

Before deploying mobile supply chain apps in offline-capable mode, validate the following:

Item — Consideration

Sync Scope — Define per-role: which storerooms, which POs, which count assignments download to the device

Device Storage — Ensure devices have adequate storage for the defined sync scope plus photo attachments

Sync Schedule — Establish expectations for how often users sync — start of shift, end of shift, or continuous when connected

Conflict Resolution — Test conflict scenarios with your actual transaction patterns — what happens when two clerks issue from the same bin offline

Count Reconciliation — Plan for reconciliation to happen in connected areas — do not assume count teams can reconcile in the field

Background Sync — Verify that background sync works reliably on your device fleet (some MDM configurations restrict background data)

Connectivity Mapping — Map your facility for WiFi and cellular coverage — know where users will be online and where they will be offline

Key Takeaways

  • Four mobile supply chain apps cover the complete material lifecycle — from receiving at the dock, to storage and counting in the storeroom, to issuing and transferring for work, to field technician consumption
  • Full offline operation is architecturally built into every app, not bolted on as an optional mode — configurable sync scope, partial data refresh, automatic conflict resolution, and background sync make offline a first-class experience
  • Barcode scanning is built in across all apps — camera-based and Bluetooth scanner support work out of the box, eliminating the manual data entry that causes transcription errors
  • Count reconciliation is the one online-only exception — plan your counting workflows so that reconciliation happens where connectivity is available
  • MAS 9.1 significantly improved receiving — bin updates, enhanced identification, return processing, and performance improvements address the most common 9.0 feedback
  • The Anywhere-to-Mobile migration is a platform replacement, not an upgrade — customizations must be re-implemented, users must be retrained, and parallel operation should be planned
  • Server-side configuration replaces device-side builds — no more MAF rebuilds, no more APK/IPA distribution, no more waiting for a mobile developer to add a field to a screen

References

Series Navigation:

Previous: Part 22 -- Procurement & Contracts
Next: Part 24 -- Integration Framework & API Strategy

View the full MAS FEATURES series index

Part 23 of the "MAS FEATURES" series | Published by TheMaximoGuys

The mobile supply chain apps in MAS 9 are not a convenience feature bolted onto Manage -- they are a fundamental shift in how storeroom operations, inventory counting, receiving, and field material management work. Organizations that deploy these apps with proper offline planning and user training will see inventory accuracy improvements within weeks. The gap between physical reality and system reality closes when transactions happen where the work happens.