Typical use cases
- Wholesalers and distributors: Enable your customers to order stock and initiate delivery simply by scanning the barcodes of in-store items with the codeREADr app. Orders can be automatically uploaded to your back-end system to automate order processing.
- Manufacturers, distributors, representatives: You can a) enable remote ordering; b) track samples given to clients; and c) monitor inventory at client locations.
Integration and branding are typically done with your own IT staff or with third-party developers.
When an item is scanned, manually entered or searched, the app will check an online or on-device database to determine if the Item ID is valid and, if so, display your associated text or HTML content for that item including description, package quantity, price, etc. and optionally a photo and URL. Follow these steps for creating a Database.
Data Collection – the Quantity
After an item’s ID (UPC, EAN, etc.) has been scanned, the app will check your uploaded database and show the item’s description to the app user. When creating the app’s flow, you can also question (prompt) your app users to enter answers via forms, dropdowns, photos, signatures, etc. which then become part of the scan record for the current scan of that item. The most common
The most common answer types for this use case would be order quantity and comments. Note: if the quantity is always ‘1’ then the first answer on a dropdown menu should be set to ‘1’. Alternatively, if no other info is required, then there’s no need to even ask for a quantity to be entered.
Create and Assign App Users
Your authorised app users must sign in to the codeREADr app with the credentials (username and password) you’ve assigned to them. Upon signing in, they are presented with only those Services which you’ve associated with their credentials. Upon selecting a Service, the app will download the database associated to that Service. The app user can then start scanning. Follow these steps for creating app users.
You can create as many users as you need. Often the username is a customer number or other identifier clearly identifying the app user’s affiliation (store, company, etc.). You can optionally limit the number of devices an app user’s credentials can be used with. You can also remove access to Services, delete the app user or change the password.
Services provide the framework for collecting and managing scanned data to achieve specific results. Services can be used to simply record scans or to record and validate scans against an on-device or online database. Account administrators control Services by assigning app users, databases and data-entry forms to specific services. Follow these steps to create a Service.
You can view, filter and export your scan records in many ways. Options include:
- Export Templates
- CSV Download Links (for selective sharing)
- Postback URL (for posting scans directly to your server)
- Scheduled FTP/SFTP and Email of filtered scan records
- Manual download
- Auto-insert to Google Sheets, QuickBase, etc.
- Fetch using our API
Developer API and Postbace URL
A full set of APIs are available to developers for integration into your back-end system.