Bluumo: Two-Sided Wellness Marketplace

Customer Interface (11+ screens)

• ·Service browsing with category, price, and duration filters
• ·Provider discovery with ratings and comparison tools
• ·Location-based search with interactive maps
• ·Real-time availability and instant booking confirmation
• ·Finnish banking transfers, card payments, MobilePay, Edenred wellness cards, KELA reimbursement support
• ·Recurring booking management
• ·Gift card purchasing with PDF generation
• ·Referral program with automated rewards
• ·Bluumo Plus subscription tier
• ·In-app voice calling via Agora
• ·"Helmi" - AI concierge powered by Claude for booking assistance

Provider Portal (13+ screens)

• ·Document-based verification onboarding
• ·Multilingual profile management
• ·Visual availability calendar with Google Calendar sync
• ·Dynamic pricing (peak hours, discounts, time-based adjustments)
• ·Real-time booking notifications
• ·Earnings tracking and payout history (Holvi payout infrastructure built, not yet active)
• ·Booking status progression through sub-steps with visual completion indicators
• ·'Mark Complete' action to finalize the provider-side booking workflow
• ·Review management tools and service area configuration

Corporate B2B Portal

• ·Corporate registration with approval workflows
• ·Employee management with bulk operations
• ·Wellbeing day booking (individual and bulk)
• ·Cost center tracking, budget management, manager approval queues
• ·Invoice analytics, usage reporting, automated invoice generation
• ·Quote request system

Admin Dashboard (12 screens)

• ·Platform-wide KPIs and analytics
• ·Provider verification management
• ·Booking oversight and support ticket system
• ·Blog publishing with SEO metadata
• ·Campaign and promotion management
• ·Refund and invoice processing

A default that means "unset" has to be NULL

Every booking was taking a flat 20% commission. The pricing trigger branched on whether commission_rate was supplied: non-null meant an explicit B2B override, so it skipped both the GMV tier (24/22/20/18) and the Bluumo Pro discount. The column had a non-null default, so the value was never absent and the override branch always won. Nothing errored, the arithmetic was correct, and every row in the table was wrong. Dropping the default let an omitted rate arrive as NULL so the trigger computes authoritatively. If a branch keys on presence, then presence, not a value, is what the schema has to be able to express.

A permissive fallback hides a feature that never worked

The distance filter did not filter. Providers were included when they had no coordinates, which is a sensible default, and no code path ever wrote provider latitude or longitude, so every provider took the fallback and appeared at any radius. The feature looked implemented, returned plausible results, and was inert. A fallback that swallows the empty case will keep the empty case from ever being noticed.

Revoking a grant changes what select('*') means

Locking financial columns behind column-level grants broke reads that asked for everything. PostgREST cannot silently narrow a select('*') to the columns a role may actually see; without table-level SELECT it raises instead. The fix is to name columns explicitly at every call site, which is better practice anyway, but the lesson is that tightening permissions is a client-side change too, not only a database one.

Degrade the optional parts, not the transaction

Push notifications on this platform return a bare 500. Rather than let that surface as a failure, the flows that use them fall through to email and in-app, and a nullable provider contact address falls back to the account email rather than dropping the message. Deciding upfront which parts of a flow are allowed to fail quietly, and which must never, is most of what makes a payment path feel reliable.