High-value-goods shippers carry real financial exposure on every outbound load, yet ERPNext core has no concept of shipment insurance or a claims lifecycle. Teams end up tracking declared values in spreadsheets, calculating premiums by hand, filing carrier claims over email, and reconciling settlements as ad-hoc journal entries — with no link back to the Delivery Note, no audit trail, and no way to report loss ratios by carrier or route. When a claim drags on for weeks, nobody in ERPNext can see its status, the accrued premium expense, or the expected recovery.

ECOSIRE builds a proper Frappe app that models this end-to-end. We add a Shipment Insurance Policy DocType linked to your Delivery Note (and optionally Sales Order/Shipment), plus an Auto-Insure Rule DocType that decides which shipments must be insured based on declared value thresholds, item groups, ship-to territory, or carrier. A hooks.py on_submit doc event on the Delivery Note evaluates the active rules, calculates the premium from a configurable rate table (flat, per-mille of declared value, or banded), and either creates the policy automatically or flags the shipment for review. Premium posting is wired through ERPNext's accounting so each policy books the expense/accrual against the accounts you nominate, keeping GL and inventory movements consistent.

The claims side is a Shipping Claim DocType with a Frappe Workflow (Draft, Filed, Under Review by Carrier, Approved, Settled, Rejected, Closed) and role-based transitions. Adjusters and warehouse staff file claims against the originating policy, attach evidence — photos, inspection reports, proof-of-delivery exceptions — through the standard Frappe File attachment and comment system, and record the carrier's claim reference and status. A scheduler event (scheduler_events in hooks.py) can nudge stale open claims and refresh SLA aging. On settlement, the app posts the recovered amount as a credit/refund against the correct account and closes the loop back to the policy, so finance sees net loss per shipment, per carrier, and per route in native ERPNext reports.

Everything is exposed the ERPNext-native way: server scripts and controller hooks enforce the premium and claim logic, client scripts add in-form calculators and validation on the Delivery Note and claim forms, whitelisted methods and the Frappe REST API let external portals or carrier integrations file and query claims, and a dedicated Role Profile plus DocType permissions keep adjusters, warehouse, and finance in their lanes. It is packaged as a versioned Frappe app installable via bench get-app / bench install-app, tested on Frappe/ERPNext v15 and v16.

This is build-to-order: it is not an existing Frappe Cloud Marketplace download. We start with a short scoping call, confirm your insurance rules, premium formulas, claim workflow, and accounting treatment in writing, then build against that spec. Typical delivery is one working week from confirmed scope depending on complexity. We install it on your bench (self-hosted or Frappe Cloud), run UAT on a staging site, train your team, and hand over the git repository and documentation.