Skip to content

Latin America · English + Español

Open-source logistics, from WhatsApp to route review.

FleteOps brings messages, documents, and planning data together to review evidence and make decisions about each route. Explore the code and adapt it to your operation.

The project

A starting point for logistics operations.

Routes and review

Organize routes, review planning imports, and record operator decisions.

Evidence and documents

Bring delivery proof, invoices, and messages into a route packet. Review missing documents and discrepancies.

Spanish and English

Originally built for logistics operations in Latin America, with an interface available in Spanish and English.

Delivery context

From the loading dock to route review.

A delivery photo adds context. Review it alongside the route’s quantities and required documents before making a decision.

Explore the review workflow
WhatsAppDemo dispatch

Here is the delivery photo.

Freight truck carrying boxed cargo at a warehouse loading dock, viewed from inside the bay.
demo-delivery.jpg

Received, thank you.

From message to decision

Context for every route review.

The demo uses synthetic data in browser memory: CSV imports, source and evidence review, approve or hold decisions, and reset. Experimental connected source includes WhatsApp and email adapters, documents, and reconciliation; it requires your own infrastructure and setup.

FleteOps / Route workspace/demo
FleteOps demo with three routes: missing evidence on DEMO-001, a quantity mismatch on DEMO-002 and DEMO-003 ready for review.

Find the gap

Quantities and documents in one review.

Review the evidence

Accept the synthetic suggestion before updating the route.

Decide the next step

Approve readiness or place the route on hold.

Route evidence

See the source. Review the difference.

A route packet connects documents, messages, and requirements. Reconciliation rules identify missing proof, quantity differences, and differences between expected and invoiced amounts.

Approval or hold remains an operator’s decision. The software provides context for that review.

WhatsApp, with explicit setup.

The code supports WhatsApp integration through Evolution API. Connecting real services requires your own installation, credentials, and review of the provider’s requirements.

Code and dependencies

The original code is released under MIT, which permits commercial use. Evolution API is a separate dependency with its own conditions. Review the repository’s license and notices before connecting services.

For developers

Explore the project and run it locally.

Start with the setup guide and the demo’s synthetic data. Review the architecture, licenses, and integration configuration before using real services.

Public repository and setup guide