# AI for New Zealand logistics.

URL: https://levystreet.com/industries/logistics/
Updated: 2026-10-19

AI for logistics in New Zealand: proof of delivery extraction, shipment exceptions and delivery enquiries, plus carrier liability and driver hours rules.

## Short answer

AI in New Zealand logistics is most useful on the paperwork and messages around freight: extracting proof of delivery details from scanned dockets, summarising shipment exceptions for operators and customers, and drafting replies to delivery enquiries from live tracking data. People keep dispatch decisions, damage claims and anything touching driver work time. Carrier liability limits and claim deadlines are set by law, so AI must quote them from source.

- Proof of delivery extraction is a contained first project with a clear accuracy measure.
- Carrier liability at limited carrier's risk is capped at $2,000 per unit under the CCLA 2017.
- Damage claims against a contracting carrier need written notice within 30 days.
- Delivery enquiry replies must use live tracking events, never a predicted arrival from the model.

## Where AI earns its keep in New Zealand logistics

AI earns its keep in logistics on the documents and messages that surround each consignment: proof of delivery dockets, tracking exceptions, damage reports, freight invoices and the stream of customers asking where their goods are. Every operator already has this data. The work is reading it, matching it and explaining it, which is exactly what language models do well.

Most organisations are not yet using AI this way. Datacom's 2026 State of AI Index, a survey of 207 senior leaders at New Zealand organisations with 100 or more staff, run by Curia between 28 July and 3 August 2026, found general-purpose assistants such as ChatGPT, Gemini and Claude were the most common AI technology at 68%, while only 13% used agentic or autonomous AI ([Datacom, August 2026](https://datacom.com/nz/en/insights/press-release/2026-state-of-ai-Index-ai-uptake-at-91-leadership-lags)). For freight, that is no bad thing. Most gains come from well-bounded automations with approvals, not agents acting on their own; our lesson on [when a workflow does not need an agent](/learn/when-a-workflow-does-not-need-an-agent/) explains the difference.

## Freight and warehouse workflows

| Workflow | What AI does | What a person still decides | Data involved | Difficulty |
|---|---|---|---|---|
| [Proof of delivery extraction](/industries/logistics/proof-of-delivery-extraction/) | Reads scanned or photographed PODs into consignment records, flags notes and missing signatures | Disputed deliveries, claims | POD scans, consignment data | Low: fixed fields |
| [Shipment exception summaries](/industries/logistics/shipment-exception-summaries/) | Groups tracking exceptions and drafts plain summaries for operators and customers | Recovery actions, customer remedies | Tracking events, notes, SLAs | Medium: many event codes |
| [Customer delivery enquiry handling](/industries/logistics/customer-delivery-enquiry-handling/) | Answers status questions from live tracking with the event history | Redelivery, compensation, complaints | Tracking APIs, enquiry emails | Medium: live data required |
| Damage claim file assembly | Collects POD, photos, notes and dates into a claim file with deadlines | Liability position and settlement | PODs, photos, contracts | Medium: legal deadlines |
| Freight invoice reconciliation | Matches carrier invoices to bookings, flags surcharges and duplicates | Disputes and payment approval | Carrier invoices, booking records | Low: rules-based |
| Dangerous goods document checks | Checks declarations for missing fields against your checklist | Acceptance of the consignment | DG declarations, labels | High: safety-critical |
| Import paperwork pre-check | Compares commercial invoices and packing lists for gaps before the broker sees them | Tariff classification, entries | Invoices, packing lists | High: broker decides |
| Driver run sheet notes | Turns driver voice notes into delivery notes and exceptions | Follow-up with customers | Voice notes, run sheets | Low: internal use |

The detailed guides cover [proof of delivery extraction](/industries/logistics/proof-of-delivery-extraction/), [exception summaries](/industries/logistics/shipment-exception-summaries/) and [delivery enquiry handling](/industries/logistics/customer-delivery-enquiry-handling/).

## Carrier liability, driver hours and other rules AI must not misstate

Freight law is specific, and a model answering from general knowledge will often reach for overseas rules. Quote New Zealand sources and get legal advice on any contested claim.

