Importers and distributors running ERPNext know the pain: the price on the supplier invoice is never the real cost of the goods. Freight forwarders, customs duty, insurance, demurrage, and handling arrive as separate invoices, often days or weeks after the Purchase Receipt is submitted, and frequently in a different currency. ERPNext ships with a native Landed Cost Voucher, but it is a manual, after-the-fact document: someone has to remember to raise it, key in every charge, pick the receipts, and choose a single distribution basis for the whole voucher. When a team processes dozens of import shipments a month, this step gets skipped, delayed, or done wrong, and item valuation, COGS, and margin reporting drift away from reality.

ECOSIRE builds a proper Frappe app for you, delivered as its own module and DocTypes rather than a pile of loose customizations that break on the next bench update. At the center is a Shipment Cost DocType that captures every non-item charge for a consignment, each line carrying its own expense account, currency, exchange rate, and allocation basis. Unlike the single-basis native voucher, a child-table charge model lets one shipment mix bases: freight allocated by gross weight, customs duty by taxable value, insurance by declared value, and port handling flat per item. On submit, hooks.py document events fan the charges across the linked Purchase Receipt items, write the resulting per-unit adjustment back into stock valuation via the standard Stock Ledger Entry / GL Entry mechanism, and post the accounting so your balance sheet and stock account stay reconciled.

Technically, the app is built the way a maintainable Frappe app should be. Allocation logic lives in whitelisted server methods (@frappe.whitelist()), not in fragile UI hacks; document events (before_submit, on_submit, on_cancel, on_trash) enforce the valuation write-back and its reversal; and a Client Script adds live per-item breakdown preview on the form so users see landed cost before they commit. Multi-currency is handled at the charge line so a EUR freight invoice and a USD duty payment both resolve to company currency correctly. Everything is exposed over the Frappe REST API and whitelisted methods for integration with your freight-forwarder portal or a customs-broker feed, and a scheduler event can sweep unallocated shipments and nudge the responsible role. Role Profiles and DocType permissions keep charge entry, approval, and valuation posting properly segregated for audit.

Because this is build-to-order, nothing ships until we agree on your scope. We start with a short scoping call, confirm your charge types, allocation rules, chart-of-accounts mapping, and Frappe/ERPNext version (v15 or v16), then build against a staging copy of your data. You get the installable source, a UAT window on staging with a documented rollback plan, and go-live support. Typical delivery is 2 to 4 weeks from confirmed scope. You keep the git repository and the app remains yours to run on your own bench or on Frappe Cloud.