AvePoint Opus App

What happens when you scan a physical record barcode

Open the AvePoint Opus App and point the camera at a Cloud Opus barcode. The app reads it instantly. A list of actions appears on screen. Move that item to a different user. Assign it to a new location. Or mark it as destroyed right then and there. No paperwork. No back-and-forth with a records clerk. Just a single scan and a tap.

The AvePoint Opus App handles physical records the way a barcode scanner handles products in a warehouse. But this is not a retail tool. It is built for organizations that track physical files alongside digital ones. The app connects to the AvePoint Opus platform, which manages information lifecycle across Microsoft 365, on-premises SharePoint, and even physical storage. The mobile piece is simple: scan, choose, confirm. That is the entire interaction model. No menus to navigate. No settings to tweak before your first scan. Just a camera view and a short list of possible outcomes.

Bulk scanning changes the game. Instead of scanning one barcode at a time, the app lets you scan multiple items in sequence. The actions you choose apply to everything in the batch. Move twenty boxes to a new storage room with a single confirmation. Mark an entire drawer of old files as destroyed in under a minute. The bulk mode is where the app stops being a convenience and starts being a time-saver for anyone managing physical records at scale.

Where the bulk scan meets the move action

Scan one barcode and you have options. Scan fifty barcodes and you have the same options, but applied across all of them at once. That is where the app's real utility emerges. The Play Store description mentions bulk scanning and moving items, but it does not show how these two features work together in practice. Imagine a shelf of records that need to be relocated to a different floor. Without this app, someone would need to note each box's barcode, update a spreadsheet, and manually change the location field for every single entry. With the AvePoint Opus App, you walk down the shelf, scan each barcode in sequence, select 'move to location,' pick the new floor, and confirm once. Every scanned item updates in the system simultaneously. The location field for all fifty items changes in the same moment. No spreadsheet. No manual data entry. No transcription errors.

This workflow only exists because the app combines two features that are individually simple: barcode reading and action execution. The bulk mode is what makes the combination powerful. It turns a tedious administrative task into a physical activity that takes less time than walking between floors. The app does not describe this workflow anywhere in its marketing copy. But anyone who has ever moved a file room knows exactly why this matters. The bulk action is not a bonus feature. It is the feature that makes the whole thing worthwhile.

What the Code 39 support actually changed

The latest version added support for Code 39 barcodes. That is a specific symbology used in many older records management systems. Before this update, the app could only read Cloud Opus barcodes, which are generated by the AvePoint platform itself. Code 39 support means the app can now read barcodes that were printed years ago, before Cloud Opus existed. Organizations with legacy physical records can now use the app without re-labeling every single file. The changelog also lists bug fixes, but no details are provided about what those fixes address. The Code 39 addition is the only concrete change in the current version. It is a small update, but it expands the app's compatibility significantly for organizations that have been managing physical records for decades.

One limitation that is not mentioned on the Play Store page: the app cannot manage Microsoft 365 data that is protected by a retention policy. According to the official AvePoint documentation, sites with retention policies applied are automatically skipped in Opus jobs. If you need to run jobs on those sites, you have to remove or disable the retention policy first, or contact AvePoint Support for assistance. This is not a mobile app issue specifically, but it affects anyone using the AvePoint Opus platform to manage both physical and digital records. The mobile app is only as useful as the backend allows. And the backend has clear boundaries around what it can and cannot process.

What the app actually does when you mark something as destroyed

Marking a physical item as destroyed is not just a status change. The action triggers a chain of events in the AvePoint Opus platform. The item is removed from active inventory. The system records the destruction date and the user who performed the action. If the organization has retention schedules configured, the destruction action may be part of a defensible disposal process. The app does not show any of this. It just shows a confirmation message. But behind the scenes, the action is logged, audited, and stored as part of the permanent record. This is why the app exists: not to make scanning fun, but to make physical records management auditable and compliant without adding extra steps for the person holding the scanner.

The app does not require any special permissions beyond camera access. It does not collect user data. It does not share data with third parties. The privacy policy, as listed on Google Play, states that no data is collected and no data is shared. That is unusual for an enterprise app. Most business tools collect usage data for analytics. This one does not. The trade-off is that the app is minimal. It does one thing and does it without storing anything locally. Every scan and action requires a connection to the AvePoint Opus backend. If the backend is unreachable, the app cannot perform any action. The app itself does not cache scans or queue actions for later. It is a live interface to a cloud platform, not a standalone tool.