Failed catching PA-sale by roughly 1 minute...

unLight865

And lost ~25$ because of that ( from 31.01 to 56.58 ) .

It still was 31.01 on the checkout page (sadly made no screenshot of it, but do have some from the cart)... Wouldn't have happened if I hadn't tried to squeeze in one more product and then removed it again - as it turns out, not removing it would still have been 16$ cheaper (39.98 actually) .

 

[edit:  The adding in and then removing of the additional product was before going to the checkout-page... just to clarify.]

 

Is it possible to get the difference back?

 

3Diva

Put in a support ticket and ask. :) Doesn't hurt to ask for a chance of getting the difference back.

Taoz

As said many times before, the prices should be locked in the cart for a few minutes as soon as you're on the checkout page.

Toonces

From a programmer's perspective, I imagine it would be quite a challenge. You'd have to instance pricing for every 'current' user with a timeout mechanism. You'd also have to consider abuse, techy users who script a bot that auto enters/updates cart every few minutes to keep locks refreshed. You'd also need a visual for how long the lock will last, otherwise users would still complain that lock expired. I'd predict lots of bugs due to complexity.

It would be far simpler to implement a warning. I.e., as you are click on the final button to purchase, notify that prices have changed recently and take user back to cart. Granted, still plenty of comlpaints, but at least it eliminates the scenario where your credit card shows a different amount withdrawn than what you'd expect.

Or perhaps a compromise: a banner at the top of the screen which always shows impending updates. Whenever magneto pushes the price updates to server (or manually by web admin prior to a push), there's a 5 minute delay and banner shows 'pricing updates to X number of products will occur in 5 minutes'. Drawback would be situations where prices have to be updated multiple times within that 5 minutes to fix pressing issues.

unLight865

Toonces said:

From a programmer's perspective, I imagine it would be quite a challenge. You'd have to instance pricing for every 'current' user with a timeout mechanism.

Technically, users should be instanced already, I'd guess... Otherwise all would share the same cart/account, wouldn't they?

So what would be needed is the adding of said timer to those user-instances ( of course, depending on the complexity of the current state, this might still be complicated to do right - but the instancing should already be there ) .

Toonces said:

You'd also have to consider abuse, techy users who script a bot that auto enters/updates cart every few minutes to keep locks refreshed.

Not when refreshing the cart would update to the current prices... !

Toonces said:

You'd also need a visual for how long the lock will last, otherwise users would still complain that lock expired.

That would be nice, but I wouldn't consider it essential.

Toonces said:

I'd predict lots of bugs due to complexity.

Well, that's usual for software updates - you don't want to say you wouldn't want any update for any software at all, would you?

 

Toonces said:

It would be far simpler to implement a warning. I.e., as you are click on the final button to purchase, notify that prices have changed recently and take user back to cart. Granted, still plenty of comlpaints, but at least it eliminates the scenario where your credit card shows a different amount withdrawn than what you'd expect.

Hm - wouldn't have helped me in that situation. I knew it was close, but still was a little too undecided.

But for some people it might help, I'd guess.

 

 

[Edit:]

Divamakeup said:

Put in a support ticket and ask. :) Doesn't hurt to ask for a chance of getting the difference back.

Ticket now submitted.

Didn't get to it earlier - got lost in the forum when I had logged in last time...

[/Edit]

 

[Edit 2:]

The matter is solved by now - Big thanks to the support team. 

[/Edit 2]