I searched the forum for any threads related to my issue and found none. So either the 2007.0.5 version we're using is not the latest, or no one has come across these issues and reported them here...
First of all, I had hoped that a vendor return could be performed at the P.O. level since we generally do not hold inventory and then do a massive return to vendor. This feature is available.
Second of all, I have had problems trying to keep track of returns in the old system because of the time it took to get the credits from the vendors.
Third, we needed a method to use our UPS system to create a shipping label to return the goods. I will say that we normally wait for a call tag from the vendor so it's on their dime.
I took the time today to try my first Vendor Return. I read the documentation (which by the way is good but several links lead to "Page Not Found"). After about an hour of testing in our live account, and I found a few issues, I decided to call Support...Gold Support...and ask a few questions...After more than 30 minutes on the phone, here is what was verified.
1. A vendor return does NOT open up the original P.O. so you can receive against it when the correct item arrives. You have to enter a new P.O. which now is not tied to the original sales order.
2. A vendor return will let me "return" items I did not receive. The item type I was struggling with was a non-inventory item for resale which is used for a fee the vendor charges. So I'm not sure if it is related to the item type.
3. A vendor return will let me "return" the P.O. multiple times. Meaning, someone could enter the Vendor Return two or three times.
4. I couldn't get the return authorization to ever be completed. It kept showing on my dashboard as partially received. I tested and found it was related to the original shipping cost from the vendor that was entered on the expense tab. Somehow you will have to remember this and enter it on the bill credit.
Please note I have not tested the drop ship feature.
Would like to hear from anyone who has found a work-around or experienced the same issues. If you haven't tested this, someone should be looking into it. I'm just disappointed this made it thru the QC and beta testing.