Live delivery tracking alongside project44

What project44 shows about a delivery today

project44 covers carrier-side visibility well. The gap shows up when delivery is on your own fleet and the end customer wants to see where the truck is right now.

• project44 shipper view. Internal-facing dashboard for shipper operations: every load across carriers, predictive ETA, exception alerts, OS&D management. Not a per-customer link branded for the end customer.
• Carrier-fed live position. Via ELD, AIS and carrier APIs. The end customer doesn’t see this directly.
• Webhook events for downstream consumers. Operations teams can subscribe to shipment-status and milestone events and feed them into a TMS, OMS or BI tool.

All of that is internal carrier-side visibility for the shipper. It is not a branded end-customer tracking page for own-fleet deliveries.

What live delivery tracking actually means

For own-fleet operations, the customer-facing tracking experience that drives repeat orders and reduces support load looks like this:

• Live driver GPS on a map. The customer sees where the truck is right now and what stop number they are on the route.
• Real-time ETA. Recalculated as the driver moves and as the plan changes; not a static morning estimate that’s out of date by lunchtime.
• Driver name and contact. Customer knows who’s coming and can call if access changes.
• Branded. The page carries the operator’s branding (logo, colors, layout), not a generic delivery widget. Multi-brand support for operators running multiple consumer brands.
• Embedded content. NPS micro-survey at the end. Safety briefings before a hazmat delivery. Access codes for a gated community. Care instructions for a piece of equipment.
• Self-service rescheduling. If the customer can’t take the delivery, the page offers a route-aware reschedule that already fits the optimized plan.

This is a separate surface from the shipper-facing carrier view project44 ships natively. The two complement each other.

Where project44 users land today

Three patterns are common before a live-tracking layer is added.

• Customer support absorbs the “where’s my order” calls. The customer phones in. The CSR opens the shipper view, sees a carrier-shipment status from earlier, calls the driver, calls back the customer. Cycle time per call: 4 to 8 minutes. Aggregate cost at scale: significant.
• Generic SMS templates. Driver sends a manual SMS at start of day with an estimated window. No live tracking, no map, no self-reschedule. Works until a customer asks a follow-up.
• Third-party tracking widget, no eLogii. A basic tracking widget is bolted onto the storefront, but it has no real connection to the live driver position or to the optimized plan. The ETA is a guess.

The fix is a tracking page driven by the same live GPS and route data the dispatcher is looking at, branded to match the operator, surfaced wherever the customer expects to find it.

How eLogii’s live tracking works

The driver app streams GPS as the driver moves. eLogii recalculates ETAs continuously as drivers progress and as the plan changes. The customer-facing tracking page shows the live state.

• Live driver GPS stream. From the driver app to eLogii in real time.
• Real-time ETA. Recalculated against the current plan and current driver position.
• Branded tracking pages. Configurable logo, colors and layout per brand. Multi-brand support for operators running several consumer brands from one fleet.
• Embedded content. NPS, safety briefings, access codes, care instructions, treatment notes – configured per task type or per customer segment.
• Self-service rescheduling. Customer can pick a route-aware slot if they can’t take the delivery. Around 70% of reschedule requests get handled without coordinator involvement.
• Notification triggers. SMS or email when the driver is N minutes out, when arrival is imminent, when the delivery is complete.

How live tracking fits alongside project44

The end-customer tracking page is served by eLogii. project44 remains the carrier-visibility system on its side of the stack. Three display shapes are common, and the choice depends on where you want the customer to land.

1. SMS / email link. Customer gets a link via SMS or email at key moments (booked, driver en route, N minutes out). Link opens the eLogii tracking page directly. Simplest integration; no portal work required.
2. Embedded in your customer portal. The eLogii tracking page embeds via iframe in your existing customer portal, so customers logging in to check an order see the live tracking inside their familiar portal.
3. Embedded in your storefront. Same iframe pattern but inside your e-commerce storefront on the order details page.

Each is display-side: where the customer sees the page. eLogii streams live position from the driver app; nothing eLogii produces gets written into project44.

Frequently asked questions

Does project44 have end-customer delivery tracking?

project44’s shipper view shows carrier-shipment status and predictive ETAs to the shipper. It does not ship a branded end-customer delivery tracking page, a route-aware ETA for own-fleet deliveries, or embedded content like NPS, access codes or safety briefings. That layer is what eLogii adds for own-fleet operations.

Why doesn’t project44 show live ETAs for own-fleet deliveries?

project44 is a multi-carrier in-transit visibility platform. It tracks loads moving across carriers, not the stop-by-stop ETA on your own-fleet routes. The route plan that would feed a live per-stop ETA lives in the routing layer above the order system, not in project44.

How does eLogii’s live tracking work?

The eLogii driver app streams live GPS coordinates as the driver moves. eLogii recalculates route ETAs in real time as drivers progress and as the plan changes. Customer-facing tracking pages, branded per customer, show the live map, the next-stop ETA, the driver name and contact, and any embedded content the operator configured (NPS, access codes, safety briefings, treatment notes). Pages can be embedded in your customer portal or storefront via iframe, or sent to end customers via SMS / email links.

Does eLogii write live state into project44?

No. The two systems coexist via the order system in the middle, not by writing into each other. eLogii’s live GPS feeds the eLogii dispatch desk, the branded end-customer tracking page and your operational system. project44 continues to capture multi-carrier visibility on its side.

Can the tracking page be branded per customer?

Yes. Multi-brand tracking is supported. Run three brands from one dispatch desk, each with its own logo, colors, layout and embedded content. Useful for operators running multiple consumer brands off a single own fleet.