When ordering multiple items in the shopping cart, allow the quantities to be different for each item.
Here's the scenario, I am a corporate buyer and want to purchase 5 of course A, 10 of course B, 8 of course C. I'm expecting to receive a separate enrollment key for each.
When you currently update the quantity in the shopping cart, it applies the quantity to all the items. It creates one enrollment key, assuming that the learner needs all the items in the order.
Understand the logic, sort of, but this one's a show stopper for our largest clients.
This is an issue for us as well. It can create issues for purchasers as well if they do not realize the quantities all update. Is the enrollment key necessary? Or, why can't multiple enrollment keys be created through a single check-out?
I know AbsorbLMS is an LMS platform first, but I did make my decision to go with AbsorbLMS because it had a built-in storefront as a differentiator. Fronting this with another storefront solution, possibly needing to use APIs, will cost me more money and add time and complexity. Other workarounds could potentially drive away customers because of the time and effort needed to make multiple purchases. I am hoping that this can be modified to accommodate what I think is a pretty basic feature.
After discussing this issue with our Absorb Client Success Manager, it seems like it might not be possible to fix this issue, due to the way enrolment keys are assigned. As an interim fix, or possibly a final solution, could functionality be added that will allow each client to switch off the feature that is responsible for this issue? Could you create a toggle switch in the E-Commerce Settings that allows clients to toggle off multi-course purchases. Switching off multi-course purchases would prevent customers from being able to purchase more than one type of course at a time (per shopping cart session), but still allow them to purchase multi-seats for the course they are purchasing. So in the example scenario above, with multi-course purchases toggled off, the corporate buyer would need to perform 3 separate transactions (checkouts) to be able to complete all their purchases: purchase 5 of course A - then checkout, purchase 10 of course B - then checkout, and finally purchase 8 of course C - then checkout. This would show up as 3 different transactions, and would be slightly more inconvenient for the buyer, but I think this small inconvenience would be much better than having to deal with an incorrect purchase. Currently we would need to manually refund the buyer and unenrol them from all the additional course seats that they didn't actually choose in their shopping session, but appeared in their shopping cart and were charged for.
Possibly Absorb Support are not treating this as a bug, although I think it does qualify as a bug because it is not working as intended - this is not a feature request or enhancement request. Perhaps Absorb Support "is" treating this as a bug, but as a low priority because there are potential work arounds. From a client point of view this is a high priority because it is impacting on client revenue. The workaround costs time and money, and the poor customer user experience might be damaging customer relations and limiting potential subscriptions etc. The way a client would assess the level of the bug would result in a "severe" level bug. But maybe the way Absorb Support is assessing the bug is resulting in a "low" impact bug. If this is the case, then maybe the method of classifying bug severity/priority - should be modified to account for client needs.
This is still an issue, and we would also like different quantities for different courses.