Dutchie POS Proof of Delivery with SuiteFleet

1. Start with the Dutchie POS delivery order

Open the delivery order D-01842 for Alex Morgan and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains ACC-100 | Storage case | 1 EA and ACC-200 | Cleaning kit | 2 EA.

Confirm the order is a delivery order for the correct store, and complete the store’s release checks before assigning its driver and route. Keep the delivery allocation linked to the original POS order.

Dutchie separates delivery preparation, route start, skipped deliveries, and checkout. Guestlist statuses can be configured, so map the store’s actual events rather than assuming one universal status list. Dutchie delivery setup.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Use the permitted recipient and evidence workflow for the store. Keep handover evidence separate from payment confirmation and store-controlled identity checks.

3. Define and check the evidence requirements

Agree the evidence policy before dispatch: which shipments need a recipient name, photographs, signature, and completion information, and who reviews missing evidence. Only require capture methods verified in the deployed driver workflow. Confirm that the connector can retrieve each required evidence field.

Before opening proof, match the task to Delivery allocation D-01842-1 through the correlation record. Names, addresses, and order display numbers alone are insufficient when the customer receives repeat or split shipments.

Distinguish the expected consignee from the person who actually accepted the goods. Validate file access and retention requirements with the deployment owner so a saved link remains useful to the intended support team.

4. Review proof of customer handover

Open Proof from the task or Reports → POD Analysis → Full proof. Review delivery photos, signature, recipient, and recorded completion together. Review Proof of pickup and Proof of delivery separately. Confirm customer receipt from the delivery record.

Do not infer received item quantities from a photograph, a signature, or the package count. Store the event time with its time zone. This example uses America/Chicago (CDT).

A skipped stop must preserve its reason and route relationship. Do not close the order or create a second sale merely because the driver needs another delivery attempt.

If there is a shortage, refusal, or disputed recipient, preserve the original evidence and record the exception. Retain the source shipment and line keys during review; do not create a new shipment simply because proof needs correction.

5. Store controlled evidence references

Confirm access to Dutchie’s approved integration interfaces, order identifiers, delivery events, and evidence destinations. Existing third-party integrations do not establish SuiteFleet field access. Dutchie order processing.

Write recipient, event time, outcome, and evidence references only to validated destinations. Check whether the interface stores a file, an attachment relationship, or an external URL. Apply access controls to the evidence location; a link in a transaction does not itself grant appropriate access.

Handle status and attachment updates independently. If the status sync succeeds but a photo reference fails, retain the partial integration error and retry that operation safely. Verify the target record after retry before reporting a clean sync.

6. Verify the result in Dutchie POS

Return the delivery outcome to the linked order record and complete checkout through the authorized POS workflow. A delivery event must not tender payment or close the sale without the configured checks. Dutchie delivery setup.

Read back the linked record and review every outstanding allocation before reporting the full delivery requirement complete. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.