Scope custom retailer banner image uploads in admin panel

Source: Featurebase post 6a1dbe90d52c7ddba4eede9a (allowing uploading of banner image) Featurebase: https://cardeio.featurebase.app/p/allowing-uploading-of-banner-image Submitted: 2026-06-01 17:17 UTC by Nicola C / Dungeon Street Signal: 1 upvote

Request

The retailer asks whether stores can upload their own image in the "banner section" and says this would be an "amazing graphic update". They also ask whether the option already exists and they simply could not find it.

Product skepticism / problem framing

This is a real retailer-admin customization signal, but it is not yet ready for backlog acceptance because the affected surface and underlying problem are ambiguous:

• Which banner section is meant: store profile, public store page, event banner, Dashboard 2.0/admin landing surface, or another retailer-admin area?
• Is this a discoverability problem for an existing upload path, or a missing capability?
• Who sees the banner and what job does it do for the retailer: branding, player trust, event promotion, or store identity?
• What constraints matter for a safe 90/10 version: image dimensions, moderation, game/publisher policy, default fallback, and whether custom images appear publicly?

Current status quo / workaround

Unknown. The post suggests the submitter could not find the option if it exists. There is no confirmed workaround or screenshot yet.

Evidence

Featurebase quote: "we think that allowing stores to upload their own images in the banner section could be an amazing graphic update. let us know if that is already possible and maybe we didn’t found the right option"

90/10 scoping path

1. Ask the submitter for the exact page/banner section and a screenshot.
2. Verify whether the requested upload path already exists and is discoverable.
3. If missing, scope the smallest safe custom-banner upload for the intended retailer-admin surface, including validation, default fallback, and public/private visibility rules.

Success criteria before moving to Backlog

• The exact banner surface is identified.
• Product decides whether custom retailer images are allowed on that surface.
• The first-version upload rules are explicit: dimensions, file types, moderation/abuse handling, default/fallback behavior, and where the image appears.
• If this is only discoverability, the accepted fix is framed as UI/help copy rather than a new upload feature.