Actually, that's not entirely accurate. Creating the POs in Volusion is fairly straight-forward, as long as the items are listed in your Products table, and the prices are correct in the Vendor Rules table (which is an entirely separate section than the vendor price in the Products table, and requires a separate import when importing products, but don't get me started on that).
The problems arise when either the product isn't in your product table, or when you need to modify an item in the PO. Then, the workflow becomes all jumping through hoops.
It's not so much that you can't modify or create a new item for a PO, just the nonsensical way it needs to be done. For instance, in the POs section, if an item doesn't exist in the Products Database, you must click on the link for "Edit Items currently associated with this PO." Then, you have to enter some basic data, such as price, product code, description and quantity, along with the PO number of the PO that you're attempting to create in the previous screen.
That's right. You have to remember (or write down) the PO number so you know what it is before you can add an item to that PO. Apparently it is just WAYYY too difficult for Volusion to know that when you want to create an unlisted item on a purchase order that it should remember the PO number of that specific PO that you're editing.
Then, after creating the new item (or modifying an existing item) in the PO, there is no way to get back to the same PO you just modified, so you have to go all the way back to the breadcrumb trail in the top and select the PO from the list.
I ask again. Does anybody at Volusion actually use (or test) their product?
I'm dumbfounded at the logic.
No comments:
Post a Comment