Order requirements

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

Requirement	Description
`photo_proof_of_delivery`	Require a picture of the order after drop off
`signature_proof_of_delivery`	Require the customer’s signature after drop off
`photo_proof_of_pickup`	Require a picture of the order after picking it up
`signature_proof_of_pickup`	Require the customer’s signature after picking up the order
`age_verification_on_delivery`	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: 18
`alcohol`	Lets the provider know there’s alcohol in the order 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: 18
`id_verification_on_delivery`	Requires driver to verify the recipient’s ID when dropping off the order (for pharmaceutical delivery)
`barcode_scan_on_pickup`	Requires driver to scan a barcode on pickup. Barcode values are provided in `pickupBarcodes`
`barcode_scan_on_dropoff`	Requires driver to scan a barcode on dropoff. Barcode values are provided in `dropoffBarcodes`
`barcode_scan_on_return`	Requires driver to scan a barcode when returning an order
`display_barcode_on_pickup`	Requires driver to display a barcode at pickup (for example, for store staff to scan). Barcode values are provided in `pickupBarcodes`
`meet_on_delivery`	Instructs driver to meet customer on delivery and hand off order. Note: Supported by select providers only, and best effort rather than guaranteed.
`shipping_label`	Requires 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 order depending on the provider.
`two_person_team`	Requires a two-person team to assist in the delivery
`pincode_verification`	Requires 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"}]`
`parking_check_in`	Requires courier to check in upon arrival while waiting in their vehicle. The courier will provide the parking location information. Note: The parking location can be found in the `delivery.courier_vehicle.parking_location` field.
`schedule_ii_controlled_substances`	Require the order to be handled by a provider that is certified to handle Schedule II Controlled Substances (US)
`tobacco`	Lets the provider know there’s tobacco in the order 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: 18
`vapes`	Lets the provider know there are vape products in the order
`pick_and_pack`	Enables item-level fulfillment with store picking before delivery. See Pick and Pack.
`custom:{requirement_name}`	Custom requirement that will filter any provider/contract without this specific requirement. The requirement must be added to the wanted contract before being used. Example: “custom:refrigerated” will only match providers that explicitly support refrigerated transport.

Notes

Multiple requirements are allowed. Example: requirements: ["photo_proof_of_delivery", "signature_proof_of_delivery"]Not all providers support all requirements. Providers that don’t support provided order/package requirements will be ineligible and will show in the failedQuotes section. A quote rejected for that reason carries a machine-readable errorCode and an errorDetails object naming the requirements the provider wouldn’t take, so you can branch on the cause instead of reading the message. When every eligible provider rejects a package on its requirements, the delivery carries a quoteFailure summary and a normalized failureCode, and dispatching it returns a 422 rather than a generic failure.

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

Getting started

Order

Dispatch strategies

Notifications

Store locations & zones

Jobs

Batch jobs

Providers

Routes

Optimization strategies

Shifts

Templates

Store catalog

Feedback

Shipping

Simulate delivery

Fleet

Miscellaneous

Order requirements

Notes

​Notes

Notes