← Knowledge base

📦 Product Profile — Field Reference

Explains every field on a MultiRoute product record. Use this to understand what each setting controls and how it affects the rep's experience in the field.

Field Groups
🏷️
Identity
Core fields that identify and classify the product
Item ID Text

The unique code that identifies this product across the entire system. It is the primary key used in orders, deliveries, returns, and syncs between the device and the back-office.

Assigned by the ERP and cannot be changed on the device.

💡 This is what the back-office uses to match the product record during sync. Every transaction references this ID.
Description Text

The full product name shown in the catalog, on order lines, and on printed documents such as invoices and delivery receipts.

This is what the rep and the customer see on the screen.

Short Description Text

An abbreviated version of the product name used in compact views where space is limited, such as small print formats or summary screens.

Category Text

The product group or family this item belongs to (e.g., Beverages, Snacks, Dairy). Used to filter and organize the catalog on the device.

The rep can browse the catalog by category to find products faster.

Brand Text

The brand or manufacturer of the product. Supports additional filtering in the catalog and can drive commission or reporting logic.

Package Text

Describes the physical packaging configuration of the product (e.g., 6-pack, 12-pack, single). Informational — used for display and reporting.

Division Text

The organizational division or business unit responsible for this product. Used in reporting and can restrict visibility by rep assignment.

Image Group ID Text

Intended to link this product to a set of product images stored on the device or server. The value is synced from the ERP and stored on the device.

⚠️ Not currently used in the app. No product images are displayed anywhere in the current version.
Most used fields
Core — used in 30+ places
🏷️
Description
Shown on every screen — catalog, orders, invoices, delivery receipts
91 files
📐
Sale UOM
Every quantity entry depends on this — case vs. unit
38 files
💰
Case Price
Primary driver of order totals when selling by case
38 files
💰
Unit Price
Used whenever the product is sold by individual unit
37 files
Essential — used in 10–19 places
📐
Conversion
Units per case — needed any time case and unit quantities are mixed
19 files
⚙️
Taxable
Checked on every transaction to determine if tax applies
12 files
🏭
Serialized
Triggers serial number capture at the time of delivery
12 files
🏭
Uses Lot Number
Triggers batch/lot capture at delivery for traceability
13 files
✏️
Associate
Links product to a rep for attribution and commission logic
12 files
💰
Unit Cost
Used across margin and profitability calculations
10 files