Skip to content

Code cleanup & fixes ​

Automatic cleanup (always on) ​

For scan/product matching and Baseline/report matching, codes go through the same cleanup. This doesn't apply to the barcode + SKU + external ID identity combination used to build Product IDs:

  1. Trim spaces from both ends
  2. Uppercase — abc123 becomes ABC123
  3. Drop leading zeroes on all-digit codes — 000123 becomes 123 (all-zero codes stay 0)

The mobile app cleans lookup keys the same way, so a shelf scan matches your imported catalogue 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 ​

OperationWhat it does
dropFirstRemove the first character
dropLastRemove the last character
takeMiddleKeep 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 ​

The mobile app applies only the automatic cleanup when looking up a product. It submits the scanned code itself after trimming surrounding whitespace, preserving letter case and leading zeroes; it doesn't submit the normalised lookup key or apply import fix-up rules. Lookup follows the layered match order within the Inventory's catalogue.

QuantalCount Help Centre