Set up proof of delivery

You can configure and manage settings for handling delivery events on the Proof of Delivery Setup page. Additionally, you can customize the proof of delivery process to meet specific operational needs, ensuring seamless integration and functionality.

To set up the proof of delivery, follow these steps:

1. Select the Search icon , enter Proof of Delivery Setup, and then choose the related link.
   The Proof of Delivery Setup page opens.

2. On the General FastTab, enter the required information in the following fields:

   Field	Description
   Enabled	Turn on the toggle to process inbound events for proof of delivery (POD) and include POD details in outbound events.
   Create Manifests in POD	Turn on the toggle to allow creating or modifying transport orders in Business Central. Turn it off if an external software manages the manifest and prevents changes to transport orders.
   Client Number	Enter the number associated with the client to track the delivery.
   Post Invoice Upon Driver Completion	Turn on the toggle to automatically post the invoice related to an event when the driver completes the delivery.
   Print POD upon Driver Completion	Turn on the toggle to automatically print a proof of delivery when the driver completes the delivery.
   Acid	Enter the unique Acknowledgement Confirmation ID (ACID) used to track the proof of delivery for this transport order.
   Scan Code Source	Select which item field the system uses to match scanned codes during proof of delivery. The available options are: Item Reference (Barcode) Item Identifier Item GTN Item Number This field value is set to Item Reference (Barcode) by default.
   Email Recipient for Errors	Enter the email address that should receive notifications when an error occurs during the processing of POD results.

3. On the Rejections FastTab, enter the required information in the following fields:

   Field	Description
   Default Exception Code	Select the code that the system must automatically assign when a specific delivery was not completed as expected due to missing or damaged products. This code is used for rejected units received from the proof of delivery in an inbound event.
   Move Items on Undo	Turn on the toggle to automatically move items from the shipping bin back to their original bin when they are rejected and returned as part of a POD inbound event. This process is executed through an automatic put-away using a reclassification journal.
   Journal Template Name	Select the journal template that the system uses to create a reclassification journal when items are rejected and returned as part of a POD inbound event.
   Journal Batch Name	Select the journal batch within the selected journal template that the system uses to post the reclassification journal for rejected items that are confirmed to be re-shipped.

4. On the Over Delivery FastTab, enter the required information in the following fields:

   Field	Description
   Over Delivery Reason Code	Select the reason code to use when over-deliver items during Proof of Delivery. This applies only to items that are not lot-tracked and the Overdelivery Allowed toggle on the Shipping FastTab of the associated Customer Card page is turned on. This value is inherited in the Over & Underdelivery Reason Code field of the related sales order line. If you leave this field blank, the system does not record a reason code.
   Over Delivery Default Exception Code	Select the default exception reason code used for over-delivery during Proof of Delivery. This applies only to items that are not lot-tracked. This value is inherited in the Delivery Exception Code field on the Proof of Delivery Drop Detail Card page indicating over delivery is applicable for the associated record. If you leave this field blank, the system does not assign a default exception code and over-delivery cannot be processed automatically.

   
   This FastTab is visible only when the Aptean Over Under Delivery extension is installed.

5. On the Blob Storage FastTab, enter the required information in the following fields:

   Field	Description
   Use Blob Storage	Turn on the toggle to use Azure Blob Storage for storing and managing documents related to deliveries.
   Access Key	Enter the secret key for Azure authentication.
   Blob Storage Account Name	Enter the name of the Azure Blob Storage account used to access the storage for proof of delivery files.
   Blob Storage Container Name	Enter the name of the container within the Azure Blob Storage account where files, such as photos and signatures, are uploaded and stored from the POD result event.

6. On the action bar, select Actions > Configure with AIP to load data into AIP and create consumer events for Proof of Delivery (POD) and Routing and Scheduling (RAS).

   The Proof of Delivery Setup page is configured.

Automated put-away for rejected items

When items are rejected and returned as a part of Proof of Delivery (POD) inbound event, the inventory should be restored to its original bins without errors. This feature automates the creation of put-away during the undo shipment process in sales orders as manual put-away is time consuming. This moves the items from the shipping bin to the original bin by using the reclassification journal with the configurations on the Rejections FastTab. The system moves only the items that are confirmed to be re-shipped and do not handle the other rejected items.

Deletion of sales order based on rejected items

The system automatically deletes a sales order line when it is fully rejected during the Proof of Delivery (POD) process, based on the Default Exception Code field value defined on the Proof of Delivery Setup page. If the rejection action for the code is Redo the Shipment and Cut the Order, the system removes the line. However, if the sales order has only one line, the line is removed but the order remains in the Open status.