App
Inventory & dataNumber ranges
Inventory & data

Number ranges

Uslimato issues sequential numbers for two things: asset tags like AST-000001 and movement numbers like MOV-000001. Both ranges have a finite capacity — and Uslimato warns in good time rather than one day running out of numbers.

#Configuring asset tags

You set the format under Settings › Asset tags. The number of N characters in the template decides how many tags are possible at all.

TemplateCapacityExample
{PREFIX}-NNNNNN999,999AST-000001
{PREFIX}-{YYYY}-NNNN9,999 per yearAST-2026-0001
{PREFIX}-{TYPE_CODE}-NNNNNN999,999 per typeAST-LAP-000001

#Movement numbers

Movement numbers follow the format MOV-NNNNNN. Every tenant has its own independent counter, which advances with each new movement.

#Monitoring

The usage of both ranges is checked continuously — current position, maximum capacity and the share in percent.

LevelFromWhat happens
Warning80 % usedYellow notice on the dashboard
Critical95 % usedRed notice on the dashboard

#Automatic extension

By default Uslimato extends a number range on its own before it fills up.

  1. Usage reaches 95 %
  2. The template gains one digit, NNNNNN becomes NNNNNNN
  3. Tags and numbers already issued stay unchanged
  4. New entries use the extended format
  5. The change is recorded in the audit log

If you prefer to steer this yourself, turn the extension off under Settings › App › Extend number ranges automatically. The warnings still arrive — only adjusting the template is then up to you.

#Changing the format later

  1. Open Settings › Asset tags
  2. Add further N positions to the template
  3. Save
Caution
There is also an option to regenerate existing tags. It replaces every asset tag you have. If devices are already physically labelled, label and system will no longer match afterwards. Use this deliberately, and ideally before the first labelling run.

#Recommendations

  • Leave automatic extension on unless you have a concrete reason not to
  • Start with at least six digits — that lasts indefinitely for the vast majority of organisations
  • A year-based template ({YYYY}) resets the counter naturally each year and keeps numbers short
  • Treat the dashboard notices for what they are: an early warning with plenty of headroom, not an emergency
Was this helpful?
Suggest an edit