Wishlists: Set price watch at lowest price plus x?

Edit Subject

We've got a feature in the bulk editor that almost does that. I need to add an option to the relative pricing section that allows you to choose plus or minus instead of just minus. I'll look at adding it to the wishlist import too. Good suggestion.

Done! In case you haven't noticed, wishlists now allow for positive or negative relative pricing. I also implemented the +/- option in bulk edits so you can change prices on large sets of non-wishlist items in the same way.

I'm not sure it is working properly yet. I imported a new wishlist, selected all three price watches (Amazon Price, 3rd Party New Price, and 3rd Party Used Price), and chose "Lowest Price + $1.0". However, all the price watches were created with the lowest price.

I haven't been able to reproduce the problem you're having with new wishlist imports. Be aware that updating the settings for wishlists you've previously imported to Camel affects only items you add to that Amazon wishlist in the future. Price watches created from the initial import will not change because if we synced the price watch settings constantly you'd have constantly changing price targets.

Try importing a brand new wishlist from Amazon and see if the relative price settings work for you then. If not definitely let me know...maybe I'm doing something dumb that prevents me from seeing the issue you are talking about.

For wishlist items you've already imported and want to change the desired prices for, try using the bulk edit tool. Select a couple of products from the tracker page (http://camelcamelcamel.com/tracker?fi...) by clicking on the checkbox below the product image. Then click on the 'edit' button at the top of the page. On the following page you should be able to "Set a Relative Price" in the same manner as the wishlist import.

Again, let me know if this doesn't fix your problem.

Wait a minute. This brings up three issues. :-)

1) On the tracker page, how do I bulk edit the items that came from a particular wishlist? Without this feature, the bulk edit functionality is essentially lost on me because I can't follow your suggestion on how to reprice the items.

2) I deleted every wishlist from the wishlist importer section. I deleted every price watch. Now I have a blank CamelCamelCamel account. I readded my same three wishlists but with different price rules. I waited a few hours for the wishlists to be imported. If the items return to CamelCamelCamel with their previous price watches, I would consider this a bug. Are you saying this is by design? This is the problem I'm having. If I delete a price watch from CamelCamelCamel, then the wishlist importer runs again, it should re-add the price watch I deleted (assuming the item is still in my wishlist, of course) but with the new rule and based on the prices at that particular moment (new lowest price/current price).

3) Why doesn't "lowest price" reapply dynamically? It doesn't make sense to use the lowest price at the one particular moment the item was added. (This makes sense for "current price" and "static price"). If an item reaches the "lowest price" threshold, I should get an e-mail alert and the threshold should be updated. If I buy the item, it will be removed next time CCC updates my wishlist and what happens to the price watch (update or not) is irrelevant. If I don't buy the item, however, (I decided the price still wasn't low enough), then I want to keep monitoring it and of course the "lowest price" I'm comparing it to should now be the new lowest price from the last e-mail. In other words, if the "lowest price + $1" was at $15, then the item reaches $14.99, I don't want any more e-mails unless the item reaches $13.99 and I haven't yet purchased the item (or deleted it from my wishlist).

I created a brand new wish list and added one item to it that I'd never tracked before. I imported it into CCC and selected "lowest price + $1". In this case, it did work as expected (price watches set at $1 above lowest levels seen for Amazon, 3rd party new, and 3rd party used). So I guess the bug is scenario #2 above. If I delete an item from CCC, I expect it to actually be deleted with no memory of prior price watch settings.

Nice work anticipating our internal goals! We were just talking about implementing labels for each wishlist so you could do bulk edits for wishlists more easily.

Regarding #2, are you actually seeing this issue or are you still waiting for wishlists to import? I just tried doing this (delete wishlist price watches, delete wishlist, re-add wishlist) and it's setting prices as I would expect. That is, it's setting prices relative to my new wishlist request and disregarding all previous price watch and wishlist settings.

#3 isn't a bad idea, but it would require some significant changes to the wishlist operation on the backend. We'll have to think about that one. But if we get labels working on wishlsits (#1) and if that allows you to more easily update existing wishlist data via bulk editing, maybe that will be alleviate most of the trouble.

Thanks for your suggestions!

Yeah, I suppose #3 isn't a big deal if I can bulk edit by wishlist, or if I can just delete the items and have them automatically added again when the next import cycle runs.

I tried again (delete all wishlists, delete all price watches, reimport all wishlists) and it worked properly this time. Perhaps I forgot a step when I tried it the first time or something -- sorry for the false alarm there. Thanks for your help!