Wishing you and your team a veryHappy DiwaliTeam FreGo

Apply to FreGo

Tell us a bit about yourself

Fields marked * are required.

PDF or Word · Max 4 MB per file

FreBot
Automated assistant — not a person
Home Platform Modules About Team & Management Careers Contact
Guide

FTL vs PTL: how each workflow runs in FreGo

Full truckload and part truckload are different jobs. Here is how each one runs, step by step, in FreGo.

The difference in one paragraph

FTL (full truckload) moves a consignment that fills a vehicle, usually directly from the loading point to the delivery point. PTL (part truckload) combines smaller consignments on a vehicle and moves them through hubs, with pickup, hub-to-hub transfer and local delivery. FTL is a short chain of steps. PTL has many more, because goods change hands between vehicles and branches.

FTL in FreGo: 4 steps

  1. Indent. The customer or branch raises a vehicle requirement with route, material, weight, vehicle type and loading date. It is tracked until a truck is placed.
  2. Docket. A docket (LR) is created against the indent. The E-Way Bill is validated and the consignor, consignee, goods and freight details fill in automatically.
  3. Trip. An own or hired vehicle and a driver are assigned. Part B of the E-Way Bill is updated with the vehicle number and the trip is followed until it arrives.
  4. Delivery (POD). Delivery is confirmed and the POD is captured. The POD starts the customer invoice and releases the vendor balance.

PTL in FreGo: 12 steps

  1. Booking. Create the docket with consignor, consignee, packages, weight and charges, with E-Way Bill validation.
  2. Pickup. A pickup run with a pickup vehicle; Part B is updated for it.
  3. Pickup update. Confirm packages and weight actually collected and record any mismatch at the pickup point.
  4. Manifest. Group dockets by destination into a hub-to-hub manifest.
  5. THC. A Truck Hire Challan for the linehaul vehicle, so the owner's payment is traceable.
  6. Trip arrival. Record arrival at the destination hub and check the manifest against what was received.
  7. Trip update. Close the trip and note exceptions such as shortage or damage.
  8. Delivery sheet. Group dockets for local delivery with a vehicle and a delivery executive.
  9. Delivery sheet update (POD). Update status and POD for every docket on the sheet; this starts customer billing.
  10. Godown delivery. Hand goods to consignees who collect, and record their POD.
  11. Crossing challan generation. For goods handed to a partner transporter, generate a challan and assign the E-Way Bill to the other transporter.
  12. Crossing challan update (POD). Update the partner's POD so every docket is closed end to end.

What both share

  • One docket record from booking to final POD, with every status change recorded.
  • E-Way Bill actions at the step that needs them.
  • POD capture, audit and bulk update, which then triggers billing and the vendor balance.
  • Vendor payments with TDS, bank reconciliation, dashboards and reports.

If you run both, FreGo keeps them on one platform with one set of customers, rate cards and reports. Next: where E-Way Bill and E-Invoice actions happen, full detail on Modules, or book a demo.