FASTPATH to CUSTSUMM
Enter the FROM and TO dates
Customer Select: ALL
Driver Select: ALL
Service Types: SELECTED
12 (OTR Courier)
13 (OTR Bobtail)
Scope: DETAIL
Sort: NONE
Ordered By: Doesn't Matter
Page Break by Customer?: NO
Page Break by Date?: NO
Print Ref Summary Page? NO
Print PU and DEL Times? Doesn't Matter
Print PU and DEL Addresses? YES
Print Billing Comment?: Doesn't Matter
OUTPUT: (Print the Report, if there were no OTRs, it will tell you and you are finished)
REVIEW THE REPORT
Highlight the job numbers, service type (OTR COU or BOR BOB), lookup each job and write the from and to zones on the sheet, see below:
OTR RATING IS ALWAYS FROM THE OUTER
ZONE,
SO, EVEN THOUGH THE DELIVERY ABOVE WAS
FROM ZONE 21, WHEN WE MAKE CHANGES TO IT, WE WILL CORRECT THE RATE FROM ZONE 99
TO 21.
THIS IS BECAUSE WE CANNOT POSSIBLY ENTER ALL THE OUTER ZONES TO ALL THE DALLAS
ZONES,
AS IT WOULD REQUIRE TENS OF THOUSANDS OF ENTRIES. COPS WILL ALWAYS TAKE THE
PRICE FROM
HIGHER ZONE (99) SO THERE IS NO NEED TO HAVE A RATE IN THE LOWER ZONE (21).
The above example is
the product of looking up the job on OE, writing down the zones. Then you divide
the rate
by 2 for courier miles ($2 per mile), or divide the rate by 2.75 for Bobtail
OTRs. Next lookup the actual Yahoo
mileage and write that down.
If the price is
LOW, we will correct it. If it is HIGH, we leave it alone unless it is obviously
in error. This is because
our zones can be quite large and the target city can be spread out as well. So,
a higher price almost always
reflects a previous edit from another customer address. If we lower the rate,
that customer will be under-charged
the next time, the rate will be raised and we just go around in circles. KEEP
THE HIGHER RATE intact.