Product documentation / WexaLogistics

WexaLogistics Scope & Evaluation Guide

Review WexaLogistics: Standalone transport planning, vehicle checks and driver work, with optional CRM and ERP connections. Confirm the current evaluation boundary, tasks and remaining delivery requirements.

Scope and versionInteractive local prototype, reviewed 16 October 2026. No public release version or customer deployment is confirmed. WexaLogistics is a working name; it is a separate catalogue entry from LoadSmart.

What the product does.

WexaLogistics is the working name for our independent logistics application. Its local interactive prototype connects planning, vehicles, maintenance checks and driver tasks. CRM and ERP are optional integration scopes.

Local web and PWA workflows use synthetic data. Native Android/iOS apps, production identity, background location and live CRM/ERP connectors are pending.

Product capabilities

Plan trips around the work

Build trips from stops, steps and work orders. The local prototype includes searchable driver and equipment selection, contract links, workflow templates and revision-aware planning.

  • Trips, stops and workflow templates
  • Vehicles, equipment and trip crews
  • Contracts and transport work orders

Keep vehicle checks and driver tasks connected

The local web/PWA driver flow shows today’s assigned work, vehicle checks, required forms and actual distance or time. Pending offline submissions remain pending until the server accepts them. A local operations board brings authorized driver tasks, checks, attendance and location freshness together. Maintenance reports and service repairs are separate records.

  • Vehicle checks and repair follow-up
  • Driver task and handover history
  • Offline submission queue in the local prototype

Evaluate the relevant tasks.

Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.

  1. Describe a representative journey, its stops and responsible people.
  2. Review vehicle readiness, driver assignment and a required form using synthetic records.
  3. Check a pending offline update and confirm the server acknowledgement.
  4. Agree native mobile, identity, GPS and ERP requirements separately.
Arrange a product demo

Workflow walkthroughs

Follow one trip from planning to completion

Bring a high-level transport workflow, device requirements and the systems you may want to connect. Use fictional stops and people.

  1. Describe a representative journey, its stops and responsible people.
  2. Review vehicle readiness, driver assignment and a required form using synthetic records.
  3. Check a pending offline update and confirm the server acknowledgement.
  4. Agree native mobile, identity, GPS and ERP requirements separately.

Prepare a useful support request.

Include the exact WexaLogistics package or preview, environment and workflow. Confirm whether the issue concerns a local evaluation or an accepted customer installation.

  • Bring a high-level transport workflow, device requirements and the systems you may want to connect. Use fictional stops and people.
  • Describe expected behaviour, what happened and any steps already tried. Do not send passwords, tokens, private files or production records.
  • Remaining acceptance scope: Native Android/iOS packages and real-device tests; Production identity and full organization permissions; Background GPS and live CRM/ERP connectors; Customer environment and operational acceptance.
Get product support

Your questions, answered.

Is WexaLogistics a Dolibarr module?

The active direction is an independent application. Dolibarr, Dynamics 365 Finance and other CRM/ERP systems are optional integration targets; no live connector is confirmed.

Can we install the native driver app today?

Native Android and iOS packages are pending. The current evaluation covers local web/PWA workflows with synthetic data.

References and product context