Shipment, Delivery Evidence and Exception Tracking
I can develop a custom web application connecting your logistics team’s shipment records, carrier updates, delivery documents and customer questions. I define the scope around your own-fleet or external-carrier operating model and existing systems. This page describes proposed development services, rather than an available product, a live operational screen or a completed customer result.
A delivered status does not necessarily mean the required delivery evidence is complete. Carrier updates, document reviews and customer confirmation come from different sources. I connect these records while keeping their states separate. The manager can see why a shipment remains open and who owns the next action.
Where information gets lost in shipment tracking
The operations list may be in Excel, carrier updates in a downloaded file and delivery photos in messages. When a customer asks for an update, staff must first establish which source is current. A single order split across several shipments can be misrepresented by one summary row.
I first map the relationship between orders, consignments, loading events and packages. One customer order may create several shipments, while one vehicle may carry goods for different customers. Record identity must reflect those relationships. Updates show their source and retrieval time. Preventing stale data from appearing current is an earlier priority than adding a tracking map.
Example workflow: delivery reported, evidence missing
The following scenario is illustrative. An external carrier marks a shipment delivered, but the document required by the customer’s service conditions has not arrived. The application can show these as two separate states.
| Event | Record | Owner | Result and control |
|---|---|---|---|
| Shipment created | Order, consignment and delivery locations | Operations | Identifiers and required fields checked |
| Handed to carrier | Carrier reference and handover details | Operations | Linked to the matching shipment |
| Delivery reported | Source status and event time | Interface or user | Original source retained |
| Evidence found missing | Document request and owner | Documentation team | Record remains open |
| Evidence reviewed | Delivery document and assessment | Authorised reviewer | Returned if incomplete |
| Record closed | Closure conditions satisfied | Authorised operations owner | Customer confirmation awaited if required |
Reading a document does not establish an undisputed delivery. An unclear signature, recipient name or package discrepancy requires review. Corrected carrier updates retain the earlier event. Cancellation, return and partial delivery remain separate movements rather than unexplained overwrites of the delivered status.
What a logistics customer CRM should answer
The CRM tracks service conditions, delivery requirements, shipment-related questions and the responses provided, alongside customer contacts. The customer’s warehouse contact may differ from its commercial representative. Delivery-location information should not expand into unnecessary personal data about recipients.
When someone asks where the evidence is, the representative should see the missing document and its owner. A complaint links to the consignment, event and next action instead of remaining an isolated note. A carrier investigation and its response follow the same record. Commercial prices and carrier agreements remain restricted to authorised roles. The CRM does not invent a firm delivery commitment from incomplete customer history.
Shipment identity, status and event history
Internal shipment ID, customer order reference, carrier tracking number and package identifier are distinct fields. Matching rules account for a carrier reusing references over time where relevant. Free-text identifier formats are checked before import.
Each status event retains its actual event time and the time it reached the application. A delayed old update must not roll back a newer status. Status mappings preserve the carrier’s original wording rather than interpreting out for delivery as delivered. Manual events identify the user who entered them. Corrections, reopened records and returned documents require reasons. Customer-visible states are explicitly defined rather than exposing every internal update.
Screens and practical functions that can be developed
| Screen | Work presented | Important control |
|---|---|---|
| Shipment creation | Consignment and delivery points | Order versus shipment identity |
| Operations board | Open and waiting shipments | Source and freshness |
| Carrier handover | Reference and collection details | Authorised carrier matching |
| Delivery document inbox | Uploads and evidence review | Correct consignment relationship |
| Exception queue | Delays, missing information and damage reports | Owner and next action |
| Customer CRM record | Service conditions and open questions | Authorised contact |
| Customer view | Explicitly shared status and documents | Customer-level data separation |
| File import review | Source rows and discrepancies | Duplicates and totals |
| Notification history | Event, channel and delivery result | Duplicate-event protection |
| Management report | Pending work and closure reasons | Source-level drill-down |
The first release need not include every function. Shipment records, delivery evidence and exceptions may form the initial scope. A driver or warehouse phone interface requires testing uploads, connectivity and actual devices. Offline capability and location collection are not assumed features; their necessity and permissions are reviewed separately.
Roles, customers and external carrier access
| Role | Access | Permitted action | Boundary |
|---|---|---|---|
| Logistics manager | Authorised operations records | Assignment, review and closure | No undefined financial authority |
| Operations team | Assigned shipments | Creation, handover and exception entry | Customer boundaries apply |
| Documentation owner | Relevant delivery evidence | Review and missing evidence requests | No independent commercial acceptance |
| Customer representative | Authorised customer records | Questions and replies | Other customers’ commercial information restricted |
| Driver or warehouse user | Assigned load and necessary address | Defined events and evidence entry | No unrestricted shipment list |
| External carrier | Explicitly shared work | Status and evidence submission | Other carriers’ prices restricted |
| Customer | Own shared records | Viewing status and raising missing information | Internal operations notes restricted |
The server enforces record and file permissions. A customer must not access another customer’s evidence by guessing its address. Simultaneous edits produce a visible conflict rather than a silent overwrite. Accounts of departing employees are disabled and open tasks reassigned while activity history remains. Signatures, phone numbers and addresses in delivery evidence have defined access and retention boundaries.
Controlled imports from Excel and carrier files
The initial transfer starts from a copy of the source file, a field map and a named data owner. Consignment, package, weight and status fields need clear meanings. Decimal separators or changing weight units must not create incorrect totals. Leading zeros in carrier references are preserved when meaningful.
A repeated identifier does not automatically create another shipment. Identical rows, changed statuses and new records are treated separately. A genuine additional shipment for the same order must not be deleted as a duplicate. Source row counts, accepted and rejected records, package counts and weights by unit are reconciled. Any financial balance transfer requires a separate opening and closing reconciliation. Unmatched records enter review and block the affected critical closure. The source, mapping rule and reversal history remain available.
How AI can assist with documents and customer replies
AI can draft extracted fields from delivery evidence, summarise long carrier explanations or suggest a response grounded in authorised service documents. Suggestions link to the relevant source and record. An unreadable signature or missing page is flagged rather than filled with invented information.
AI does not decide delivery certainty, damage liability or customer compensation. Defined rules handle package, weight and financial calculations. Reply suggestions must identify stale information and cannot invent arrival times from unavailable location data. Personal information in documents is limited before any approved external processing. Where sharing a sensitive document is inappropriate, the corresponding AI function stays disabled. An unreviewed suggestion does not become a customer commitment.
WhatsApp and SMS triggers
Checked 30 October 2026: the WhatsApp Business messaging policy requires approved templates outside the 24-hour window following the customer’s last message. Consent and opt-out rules also apply.
| Event | Recipient | Condition before sending |
|---|---|---|
| Delivery address incomplete | Authorised customer contact | Operations confirms the missing field |
| Carrier handover received | Authorised customer contact | Shareable state confirmed |
| Delivery attempt unsuccessful | Operations and, if appropriate, customer | Source event checked |
| Delivery evidence outstanding | Relevant carrier contact | Documentation owner approves request |
| Evidence discrepancy found | Assigned operations owner | Reason recorded |
| Customer question unanswered | Relevant customer representative | Defined follow-up condition met |
WhatsApp connections use the official business API, subject to permission and template requirements. SMS uses an authorised provider and applicable consent, opt-out and Turkish IYS controls. Ongoing shipment notifications and promotional campaigns are separate workflows. The official WhatsApp documentation and IYS guidance are checked before implementation.
Event and recipient identifiers prevent duplicate messages. Retry behaviour checks the earlier sending result. Provider acceptance, recipient delivery and failure are separate states. An opt-out stops the relevant marketing workflow. Having a phone number does not establish permission for every type of communication. A notification failure must not make the underlying operations task disappear.
The actual limits of carrier, GPS and ERP connections
CSV exchange can be the starting point. A carrier or ERP API requires review of the documented interface, licence and access permissions. Different carriers do not necessarily provide equivalent status information. Without an API, an authorised file transfer or controlled manual record may be appropriate.
GPS positions are available only if data ownership, device sources and technical access are verified. Entering a vehicle registration does not grant live location access. Sharing and retention rules must be defined. Read access does not authorise creating transport orders or writing financial entries into an ERP. Write connections require separate approval, field ownership and retry controls. Replacing every TMS, WMS, ERP or accounting tool is not the initial promise.
Management reports, estimates and exception queues
The manager can separately review deliveries awaiting evidence, unassigned exceptions and customer questions awaiting replies. Every report line links to a source event or document. The filtering time field is explicit so historical events entered today are not misinterpreted.
An arrival estimate shows its source, generation time and uncertainty rather than becoming a guaranteed delivery promise. An absent carrier update does not prove that nothing moved. Connection failures, suspected duplicates and unreadable evidence enter separate queues. Incorrect shipment identity or missing mandatory documents block the affected closure. The emphasis is the operational reason and next action rather than automatic employee punishment.
First scope, training and operational handover
Initial paid scoping reviews the current path of an ordinary shipment, missing evidence and a return. I document roles, required fields, external connections and exclusions. We then assess the screens with sample data and plan limited operational use and data transfer.
Operations, documentation and customer-service training follows each team’s daily tasks. External carrier accounts need a named sharing owner. Delivery defines the support channel, issue priorities, backup owner, restore test and retention periods. New feature development and ongoing operational support are treated separately. Timing and cost are agreed after the actual requirements are understood.
Acceptance scenarios to test
- Reimporting the same carrier file does not duplicate shipments.
- A genuine split shipment is not removed as a duplicate.
- An older event cannot roll back a newer status.
- A delivered update does not automatically complete missing evidence.
- A customer cannot open another customer’s document link.
- Reprocessing an event does not send another external message.
- A carrier outage shows the failure and last update time.
- Restoring a backup preserves document, event and permission relationships.
Expected outcomes and test data are written first. Incorrect identifiers, missing evidence and denied access are as relevant as the ordinary flow. Corrections and retest outcomes are recorded before the affected step is accepted.
When standard software may be sufficient
If the existing TMS or WMS supports the workflow, adjusting its configuration and team usage may be preferable. A small list maintained by one person may remain suitable for a controlled spreadsheet. Custom development is considered for the evidence, responsibility and customer-sharing gaps specific to your operation.
This scope does not include collecting carrier data without permission, displaying inaccessible GPS information or making definitive delivery decisions from incomplete evidence. Screens cannot establish reliable operations without a data owner and closure authority. We agree shared definitions and responsibilities before turning them into software rules.
Frequently Asked Questions
Can every carrier be connected automatically?
No. Each carrier’s interface, permissions and available fields require verification. A controlled file exchange or manual record can be the starting point.
Can a vehicle registration provide live location?
Not by itself. You need a device or data provider, access rights and a technical interface. Personal data and sharing boundaries require separate assessment.
Does a delivered update close the record?
That depends on the defined closure conditions. If evidence or customer confirmation is required, the carrier’s status alone is insufficient.
Does AI definitively validate delivery evidence?
It can suggest extracted fields and missing information. Signature validity, responsibility and final delivery assessment remain with authorised human reviewers.
Can we upload the same Excel file again?
Yes. Matching rules distinguish repeated shipments, status updates and genuine additional shipments. Discrepancies remain visible in the import report.
Does every status change trigger a customer SMS?
Shareable events, recipients, permissions and message types are explicitly defined. Duplicate-event controls prevent repeat messages. Internal changes do not all need external notifications.
Request a scope for your shipment workflow
Describe whether you operate your own fleet or use external carriers, which delivery evidence you need and how you maintain the current list. You do not need to send real recipient phone numbers, signatures or transport documents in your first message. An anonymised field list and one example of a recurring problem are enough. Initial scoping is paid work, leading to defined screens and acceptance conditions.
For the shared record structure, explore custom web applications for teams.
Contact relationships and follow-up are explained in CRM setup.
