The Hub

Here is what you need to know to get ahead of the Q3 scorecard changes occurring October 8 (week 41) covering week 40 (Sept. 28–Oct. 4). The changes should make it easier to earn Fantastic Plus. However, your DSP will want to make a few tweaks to take advantage of factors you can control.

PSB and Fleet Execution

First, two factors that account for 10% of the scorecard, High Performers Share and Low Performers Share, are being replaced by Pickup Success Behaviors (PSB) and Fleet Execution. The new factors will help increase the overall score because they’re easier to control.

Leading up to the changes, you’ll want to track the two new metrics previews in Cortex. Here is where to find the previews:

PSB can be tracked by clicking a link highlighted in light blue at the top of the Performance/Quality page in Cortex. Included in the PSB metric is a new route type called a Pickup Route. You can find out more about Pickup Routes by searching for the “Amazon Shipping Resource Guide” pdf in Support Central.

Fleet Execution can be found in Performance/Supplementary Reports and is listed as the “Fleet Execution Dashboard.” To ace the score, you’ll want to make sure all non-grounded vans go out at least once every 14 days.

Safety and Quality

Safety will increase in importance from 42.4% to 44.8% of the scorecard. Since most DSPs are adept at working with their safety score, this increase should be positive.

Quality, an area where many DSPs struggle, will decrease slightly from 42.4% to 40.1% of the scorecard. There is a catch. Amazon has added a fifth way to get DSB defects, “Not Delivered-Not Returned” which, if not managed properly, will bring your Quality score down. These defects can occur in several ways:

1.          The package was delivered without the use of Flex. For example, a package that was marked missing is found later and delivered, but the driver doesn’t know how to use the reattempt dialog or manually enter the TBA after delivery.

2.          The package was left in the van and not turned in at RTS.

3.          There was an RTS problem. For example, the driver self-returned the package at RTS but didn’t scan it first.

4.          Driver support was called and given TBA numbers but failed to mark packages as delivered.

To preview the impact of Not Delivered-Not Returned packages, go to the Quality page in Cortex. Select a date or week that is at least two days past. Click on the linked number that represents the DSB DPMO, just to the right of the Delivery Completion Rate (DCR.) The DNR dialog will open. On the upper right side of the list of DNRs, click the link for “See Preview Data.” You can then sort by “Scanned-Not Delivered-Not Returned” to see how many have occurred. Click on each TBA to see if the delivery date is available, then enter the TBA in the Operations/Delivery filter for that day to see why the package is missing.