🏪 Customer Profile — Field Reference

The unique account number that identifies this customer across the entire system. It is the primary key used in all transactions — orders, deliveries, collections, and syncs.

The full business name of the customer. This is what the rep sees in the customer list and on all printed documents such as invoices and delivery receipts.

The customer's physical street address, split across three lines. Printed on invoices, delivery receipts, and shown on the customer detail screen. Used by the rep to confirm they are at the correct location.

The customer's main phone number. Shown on the customer detail screen so the rep can call ahead or coordinate while in the field.

The customer's fax number. Stored and displayed on the customer detail screen. Rarely used in the field today but kept for back-office document delivery compatibility.

The customer's email address. Used for sending digital copies of invoices or receipts after a transaction is completed. Also shown on the customer detail screen.

The customer's postal code. Shown on the customer detail screen and printed on documents. Can be used for regional reporting and grouping.

The name of the primary contact person at this customer location (e.g., store manager, buyer). Shown on the customer detail screen for the rep's reference.

The geographic or commercial region this customer belongs to. Used for route filtering — the rep can filter the customer list by region using Route Preferences. Also used in back-office reporting.

The GPS coordinates of the customer's location. Used to display the customer on a map within the app and to calculate the route between stops.

The maximum outstanding balance the customer is allowed to carry. The app checks this before allowing the rep to complete a new order — if the customer is over their limit and credit enforcement is on, the order is blocked.

The remaining credit the customer has before reaching their limit (Credit Limit minus current balance). Shown on the customer detail screen so the rep knows at a glance how much more the customer can order.

Indicates whether the customer's account is on credit hold. A customer on hold is flagged in the customer list (shown in red) and the rep is warned when attempting to place an order.

• No Credit Hold — normal account
• Credit Hold — account is on hold; orders may be blocked

Defines how the customer's credit usage is calculated — for example, whether open invoices only count, or whether pending orders also reduce the available credit.

A percentage that allows the customer to exceed their credit limit by a defined margin. For example, 10% means the customer can go up to 110% of their credit limit before being blocked.

When enabled, the rep must enter a supervisor password to override a credit limit block for this customer. Prevents reps from bypassing credit limits without management approval.

The accounts receivable account code in the ERP that this customer's transactions are posted to. Used by the back-office to route payments and charges to the correct ledger account.

A bitmask field that controls several AR-related behaviors at once. Each bit enables a different option:

• Bit 1 (0x01) — Enable the AR button for this customer
• Bit 2 (0x02) — Allow the rep to collect payments from this customer
• Bit 3 (0x04) — Include this customer in AR reports
• Bit 4 (0x08) — Block sale if customer has reached their credit limit

The payment terms code for this customer (e.g., NET30, COD, NET15). Printed on invoices and used by the back-office to determine due dates on open balances.

Controls whether the rep is allowed to change the payment terms at the time of the sale. When disabled, the terms are locked to whatever the customer record has. When enabled, the rep can select different terms on the order.

Defines what payment methods the rep can accept from this customer. Controls whether cash, check, or other methods appear as options during a collection transaction.

Specifies whether the rep must collect payment at the time of delivery. If set to required, the rep cannot complete the delivery without recording a payment first.

The minimum cash amount the rep must collect from this customer on each visit. Used alongside Require Payment to enforce a floor on collections.

Flags that this customer has a history of returned (bounced) checks. Intended to warn the rep not to accept checks from this customer.

Links this customer to a promotional pricing group. When a promo is active, products in that group are automatically discounted for this customer during order entry.

Three price break group codes that assign this customer to tiered pricing structures. A price break group defines quantity-based discounts — for example, "buy 10 cases or more, get a lower price."

Having three separate IDs allows a customer to belong to up to three different break tables simultaneously (e.g., one for beverages, one for snacks, one for seasonal).

Links this customer to a specific pricing contract in the ERP. A contract overrides standard pricing for agreed-upon products and quantities, commonly used for key accounts with negotiated rates.

Assigns this customer to a customer group. Groups can control which products are visible in the catalog, which promotions apply, and reporting segmentation.

The minimum profit margin percentage that must be maintained when selling to this customer. If the rep enters a price that would fall below this margin, the app blocks or warns before completing the order.

