Deliver Control Files

All signatures taken through Deliver will be stored in this profile by default. However, you have the option of using a different profile as this is the default profile for Signature Touch Counter Mode and Will-Call Mode. If you want delivery signatures to be stored in the same profile as counter signatures, no other action is needed. If you want delivery signatures stored in a different profile than counter signatures, make sure control file "Innovo Deliver Manifest Signature Profile" is set before taking a signature in Deliver.

*Applies to Counter & Will Call Modes as well

This is a branch-specific control file (based on the manifest branch) and will update the print status of all orders on a manifest when the manifest is closed in Eclipse. 

Enter the Print Status you would like the orders to switch to when the manifest is closed.

*Applies to Deliver Only

Delivery Notifications respect Activity Trigger Inheritance, if enabled on your system. For more information on inheritance, click here.

Delivery Notifications respect the Corporate Customer control file. Even if you don't enable activity trigger inheritance, you can still set up this control file and enable that customer for notifications in Deliver Web -> Notifications. For more information, click here.                                          

By Default, when adding the receiving generation of a transfer to a route, the receiving branch address will display. In an effort to better support transfer pick-ups, enabling this control file will force Route and Deliver to display the shipping branch address.                             

We recommend using a different profile than what you are using for signatures; however, you can use the same one. If you plan on taking pictures during the delivery route, this must be set. If not set, you will see an error message when trying to complete the manifest on the device when pictures have been taken.

When a stop is completed, the change log is always updated with details of who signed the order, where it was signed, and what time it was signed. Enabling this branch-specific control file will also add this information to the shipping instructions when a stop is completed in Deliver. If we are not 100% sure Google returned a good address, the signed at will say (Approx.). If a new order generation is created from a prior generation that has already been delivered, the prior gen's signed at location will be copied to the new gen, as that cannot be prevented. However, we will overwrite any existing delivery information once the new generation has been delivered. 

Enabling this control file will include the first 10 photos taken at the stop in the Delivered email notification. By default, they are not included. We use the ship branch of the order to determine if the photos should be included.

Enabling this control file will include the first 10 photos taken at the stop in the Delivered SMS notification. By default, they are not included. We use the ship branch of the order to determine if the photos should be included.  

Enabling this control file will attach a copy of the ship ticket to all email notifications. By default, it will not be included. We use the ship branch of the order to determine if the ship ticket should be included.

Please note: If your site is enabled for Eclipse forms, the INNOVO user must also be enabled for Eclipse forms. Otherwise, the ship ticket attachment will look like a non-Eclipse forms ship ticket.

Enabling this control file prevents the expected times on the Eclipse manifest from being updated. This was done in case you update estimated delivery times from the Eclipse sales order status screen.

Please note: you will still be able to see expected times from in Deliver and actual delivery times will still be updated on the manifest in Eclipse.

If you are using a template for delivered notifications that includes product images but don't actually use product images in Eclipse, you can remove those placeholders by enabling this control file.

Deliver by default displays only those manifests with a date of today or tomorrow (also respecting the "Innovo Deliver Show Manifest Types" control file - open/locked/closed). This control file will allow you to ignore the manifest date and show all manifests when set to Y.

If you want delivery signatures stored in a different profile than counter signatures, enter that profile in this control file before taking a signature in Deliver.

By default, email notifications from Deliver use your standard "from" email address that other documents emailed out of Eclipse use. If you would like to make your notifications more specific, set the from email address here. We use the price branch of the order to determine the from email address. You can also use the email address of the order writer by enabling the next control file.

You can set up pre-and-post delivery notifications for individual customers which will always override this global setting. If you want to set up notifications that apply to all of your customers, set the global customer here and then on the Customer Portal -> Deliver -> Notifications page, load this customer under customer setup. Once the customer is loaded, use the email overrides to determine what email address will be used to send the notification for each order.

When this branch-specific control file is enabled, the from email address of the delivery notification comes from the order writer. This control file overrides Innovo Deliver Notification From Email Address. We use the price branch of the order to determine if this control file is enabled.

When this branch-specific control file is enabled, the driver will be required to take at least one photo for each stop. This can be overridden at the customer level as well.

Note: If there are multiple orders on the stop, any photos taken at the stop level will be added to each order. The driver also has the option of taking photos at the order level.

By default, COGS is used in all profit calculations displayed on the Deliver Web's Summary page. If you would like to use COMM-COST instead, update the setting here. When blank, COGS is used.

If you want to set up local phone numbers from your Twilio account to use by branch or territory, enter the Twilio number in this control file.

When enabled, either the inside salesperson, outside salesperson, or order writer will be sent an Eclipse message when a stop is completed during the delivery route.  The message will include the sales order and ship-to customer index.

This control file controls which manifests display in the Deliver app based on the manifest status (open/closed/locked). By default, if none of these are set then all manifests (open, closed, and locked) will appear in the app.

When enabled, this branch-specific control file (based on the manifest branch) will only send a job queue when a manifest is completed on the device if there are discrepancies during the route. A discrepancy is defined as a line item comment, order comment, internal note, skipped stop, or refused order.

You now have the ability to send a job queue real-time when a discrepancy happens at the stop level. In previous versions, a job queue would only be sent real-time when either a stop was skipped or an order refused. As of Deliver 1.1.0, a job queue will be sent real-time to any user(s) specified in this control file when the following happens:

• Skipped stop
• Refused order
• Line item comment added
• Order comment added
• Internal notes added

If multiple discrepancies happen at a stop, a single job queue will be sent to all specified users noting all discrepancies. In addition to sending the job queue to any user and/or message group, you can also send the job queue to the writer of the order and/or inside salesperson. With Deliver 1.2.0, all job queue entries are also added to the order change log.

If not set, the user(s) specified in control file, “Innovo Deliver User to be Notified on Manifest Complete” will receive all real-time job queue’s.

This is a branch-specific control file (based on the manifest branch) that will send a job queue to the user or message group defined when a manifest is completed on the device. The job queue will contain information related to discrepancies, photos, or notes taken during the route by stop. The full list of discrepancies includes: photos, line item comments, order comments, internal notes, and notes for a skipped stop or refused order. Note that in the case of a skipped stop or refused order, a job queue will be sent to this user in real-time if the device has cellular or WiFi connectivity.

This user will also receive a job queue when one of the following occurs, unless set to go to someone else in the "Innovo Deliver User to Notify of Stop Discrepancies" control file.

• Skipped stop
• Refused order
• Line item comment added
• Order comment added
• Internal notes added

With Deliver 1.2.0, all job queue entries are also added to the order change log.

This control file prevents pricing from displaying in Deliver. You can override individual customers on the customer UD screen.

Please note there is another control file, "Innovo SigTouch / Deliver Use Print Style for Hide Pricing" that will override this setting.

This setting will require a “Signed By” to be entered. The app will remind the user to enter the "Signed By" when signing for the invoice if not entered.

This branch-specific control file allows you to specify a URL with your terms and conditions that you would like to display to the user on the sign order screen.

When enabled, and the invoice is set to a BLIND print style, pricing will not display in the app. If not set to BLIND, we will check the customer's default print status and if set to BLIND, pricing will not display in the app. This control file overrides "Innovo SigTouch / Deliver Hide Pricing Default" and also overrides any setting on the Innovo Customer UD Screen.