I would like to suggest an option for "Offline Deployment" to allow customers with low/limited bandwidth to perform self installs while offline.
We have several low bandwith users (around 800) that basically live out of Hotels and secure locations. Deploying large packages/apps/Task sequences are always an issue because said deployments become available in Software Center, and yet the content has not arrived yet.
Due to the nature of their work, we need to give them the ability to deploy apps/packages/task sequences on their schedule. Once a package is made available, it shows up in Software Center yet the bits are not cached. This can mean that should they initiate the action, they now MUST stay online until the data caches over a slow link (in some cases Gigs). Making it Required, on the other hand, could interfere with their work should it happen at an inopportune time.
Understanding that "Available" does not cache content, allowing for the checking of a "staged" box would allow the payload to be cached, and once that is complete, THEN and ONLY THEN make it available (VISIBLE) in Software Center. Would only apply to Large Deployments.
This would allow for payloads to cache through BITS as they are connected (sporadic) and still be able to have a good customer experience and individual controls when they do their installs.