Logistic

End-user documentation

Logistic

Fleet and delivery operations for vehicles, drivers, dispatch, deliveries, fuel, odometer logs, services, contracts, and reports.

Purpose and What Problem This Solves

The Logistic module organizes fleet assets, drivers, deliveries, routes, service history, and operating logs. It helps dispatchers know what can be assigned, managers see fleet cost and utilization, and drivers report activity consistently.

Who normally uses this module

What You Can Do Here

• Maintain vehicle records, states, tags, categories, brands, models, and contracts.
• Track drivers, driver logs, fuel logs, odometer logs, service types, and vehicle services.
• Plan and monitor deliveries and dispatch activity.
• Review fleet reports for utilization, maintenance, cost, and exceptions.
• Keep operational evidence for mileage, fuel, service, and delivery status.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

1. Create vehicle categories, brands, models, states, tags, and service types.
2. Add vehicles with plate number, ownership/contract details, status, and starting odometer.
3. Create driver records and confirm license or qualification requirements.
4. Record a test dispatch or delivery and update milestones.
5. Review fleet reports and agree on daily log responsibilities.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Dispatch a delivery

1. Confirm delivery details, pickup/drop-off, promised time, and customer requirements.
2. Select an available vehicle and qualified driver.
3. Record dispatch assignment and starting odometer if required.
4. Monitor delivery milestones and close the dispatch after completion.

Record fuel or odometer activity

1. Capture vehicle, date, odometer, quantity, amount, and receipt reference.
2. Check that the odometer reading is reasonable compared with the previous record.
3. Save the log and attach evidence where policy requires it.
4. Flag suspicious mileage, missing receipts, or abnormal fuel consumption.

Schedule or record vehicle service

1. Review service due indicators, driver reports, or manager requests.
2. Create the service record with issue, provider, cost, date, and vehicle downtime.
3. Update vehicle status if it should not be dispatched.
4. Close the service only after the vehicle is cleared for use.

Industry Notes and Good Practice

• Fleet control depends on timely logs. A missing odometer reading can hide service risk or delivery cost problems.
• Use vehicle states consistently: available, in use, under maintenance, retired, or otherwise defined by your operation.
• Separate delivery status from vehicle status. A vehicle can be available while a delivery is delayed for customer reasons.
• Fuel, mileage, and maintenance trends are most useful when captured daily, not reconstructed weeks later.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

• Every active vehicle has a plate or asset identifier, status, category, model, and current odometer baseline.
• Drivers have current qualification or license evidence according to company policy.
• Fuel and odometer logs do not go backward without a documented correction.
• Vehicles under maintenance are not dispatched until cleared.

Related ERPat areas

FAQ and Troubleshooting

Why can I not assign a vehicle?

Check vehicle status, maintenance state, active driver assignment, and permission.

Should transfers be handled here?

The logistics menu may show transfer links, but stock-transfer logic belongs to Warehouse/Inventory.

What if an odometer reading was entered wrong?

Correct it through the approved adjustment process and keep the reason visible.

What should drivers update?

Delivery milestones, trip notes, odometer readings, fuel receipts, and incident/service issues according to policy.

ERPat Logistic user guide. This static HTML page is documentation-only and does not change module routing, permissions, or runtime behavior.