Organisation Settings

Commission Rate

The percentage of sales revenue paid as commission to field agents. Changes take effect immediately for future calculations. Historical commission already calculated is not affected.

Field Agent Allowances

Daily field allowance (paid per day worked in the field) and monthly transport allowance (fixed per month). Both are added to the agent's total field earnings.

Commission Rate History

Audit trail of all commission rate changes. Previous rates are preserved for historical commission calculations.

Offline Zone Settings

Mark zones where field officers operate with low or no internet connectivity. Agents and supervisors assigned to offline zones receive extended login sessions so their data is never lost during long trips without signal. The Session Duration should match the longest time your team typically spends in that area without connectivity.

Role Names

Rename the six reporting tiers to match how your company refers to them. These labels appear everywhere across the platform. The underlying permissions are unchanged — you are only changing what each role is called. Leave a field blank to restore the default.

Terminology

Rename the words this platform uses for your own business (an outlet, a visit, a target…). These labels appear everywhere across the platform. Leave a field blank to restore the default.

Check-in GPS Radius

How close a field officer must be to an outlet to check in. The default of 100 metres tolerates normal GPS drift (the outlet's own saved coordinates also carry error) while still preventing check-ins from home. Tighten it for dense, open areas; loosen it where signal is poor.

Operating Area

Which country (or region) your team operates in. A live GPS check-in outside this area is rejected as a device GPS glitch; an imported outlet outside it is imported without coordinates (its real location is captured on the agent's first visit). Leave as "No restriction" if you'd rather not check this.

Check-in Working Hours

The field day window during which check-ins are accepted. Check-ins logged outside these hours (for example a stray 2am attempt) are blocked, keeping the visit record clean. Times are 24-hour EAT. The default is 07:00–20:00 — adjust it to match your team's real working day.

Daily Visit Cap

The maximum number of outlets a field officer may plan and visit in a single day. This keeps daily routes realistic and prevents over-committed journey plans. The default is 15 outlets per day.

Visit-Frequency Targets

How many visits per month each outlet tier requires. This is the ONLY thing that decides an outlet's "on target" status everywhere it's shown — My Book, the churn/risk model, and the Territory map all read this same policy, so a change here takes effect across the whole platform immediately.

Outlets with no tier assigned yet default to 1 visit/month and aren't editable here — assign a real tier to bring an outlet under this policy.

Geographic Area Visit Caps

Limit how many total visits (any agent, any outlet) a zone, region, or street may receive in a rolling period — flags a check-in that would exceed it and notifies the manager, without blocking field work. Separate from the per-tier targets above, which address under-visiting; this addresses over-visiting one convenient area.

Churn Risk Scoring Weights

How heavily each factor counts toward an outlet's churn-risk score: recency (days since last visit), frequency (visits vs. this outlet's target above), monetary (sales trend), and signal (competitor activity, stock-outs, complaints). Any positive numbers work — they're automatically scaled to add up to 100%.

Risk Band Cutoffs

The churn score (0-100, computed from the weights above) that classifies an outlet into each risk band. Must increase left to right.

Alert Notifications

Which alerts fire for this organisation, at what severity, to which roles, and how often — turn down noise without losing the alerts that matter.

Integrations

Feed live data from this organisation into an external system — either they pull it with a key, or we push it to a URL you register, on a schedule you choose.

Business Model & Field Rules

How this organisation operates in the field. Your business model — — — decides which entity kinds your officers register and whether performance is scored on sales or on field activity.

Sales Structure

Pick the hierarchy that matches how your sales force is organised. A preset sets the business model and renames every tier to your language in one step — you can still fine-tune the names below in Role Names. The reporting chain is flexible: a field officer can report to any manager above them, so an optional middle tier (e.g. an Area Sales Manager present in one region only) can be added or removed anytime without reshaping the rest.

Regions & Zones

Your own named territories — not administrative map boundaries. Create and rename them freely; officers pick a region and zone when they register an entity, and see everything in their zone. A zone belongs to a region.

Languages

Choose which languages your team can use across the app. English is always available as the base language. A language only appears here once the TradeMetriq platform has published it; turning one off hides it from your team's language picker without affecting anyone else.

Data Protection — Access Requests

Team members without screenshot/print access see a request form when they try to capture or print a protected screen. Approve or deny each request here; approved access can be time-limited or permanent.