Follow

ID232 - Barcode Scanning Power App (in Beta)

ID232 Inventory Scanner

Jump to a specific section by clicking a link

Overview | Video Walkthrough | Samples | Accessing App | App Functionality | Best Practices & Tips | Related Alerts

 

Click to Subscribe

 

Overview

Overview

We have many clients asking us for a scanning solution, so here is where we are with ours.

Digital Barcode was a long-standing, well-adopted tool that many clients still miss since its retirement. ScanIT covers important functionality today, and alongside it there remains a desire for a broader solution that supports more of the warehouse’s day. CEO Juice has built an inventory scanning app on Microsoft’s Power Platform (ID232 Inventory Scanner) that runs on the phones your team already carries, inside your own Microsoft 365, and records what they scan in e-automate under each person’s own e-automate login, with the same checks e-automate applies at a desk.

It is also a different kind of app for us. Microsoft’s new native mobile platform for Power Apps lets us publish one app through the app stores while everything in it stays yours: your people sign in with the Microsoft 365 account they already have, the app talks only to your e-automate through your own tenant, what each person may post comes from their e-automate rights, and CEO Juice holds no copy of your data, your users or your permissions. We have been working directly with Microsoft’s engineering team on this platform since before its public release, so there is nothing to install on a server and nothing for us to touch when you add a person.

The first version covers the warehouse’s day end to end: physical inventory counts recorded in e-automate as they are scanned, with errors caught at the scan (wrong item, wrong bin, a serial that is not where e-automate thinks it is) rather than after the sheet is posted; stock transfers; put-away from the receiving dock to the shelf; order picking; and item, barcode and serial lookup. Receiving and shipping come after that, shaped by what the first users ask for.

After years of working with barcode scanning solutions, the hard part has always been the manufacturers’ own barcodes: every brand prints something different, and most tools gave up and made you print your own labels. This app reads what is already on the box, the UPC, the GS1 label and the serial label, from the major OEMs and the compatible brands, and when it meets a label it has not seen, you tell it once and it is known for every scan after that. Printing your own labels is optional, never required. If a manufacturer or distributor has ever sent you a price file with barcodes in it, we would like to see one; loading those in bulk is the next step after teach-once.

It is built and in our own testing now, and we are choosing the first beta clients. Sign up if you want to be one, tell us if you have built your own solution, and tell us what your warehouse needs that this does not do yet.

 

Run Schedule:  N/A

Type of Output: App

 

*  *  *

Video Walkthrough

Video Walkthrough

Watch the 8-minute walkthrough of counting, lookup, transfers, put-away, picking, settings and admin tools. Use the chapter menu inside the player to skip to a task. English captions are available.

Watch the 1-minute put-away and order picking preview

AI-narrated walkthroughs with simulated taps and sample data. Updated October 15, 2026.

*  *  *

Sample

Sample

The home screen offers five workflows: Count inventory, Transfer stock, Put away, Pick orders, and Look up inventory. App admins see a sixth tile, Admin. Under the title the app says who you are to e-automate. Screens below are shown with sample data.
 

 

A count sheet in progress: lines grouped by warehouse and bin, the scanned line counted, Review & commit at the bottom.

 

A pick ticket half done: three lines picked in full, one marked short, Finish ready.

 

*  *  *

Accessing App

Accessing App

1. The app is installed on your iOS or Android phones from the app store as part of setup with CEO Juice. It works with the phone’s camera, and it also accepts input from dedicated scanner guns (see Best Practices below).

2. Each person signs in with their own Microsoft 365 work account. There is no separate password to manage. The first time, the app asks which environment to use: pick the one named CEOJuice, once.

3. Who you are to e-automate comes from your Employee record. The app matches the Microsoft 365 email to the Email field on the Employee record and, through its User ID field, to your e-automate login. Every count, transfer, put-away and pick is recorded under that login, as if you had done it at a desk. Home shows the result under the title: “Signed in as name@company.com, e-automate user JSMITH (Jane Smith)”.

If the email is not on exactly one active Employee record with an active login, Home says so above the tiles, says what the admin must fix, and offers Copy for your admin, a ready-made request to paste into Teams or email. Looking things up still works; posting anything is refused until the record is fixed.

4. What each person may post comes from their e-automate security, their own rights plus their groups’, exactly as e-automate itself checks them. Members of e-automate’s Admins group have everything. For everyone else, grant these in e-automate’s security screen:

- Count inventory: I/C Physical Inv, Edit
- Transfer stock and Put away: I/C Transfers, Add
- Pick orders (finish a pick ticket): Sales Order Pickets, Edit
- Short pick (cancel, backorder, re-ticket): Sales Order Pickets, Add

A tile the person may not use shows a lock and names the missing right in e-automate’s words, so nobody wonders where a feature went and the admin knows exactly what to grant. Teaching barcodes is not an e-automate right; the app admin turns it on or off per person (item 6).

5. App admins. Some things are the app’s own, not e-automate’s: who may change the app’s settings, and what people see in the scanner. Until someone is named, every member of e-automate’s Admins group is an app admin. An app admin opens the Admin tile and names people by name, email or login; from then on only the named people are app admins, which is the usual case, since the person who runs the scanner is often not an e-automate admin.

6. What people see, per person. On the Admin tile, tap a person to see what e-automate lets them post (read only there; grant it in e-automate) and to set the four things the scanner decides itself: count blind, see variances, see on-hand quantities in Lookup, and teach barcodes. Company defaults cover everyone not set otherwise. The Admin tile also shows the sign-ins refused in the last 30 days (who, what they tried, why) and the bins a short pick flagged for a recount.

No user list, permission list or data leaves e-automate for any of this. CEO Juice holds no copy.

 

*  *  *

