As of 13 August 2026, AI can choose delivery tracking software for your business.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open a blank document and record your delivery volumes, delivery areas, carriers, current systems, users, must-have features, budget constraint and the operational problem you are trying to fix.
   2. Paste those details into the prompt, replacing each bracketed slot with your own information, and ask the model to produce the shortlist with sources.
   3. Open every supplier page and source cited for a must-have feature, then mark the comparison table as confirmed, supplier-claimed, unclear or unsupported.
   4. Send the model the corrected table and ask it to remove any candidate that lacks a confirmed must-have integration or workflow, rather than filling the gap with an assumption.
   5. Contact the remaining suppliers with the generated questions and request a demonstration using your actual carrier, order and notification workflow.
   6. Run the proposed trial or acceptance tests, compare the results against your must-have list, and ask a colleague who will use the system to record any failed or awkward step.
   7. Choose only after comparing the trial results, implementation work, contract terms and total operational fit against the original requirements.

   Prompt

   Act as a UK business software researcher, not the final decision-maker. Help me shortlist and assess delivery tracking software for this business.
   
   Business context:
   - Business type: [business type]
   - Delivery model: [own fleet, couriers, carriers, or mixed]
   - Delivery locations: [UK regions or countries]
   - Approximate deliveries per [day/week/month]: [volume]
   - Carriers or platforms already used: [names]
   - Required integrations: [systems and platforms]
   - Users and roles: [teams and permissions needed]
   - Must-have features: [features]
   - Nice-to-have features: [features]
   - Current problems: [problems]
   - Budget or purchasing constraint: [constraint]
   - Implementation deadline: [deadline]
   
   Research current options using official supplier pages and other reliable sources. Consider UK availability, carrier and integration support, customer notifications, proof of delivery, live tracking, reporting, user permissions, data handling, implementation effort and contract constraints. Do not invent features, integrations, prices, legal terms or customer claims. Mark each point as verified, supplier-claimed, unclear or needing a trial. Cite the source for every material claim and state when a source is unavailable or ambiguous.
   
   Return:
   1. The five most suitable candidates, explaining why each does or does not fit.
   2. A comparison table covering every must-have feature and integration.
   3. The information still missing before a decision.
   4. Ten precise questions to ask each supplier.
   5. A low-risk trial and acceptance-test plan using realistic delivery scenarios.
   6. A provisional recommendation only if one option is clearly ahead, with the main reason not to choose it.
   
   Do not make the decision on my behalf, and do not treat a marketing statement as proof that the software will work in my workflow.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.