From a family’s first call to the last payout.

A funeral home registers a new case

A family has just lost a loved one and chosen this funeral home. Staff sign into the tenant admin and create a case — the internal record that ties together every downstream artifact: obituary, service events, orders, and condolences.

Look for: Notice the case has its own internal number for staff and is separate from the public-facing memorial.

Staff draft an obituary

From the case, staff draft the public memorial: name, dates, biography, photos, and service events. Drafts can be saved and edited; publishing pushes the memorial live on the family-facing site.

Look for: The editor supports bilingual content (English / Spanish) and lets staff schedule a publish time.

Family and friends visit the memorial

Once published, the obituary appears on the public site. Visitors can read the life story, view service times, and leave a note of condolence in the digital guestbook. Notes are moderated by funeral home staff before appearing.

Operator moderates incoming condolences

Condolences land in a moderation queue. Staff can approve, hide, or remove notes. Approved notes appear publicly on the memorial. This protects families from spam without slowing down the flow.

A visitor sends flowers

From the memorial, a visitor can browse the funeral home’s sympathy catalog — flowers, baskets, keepsakes — and send a gift to the family. The catalog is curated per tenant and priced by a server-side pricing engine.

Look for: Prices already include any tenant-specific markup (the demo adds 15% on flowers).

Checkout and order tracking

The visitor enters delivery details and pays. For the demo we use the stub payment provider so anyone can complete the flow without a real card. Right after checkout a tracking link is generated — the visitor doesn’t need an account to follow the order.

Funeral home sees the new order

Orders for this tenant land in the operator console immediately. Staff can see who sent the gift, the card message, the delivery address, and the fulfillment partner assigned to it.

A florist partner picks up the assignment

The order is routed to Bloom & Bough — the local florist partner for this tenant. The partner sees the assignment in their own portal: card message, delivery window, service area check. They accept (or reject with a reason).

Florist fulfills and uploads proof

As the order moves through preparation and delivery, the florist updates status. Once delivered, they upload a proof-of-delivery photo. The status change cascades back to the order tracker the family is watching.

Look for: The status timeline on the public tracking page now shows every transition with timestamps.

Platform admin closes the weekly settlement

At the end of each week the platform admin closes the settlement period. This generates per-tenant statements (what the funeral home earned net of platform fees) and per-vendor payouts (what each florist is owed).

Statements and payouts are issued

Once the week is closed, statements and payouts are visible to both sides. Funeral homes see their net revenue; florists see what they will be paid. Disputes happen here — the underlying order data is still intact and auditable.

The funeral home keeps the relationship going

After the service, the obituary continues to live as a permanent memorial. Friends can return to leave notes on anniversaries. The funeral home can publish content (anniversaries, grief resources) through the built-in CMS, and tweak their public branding any time.