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.

RUNIFC builds the arrangement catalogue

Before any family shops, RUNIFC keeps one master list of components (roses by colour, greenery, easels, ribbons) and turns each funeral design — corona, arreglo de pie, cubre-urna, cruz — into sizes with a recipe, colour palettes, flower choices, add-ons and a banda. Every combination a family can pick resolves to a recipe the florist can build. The flower store is then switched on per funeral home.

Look for: The design editor’s combinations table: each size × colours × flowers, whether it can be made, and the worst margin across florists.

The funeral home picks its featured arrangements

Each funeral home decides which arrangements its families see first. Featured designs lead the store’s home under “Recommended by the funeral home”; any product can also be hidden from its store.

A visitor chooses an arrangement

From the memorial (“Send flowers”) a visitor enters the store with the tribute already attached — “For: {name}” and the next service. They browse by kind (coronas, arreglos de pie, cruces…), then compose the arrangement: size, colours, flowers, add-ons such as an easel, a banda with its message previewed as it will read, and the quantity.

Look for: Choices that cannot be made together are greyed out, and the price shown is the server’s, including the funeral home’s markup. With the store switched off, this link shows the previous catalogue.

Checkout, delivery to the service, and tracking

The cart shows each arrangement’s choices and banda text. At checkout the visitor delivers to the funeral home, to the place of one of the person’s upcoming services, or to another address, and pays (the demo uses the stub payment provider). The server re-prices every line and refuses a choice that can no longer be made. A tracking link follows the order — no account needed.

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 work order

The order is routed by the funeral home’s florist rules — its designated florist, or the cheapest linked florist that offers every item. The florist accepts (or rejects with a reason) and reads a work order frozen at checkout: where and when to deliver, the service, the card, the banda as it will read, and a build list of components per arrangement and in total. It prints for the bench.

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.