New Features for Release 1.52

Modified on Mon, 7 Nov, 2022 at 11:38 AM


These features will be available in your Test environment on October 31 and will be available in Pre-production on November 3rd.


New features included in this release

  • Back Office Enhancements:
    • Order
      • When selecting a pickup or delivery address suggestion, all fields previously cleared will now be kept and can be edited by the user. 
    • Transactions
      • Payments will now be created automatically and applied against the corresponding invoice or debit note when paid by credit card (Stripe)  
    • Pricing
      • New rounding options were added to calculate extra fees.
  • Dispatch Board Enhancements:
    • When locked stops are enabled, Dispatcher can now reorder the driver stops in Driver Details section of the Dispatch Board Grid. 
    • Driver next stop and ETA is now available on the Driver Details section of the Dispatch Board Grid. 
  • Administration
    • Sales Tax
      • A new tax rule table is available to setup sales taxes based on pickup and delivery state/province.
  • Other Enhancements
    • Drop-down user fields now have a blank selection to clear the field.
    • On Dispatch Grid Board, in Pickup note, Delivery note, Internal note, URLs will show as links and be clickable.

Definition

The release notes refer to different sections of the application:

Back Office: Where Customer Service Representatives (CSR) create and edit orders, create accounts, review drivers, etc.

Dispatch Board: Where Dispatchers assign orders to drivers, get notifications for invalid orders, etc.

Auto-Dispatch: This section refers to the automated order assignment setup and its process.

Administration: This section is in the Back Office but refers to sections only an administrator will use like Settings and Pricing.

Customer Portal: Where account users log in to create orders, view their order history, enter a credit card, etc.

Tracking site: Where customers enter a tracking number like the order ID or a reference number to view the status of their order.

OData: Data fields and variables saved in OData

Account API: API provided to your accounts to create, update and get orders. For documentation, please follow this link: https://api.dispatchscience.com/
Tenant API: API provided to you to create orders for your accounts, retrieve invoices and change invoice status. For documentation, please follow this link: https://api.dispatchscience.com/  


Driver App Version 1.52


No new Driver App features with this release


Back Office

Orders

Editing an Address

When editing an address and selecting a suggestion in the pickup or delivery section, previous values, such as company, address line and notes are now saved and can also be modified as needed. Previously, the values were cleared.


Transactions

Payment Transactions Automatically Created when Credit Card Payment processed via Stripe

Accounts configured with a Credit Card Billing Method will now automatically have a Payment Transaction created and applied against the corresponding invoice or debit note. These payments will appear automatically in the Transactions and show as Applied.

Payment information will show as follows:

Payment Method will be credit card, Reference Number will contain the Stripe transaction ID and the Memo will show the last four digits of the card used.


If a payment is declined by Stripe, the payment information will be created in Dispatch Science and set as cancelled and the invoice will not be paid.

The payment will show the error in the Memo:


Pricing

Rounding Options on Extra Fees

A new rounding option has been added on Extra Fees. 


Previously the quantity was always rounding up to the next unit of the Per Unit field when an extra fee was added.  


Round Up: This is what was used previously. The quantity was rounding up to the next Per Unit field. As an example, if 2.1 was entered in the quantity on an order's Extra Fee and the Per unit was 1, 3 would be used to calculate the total Extra Fee. Upon deployment of this release, this is how all extra fees will be set to maintain the previous behavior. 


No Rounding: This will allow you to use the quantity field as is on the order to calculate the extra fee total. 

As per the example above, a quantity of 2.1 with a Per unit of 1 would use 2.1 to calculate the total Extra Fee.


Round Down: This will allow you to round the quantity down to the previous Per unit. 

As per the example above, a quantity of 2.1 with a Per unit of 1 would use 2 to calculate the total Extra Fee.

When using a sliding Extra Fee with Round Down, the price will use the rounded down quantity to get the unit price.
When using a sliding Extra Fee with No Rounding, the price will use the rounded-up quantity to get the unit price.
Behavior for the Round Up will remain as it was.

 

Set Rounding Option on an Extra Fee

1) Open Pricing, Extra Fees and open an Extra Fee Schedule.

2) Open the Extra Fee.

3) Scroll down and select one of the rounding options then click save.


Dispatch Board

Grid Board

Locked Stops on Driver

If you are setup with Locked Stops for your drivers, you can now re-order the driver's stops from the Grid Board when you open a Driver Stop List. This was previously only available from the Dispatch Board Drivers stop list.


Next Stop and ETA

The next stop and ETA that was available on the Dispatch Board Driver detail is now also available on the Grid Board when viewing a Driver. 


The Next Stop and ETA is also available directly on the Driver Grid (vertical and horizontal). You can add the 2 columns by clicking on the Driver Column selector icon and checking Next Stop and Next Stop ETA.


Administration

Sales Tax Rules

Sales Tax Rules can now be setup to have different taxes depending on both the pickup and the delivery address. The Tax Rules will use your Tax Schedules to associate different taxes based on the pickup and delivery states/provinces or tax zones if those are used. 

Upon release of this new feature, the tax schedules currently in use will be migrated to the new Tax Rules. To keep the same functionality, the pickup will be set as Any and the delivery as the state/province or if using zones, the delivery will show the zone. 


Create a New Tax Rule

1) Open Settings, Configuration then Accounts. 

Make sure you have Tax Schedules created so they can be associated to the new Tax Rule. 

2) Click on New Tax Rule.

The New Tax Rule window will open:

3) Define the type of Tax Rule:

State/Province: This will use the pickup and delivery state/province to assign the Tax Rule. 

4) Enter the pickup state/province code (or zone, if using type Zone) or check Any if you wish to only use the delivery address to calculate the tax on your invoice.

5) Enter the delivery state/province code (or zone, if using type Zone).

6) Select the Tax Schedule in the drop-down field.

7) Enter a priority or leave blank. 

This is used if more than one Tax Rule could be used according to the addresses on an order. 

Upon invoicing, Priority 1 Tax Rule will first be checked to see if the addresses on the order match, otherwise, Priority 2 Tax Rule will be checked and so on.

If no priority is specified, the first Tax Rule that corresponds to the order addresses will be used. 

8) Click on Save. 


If the Account Tax Schedule is set as No Override, all orders will use this Tax Schedule regardless of the Tax Rules.



Edit a Tax Rule

1) Open Settings, Configuration then Accounts.

2) Click on a Tax Rule to open it.

3) Make necessary changes and Save. 


Delete a Tax Rule

1) Open Settings, Configuration then Accounts.

2) In the list of Tax Rule, click on the garbage can located at the right of the row to delete. 

3) In the confirmation dialog box, click on Delete to delete the Tax Rule or Back to return to the list without deleting the Tax Rule.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article