App Functionality

App Functionality

1. Counting inventory

The problem: counts are slow, and mistakes are invisible until the sheet is posted.

The solution: pick an open e-automate count sheet from the list, then start scanning. The sheet opens as cards grouped by warehouse and bin. Each scan is matched against the sheet on the phone: the line lights up, the count goes up by one, and a serialized item is counted by ticking its serial. Any line can be edited directly, the list can be filtered by item, description or serial, and blind counting hides what e-automate expects while you count. Review & commit writes every line to the open count sheet at once, and each line comes back as committed or failed with the reason, so a wrong item, a wrong bin or a serial that is not where e-automate thinks it is gets fixed at the shelf, not at month end.

The sheet is stored on the phone when it opens, so a dead zone in the back of the warehouse does not stop the count: scans keep matching against the stored sheet and commits wait in a queue that sends itself when the signal returns. Anything not yet in e-automate shows on Home and on Profile, with one tap to the sheet it belongs to. Split a large sheet across phones by location; each phone commits the lines it counted.

 

2. Reading the box, and learning the labels it has not seen

The problem: every manufacturer prints a different barcode, and in older scanning products an unknown label just disappears, so the count is short with no explanation.

The solution: the app reads the label as printed, the UPC, the manufacturer’s GS1 label with the part number inside it, the serial label, and matches it to the item through every key e-automate holds: item number, OEM number, preferred and vendor manufacturer numbers, and the e-automate barcode. A label the app has not seen is called out on the spot with “Did you mean?” suggestions. Pick the right item, or type the item number once, and the label is known for every phone in the company on the next scan, and promoted into e-automate overnight as a vendor number on that item. A family label (one barcode for four toner colors) is matched for that scan only and never saved. A web-link QR is refused as a label. Every unknown label is kept for review, so nothing vanishes silently.

 

3. Looking up inventory

The problem: answering “do we have this, and where is it” means walking back to a terminal.

The solution: scan or type an item number, barcode or serial number and see the item, its on-hand quantity by warehouse and bin, or the unit and its location and status. It is read only and open to everyone who can sign in.

 

4. Transferring stock

The problem: stock moves physically, but the transfer gets keyed into e-automate later, if ever, so bin accuracy drifts.

The solution: set the FROM and TO warehouse and bin, scan the items being moved, and commit. The app posts a real e-automate transfer document through e-automate’s own transfer procedures, under the login of the person who scanned, with a result for every line. There is no shell transfer waiting for someone at a desk to finish; the stock is where the scanner left it.

 

5. Putting away what was received

The problem: received stock sits in the receiving bin in e-automate long after it is on the shelf, so picks and counts argue with reality.

The solution: open a recent receipt, and for each line scan the shelf bin it went to. Each line becomes a transfer out of the receiving bin to that shelf, posted the same way as a transfer. If the bin already holds something else, the app says so before you commit.

 

6. Picking orders

The problem: the picker scratches a 2 over the printed 3, and whoever fulfills the order finds out later, if at all.

The solution: open a pick ticket and walk it in line order or bin order, whichever your warehouse uses. Scan what you pull; a line is done when its quantity is reached. Mark a line short when the bin does not have it. Finish adds a note to the sales order for whoever fulfills. A short line follows e-automate’s own process, done by the scanner in one step: the ticket is canceled, the shortfall is backordered on the order for that warehouse and bin, a new ticket is opened in the same batch for what was picked, and the bin is flagged for a recount. A picker who may not open tickets still finishes; the note tells the office what to cancel and re-ticket.

 

7. Matching the app to how your team works

The problem: every warehouse is different. Some stock carries barcodes, some does not; some shelves are labeled, some are not; some teams count blind, some do not.

The solution: Settings on each phone. “Scan product, key location” is for stock that carries barcodes. “Scan location, key product” (bin mode) flips Count and Transfer: scan the bin label, then key the part number and quantity, with an optional check of the part number against the catalog. A default warehouse pre-fills the transfer screens and the count-sheet list. Blind count hides expected quantities on this phone, or on every phone when an app admin sets it for the company. The pick order you chose last is remembered.

 

*  *  *

 

Best Practices & Tips

Best Practices & Tips

1. You do not need to print labels. The app reads the barcodes already on the box. If you do print your own, for shelves or for unlabeled parts, use Code 128 or QR: both read reliably with a phone camera. MSI Plessey shelf labels cannot be read by a phone camera; a scanner gun reads them.

2. Scanner guns are fully supported. Bluetooth and USB wedge scanners type straight into the “Scanner wedge or manual entry” field on every screen. The gun decodes the barcode in hardware, so any symbology your gun supports will work.

3. With the camera, hold the phone on one label at a time. When two barcodes sit in the box together, the app shows both and lets you tap the one you meant instead of guessing. A held label reads once; move to the next one.

4. Commit at the end of each aisle or section. Pending lines live on the phone until they are committed; Home and Profile show how many and on which sheet.

5. Teach at the shelf. When a label is unknown, pick from “Did you mean?” or type the item number once; nobody in the company has to teach that label again. If a manufacturer or distributor has sent you a price file with barcodes, send it to CEO Juice: loading those in bulk is next.

6. Set people up in e-automate before day one: the sign-in email in the Email field and the login in the User ID field of each Employee record, and the rights listed under Accessing App. Then one member of e-automate’s Admins group opens the Admin tile and names the app admins.

7. Your e-automate process does not change. Count sheets are still reviewed and posted inside e-automate; transfers and pick tickets look exactly as if they had been entered at a desk, under the person who scanned.

 

 

*  *  *

Related Alerts

Related Alerts

None yet. Security for this app is set in e-automate and on the app’s own Admin tile, as described under Accessing App.

 

*  *  * 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk