Cart buying option

Practical notes for @leemyers based on the thread: the UI you want—select a software product and tick multiple optional items to add to the cart in one action—is a common requirement. @Ritesh_4 and @pgmco are right that many platforms can do it, but the key is confirming specific capabilities rather than picking a name off a list.

The checklist to evaluate a cart or extension:

• Downloadable/virtual product support (secure delivery links).
• Grouped/bundled or composite-product features (present base + selectable modules).
• Product add‑ons or configurable options that allow checkbox/multi‑select behavior.
• Bulk add‑to‑cart support or an API/hook to programmatically add several SKUs in one request.
• License key generation or integration with a license server for automated delivery.
• Active extension ecosystem and maintained modules for security and compatibility.

Implementation and testing guidance: implement the UI with a bundle/add‑ons extension when available; otherwise map selected options server‑side and use the cart API to add multiple SKUs in one transaction. Fully test the end‑to‑end flow: checkout, automated license issuance, download limits/expiry, partial refunds, and reissue scenarios. Also confirm tax/VAT handling for digital goods and that the payment gateway permits automated digital delivery.

Summary: prioritize carts with bundled-product or add‑ons support plus license/digital delivery automation. If the cart lacks a ready UI, implement multi-add via the platform API and validate every step of order fulfilment.