Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $299.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
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.
$299.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
`ClickPost Settings` single DocType storing API key and account credentials in Frappe encrypted password fields, with sandbox/production environment toggle
`Courier Allocation Rule` DocType: priority-ordered rules matching on serviceable pincode/zone, weight bracket, COD vs prepaid, SLA, and per-carrier cost — resolved server-side to auto-pick the optimal courier
Serviceability and pincode-check calls to ClickPost run before allocation so non-serviceable carriers are excluded from the decision
AWB registration and label generation triggered on Delivery Note submit via `hooks.py` doc events, with the shipping-label PDF attached to the document
Unified manifest generation across mixed carriers, printable from a client-script action button on the ERPNext form
Real-time tracking via a `scheduler_events` cron poll that writes normalized status transitions into a `Shipment Tracking Event` child table
ETA prediction pulled from ClickPost surfaced on the Sales Order and Delivery Note, updated on each poll
Inbound ClickPost webhook received by a whitelisted `@frappe.whitelist(allow_guest=True)` endpoint with signature/token verification
`NDR Resolution` DocType with a Frappe Workflow (Open → Reattempt → Address Update → RTO → Closed) for structured non-delivery handling
NPR (non-pickup) events routed into the same resolution queue so warehouse pickup failures are tracked, not dropped
All outbound carrier calls run through `frappe.enqueue` background jobs with retry/backoff so the ERPNext UI never blocks on a carrier API timeout
Dedicated role profile and permission rules so ops staff work the NDR/tracking queue without broad system access
Frappe REST API and whitelisted methods exposed for allocation, label fetch, and tracking so external channels (marketplace/OMS) can trigger the flow
Idempotent shipment registration keyed on Delivery Note name to prevent duplicate AWBs on resubmit or retry
Über dieses Produkt
Mid-market retailers running ERPNext outgrow its native shipping quickly. ERPNext core gives you a Shipment DocType, a handful of Shipping Rule records, and manual tracking-number fields — but it has no concept of rule-based carrier selection, no live status ingestion, and no structured way to work a non-delivery. When you ship across five or ten couriers, teams end up allocating orders in spreadsheets, pasting tracking IDs into carrier portals one at a time, and chasing failed deliveries over email. The cost is real: higher RTO rates, WISMO tickets, and working capital stuck in packages that will never be delivered. ClickPost solves the aggregation and intelligence layer, but nothing connects it cleanly into ERPNext's order-to-cash flow.
Warum ClickPost Logistics Intelligence Connector for ERPNext wählen
`ClickPost Settings` single DocType storing API key and account credentials in Frappe encrypted password fields, with sandbox/production environment toggle
`Courier Allocation Rule` DocType: priority-ordered rules matching on serviceable pincode/zone, weight bracket, COD vs prepaid, SLA, and per-carrier cost — resolved server-side to auto-pick the optimal courier
Serviceability and pincode-check calls to ClickPost run before allocation so non-serviceable carriers are excluded from the decision
AWB registration and label generation triggered on Delivery Note submit via `hooks.py` doc events, with the shipping-label PDF attached to the document
Unified manifest generation across mixed carriers, printable from a client-script action button on the ERPNext form
Real-time tracking via a `scheduler_events` cron poll that writes normalized status transitions into a `Shipment Tracking Event` child table
ECOSIRE builds that connection as a proper Frappe app — a dedicated clickpost_connector module with its own DocTypes, not a pile of custom fields bolted onto stock forms. We add a ClickPost Settings single DocType holding your API credentials (stored encrypted via Frappe's password fieldtype), environment toggle, and default account mappings. Courier allocation is driven by a Courier Allocation Rule DocType — priority-ordered rules matching on pincode/zone, weight, payment mode (COD vs prepaid), SLA, and serviceability, resolved server-side so the cheapest serviceable carrier wins automatically. Outbound calls to ClickPost's API run through whitelisted server methods and Frappe's enqueue background jobs so the UI never blocks on a carrier timeout, with ret/backoff on transient failures.
On the ERPNext side, hooks.py doc events fire the integration at the right moments: on Delivery Note submit we register the shipment, request an AWB, and pull back a Shipment Package record with the label PDF and manifest attached to the document. A scheduled event (scheduler_events) polls ClickPost's tracking endpoint on a cadence you choose, writing normalized status transitions into a Shipment Tracking Event child table and surfacing the predicted ETA on the Sales Order and Delivery Note. When ClickPost reports an NDR (non-delivery report) or NPR (non-pickup report), a webhook received by a whitelisted endpoint opens an NDR Resolution DocType — a workflow with states like Open, Reattempt Requested, Address Updated, RTO Initiated, and Closed — assigned to your ops role profile so failed deliveries become a tracked queue instead of lost email. Client scripts add action buttons (Generate Label, Reprint Manifest, Track Now, Raise Reattempt) directly on the ERPNext forms your team already uses.
Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm your ClickPost account setup, carrier mix, allocation logic, and which ERPNext documents drive the flow. We then build against your Frappe/ERPNext v15 or v16 instance, deliver on a staging site for UAT, and only promote to production once you sign off — with a rollback plan and the full git repository handed to you. Typical delivery is 2–4 weeks from confirmed scope, followed by a post-go-live support window.
Was Sie bekommen
- Installable source code for your Frappe/ERPNext version (v15 or v16), packaged as a standard `clickpost_connector` app
- Installation and configuration on your instance, including ClickPost credential setup and initial allocation rules
- Technical documentation: DocType reference, hooks and scheduler events, whitelisted endpoints, and webhook setup
- User guide plus a live training session for your ops and shipping team
- UAT on a staging site with a documented rollback plan before production promotion
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history and README
- Configured `Courier Allocation Rule` set reflecting your carrier mix and business logic at go-live
Für wen das ist
ERPNext Ops / Logistics Manager
Owns dispatch across multiple couriers and needs allocation, labeling, and NDR handling to happen inside ERPNext instead of carrier portals and spreadsheets. Judged on RTO rate and on-time delivery.
Mid-market D2C / Retail Founder or COO
Runs ERPNext as the system of record and wants logistics intelligence to cut shipping cost and reduce failed deliveries without adding a separate shipping SaaS the team has to re-key orders into.
ERPNext System Administrator / In-house Developer
Maintains the Frappe instance and wants a clean, upgrade-safe app — proper DocTypes, hooks, and background jobs — with the git repo handed over so they can extend and support it internally.
Customer Support / Post-Purchase Lead
Fields WISMO and failed-delivery queries and needs live tracking, ETA, and a structured NDR resolution queue surfaced on the order so responses are accurate and reattempts are actioned fast.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der ClickPost Logistics Intelligence Connector for ERPNext-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um ClickPost Logistics Intelligence Connector for ERPNext zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie ClickPost Logistics Intelligence Connector for ERPNext im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Courier allocation | Rule-based auto-selection via `Courier Allocation Rule` DocType (zone, weight, COD, SLA, cost) | Possible, but you design and maintain the rule engine yourself | Often fixed or single-carrier; limited rule logic | |
| Multi-carrier tracking | Scheduled poll writes normalized status transitions + ETA onto the order | Build and maintain polling and normalization yourself | Basic tracking, often per-carrier and not normalized | |
| NDR / NPR resolution | Dedicated workflow DocType with states and ops role assignment | No standard pattern; fully bespoke build | Rarely handled inside ERPNext | |
| Labels & manifest | Unified label PDF + cross-carrier manifest from form buttons | Integrate each carrier's label API by hand | Varies; often carrier-specific formats | |
| ERPNext fit | Proper Frappe app: DocTypes, hooks, scheduler, whitelisted methods | Depends entirely on your team's discipline | Generic app; may not match your document flow | |
| Reliability under carrier timeouts | Background jobs via `frappe.enqueue` with retry/backoff; UI never blocks | You must design the async and retry handling | Often synchronous; UI can hang on carrier lag | |
| Ownership & extensibility | Full git repo handover; extend it in-house | You own it, but also own all the maintenance | Closed source; locked to vendor roadmap | |
| Support model | Scoping call, UAT, training, and a post-go-live support window | Whatever your internal team can staff | Generic ticket support, not instance-specific |
Häufig gestellte Fragen zu ClickPost Logistics Intelligence Connector for ERPNext
+Is this an app I can download and install instantly from the Frappe marketplace?
No. This is build-to-order. ECOSIRE builds the ClickPost connector against your specific ERPNext instance, carrier mix, and allocation logic, then installs and supports it. It is not an existing off-the-shelf marketplace download, so nothing ships until we confirm scope with you first.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on the number of couriers, the complexity of your allocation rules, and how many ERPNext documents drive the flow. We agree the scope and timeline on the initial scoping call before any build starts.
+Which ERPNext and Frappe versions are supported?
We build for Frappe/ERPNext v15 and v16. We target your running version so the app installs cleanly, and we keep to standard Frappe app structure (DocTypes, `hooks.py`, scheduler events, whitelisted methods) to stay upgrade-safe.
+How do updates and support work after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your own team can maintain and extend the app. Beyond the included window, ECOSIRE offers ongoing support and enhancement work as a separate agreement.
+Do I need my own ClickPost account?
Yes. ClickPost is a separate logistics-intelligence platform with its own contract and carrier integrations. This connector wires your existing ClickPost account into ERPNext — we configure the API credentials, account mappings, and webhooks during installation.
+Will it overwrite or break my existing ERPNext customizations?
No. We deliver a self-contained `clickpost_connector` app with its own DocTypes rather than editing core files, and we validate everything on a staging site during UAT with a rollback plan. Production promotion only happens after you sign off.
+Can other systems trigger allocation or tracking, not just the ERPNext UI?
Yes. Core actions are exposed as whitelisted methods over the Frappe REST API, so an external OMS, marketplace integration, or channel manager can request allocation, fetch labels, or query tracking programmatically. We scope the exact endpoints you need during discovery.
Angebot anfordern
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.
- `ClickPost Settings` single DocType storing API key and account credentials in Frappe encrypted password fields, with sandbox/production environment toggle
- `Courier Allocation Rule` DocType: priority-ordered rules matching on serviceable pincode/zone, weight bracket, COD vs prepaid, SLA, and per-carrier cost — resolved server-side to auto-pick the optimal courier
- Serviceability and pincode-check calls to ClickPost run before allocation so non-serviceable carriers are excluded from the decision
- AWB registration and label generation triggered on Delivery Note submit via `hooks.py` doc events, with the shipping-label PDF attached to the document