商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $249.00 USD
- ERPNext のバージョン
- —
- セットアップ時間
- 30分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
Aramex Shipping Connector for ERPNext
A build-to-order ERPNext app that connects Aramex directly to your Delivery Notes — generate AWB labels, book COD shipments, create pickups, and track parcels without leaving ERPNext. ECOSIRE scopes, builds, installs, and supports it for your GCC/MENA operation.
$249.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
`Aramex Settings` single DocType holding account number, PIN, entity, source, and default pickup address — no hardcoded credentials, stored in site config
`hooks.py` `doc_events` hook on `Delivery Note` submit that calls the Aramex `CreateShipments` API and writes the returned AWB back to the document
Air waybill (AWB) label PDF retrieved from the Aramex response and attached to the Delivery Note via the Frappe File API for one-click printing
Cash-on-delivery shipments with COD amount, currency, and returned COD reference stored on a dedicated `Aramex Shipment` DocType for reconciliation
Rate & Calculator API lookup so staff preview shipping cost and available services before booking a shipment
`FetchCities` city/service-availability lookup that validates the destination and prevents un-serviceable addresses at entry
Pickup creation via the Aramex `CreatePickup` service, scheduling warehouse collection directly from ERPNext
Frappe scheduler event polling `TrackShipments` on a configurable cadence, updating shipment status and stamping the source document
Whitelisted server-side methods exposed over the Frappe REST API for storefront or headless booking and tracking triggers
Client script adding contextual 'Book Shipment' / 'Book COD' / 'Track' actions to the Delivery Note form for authorized roles
Role profile and permission rules so only fulfilment and shipping roles can call Aramex actions or edit settings
All API failures captured in the Frappe Error Log with request context, plus idempotency guards to avoid double-booking on re-submit
Multi-currency and multi-warehouse aware — origin and COD currency resolved per company and source warehouse
Packaged as a versioned Frappe app compatible with ERPNext v15 and v16, installable via `bench get-app` / `bench install-app`
この製品について
GCC and MENA e-commerce sellers running ERPNext hit the same wall every fulfilment day: ERPNext core issues a Delivery Note but has no idea Aramex exists. Warehouse staff re-key each order into the Aramex portal, copy the returned AWB number back into a custom field by hand, print labels from a second browser tab, and chase COD reconciliation in a spreadsheet. Every manual hop is a wrong address, a mismatched weight, or a lost tracking number — and ERPNext's native Shipment DocType only models a generic carrier, with no Aramex Shipping & Rate Calculator API, no COD flag, and no live status feedback.
Aramex Shipping Connector for ERPNextを選ぶ理由
`Aramex Settings` single DocType holding account number, PIN, entity, source, and default pickup address — no hardcoded credentials, stored in site config
`hooks.py` `doc_events` hook on `Delivery Note` submit that calls the Aramex `CreateShipments` API and writes the returned AWB back to the document
Air waybill (AWB) label PDF retrieved from the Aramex response and attached to the Delivery Note via the Frappe File API for one-click printing
Cash-on-delivery shipments with COD amount, currency, and returned COD reference stored on a dedicated `Aramex Shipment` DocType for reconciliation
Rate & Calculator API lookup so staff preview shipping cost and available services before booking a shipment
`FetchCities` city/service-availability lookup that validates the destination and prevents un-serviceable addresses at entry
ECOSIRE builds a proper Frappe app — installed on your own bench, not a hosted middleman — that makes Aramex a first-class carrier inside ERPNext. The app ships as a versioned Frappe module with its own DocTypes (an Aramex Settings single for account number, credentials, and pickup defaults; an Aramex Shipment link that stores the AWB, label PDF, COD amount, and last-known status). A hooks.py doc_events hook on Delivery Note on submit calls a whitelisted server-side method that hits the Aramex CreateShipments endpoint, receives the air waybill, attaches the returned label to the document via the Frappe File API, and writes the AWB back onto the Delivery Note — no copy-paste. Rate and city-service lookups run through the Aramex FetchCities / rate calculator so staff pick a validated destination and see the cost before booking.
Cash-on-delivery is handled as a real shipment attribute: the COD amount and currency flow into the Aramex payload, the returned COD reference is stored for reconciliation, and a client script surfaces a one-click "Book COD" action on the Delivery Note form for users with the right role profile. Pickup creation posts to the Aramex CreatePickup service so the warehouse schedules a collection without leaving ERPNext, and a Frappe scheduler event polls TrackShipments on a configurable cadence, updating each Aramex Shipment's status and stamping the Delivery Note so support and customers see live movement. Everything is exposed over the Frappe REST API and whitelisted methods, so your storefront or a portal page can trigger a booking or read a tracking status programmatically. Credentials live in site config, all API calls are permission-gated by role, and failures are logged to the Frappe Error Log rather than swallowed.
This is a build-to-order engagement, not an instant download. We start with a short scoping call to confirm your Aramex account setup (account number, PIN, entity, source/origin), your Delivery Note workflow, COD reconciliation needs, and whether you're on ERPNext v15 or v16. From confirmed scope, typical delivery is 2 to 4 weeks: we build against your requirements, run UAT on a staging bench, then install on production with a rollback plan. You receive the full source as an installable Frappe app plus the git repository, so nothing is locked to us — but we stay on for a post-go-live support window to tune it against real Aramex traffic.
得られるもの
- Installable Frappe app (full source) built for your ERPNext v15 or v16 bench
- Installation and configuration on your bench, including Aramex credential setup and role assignment
- Technical documentation: DocType schema, hooks, whitelisted methods, scheduler events, and REST endpoints
- End-user guide plus a live training session for your fulfilment and support teams
- UAT on a staging bench with a documented test plan and a production rollback plan
- Post-go-live support window to tune the integration against real Aramex traffic
- Git repository handover — full commit history, no vendor lock-in
- Configured Aramex Settings, city-service lookups, and a validated end-to-end booking/tracking demo
これは誰のためのものですか
GCC/MENA e-commerce operations lead
Runs daily fulfilment on ERPNext and needs Aramex AWB generation, COD booking, and tracking to happen inside the Delivery Note flow instead of a second portal, cutting re-keying errors and reconciliation time.
ERPNext system administrator / partner
Owns the bench and wants a clean, versioned Frappe app with proper DocTypes, hooks, permissions, and Error Log handling — installable via bench and maintainable on v15/v16 without brittle customizations.
Finance / COD reconciliation manager
Needs COD amounts and Aramex COD references captured against each shipment so cash collected by the courier reconciles against ERPNext sales, not a manual spreadsheet.
Growth-stage online retailer scaling regional shipping
Shipping hundreds of parcels across the UAE, KSA, and wider MENA, wants city-service validation and live tracking exposed to customers and support without adding headcount at the warehouse.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Aramex Shipping Connector for ERPNext アプリの ZIP をダウンロードします。
アプリをベンチに追加する
ZIP をベンチのアプリ フォルダーに抽出するか、抽出されたアプリへのパスを指定して「bench get-app」を実行します。
サイトにインストールする
`bench --site SITE_NAME install-app APP_NAME` を実行し、続いて `bench maigrate` を実行して、Aramex Shipping Connector for ERPNext をインストールし、そのスキーマを適用します。
ライセンスをアクティベートする
サイトの ECOSIRE ライセンス設定を開き、ライセンス キーをアクティブ化します。無料の ecosire_connect アプリと ecosire_license_client アプリが必要です。
Aramex Shipping Connector for ERPNext の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Aramex API coverage | AWB, COD, pickup, rate, city lookup, and tracking wired end-to-end | Whatever you scope and have time to build | Often generic label-only, partial Aramex support | |
| COD support | COD amount + Aramex reference stored for reconciliation | Possible but must be built and tested from scratch | Frequently missing or basic | |
| ERPNext integration depth | Delivery Note hooks, DocTypes, scheduler, REST methods | Depends on your team's Frappe expertise | Bolt-on, may not follow your workflow | |
| Fit to your process | Built to your confirmed scope and roles | Fully custom but you own all the risk | Take-it-or-leave-it feature set | |
| Version compatibility | Built and tested for your v15 or v16 bench | You maintain compatibility yourself | May lag ERPNext releases | |
| Delivery time | 2-4 weeks from confirmed scope | Weeks to months depending on staffing | Instant install, but generic | |
| Ownership & lock-in | Full source + git repo handover, no lock-in | You own everything you build | Often closed-source or license-gated | |
| Support after launch | Post-go-live support window + optional ongoing | Only what your team provides | Vendor tickets, variable response |
Aramex Shipping Connector for ERPNext に関するよくある質問
+Is this an existing app I can download and install today?
No. This is a build-to-order engagement. ECOSIRE builds the Aramex connector against your specific Aramex account, Delivery Note workflow, and ERPNext version, then installs and supports it. You are not buying a pre-existing Frappe Cloud Marketplace download.
+How long does delivery take?
Typical delivery is 2 to 4 weeks from confirmed scope. We start with a short scoping call, lock the requirements, build against them, run UAT on a staging bench, and then install on production. Complex COD reconciliation or multi-entity setups can extend the timeline, which we flag during scoping.
+Which ERPNext versions are supported?
The app targets ERPNext and Frappe v15 and v16, packaged as a versioned Frappe app installable via `bench get-app` and `bench install-app`. We confirm your exact version and bench setup during the scoping call so the build matches your environment.
+What happens with support and updates after go-live?
You get a post-go-live support window to tune the integration against real Aramex traffic and fix any issues. Because you receive the full source and the git repository, you can maintain it yourself or engage ECOSIRE for an ongoing support and update arrangement — for example when Aramex changes an API or you upgrade ERPNext.
+Do I own the code, or is it locked to ECOSIRE?
You own it. Deliverables include the full installable Frappe app source and a git repository handover with commit history. There is no hosted middleman and no vendor lock-in — the app runs on your own bench.
+How does cash-on-delivery work in the integration?
COD is modeled as a real shipment attribute. The COD amount and currency flow into the Aramex `CreateShipments` payload, and the returned COD reference is stored on the `Aramex Shipment` DocType so finance can reconcile courier-collected cash against ERPNext sales rather than a manual spreadsheet.
+Can my storefront or another system trigger bookings and read tracking?
Yes. Booking and tracking are exposed through whitelisted server-side methods over the Frappe REST API, so a storefront, portal page, or external system can create shipments and read live tracking status programmatically, subject to role permissions.
見積もりを依頼
Aramex Shipping Connector for ERPNext
A build-to-order ERPNext app that connects Aramex directly to your Delivery Notes — generate AWB labels, book COD shipments, create pickups, and track parcels without leaving ERPNext. ECOSIRE scopes, builds, installs, and supports it for your GCC/MENA operation.
- `Aramex Settings` single DocType holding account number, PIN, entity, source, and default pickup address — no hardcoded credentials, stored in site config
- `hooks.py` `doc_events` hook on `Delivery Note` submit that calls the Aramex `CreateShipments` API and writes the returned AWB back to the document
- Air waybill (AWB) label PDF retrieved from the Aramex response and attached to the Delivery Note via the Frappe File API for one-click printing
- Cash-on-delivery shipments with COD amount, currency, and returned COD reference stored on a dedicated `Aramex Shipment` DocType for reconciliation