# How to fix a naming pattern while bulk enrolling Android devices?

Last updated: July 24, 2026

This guide explains how to apply a consistent device naming pattern when bulk enrolling Android devices, since MDM identifies devices by model number by default, making them hard to tell apart. Administrators create or edit a QR Code enrollment template under Enrollment > Android Enrollment and use the device naming option to apply variables such as %serialnumber%, %devicenumber%, %easid%, %username%, %email%, or %imei% so each enrolled device is automatically named accordingly.

By default, MDM servers identify devices by model number. When there are multiple devices and the IT administrator needs to know which user has which device assigned to them, this can be complicated. With Mobile Device Manager Plus, you can apply a naming pattern to the devices while bulk enrolling them.

## So, how exactly does a naming pattern work?

1. When enrolling a device using a template with a naming pattern of **%serialnumber%**, the device's unique serial number such as SG87I, XB456K, and BG77N, becomes the device's name. Using this naming convention makes it easy to identify each device individually on the MDM console.

2. The floor manager aims to establish consistent naming patterns, like Floor Device1, Floor Device2, and Floor Device3, in incremental order for the devices on the floor. To achieve this, **%devicenumber%** can be fixed in the template for all devices, making the device number the device's name.

*Note:* Similar to **%devicenumber%**, **%serialnumber%**, you can also use other naming conventions such as **%easid%** (EAS Device Identifier), **%username%** (User Name), **%email%** (Email Address), **%udid%** (UDID), **%imei%** (IMEI).

## How to create an enrollment template for applying naming pattern?

Go to **Enrollment** > **Android Enrollment** > **QR Code Enrollment**

- Click **Create New Template** and provide a name for the template.
- Next, choose **Automatically** and select **To Single User** or **by Directory Authentication** based on the purpose of the device. Specify which user the devices should be enrolled under if assigning to single user.
- Select the **Device Group** that these devices should belong to.
- Use the device naming option to easily identify these devices. Provide any of the above mentioned naming convention to apply the naming pattern to the devices enrolled using this template.

![How to fix a naming pattern while bulk enrolling Android devices? illustration 3](https://cdn.manageengine.com/mobile-device-management/help/images/Device-name.png)

## Frequently asked questions

### Why would I want to apply a naming pattern when bulk enrolling Android devices?

By default, MDM identifies devices by model number, which makes it hard to tell devices apart when many are enrolled — applying a naming pattern (e.g., based on serial number or an incremental device number) lets you identify each device individually on the console.

### What variables can I use to name devices automatically?

You can use %serialnumber%, %devicenumber%, %easid% (EAS Device Identifier), %username%, %email%, %udid%, or %imei%, depending on how you want devices named.

### Where do I set up a naming pattern for enrollment?

Go to Enrollment > Android Enrollment > QR Code Enrollment, create or edit a template, and use the device naming option to apply one of the supported variables.

### Can I name devices in an incremental sequence instead of by serial number?

Yes — use %devicenumber% in the template to name devices incrementally, for example Floor Device1, Floor Device2, Floor Device3.