Support Guide
This English guide is written for the current version of the app. It covers what the app does, how Free, Pro, and Max differ, where ScannerAction fits in real life, and how to move from one scan to fields, submission, retry, and proof.
Feature Overview
At its core, ScannerAction captures QR codes and barcodes, stores the result locally, and gives you a clean next action. That next action can stay simple or become a real submission workflow depending on your plan.
Tier Comparison
Think of the tiers as three different stopping points in the same product: stop after scan, stop after structured export, or continue into submission at higher volume.
Use Free when the scan result itself is the outcome, history is enough, and 10 requests per day covers your volume.
Use Pro when you need templates, structured fields, files, reports, archives, visual code assets, and still only moderate request volume.
Use Max when a scan should create or update something in another system and you do not want a daily request ceiling.
Use Cases
These scenarios are deliberately imaginative because ScannerAction is flexible. The same product can behave like a pocket scanner, a field notebook, an export tool, or the front end of an operations pipeline.
Scan incoming box labels, keep snapshots for disputes, export the morning shift to XLSX, and attach images when someone asks what arrived.
Scan a device barcode, copy the serial instantly for support staff, and send the same value through a request template to open a repair ticket. Max is useful once the volume becomes continuous.
Keep scanning badges even when the venue Wi-Fi is bad, then batch-send queued records when the network becomes stable.
Scan product barcodes during a store walk, search history by code later, and export exceptions for the pricing team.
Walk through equipment points, scan tags in sequence, and rely on timestamps instead of handwritten notes during long rounds.
Capture QR codes from magazines, posters, packaging, manuals, or trade-show materials and turn them into a searchable campaign list.
Quick Start
If you only need the shortest path: scan, review, and either copy, export, or send. The steps below map directly to the app tabs.
Use Live Scan for camera capture or Photo Recognition if the code already exists in your Photos library.
After recognition, the newest record appears with the scan image, code text, code type, source, template, and business status.
Copy the result, open a URL in the browser, export a code image, or open the full detail view to edit fields and submit.
Use search, filters, exports, or batch tools when you are working with more than the single newest scan.
Stay on Free for capture and light requests, use Pro for files and code assets with the same 10 requests per day, or use Max when scans should trigger requests continuously.
Step-by-Step
The Scan tab is designed to make the first action obvious and the second action fast. It is the best place to start whether you are a Free, Pro, or Max user.
Tap Live Scan to open the camera, or tap Photo Recognition to choose an existing image.
Once recognition succeeds, the latest result panel shows the scanned text, scan time, image thumbnail, source, and request state.
The Scan tab also surfaces lightweight counters like total records, today’s scans, QR count, barcode count, and URL count.
The newest few records stay visible below the latest result so you can jump back without opening the full data workspace.
Suggested capture: scan entry buttons, metric pills, and recent history block.
Suggested capture: latest record card with image thumbnail, copy button, and URL button.
Step-by-Step
The Data tab is where ScannerAction becomes much more than a one-shot scanner. Think of it as the working area for saved records.
Use the built-in search field to narrow the current dataset by the scanned string itself. This is useful when you remember part of a code, URL, or identifier.
You can filter by request state, code type, source, export state, and date range, then treat that filtered set as a working list.
From a record row, open the full detail page to inspect the scan image, code, type, source, request body, response body, or error message if a request exists.
The toolbar menu lets you export the current data, batch-request the current list, clear successful request states, or delete the current list if needed.
Suggested capture: history statistics view and filter card.
Suggested capture: searchable record list with row actions and pagination.
Pro Workflows
Pro is the right tier when the scan result needs to leave the app in a clean format.
Open the current dataset, tap the toolbar menu, then choose Export CSV, Export JSON, or Export XLSX.
The export respects the current data scope, which means you can export everything or first narrow the list with filters and search.
XLSX is especially useful for operations handoff, and it can include the stored scan images.
From the latest-result panel or from a record row, export the code as PNG or PDF using the current code export preference.
This helps confirm what was already generated and how many records were included.
Suggested capture: CSV, JSON, and XLSX export actions from the Data tab menu.
Suggested capture: PNG or PDF setting with PNG size options.
Request Workflows
Request mode is available before purchase so you can understand the feature in real work. Free and Pro can send up to 10 requests per day. Max removes that cap for sustained usage.
Go to Settings → Requests & Batch and choose one of three modes:
Set the method, request interval, URL, headers, cookie, and body. Insert variables so one template can adapt to many scans.
{{code}} for scanned value{{time}} for scan timestamp{{type}} for detected code type{{source}} for camera or photo{{id}} for the record identifierThe app can render the latest scan through the template so you can confirm the final URL, headers, cookie, and body before using the flow operationally.
Queue scans during a shift or while offline, then open the Dashboard tab and tap Send Pending when you are ready. If you hit the daily cap on Free or Pro, the remaining items stay queued for later.
Suggested capture: trigger mode selector, URL field, header field, and variable chips.
Suggested capture: pending count, progress bar, success and failure cards, send button.
Dashboard
The Dashboard tab becomes more valuable as you use queued requests. It helps Free and Pro users track the daily cap, and it lets high-volume teams run without that limit on Max.
The batch section shows how many requests have been sent, how many remain pending, and how many succeeded or failed.
You can begin sending pending records or stop the process if you need to pause and review the queue state.
Open the export history area to see previous exports, their file format, time range, and record count.
Queueing is especially useful in field work, trade shows, or warehouses where reliable connectivity is not guaranteed all day.
Settings
The Settings tab is not just a place for subscription screens. It is where you shape how the app behaves for export, language, and request behavior.
Choose how many items appear per page for data lists, request history, and export history.
Set the default export format to PNG or PDF and define the PNG long edge size for better delivery quality.
Switch between supported interface languages directly inside the app without restarting.
Use the built-in notes to understand storage behavior, permissions, network requests, and subscription handling.