IDEAS - BevvyTech/BrewskiDocs GitHub Wiki

Product Ideas

  • Send clients an automated email one week after delivery asking them to rate the beer, prioritising first-time orders but including repeat purchases when feedback is missing. Link the email to a central ratings page that groups all outstanding review requests for that email address, even if the orders came from different breweries, and automatically expire any unfulfilled review requests after two months.
  • Build a mobile app that lets staff scan container barcodes/QRs to track movements, returns, and cleaning cycles in real time.
  • Marketplace “intro offer” flagging: allow breweries to search for prospective clients who explicitly opt in to “accepts discount offers” and define a minimum order value (“above certain value”) threshold. Surface these signals so breweries can pitch introductory deals that meet the client’s expectations and are automatically suppressed when the deal doesn’t qualify.
  • Team-level order multiples: let breweries define one or more rules that force client orders into specific pack counts (e.g. minimum three kegs, cans/bottles only in multiples of 6/12/24). Expose these constraints in the checkout and admin tooling so the system validates quantities before confirming.
  • Keg accessory upsell: bundle the correct coupler type for keg orders, optionally including fittings, so buyers can add the required hardware at checkout and breweries can manage which coupler variants map to each container type.
  • “Make this beer again” requests: give customers a way to flag retired or out-of-season beers they loved. Aggregate votes per beer, notify the brewery when interest spikes, and optionally let them announce when a rerun is planned.
  • Pub feedback follow-up: schedule automated check-ins one to two weeks after delivery asking pubs and venues how the beer performed (quality, pour, sales velocity). Feed the responses into batch QA dashboards and highlight issues needing brewer attention.
  • Brewer media showcase: provide a workflow for breweries to upload “cool pics” (and short clips) of their beers, tag them by product, and mark which assets can be syndicated to the public site or socials. Include lightweight moderation and auto-resizing for channel-specific crops.
  • Bevvy hardware integration: hook fermentation sensors and brewhouse telemetry (“Bevvy” devices) into the platform so breweries can auto-publish fermentation milestones and “next batch dropping” updates to engaged customers without manual effort.
  • Container SKU/barcode fields: add optional SKU + barcode fields to each enabled container type so teams can register packaging identifiers once and reuse them across stock systems and label workflows. Optionally offer auto-generated SKUs in settings so racked products receive managed identifiers without manual input.
  • Pro-forma invoices: introduce a pro-forma document flow that mirrors orders before confirmation, includes deposit instructions, and can be regenerated as items change until the official invoice is issued.
  • Messaging campaigns: enable SMS and WhatsApp broadcasts to wholesale clients when new releases drop, with deep links to the relevant beer detail or order page and unsubscribe controls per channel.
  • Shop settings gating: restrict Admin shop configuration tools to breweries operating in the UK until wider regional compliance and rollout plans are validated.
  • Social login consent: when a user signs in to the Admin or Shop via Google or another social provider and the email is unknown to the platform, prompt them, showing the exact address ("This email [email protected] isn't registered..."), to confirm account creation before provisioning a new profile.
  • Verified purchaser badge: when someone who actually bought a beer leaves a comment, display a verified purchaser icon beside their name with a tooltip explaining the badge.
  • Email ingestion subdomain: provision a platform-owned subdomain with per-user virtual mailboxes, fan incoming messages through DigitalOcean Functions, and let AI classify and ingest them into invoices, payments, orders, and related records.
  • Merch fulfillment partner integration: contract a white-label merch printer to produce team apparel on demand. Teams upload artwork, Shop orders route directly to the printer for fulfillment, and the payment system splits revenue automatically (10 percent platform fee) so the printer is paid immediately and the balance goes straight to the brewer.
  • Customer messaging workspace: provide an optional chat surface inside group orders so pubs and participating breweries can coordinate in real time, while keeping email notifications as the fallback channel.
  • Internal brewery chat: allow internal chat within local brewery groups so team members can coordinate without leaving the platform.
  • Wholesale customer chat: let wholesale buyers initiate direct chat conversations with breweries, keeping communication in-platform for order follow-up and relationship management.
  • Brewery catalogue profiles: expand each public brewery profile beyond the logo by supporting curated image galleries (taproom, production, team shots) so the catalogue feels like a destination instead of a static logo card.
  • Newsletter bounce tracking: add an email-bounce tracker that writes per-campaign logs (e.g. JSON summaries) into DigitalOcean Spaces so we can audit newsletters, reconcile suppressions, and investigate deliverability without hitting provider dashboards.
⚠️ **GitHub.com Fallback** ⚠️