A funeral home does not run on a sales pipeline. A case begins with a first call at 02:00, and within hours it has a decedent record, a next-of-kin who is often the payer but frequently not the legal authorising party, a removal already in motion, a chapel and a cremator to book, a coroner or medical examiner release to wait on, a death certificate and burial-transit permit to file, a casket or urn drawn from inventory, and a statement of goods and services that must be itemised in the exact form your jurisdiction demands. ERPNext core has real strength underneath all of this — Item, Stock Entry, Sales Invoice, Payment Entry, Employee, ledger and cost centres — but it has no notion of a decedent, no authorising party distinct from a bill-to party, no permit whose expiry blocks a disposition, and no way to stop a chapel being double-booked against a cremation retort. Homes end up running the actual work on a whiteboard, a shared calendar and a spreadsheet of case numbers, then re-keying into ERPNext days later so the accounting reconciles. The re-keying is where names get misspelled on a memorial folder and where a service is billed to the wrong family.

ECOSIRE builds you a proper Frappe application — its own app directory, its own module, installed on your bench alongside erpnext — rather than a pile of custom fields on Sales Order. The spine is a Funeral Case DocType with a naming series, a workflow (Intake → Arrangement → Scheduled → Service Held → Disposition Complete → Closed), and child tables for service selections, merchandise, cash advances and disbursements, and the documents a case must produce. Decedent, Authorising Party and Case Contact are separate DocTypes with Link fields into Customer and Contact, so the person who signs the authorisation, the person who pays, and the person who receives correspondence can be three different people without a workaround. Services and merchandise are ordinary ERPNext Item records — a Funeral Service Item extension carries the disclosure category, whether the line is a cash advance handled on behalf of the family, and whether it is a package component — so caskets, urns and register books move through real Stock Entry and Serial No records and your inventory valuation is the one ERPNext already computes.

Technically it is deliberately conventional Frappe. Scheduling is a Facility Booking DocType against Facility records (chapel, viewing room, preparation room, retort, hearse, fleet vehicle) with an overlap check in a validate hook that raises before save, plus a staff assignment child table that checks a director's or embalmer's existing bookings and their Leave Application records. Document control lives in Case Document, each row carrying a type, an issuing authority, an issued and expiry date, and an attached file; hooks.py doc_events on Funeral Case prevent a transition into Disposition Complete while a required document type is missing or expired, so the block is enforced server-side and not merely hidden in the UI. scheduler_events run a daily pass that flags permits approaching expiry, chases outstanding death-certificate copies, and produces the day's service run sheet. Billing is generated by a whitelisted method (@frappe.whitelist()) that assembles the case into a Sales Invoice in your jurisdiction's disclosure order, keeps cash advances in their own group so they are visibly not marked up, and posts through standard ERPNext accounting — nothing about the general ledger is re-implemented. Client scripts drive the arrangement conference screen, with package selection auto-expanding into component lines and a live running total as a family adds or removes items. Permissions ship as role profiles — Funeral Director, Arranger, Preparation Staff, Office Manager, Accounts — with field-level rules so preparation notes are not visible to front-office roles, and the whole surface is reachable over the Frappe REST API for a website enquiry form, a monument supplier, or an obituary feed.

Everything is scoped to your jurisdiction and your paperwork. Cremation authorisation requirements, coroner release workflow, disclosure-statement formats, permit types and retention rules vary by country, state and county, and we build to yours rather than shipping a generic template. Print formats — statement of goods and services, authorisation forms, service programmes, register book inserts, chain-of-custody sheets — are built as Jinja print formats on your letterhead so the family-facing paper looks like your firm's, not like an ERP.

This is a build-to-order application: it is not a Frappe Cloud Marketplace download and there is no instant install. Delivery is typically 2–4 weeks from confirmed scope. We start with a scoping call, walk through a real case from first call to closed file, write the specification, then build and demonstrate on a staging bench where your directors run their own cases as user acceptance testing before anything touches production. You receive the complete source of the app, a git repository handover, installation and configuration on your bench, technical and user documentation, a training session, and a post-go-live support window. The app targets Frappe/ERPNext v15 and v16, and we build against the version you are actually running.