Total sales to this customer for the current period (Period to Date). Shown on the customer account screen so the rep can see recent purchase volume at a glance.

Total sales to this customer for the current fiscal year (Year to Date). Useful for identifying the customer's annual spend and comparing against targets.

The average sales amount per visit or period for this customer. Helps the rep gauge what a typical order looks like and flag unusually large or small orders.

The date of the most recent transaction (order, delivery, or collection) for this customer. Shown on the customer detail screen to flag accounts that have not been visited recently.

The date of the most recent payment received from this customer. Helps the rep and the back-office identify overdue accounts.

When enabled, the rep cannot create any new sales orders for this customer. The customer still appears on the route and can be visited, but the Order option is blocked.

Specifies whether the rep must enter a Purchase Order (PO) number from the customer before completing the order. Common for corporate accounts that require PO tracking for their own accounting.

The minimum total quantity the rep must order to submit a transaction for this customer — in cases (Major) and units (Minor). If the order falls below these minimums, the app will warn or block.

The minimum dollar value required for the rep to submit an order for this customer. Prevents very small orders that are not economical to fulfill.

When enabled, the rep cannot create price quotations for this customer. The quotation workflow is blocked at the customer level regardless of the company-wide quotation setting.

An internal classification code used to group customers into business segments for filtering and reporting. Also used in some pricing and commission logic to differentiate customer tiers.

Encodes the days of the week on which this customer should be visited. Stored as a bitmask where each bit represents a day (bit 0 = Sunday, bit 1 = Monday, etc.). Used by the route planning system to schedule stops on the correct days.

Whether this customer is subject to sales tax. Works together with the product's Taxable flag — tax is only applied when both the customer AND the product are marked taxable.

The tax jurisdiction code assigned to this customer. Determines which tax rate and rules apply. Overrides the product's tax code when a customer-specific tax code is set.

The customer's tax registration or exempt number (e.g., IVU Loto in Puerto Rico). Required by some tax authorities to be printed on invoices for exempt or registered customers.

A label or description associated with the customer's tax register ID. Printed alongside the register number on tax-compliant invoices.

The date on which the customer's tax registration certificate expires. Can be used to alert the rep or back-office when a renewal is needed before the current registration lapses.

Determines how the merchandising activity count is tracked for this customer. The default is Depletion — the rep records how many units were placed on the shelf, and the system decrements that from the truck inventory.

The number of merchandising display locations at this customer (e.g., number of shelf sections or cooler doors assigned to the company's products). Also encodes whether a back-room section exists — if the stored value is greater than 9, back-room tracking is enabled.

Flags whether this customer accepts deliveries on Saturday and Sunday. Used by route planning to include or exclude weekend delivery scheduling for this stop.

Enables service charge functionality for this customer. When active, applicable service fees are automatically added to orders based on the company's service charge configuration.

Additional delivery configuration fields. Default Delivery is intended to assign a default delivery method or route for this customer. Supplier No links the customer to a supplier account in multi-supplier deployments.

Ten pairs of user-defined fields — each has a Caption (the label shown on screen) and a Value (the data for this customer). The captions and values are configured per company in the ERP and synced to the device.

Can hold any customer attribute that doesn't fit a standard field — for example: license number, account manager name, store chain code, preferred language.

The number of days back to look when highlighting products in the catalog that this customer has previously ordered. For example, if set to 30, products purchased in the last 30 days are visually marked in the catalog to help the rep quickly reorder familiar items.

Default value is -1 (disabled — no highlighting).

The currency to use for transactions with this customer. Intended to support multi-currency deployments where different customers may be invoiced in different currencies.

Social media handles for the customer. Stored on the customer record and displayed on the account detail screen.

Several fields are synced from the ERP and stored on the device but are never read by any screen or logic in the current app version:

• Group ID — customer group assignment
• Exchange, Pickups, Damaged, Inventory — legacy transaction type flags
• Profile — customer profile code
• Last Statement / Last Aging — accounting dates
• Float Terms — extended payment float settings
• COV — coverage code
• Non Sale — non-sale visit flag
• Client Modify — edit permission flag
• Record Update — update tracking code
• Validate Qty Option — quantity validation setting
• Sales Under Pay — under-payment tracking
• Price on Report — show price on printed report
• User Defined Value — legacy single custom field