- الرئيسية
- Apps
- Multichannel & PIM Tools
- Customs Clearance & Clearing-Forwarding for ERPNext
معاينة توضيحيةA build-to-order ERPNext application that runs the full customs-clearance lifecycle
— declarations, HS-code duty and tax computation, bill-of-entry document tracking, and clearing-agent job costing.
ECOSIRE scopes, builds, installs, and supports it for your import/export operation.
ما هو Customs Clearance & Clearing-Forwarding for ERPNext؟
A build-to-order ERPNext application that runs the full customs-clearance lifecycle — declarations, HS-code duty and tax computation, bill-of-entry document tracking, and clearing-agent job costing. ECOSIRE scopes, builds, installs, and supports it for your import/export operation. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $999.00 USD; request a quote for a scoped proposal.
الميزات الرئيسية
مبني حسب الطلب، ننجزه بالكامل لك
لا إعداد يدوي — تطبيق جاهز يبنيه ويثبّته ويدعمه ECOSIRE.
- 1
تطلب
ابدأ بسعر بناء لمرة واحدة. نحدّد النطاق معك عند الانطلاق.
- 2
نبني ونثبّت
يقوم ECOSIRE ببنائه وتهيئته وتثبيته على ERPNext الخاص بك.
- 3
الإطلاق + الدعم
تنطلق خلال أسبوع عمل واحد تقريبًا، مع أسبوعين من الدعم بعد التشغيل. نصلح عيوب الكود الذي نسلّمه مجانًا.
المواصفات التقنية
- توافق ERPNext
- —
- الترخيص
- يلزم تأكيد الترخيص
- متطلبات Python
- Python 3.10+
- قاعدة البيانات
- MariaDB 10.6+
عن هذا المنتج
Clearing-and-forwarding agents and import/export firms live in a world ERPNext core was never designed for. A single consignment carries an HS code, a bill of entry, a customs declaration reference, duty and VAT/GST computed against tariff schedules, port and shipping-line charges, and demurrage that accrues by the day. Native ERPNext gives you Purchase Orders, Landed Cost Vouchers, and a Chart of Accounts — but there is no Customs Declaration DocType, no HS-code tariff master, no bill-of-entry tracker, and no way to run a clearing job as a billable file with cost recovery from the importer. Agents end up managing all of this in spreadsheets and WhatsApp, and reconciling disbursements by hand at month-end.
ECOSIRE builds a proper Frappe application — a versioned app installed on your own bench, not a pile of customisations bolted onto stock DocTypes. At its core are dedicated DocTypes: Customs Declaration and Bill of Entry (with child tables for line items, each carrying an HS code, assessable value, duty rate, and computed duty/tax), an HS Code tariff master, and a Clearing Job that ties a consignment to its declarations, disbursements, and the importer being billed. Duty and tax computation runs in server scripts wired through hooks.py doc events (validate, on_submit) so every line recalculates deterministically on the server — never trusting client-side math — and posts recoverable costs and agency fees into ERPNext's accounting via Journal Entries and Sales Invoices so cost recovery lands on the customer ledger automatically.
The app is engineered the way a Frappe app should be. Client scripts drive the data-entry UX — auto-fetching duty rates when an HS code is picked, flagging incomplete declarations before submit. Whitelisted methods expose the calculation and job-status logic to the Frappe REST API so your port agents, a broker portal, or an external declaration system can integrate over HTTP with token auth. Role profiles and permission rules (Clearing Agent, Customs Officer, Accounts) scope who can submit a declaration versus who can post a disbursement. Scheduler events run the demurrage/detention accrual nightly — incrementing day counts, applying free-time rules per shipping line, and raising alerts as a container approaches its free-time expiry — so charges are captured the day they arise instead of being discovered on an invoice weeks later. It is built and tested against Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing ships as an anonymous download. We start with a scoping call to map your declaration workflow, tariff sources, ports, and the charges you recover from importers, then confirm a fixed scope. Typical delivery is one working week from confirmed scope. You get the installable app source for your ERPNext version, installation and configuration on your bench, UAT on a staging site with a rollback plan, technical documentation, a user guide with a live training session, a git repository handover, and a post-go-live support window.
ما تحصل عليه
- Installable Frappe app source code built for your ERPNext version (v15 or v16)
- Installation and configuration on your bench, including DocTypes, role profiles, and scheduler events
- UAT on a staging site with a documented rollback plan before production go-live
- Technical documentation — DocType schema, hooks, whitelisted methods, and server-script logic
- User guide plus a live training session for clearing agents and accounts staff
- Git repository handover with full commit history and README
- Post-go-live support window for defect fixes and configuration adjustments
- Configuration of HS-code tariff master and per-shipping-line demurrage free-time rules to your data
لمن هذا
Clearing & forwarding agency owner
Runs consignments through customs for multiple importers and needs each shipment tracked as a billable clearing job — declarations, disbursements, and agency fees recovered on the importer's ledger instead of reconciled from spreadsheets.
Import/export operations manager
Owns the declaration-to-clearance pipeline and needs bill-of-entry status, duty payable, and container free-time expiry visible in ERPNext so nothing stalls at port and no demurrage is discovered late.
Customs / compliance officer
Needs accurate HS-code classification and server-computed, auditable duty and tax on every declaration line, with role-based control over who can submit versus assess a declaration.
Accounts / finance lead
Needs disbursements and agency fees to post automatically into ERPNext accounting as invoices and journal entries, so cost recovery from importers and month-end reconciliation are clean and traceable.
كيف يقارن Customs Clearance & Clearing-Forwarding for ERPNext.
| المعيار | ECOSIRE | بناء مخصص | منافس | ERPNext الأصلي |
|---|---|---|---|---|
| Customs declaration & bill of entry | Dedicated `Customs Declaration` and `Bill of Entry` DocTypes with submittable workflow | Possible, but you design and maintain the schema yourself | Often generic freight/CRM DocTypes, not true customs declarations | No customs declaration concept at all |
| HS-code duty & tax computation | Server-side computation in hooks against an HS-code tariff master | Must be built and validated from scratch | Basic or region-locked; rarely server-enforced | Manual entry in Landed Cost Voucher, no HS logic |
| Clearing-agent job & cost recovery | `Clearing Job` links disbursements and auto-posts recovery to the importer | Buildable, but accounting wiring is your responsibility | Job tracking varies; cost recovery often manual | No clearing-job or agent cost-recovery model |
| Demurrage & detention tracking | Nightly scheduler accrual with per-line free-time rules and expiry alerts | Requires custom scheduler events and rule logic | Seldom included | Not supported |
| ERPNext v15/v16 fit | Built and tested against your exact bench version | Depends on your team's Frappe expertise | May lag on version compatibility | Core only — no customs features to fit |
| REST API & integrations | Whitelisted methods for duty and job status over the Frappe REST API | Build and secure the endpoints yourself | Limited or undocumented API surface | Generic Frappe REST API, no domain endpoints |
| Delivery & support | one working week from confirmed scope, UAT, training, git handover, support window | Timeline and support depend on internal capacity | Instant install but self-serve support | Immediate, but you build everything above yourself |
| Ownership | Full source and git repository handed over to you | You own it, but also own all the effort | Usually licensed, source not provided | You own core ERPNext; none of the customs capability |
الأسئلة المتداولة حول Customs Clearance & Clearing-Forwarding
How long does delivery take?
This is a build-to-order product, not an instant download. After a scoping call to confirm your declaration workflow, tariff sources, and charges, we fix the scope and typically deliver in one working week. Timing depends on the number of DocTypes, integrations, and duty-computation rules in the confirmed scope.
How is this different from just customising stock ERPNext?
It's a proper installable Frappe app with dedicated DocTypes (`Customs Declaration`, `Bill of Entry`, `HS Code`, `Clearing Job`), server scripts, hooks, and scheduler events — versioned and upgrade-safe. Piling one-off customisations onto core DocTypes is fragile and hard to maintain across ERPNext upgrades; a scoped app is not.
Which ERPNext versions do you support?
The app is built and tested against Frappe/ERPNext v15 and v16. Tell us your exact bench version during scoping and we target it; the source is handed over so it stays maintainable as you upgrade.
Do you provide support and updates after go-live?
Yes. Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your team or ECOSIRE can extend it later; longer-term support and enhancement retainers are available on request.
Can it integrate with a customs portal or external systems?
Yes. Business logic is exposed through whitelisted (`@frappe.whitelist()`) methods over the Frappe REST API with token authentication, so declarations, duty calculations, and job status can be pushed to or pulled from broker portals, port systems, or a customs gateway. Specific external integrations are scoped and quoted per your requirement.
How is duty and tax calculated — can I trust the numbers?
All duty and tax computation runs server-side in `hooks.py` doc events on `validate` and `on_submit`, against the HS-code tariff master and assessable value. Nothing relies on client-side math, so figures are deterministic, auditable, and recompute consistently every time a declaration is saved or submitted.
Will duties and disbursements flow into our accounting?
Yes. Clearing-job disbursements and agency fees post into ERPNext accounting as Sales Invoices and Journal Entries against the correct importer and expense accounts, and import duties can flow into item valuation via landed cost where you also stock goods — so cost recovery and reconciliation stay inside ERPNext.
الوحدات ذات الصلة

