- Report: #949826
Complaint Review: Scotlynn Commodities/Longhorn Dist - Vittoria Ontario
Reported By:
KwikKargo -
Clear Lake, Minnesota, United States of America
Submitted:
Updated:
-
Author Not Confirmed
Why?
Scotlynn Commodities/Longhorn Dist
1150 Vittoria Rd Vittoria, N03 1WD Ontario, United States of America
Phone:
519-426-2700
Web:
Categories:
Business Rating:
(0)
Tell us has your experience with this business or person been good?
Scotlynn Commodities/Longhorn Dist Easy scam of deducting 1000.00 from truckers Vittoria, Ontario
Scotlynn Commodities and Longhorn Dist, book loads to trucking companies under 1 name and rate sheet under another. There are several sheets w/ lists of rules to sign. One of the fine print rules lists the driver must not go into rvcr w/o vest and steel boots. This rule was missed, too busy focusing on the verbal agreements making w/ Baliee at Scotlynn. Had to pulp temp product and try to deliver early per request. Driver arrived 1 day early, never got into rcvg part of facility, stopped at gate and left to go buy vest and boots. Was immiediatley notified of 1000 deduction. Want all carriers/truckers to BEWARE OF THEIR QUICK SCAM to make a buck of you.
1 Updates & Rebuttals
rdcart2
Fort Myers,Florida,
United States of America
Duplicate Complaint
#2UPDATE Employee
Mon, October 15, 2012
This complaint was already filed over a month ago. The rebuttal was and still is that the receiver has a strict policy that is on our rate confirmation and there are posting all over the receiver stating that their is a fine if you do not follow protocol.
The driver did not follow the rules so they enforced a penalty. There is nothing more to this. We make our money hauling freight and not by imposing fines that are not valid. The first report on rip off report had support that favored the receiver and had other trucking companies that would attest that the signs are clear and rules need to be followed with this particular receiver.
The person reporting that Scotlynn is a supposed scam must not of agreed and decided to report the identical incident again like it was a new issue.
