Proof of Delivery
Extract delivery confirmation data including recipient details, signature verification, timestamps, and delivery conditions.
Overview
The Proof of Delivery document type extracts structured data from delivery confirmation documents. These documents serve as legal evidence that goods were received by the intended recipient, capturing essential details like delivery time, recipient information, and cargo condition at the time of handover.
This is ideal for:
- Last-mile delivery verification
- Customer dispute resolution
- Delivery performance analytics
- Supply chain compliance documentation
- Carrier accountability tracking
Extracted Fields
| Field | Type | Description |
|-------|------|-------------|
| deliveryNumber | string | Unique delivery reference number |
| deliveryDate | string | Date of delivery (ISO 8601) |
| deliveryTime | string | Time of delivery (HH:MM format) |
| recipient | object | Receiving party information |
| signature | object | Signature verification details |
| items | array | Delivered items with quantities |
| condition | string | Overall condition of delivery |
| notes | string | Additional delivery notes |
Example Request
/v1/documents/processcurl -X POST 'https://api.docurift.com/v1/documents/process' \
-H 'X-API-Key: your_api_key' \
-F 'file=@proof-of-delivery.pdf' \
-F 'documentType=proof_of_delivery'
Example Response
{
"success": true,
"data": {
"id": "doc_pod_7e9f1a3b5c7d9e2f",
"documentType": "proof_of_delivery",
"result": {
"deliveryNumber": "DEL-2024-847291",
"deliveryDate": "2024-11-18",
"deliveryTime": "14:32",
"orderReference": "ORD-2024-00582",
"carrier": {
"name": "FastFreight Logistics",
"driverName": "Michael Torres",
"driverId": "DRV-8847",
"vehicleId": "FF-2847-CA",
"trackingNumber": "FF847291847"
},
"recipient": {
"name": "James Mitchell",
"company": "Mitchell Hardware Supplies",
"address": "4521 Industrial Parkway",
"city": "Austin",
"state": "TX",
"postalCode": "78744",
"country": "USA",
"phone": "+1 (512) 555-0847",
"email": "receiving@mitchellhardware.com"
},
"signature": {
"signedBy": "James Mitchell",
"signaturePresent": true,
"signatureType": "electronic",
"timestamp": "2024-11-18T14:32:47Z",
"ipAddress": "192.168.1.45",
"deviceId": "SCANNER-FF-2847"
},
"items": [
{
"lineNumber": 1,
"sku": "HW-DRL-4500",
"description": "Industrial Power Drill - 4500W",
"quantityOrdered": 24,
"quantityDelivered": 24,
"quantityDamaged": 0,
"unit": "units"
},
{
"lineNumber": 2,
"sku": "HW-BIT-SET-100",
"description": "Professional Drill Bit Set (100pc)",
"quantityOrdered": 48,
"quantityDelivered": 48,
"quantityDamaged": 0,
"unit": "sets"
},
{
"lineNumber": 3,
"sku": "HW-SAF-GLV-L",
"description": "Safety Work Gloves - Large",
"quantityOrdered": 120,
"quantityDelivered": 120,
"quantityDamaged": 2,
"unit": "pairs"
}
],
"condition": "Good",
"conditionDetails": {
"packagingIntact": true,
"temperatureCompliant": true,
"damageReported": true,
"damageDescription": "2 pairs of gloves had minor packaging damage, product intact"
},
"notes": "Delivered to loading dock B. Recipient inspected all cartons. Minor packaging damage on box #47 noted by recipient.",
"attemptNumber": 1,
"deliveryLocation": {
"latitude": 30.2134,
"longitude": -97.7562,
"accuracy": "GPS"
}
},
"confidence": 0.96,
"processingTimeMs": 1650
}
}
Field Definitions
deliveryNumber
The unique identifier for this delivery, assigned by the carrier or shipping system.
deliveryDate
The calendar date when delivery occurred, formatted as an ISO 8601 date string (YYYY-MM-DD).
deliveryTime
The local time when delivery was completed, in 24-hour format (HH:MM).
recipient
An object containing the receiving party's information:
| Property | Type | Description |
|----------|------|-------------|
| name | string | Name of the person who received the delivery |
| company | string | Company name (if applicable) |
| address | string | Delivery address |
| city | string | City |
| state | string | State or province |
| postalCode | string | ZIP or postal code |
| country | string | Country |
| phone | string | Contact phone number |
| email | string | Contact email address |
signature
An object containing signature verification details:
| Property | Type | Description |
|----------|------|-------------|
| signedBy | string | Name of the person who signed |
| signaturePresent | boolean | Whether a signature was captured |
| signatureType | string | Type of signature (wet, electronic, digital) |
| timestamp | string | ISO 8601 timestamp of signature |
| ipAddress | string | IP address if electronic signature |
| deviceId | string | Signing device identifier |
items
An array of delivered items. Each item includes:
| Property | Type | Description |
|----------|------|-------------|
| lineNumber | number | Sequential line number |
| sku | string | Product SKU or code |
| description | string | Item description |
| quantityOrdered | number | Original order quantity |
| quantityDelivered | number | Quantity actually delivered |
| quantityDamaged | number | Quantity with damage |
| unit | string | Unit of measure |
condition
The overall condition assessment of the delivery. Common values:
Excellent- Perfect condition, no issuesGood- Minor issues, fully acceptableFair- Some damage or discrepancies notedPoor- Significant issues requiring actionRejected- Delivery refused by recipient
notes
Free-form text containing any additional observations, instructions, or comments made during the delivery process.
Best Practices
-
Signature Verification: For high-value deliveries, verify the
signaturePresentfield istrueand thesignedByname matches expected recipients. -
Quantity Reconciliation: Compare
quantityOrderedvsquantityDeliveredfor each item to identify shorts or overs. -
Damage Documentation: When
quantityDamagedis greater than zero, ensure proper damage claims processes are initiated. -
Timestamp Validation: Use the delivery timestamp for SLA compliance checking and delivery performance metrics.
-
Geolocation Verification: If
deliveryLocationis provided, validate it against the expected delivery address. -
Photo Evidence: Many modern PODs include photo attachments. While DocuRift extracts text and structured data, photos are preserved in the original document.
-
Attempt Tracking: The
attemptNumberfield helps identify re-delivery scenarios which may indicate address or recipient availability issues. -
Condition Codes: Standardize your condition assessment criteria to ensure consistent extraction and reporting across different carriers.
-
Electronic vs. Wet Signatures: Electronic signatures (digital capture pads) may include additional metadata like timestamps and device IDs that add evidentiary value.
-
Driver Notes: Pay attention to the
notesfield which often contains critical delivery context that may not fit into structured fields.