Code cleanup & fixes
Automatic cleanup (always on)
Before any comparison, every code — from your catalog, your baseline file, or a scanner — goes through the same cleanup:
- Trim spaces from both ends
- Uppercase —
abc123becomesABC123 - Drop leading zeros on all-digit codes —
000123becomes123(all-zero codes stay0)
The mobile app cleans scans the same way, so a shelf scan matches your imported catalog with zero configuration.
Fix-up rules (only during import)
Sometimes the codes in your file differ from what's printed on shelf labels — the classic case is a check digit or a fixed prefix in the master file. Fix-up rules handle this: they're set in the import template, run only during import, and change the stored value.
Available operations
| Operation | What it does |
|---|---|
dropFirst | Remove the first character |
dropLast | Remove the last character |
takeMiddle | Keep a middle section |
You can chain up to 5 operations, applied in order.
Conditions
Each operation can carry conditions — it only runs when all of them hold:
- Length:
lengthGt/lengthGe/lengthEq/lengthLe/lengthLt - Content:
startsWith/endsWith/contains
Conditions are checked against the value as it is at that step in the chain.
Example — drop the check digit only from 14-digit codes:
op: dropLast, if: lengthEq(14)What the mobile app does
Just the automatic cleanup — nothing more. What the scanner sees is what gets submitted. Fix-up rules are an import-time, server-side thing only. When the app looks up a scan, it uses the cleaned-up code and follows your match order.