- **Carrier liability.** Under s 259 of the [Contract and Commercial Law Act 2017](https://www.legislation.govt.nz/act/public/2017/5/en/latest/), a carrier's liability for contracts at limited carrier's risk is capped at $2,000 for each unit of goods lost or damaged, or the declared value for contracts at declared value risk. An AI reply that implies full replacement value creates expectations your terms do not support.
- **Claim deadlines.** Under s 274, no proceeding may be brought against a contracting carrier for damage or partial loss unless written notice with reasonable particulars is given within 30 days after the carrier's responsibility ends. Section 275 sets a 10-day notice period for a contracting carrier's claim against an actual carrier. Claim assembly tools should calculate and display these dates from the delivery record.
- **Driver work time.** Under s 30ZC of the [Land Transport Act 1998](https://www.legislation.govt.nz/act/public/1998/110/en/latest/), a driver may not exceed 13 hours of work time in a cumulative work day, must have at least 10 hours' continuous rest, and may not exceed 70 hours in a cumulative work period. Section 30ZD requires time and payment records to be kept for 12 months. AI can summarise these records; it should not approve extra hours.
- **Safety.** The [Health and Safety at Work Act 2015](https://www.legislation.govt.nz/act/public/2015/70/en/latest/) primary duty (s 36) covers fatigue, forklift traffic and loading. Tools that change how drivers or warehouse staff report hazards need worker engagement (s 60).
- **Privacy.** Consignee details, delivery photos and telematics are personal information. If data goes to an offshore AI provider that uses it for its own purposes, the Privacy Commissioner's guidance on [disclosure outside New Zealand](https://www.privacy.org.nz/privacy-principles/12/) applies.

## Tracking, WMS and accounting systems

New Zealand operators and shippers commonly use Starshipit or GoSweetSpot for shipping labels and tracking, CartonCloud or similar warehouse systems, Cin7 for inventory, Shopify for online orders, carrier tracking APIs from NZ Post and the major courier networks, and Xero for invoicing. AI work in logistics is mostly integration: reading events from these systems, writing structured results back, and keeping the customer conversation consistent with the tracking record. Before any build, decide which system is the source of truth for each status, because a carrier's API, your warehouse system and the online store can disagree for hours after a scan, and an assistant that reads the wrong one will confidently tell a customer the wrong thing. Our [Shopify](/integrations/shopify/) and [Cin7](/integrations/cin7/) guides cover the API side for shippers.

## A first project: proof of delivery extraction


- **Inputs**: Scanned and photographed POD dockets, driver app images, consignment records.
- **Systems**: Document store, transport management or tracking system, exception queue.
- **Steps**: Classify the image, extract consignment number, date, time, receiver name, signature present and any notes, then match to the consignment.
- **Human review**: Operators clear low-confidence extractions, missing signatures and any damage notes.
- **Outputs**: POD fields written to the consignment, damage notes raised as exceptions, a searchable POD index.
- **Measures**: Field accuracy on a labelled set of 300 dockets, share auto-matched, time to answer POD queries, claims lacking a POD.


Illustrative example: a regional carrier handles 8,000 consignments a month and receives 400 POD queries from customers (assumptions). At 7 minutes each to find and send the docket, that is about 47 hours. If extracted, indexed PODs cut that to 2 minutes, the work falls to about 13 hours, saving roughly 34 hours a month. Our [document processing service](/services/ai-document-processing/) covers this pattern, and the engineering note on [OCR versus vision models](/engineering/ocr-versus-vision-models/) explains the extraction choices.

## Where AI fails in freight


- **Smudged and handwritten dockets.** A creased POD produces a confident but wrong receiver name. Control: confidence thresholds and human review below them.
- **Timestamps and time zones.** Systems mix UTC, NZST and NZDT, so a delivery appears to happen before pickup. Control: normalise times in code, not in the model.
- **Liability misquoted.** A friendly reply promises a full refund for damaged goods. Control: replies about claims use approved wording and go to a person.
- **Invented arrival times.** A model "estimates" tomorrow morning with no tracking event to support it. Control: answers quote the latest event and the carrier's own estimate only.
- **Address change fraud.** Requests to redirect high-value freight arrive by email. Control: no automated address changes; verification by phone.


If customers will talk to the system directly, our [AI customer support service](/services/ai-customer-support/) sets up the hand-off to dispatch and the logs you need when a delivery is disputed.

## Questions people ask

### Can AI answer 'where is my order' enquiries for a freight company?

Yes, if it reads live tracking events from your systems or the carrier's API and reports what those events say. It should not predict arrival times on its own or promise redelivery slots it cannot book. Hand anything involving damage, loss or a complaint to a person, and log every answer so disputes can be checked against what the customer was told.

### How accurate is AI at reading proof of delivery dockets?

Printed fields such as consignment numbers, dates and addresses are usually read well. Handwritten names, signatures and notes like 'one carton damaged' are harder, especially on creased or photographed dockets. Measure accuracy on a few hundred of your own dockets before going live, and route anything below a confidence threshold to a person rather than guessing.

### Can AI manage driver hours or logbooks?

It can summarise records and flag possible breaches for a person to check, but it should not decide whether a driver can keep working. The Land Transport Act 1998 limits work time to 13 hours in a cumulative work day and 70 hours in a cumulative work period, with at least 10 hours' continuous rest. Fatigue decisions belong with trained supervisors.

### Should we let an AI agent rebook freight or change delivery addresses?

Not at first. Address changes are a common fraud route, and rebooking has cost and liability consequences. Start with AI drafting the change for an operator to approve, keep a full audit log, and only automate narrow, low-value cases once the error rate is known. Most freight workflows need a well-designed automation with approvals rather than an autonomous agent.

### Does the Privacy Act apply to delivery data?

Yes. Consignee names, addresses, phone numbers, delivery photos and driver location data are personal information. Know which AI tools process that data and where, avoid sending it to tools that retain or train on inputs, and take particular care with driver telematics, which can become constant monitoring. Check the Privacy Commissioner's guidance before sending data offshore.


## Sources

- [2026 State of AI Index: AI uptake at 91%, leadership lags](https://datacom.com/nz/en/insights/press-release/2026-state-of-ai-Index-ai-uptake-at-91-leadership-lags)
- [Contract and Commercial Law Act 2017 (version as at 1 October 2026)](https://www.legislation.govt.nz/act/public/2017/5/en/latest/)
- [Land Transport Act 1998 (version as at 4 September 2026)](https://www.legislation.govt.nz/act/public/1998/110/en/latest/)
- [Health and Safety at Work Act 2015](https://www.legislation.govt.nz/act/public/2015/70/en/latest/)
- [Principle 12: Disclosure outside New Zealand](https://www.privacy.org.nz/privacy-principles/12/)

Published by Levy Street (https://levystreet.com), Wellington, New Zealand.