ClickPost Logistics Intelligence Connector for ERPNext
A build-to-order Frappe app that wires ClickPost's multi-carrier engine into ERPNext, adding smart courier allocation, unified labels and manifests, real-time tracking with ETA prediction, and an NDR/NPR resolution workflow. ECOSIRE scopes, builds, installs, and supports it for your instance.

COD Reconciliation & Remittance for ERPNext
A build-to-order ERPNext app that matches carrier remittance files against your COD sales orders, flags short-payments and RTO adjustments, and gives you a per-carrier aging view. ECOSIRE scopes, builds, installs, and supports it on your Frappe v15/v16 bench.

Delhivery Shipping Connector for ERPNext
A build-to-order Frappe app that wires Delhivery One directly into ERPNext v15/v16 — pincode serviceability, live rate quotes, waybill and label generation, COD reconciliation, and pickup scheduling, all driven from your Delivery Note and Sales Order flow. ECOSIRE builds it to your scope, installs it on your bench, and supports it after go-live.

Delivery Route Optimization for ERPNext
A build-to-order ERPNext extension that adds map-based route optimization, automatic stop sequencing, per-stop ETAs, and a driver navigation view on top of the native Delivery Trip. ECOSIRE scopes, builds, installs, and supports it for your fleet.
Customs Clearance & Clearing-Forwarding
A build-to-order ERPNext application that runs the full customs-clearance lifecycle — declarations, HS-code duty and tax computation, bill-of-entry document tracking, and clearing-agent job costing. ECOSIRE scopes, builds, installs, and supports it for your import/export operation.
- `Customs Declaration` and `Bill of Entry` DocTypes with submittable workflow states (Draft, Submitted, Assessed, Cleared) and per-line child tables
- `HS Code` tariff master with duty rate, VAT/GST rate, and unit-of-measure, auto-fetched into declaration lines via client script
- Server-side duty and tax computation in `hooks.py` doc events (`validate`/`on_submit`) — assessable value, ad-valorem and specific duties, never client-trusted
- Clearing-agent `Clearing Job` DocType linking consignment, declarations, disbursements, and the importer being billed