When creating a job, Nash allows specifying different requirements to suit your package delivery. Available options are:

RequirementDescription
photo_proof_of_deliveryRequire a picture of package after drop off
signature_proof_of_deliveryRequire the customer’s signature after drop off
photo_proof_of_pickupRequire a picture of package after picking it up
signature_proof_of_pickupRequire the customer’s signature after picking the package up from
age_verification_on_deliveryRequires driver to verify recipient’s age from a government-issued ID.

minimum_age depends on country:
US: 21
AU: 18
NZ: 18
GB: 18
CA: 19
alcoholLet’s the provider know there’s alcohol in package and requires driver to verify recipient’s age from a government-issued ID.

minimum_age depends on country:
US: 21
AU: 18
NZ: 18
GB: 18
CA: 21
id_verification_on_deliveryRequires driver to the verify recipient’s ID when dropping off the package (for pharmaceutical delivery)
barcode_scan_on_pickupRequires driver to scan a barcode on pickup.
barcode values are provided in “pickup_barcodes”
barcode_scan_on_dropoffRequires driver to scan a barcode on dropoff
barcode values are provided in “dropoff_barcodes”
meet_on_deliveryInstructs driver to meet customer on delivery and hand off package.
Note: This’s applicable for Doordash and Uber deliveries only and is best effort and not always guaranteed.
shipping_labelRequires driver to check or scan the shipping label at the pickup and drop-off location.

Note: The shipping label sometimes should be printed and stamped to the package depending on the provider.
two_person_teamRequires a two-person team to assist in the delivery
pincode_verificationRequires a pincode entry at dropoff. The pincode will be shared with the dropoff customer through SMS.

Note: The pincode will also be added to the proofOfDelivery object and will trigger a webhook event of type delivery.pincode_verification.
example:
"proofOfDelivery": [{"type": "pincode_verification","pincode": "1578"}]
schedule_ii_controlled_substancesRequire the package to be handled by a provider that certified to handle Schedule II Controlled Substances (US)

Notes

Multiple package requirements are allowed. Example: packageRequirements: ["photo_proof_of_delivery", "signature_proof_of_delivery"]

Not all providers support all requirements. Providers that don’t support provided package requirements will be ineligible and will show in the failedQuotes section.

By default, packageRequirements: ["photo_proof_of_delivery"] packageRequirements=[] means no requirements are expected.