Flowhub Maui Proof of Delivery with SuiteFleet

1. Start with the Flowhub Maui delivery order

Open the delivery order FH-01842 for Taylor Bennett and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains ACC-310 | Storage pouch | 1 EA and ACC-410 | Cleaning cloth | 2 EA.

Confirm Delivery is enabled for the store and identify the available dispatch workflow. Review the Ready order, driver, vehicle, delivery zone, and required release steps before dispatch.

Flowhub’s newer Dispatch board is a limited-availability feature. It distinguishes pending routes, en-route work, and route closeout; confirm the store’s release before applying those controls to the connector design. Flowhub delivery.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Match proof to the order and route stop. Separate recipient receipt, payment confirmation, return handling, and route completion in the audit trail.

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 stop FH-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).

If dispatch is incomplete or an order is not delivered, retain the route-stop identity and unresolved step. Do not create another order or replay already completed reporting actions.

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 the enabled Flowhub release and approved integration access. Select one system to own dispatch and required reporting so SuiteFleet updates do not duplicate native actions. Flowhub Dispatch board routes.

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 Flowhub Maui

Reconcile the stop outcome first, then complete the store’s payment and route closeout steps through the supported workflow. Keep returned goods and unsuccessful stops visible to the dispatcher. Flowhub delivery.

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.