(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.data-privacy-src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-PF5R8F7');

Knowledge Base

Branding and Customizing the App

Full White Label App for Android OS and iOS

We offer fully white-labeled versions of the CodeREADr app. With this option, the app will appear in Google Play and iTunes app stores as your own app. Also, the users will see your app icon on their devices once downloaded from the stores. Brand the app with your logos and colors and have no link to or mention of CodeREADr. Contact support if you would like to receive a quote. Also, we can provide quotes for custom features on request.

Free Branding

You can brand the CodeREADr app’s Tap to Scan screen with your logo at no charge. Your app users will still need to download the CodeREADr app from the stores. However, it will have your logo in the app. Thus, we are the ‘code reader’ and you are the solution provider.

Although very sophisticated, we are a ‘layer’ within your solution. Also, we enable the collection and validation of data. However, you create task-specific services for your clients and enable the use of the collected data. Check here for Branding instructions.

Also, on your CodeREADr Account page, you can change the email address for the ‘Contact Us’ email in the app’s settings. Then, redirect the in-app ‘Help’ page to your own URL.

Custom Functionality with Contextual Variables

We’ve enabled clients to add custom functionality within the CodeREADr app. For example, you can present:

  • Status dashboard
  • Tickets sold, tickets remaining, capacity, etc.
  • Last order quantity, order status, special offers, etc.
  • Asset images, asset status, etc.
  • Student/member/employee images
  • Specific instructions for actions (e.g. safety checks, maintenance, etc.)

Anyone can put URL(s) in the Response Text when creating their database. Also, you can do it in the Service Description when creating a Service. However, to use contextual variables or Webify, a Web developer is typically needed to deploy this feature effectively.

Note: We list the context variables below for various use cases. However, in some iterations, the context variable may not always be available. For example, with Service Descriptions, the __SCAN_VALUE_ variable would not be available because the presentation of the description comes before the scan is made.

Plain Text URLs in the Scan Response Text or Service Description

When creating your barcode database, put a plain text URL in the Response Text or Service Description. Also, add any other text associated to that barcode value. After the users scan a barcode, they can tap the URL to launch in-app viewing of that Web page and any links embedded within.

Developer – Context Variables Added to Plain Text URLs in the Scan Response Text or Service Description:

When adding a plain text URL to the Response Text or Service Description, you can give context and direct the app user to a specific URL. For example, you can use one of these variables:





In this way, the scan the app user will see and engage with Web content in a context relative to that variable. Also, the URL must be a plain text URL.

Webify – Web Content as a Service

In addition to the typical recording and validation Services offered, you can create a Web-View-Only Service with our Webify feature. See Webify instructions here. Webify will present to the app user an image (such as your logo) or Web page. Also, if you are using contextual variables, it will show a specific image or Web page. For example, you can use any of these contextual variables:




Webify – Web Content as a Response Text or Service Description

Web content within Response Text or Service Descriptions can be generic or contextual using our Webify feature. For example, you can use any of these contextual variables:





Webify – App’s Lookup and History Pages

On the Advanced tab, when creating or editing your Service workflow, you can override the database Lookup and scan History pages with your own custom Web content. This is useful if you don’t want app-users to see database values and/or scan history. Also, it lets you present custom content/actions/reports to the app user. For Lookup, you can use Scan Links where when tapped by the app user that value is submitted.

You could use context variables as _GET parameters including:


Webify Benefits

There are some benefits of Webify over plain text URLs. First, the URL can use anchor text for a better UI. Secondly, you can display the content immediately without requiring the app user to tap a URL.  The purpose is to enable simple and immediate contextual engagement with the app user. Please refer to our Webify instructions for more.

Alter Response Text

You can use the Alter Response Text feature to use a template for your HTML and web content. In this way, your validation database doesn’t need to have that structure for each value in column 2 (the response text). Please refer to our topic on altering response text for more information.

Alter Response View

On the Advanced step, when creating or editing your services, you can change or remove the standard labels and screen colors of the response after a scan. The option is called ‘Enable custom display configuration‘. For example, you can change the labels “Valid” and “Invalid” to anything you want. Also, you can remove them. Combined with the ability to Alter Response text, you can present a post-scan message to your app users ideal for your use case.