Skip to main content

Feature availability and current limits

This guide describes the client implementation. Your environment also needs compatible backend services, identity configuration and effective permissions. Preview success does not verify those live dependencies.

Feature availability and current limits — sales agent
Start here after sign-in. Use Sales or Capture sale to record a sale; My stock shows your assigned serials. Example screen: agent. Local sample data; records and available actions depend on your access. Open desktop image · Open mobile image.

Wallet and finance features​

The client includes payout destinations, client settlements, cash-deposit review, commission financial positions and recoveries. Your connected backend must provide the corresponding endpoints and authorise your account.

A “route could not be found” message means the request did not reach an available matching route. It is not evidence of a zero balance. Ask the administrator to confirm which backend version is deployed.

Known client-facing limits​

AreaCurrent behaviour
Cluster and team selectionAuthorised name pickers use the connected lookup service; inaccessible records cannot be selected
Live report date rangesUse report-specific period and inventory filters offered by the connected service
Live PDF exportsAvailable through report jobs; default maximum 500 rows, with explicit size/font limits
Export completenessDefault 1,000,000 rows for CSV/XLSX/JSON; exceeding configured limits fails instead of producing a partial file
Report displayPDF/XLSX use readable currency and dates; choose Africa/Nairobi or UTC. CSV/JSON retain raw values; XLSX includes hidden raw audit columns
Report historyJobs created in this browser are tracked; there is no complete server-wide history list here
Inbound provider eventsConnection view does not expose full inbound event history
Pending file scansA non-clean completion response does not attach the file; do not assume automatic background attachment
Recent-first listsSupported lists retain API ordering across cursor pages; Load more retrieves another page, not a global re-sort
Existing filtersClient fallback may be used when a connected backend does not support a requested filter
Browser pushRegistration needs a provider-issued device token; automatic browser enrollment is not implemented
Inventory actor selectionStock actions use a verified linked agent or internal staff identity; an unverified account must be reviewed by an administrator
New administrative workflowsRequire a live connection and effective access; preview or offline mode cannot submit these changes

Newly available workflows​

Use these guides for the latest client features:

  • Data purposes: prepare, review, and activate policies needed for customer records and uploads.
  • Business calendars: create and inspect versioned working schedules.
  • Privacy: legal holds, retention triggers, and controlled decisions.
  • Access management: identities, grants, merchant users, and agent memberships.
  • Notifications: inbox, preferences, verified contacts, and device registrations.
  • Payments: sale-bound and standalone collection requests.
  • Inventory: adjustment approvals and custody exception resolution.
  • Account: agent wallet funding, reservations and activity.
  • Bulk wallet work: CSV or Excel sales and top-ups for authorised operators.

An available client form does not confirm provider delivery or a completed financial action. Inspect the saved record and final outcome in the connected environment.

Account and merchant setup​

Invitation delivery, identity recovery, merchant collection approval and service-side authorisation are performed by their connected services. The client cannot grant them by displaying a successful preview or changing a local field.

How to use this information​

Check the affected guide and error message before escalating. Tell your administrator which task is blocked, rather than assuming every unavailable action is a broken button.

This page should be reviewed when backend capabilities change. Until a flow has been confirmed in your live environment, do not treat documentation examples as evidence that a financial action completed.