Sana Commerce Proof of Delivery with SuiteFleet

1. Start with the Sana Commerce webstore order

Open the webstore order WEB-01842 for Cedar Building Products and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains BLD-100 | Door hardware kit | 4 EA and BLD-200 | Cabinet hinge | 6 EA.

Open the webstore order and identify the corresponding ERP sales document. Confirm ERP release, shipment quantities, and shipping destination before exporting the delivery allocation.

Sana displays order and shipment information from the connected ERP. Shipment creation remains an ERP responsibility; avoid creating a second operational order merely to populate the webstore. Sana sales documents.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Attach evidence to the originating ERP shipment and expose only authorized customer-facing references. Verify that the recipient can access the intended evidence without exposing another order.

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 ERP shipment SHP-01842 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).

An order may have several ERP shipments. Expose each tracking reference and remaining quantity accurately instead of presenting the first delivered shipment as the full order.

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 connected ERP, supported document types, shipping-method mapping, and tracking URL configuration. Sana’s displayed shipment fields depend on that ERP connection. Sana shipment details.

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 Sana Commerce

Return tracking and delivery evidence through the supported ERP integration, then verify the customer’s shipment view. Keep the ERP shipment number and tracking reference consistent across both views. Sana sales documents.

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.