Delivery History

Documentation Index

Fetch the complete documentation index at: https://docs.florists.digital/llms.txt

Use this file to discover all available pages before exploring further.

The Delivery History section gives you a complete record of every delivery run — who drove, where they went, how long it took, and whether deliveries arrived on time. Use it to spot patterns, improve your routing, and keep your service reliable.

​

Viewing past runs

Go to Delivery and select a past date, or click History to see a list of all completed runs. Each run shows:

• The date and driver
• Number of stops — total, delivered, carded, and returned
• Total distance and drive time
• The completion time — when the last stop was dealt with

Click into any run to see the full details: every stop, the route taken, delivery times, and any proof-of-delivery photos.

​

Run performance

For every completed run you can see how long it actually took versus how long it was expected to take. The expected duration is built from the route distance and a per-stop allowance (5 minutes for an order; the configured duration for a task). Comparing planned vs actual helps you spot runs that are routinely overloaded or under-resourced. For trends across drivers, date ranges, or locations, use the Delivery section of Insights — that’s where the full analytics live.

​

Punctuality

Punctuality Monitoring is an optional feature that tracks whether each stop arrived within its planned time window. It’s off by default — turn it on in Settings > General > Delivery.

​

Stop ratings

When a run is marked complete, each stop is rated:

​

The run score

Each run gets a percentage — on-time stops divided by scored stops (Skipped stops are excluded; No Data stops count). The score is colour-coded:

• Green (80% and above) — most deliveries arrived on time
• Amber (50–79%) — room for improvement
• Red (below 50%) — a significant number of deliveries were late

Open a completed run to see the score badge, a summary by rating, the average minutes early or late, and two views:

• Stop Details — a table of every stop with planned time, actual time, deviation, and a colour-coded badge.
• Route Map — the driver’s GPS trail with colour-coded pins at each stop (green, amber, red, grey). Useful for spotting patterns — for example, late deliveries clustered in one area might mean a recurring traffic or access problem.

​

Driver punctuality

Across multiple runs, the Driver Punctuality view in Insights compares each driver’s average score, on-time percentage, and run count for the selected date range. Useful for spotting who might need support, a route adjustment, or fewer stops per run.

​

Using history to improve

A few practical ways to get value from delivery history:

​

Spot problem addresses

If the same address keeps coming up as carded or returned, there might be an access issue (gated community, no doorbell, business that closes early). Add a note to the customer’s record so drivers know what to expect next time.

​

Right-size your runs

If runs are consistently taking longer than expected, you might be adding too many stops. Most shops find 8–12 stops is a good balance between efficiency and punctuality. Two runs of 8 stops are usually more punctual than one run of 16.

​

Plan staffing

If certain days of the week are consistently busier (e.g., Fridays and Saturdays), you can plan to have an extra driver available.

​

Check driver performance

If one driver consistently has lower punctuality or more returned deliveries than others, it might be a training opportunity — or they might just be getting the trickiest runs. Use the data to have a fair conversation.

​

Tighten unrealistic time windows

If timed slots like “between 10am and 11am” keep coming up as Late, the route may not physically be able to reach them in time. Review your delivery slots to make sure the windows are achievable.

​

Common questions

​

What’s next?