A selection limit in the client gallery: why a cap helps everyone

Many photo packages include a fixed number of edited images — “30 finally retouched shots”, for example. The gallery is then the tool the client uses to pick exactly those 30. Without a technical limit, though, “pick 30” quickly becomes “I’ve marked 90, they’re all so lovely”. And then an awkward conversation begins.

The problem with the open request

A cap that only exists in the quote but isn’t enforced in the gallery invites overshooting — usually without ill intent. The client loses count while marking, and in the end you have to ask them to cut images again. That feels bad for both sides: they have to part with “their” images, and you come across as petty.

What a hard limit changes

If the gallery enforces the limit itself, the decision moves to the right place — to the client, while they’re choosing. They see that X of 30 marks are still free, and prioritize on their own. That has three effects:

• Your pricing stays stable. You deliver what was agreed, without renegotiation.
• The selection gets faster. A cap forces a decision; unlimited selection invites procrastination.
• Upsells stay clean. If the client does want more images, that’s a clear upgrade conversation — not a sheepish “surely those few extra are fine”.

When to leave it off

Not every gallery needs a limit. For a presentation gallery, a flat-rate package, or when the client gets everything anyway, you simply leave the field empty — then the selection is unlimited. The limit is a tool for the package model, not a default for everything.

Conclusion

An enforced selection limit isn’t distrust of the client, it’s clarity for both. It keeps your packages clean, speeds up the decision, and turns potential conflict into a friendly upgrade offer. Where it doesn’t fit, you simply switch it off.

Lumio is built exactly for that: per gallery you set how many images a client may mark at most — or leave the field empty for unlimited selection.