商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $299.00 USD
- ERPNext のバージョン
- —
- セットアップ時間
- 30分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
ERPNext Aramex Shipping Connector
A build-to-order Frappe app that wires Aramex shipping into ERPNext — live rate shopping, one-click AWB and label generation from Delivery Notes, automatic tracking writeback, and COD cash-collection handling. Scoped, built, installed, and supported by ECOSIRE.
$299.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
`Aramex Settings` single DocType storing account number, credentials (encrypted `Password` fields), pickup addresses, and a sandbox/production toggle
Live rate shopping via the Aramex Rate Calculator API, callable from the Delivery Note and returned per available service/product group
One-click Shipment and AWB creation from a submitted `Delivery Note`, with the AWB number written back to the document
`hooks.py` `doc_events` automation on Delivery Note `on_submit` (auto-create) OR a client-script dispatch button — chosen during scoping
Label and dispatch-document generation as the carrier PDF, attached to the Shipment via the Frappe file system
Scheduler event (`scheduler_events`) that polls open AWBs and writes tracking milestones back onto the Shipment status and timeline
COD and cash-collection support: COD amount and currency captured on the shipment and passed to Aramex, with a reconciliation view
Whitelisted methods (`@frappe.whitelist()`) for `calculate_rate`, `create_shipment`, `print_label`, and `track_shipment` — the only carrier entry points
Frappe REST API access to every whitelisted method so external storefronts or WMS tools can rate and dispatch programmatically
Custom fields on `Delivery Note` and `Shipment` for AWB, service type, COD amount, weight, piece count, and live status
Role profiles and DocType-level permissions separating rate-shopping, dispatch, and COD reconciliation duties
Structured error handling and Frappe error logs on every API call, with sandbox smoke-tests before production credentials go live
Multi-pickup / multi-warehouse origin resolution so the correct dispatch address is used per order
Idempotent AWB creation guarding against duplicate shipments on re-submit or retried webhooks
Built for Frappe/ERPNext v15 and forward-verified against v16
この製品について
MENA and cross-border sellers running ERPNext hit a wall the moment fulfilment scales past a handful of daily orders. ERPNext core gives you a generic Shipment DocType and an address book, but it has no native Aramex integration — no live rate lookup, no AWB creation, no label PDF, and no tracking status flowing back onto the order. Teams end up re-keying every consignment into the Aramex portal, copying tracking numbers by hand, and reconciling COD cash collection in spreadsheets. That double entry is exactly where wrong weights, mismatched addresses, and lost parcels creep in.
ERPNext Aramex Shipping Connectorを選ぶ理由
`Aramex Settings` single DocType storing account number, credentials (encrypted `Password` fields), pickup addresses, and a sandbox/production toggle
Live rate shopping via the Aramex Rate Calculator API, callable from the Delivery Note and returned per available service/product group
One-click Shipment and AWB creation from a submitted `Delivery Note`, with the AWB number written back to the document
`hooks.py` `doc_events` automation on Delivery Note `on_submit` (auto-create) OR a client-script dispatch button — chosen during scoping
Label and dispatch-document generation as the carrier PDF, attached to the Shipment via the Frappe file system
Scheduler event (`scheduler_events`) that polls open AWBs and writes tracking milestones back onto the Shipment status and timeline
ECOSIRE builds a proper Frappe app — installed on your own bench as an aramex_connector module, not a fragile pile of pasted server scripts — that talks directly to the Aramex Shipping, Rate Calculator, and Tracking APIs. A dedicated Aramex Settings single DocType holds your account number, credentials, pickup addresses, and a sandbox/production toggle, with secrets kept in Frappe's encrypted Password fields rather than plain custom fields. Custom fields on Delivery Note and the standard Shipment DocType carry the AWB number, service/product group, COD amount, and live status, so shipping data lives on the same documents your team already works in.
Technically, the flow is deliberate. Whitelisted methods (@frappe.whitelist()) wrap each Aramex call — calculate_rate, create_shipment, print_label, track_shipment — and are the only entry points the UI and REST API touch. A hooks.py doc_events handler on Delivery Note on_submit can create the shipment and reserve the AWB automatically, or your team triggers it from a client-script button; which of the two we wire is decided during scoping. Labels and dispatch documents are pulled as the carrier PDF (or rendered through a Frappe Print Format) and attached to the document. A scheduler event registered in scheduler_events polls open AWBs on an interval and writes each milestone back to the Shipment status and timeline, so nobody refreshes the Aramex site. Role profiles and DocType permissions gate who can rate-shop, dispatch, and reconcile COD. Everything targets Frappe/ERPNext v15 and is forward-checked against v16.
Because this is build-to-order, there is no instant download. We start with a short scoping call, confirm your Aramex account type (domestic, international, COD, cash-on-delivery reconciliation), your ERPNext version and warehouse/pickup topology, then build against your sandbox. You review on a staging bench during UAT, we cut over with a rollback plan, and you receive the versioned source and Git repo. Typical delivery is 2–4 weeks from confirmed scope, depending on how many Aramex service products and COD workflows are in play.
得られるもの
- Installable source code for your ERPNext version (v15 or v16), delivered as a proper `aramex_connector` Frappe app
- Installation and configuration on your bench, including `Aramex Settings` wiring and sandbox-to-production credential cutover
- Technical documentation: DocType schema, whitelisted methods, hooks/doc-events, scheduler jobs, and REST endpoints
- End-user guide plus a live training session for your dispatch and finance teams
- UAT on a staging bench with a documented rollback plan before production cutover
- Post-go-live support window for bug fixes and adjustments (duration agreed at scoping)
- Git repository handover with full commit history and setup instructions
- Aramex sandbox test evidence (rate, shipment, label, tracking) captured before production go-live
これは誰のためのものですか
MENA e-commerce operations lead
Runs daily fulfilment across UAE/KSA/Egypt on ERPNext and needs Aramex AWBs, labels, and COD reconciliation created straight from Delivery Notes instead of re-keying every order into the carrier portal.
Cross-border D2C brand owner
Ships internationally via Aramex and wants live rate shopping at dispatch plus tracking that flows back onto the order, so customer-service can answer 'where is my parcel' without leaving ERPNext.
ERPNext implementation partner / systems integrator
Delivering an ERPNext rollout for a retail client and needs a maintainable, version-safe Aramex integration with clean source and docs to hand over, rather than building the carrier plumbing from scratch.
Finance / COD reconciliation manager
Owns cash-on-delivery collection and needs COD amounts captured on each shipment and a reconciliation view that ties Aramex cash-collection back to the ERPNext order and payment.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから ERPNext Aramex Shipping Connector アプリの ZIP をダウンロードします。
アプリをベンチに追加する
ZIP をベンチのアプリ フォルダーに抽出するか、抽出されたアプリへのパスを指定して「bench get-app」を実行します。
サイトにインストールする
`bench --site SITE_NAME install-app APP_NAME` を実行し、続いて `bench maigrate` を実行して、ERPNext Aramex Shipping Connector をインストールし、そのスキーマを適用します。
ライセンスをアクティベートする
サイトの ECOSIRE ライセンス設定を開き、ライセンス キーをアクティブ化します。無料の ecosire_connect アプリと ecosire_license_client アプリが必要です。
ERPNext Aramex Shipping Connector の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Aramex API coverage | Rate, shipment/AWB, label, and tracking wired end-to-end | Whatever you scope and have time to build | Often rates + label only; tracking patchy | |
| Fit to your workflow | Built to your Delivery Note, warehouse, and COD flow | Fully bespoke but you own every decision | Generic; you adapt to its assumptions | |
| COD & cash reconciliation | COD captured on shipment with reconciliation view | Only if you build it | Rarely tied back to ERPNext payments | |
| Automation | Auto-create on submit via doc_events or dispatch button | You wire your own hooks | Manual trigger typical | |
| Source & ownership | Full source + Git repo handover, no lock-in | You own it; you also maintain it | Often closed or per-shipment fees | |
| Version safety | Built for v15, forward-checked to v16 | Depends on your team's discipline | May lag ERPNext releases | |
| Support & updates | Post-go-live window + optional retainer | Your team or none | Vendor SLA varies; may be community-only | |
| Time to live | 2–4 weeks from confirmed scope | Weeks to months depending on team | Fast install but rework to fit |
ERPNext Aramex Shipping Connector に関するよくある質問
+How long does delivery take?
This is a build-to-order app, so there is no instant download. Typical delivery is 2–4 weeks from confirmed scope, depending on your Aramex account type (domestic, international, COD), the number of service products, and your ERPNext version. We begin the moment scope and sandbox credentials are agreed.
+Which ERPNext and Frappe versions are supported?
We build and test against Frappe/ERPNext v15 as the primary target and forward-verify against v16. Tell us your exact version at scoping and we build for it specifically; the app is a standard Frappe app installed via bench, not a patch to core.
+How does the integration actually connect to Aramex?
The app calls the Aramex Shipping, Rate Calculator, and Tracking APIs through whitelisted methods. Your account number and credentials live in an encrypted `Aramex Settings` DocType with a sandbox/production toggle, so nothing is hard-coded and you can test safely before going live.
+Do we get the source code, and can we modify it?
Yes. You receive the full versioned source and a Git repository handover with commit history. It is your code to run, extend, and maintain — there is no runtime lock-in or per-shipment SaaS fee to ECOSIRE.
+What about support and future updates?
Every build includes a post-go-live support window (agreed at scoping) covering bug fixes and adjustments. Beyond that, we offer optional maintenance retainers for Aramex API changes, ERPNext version upgrades, and new service-type or COD workflow requirements.
+Can it create shipments automatically, or only manually?
Both are supported and it is your choice. We can wire a `hooks.py` `doc_events` handler that creates the shipment and AWB automatically on Delivery Note submit, or a client-script dispatch button so your team triggers it deliberately. We confirm the workflow during scoping.
+Does it handle COD and cash collection?
Yes. The COD amount and currency are captured on the shipment, passed to Aramex, and surfaced in a reconciliation view so finance can tie cash-on-delivery collection back to the ERPNext order and payment.
見積もりを依頼
ERPNext Aramex Shipping Connector
A build-to-order Frappe app that wires Aramex shipping into ERPNext — live rate shopping, one-click AWB and label generation from Delivery Notes, automatic tracking writeback, and COD cash-collection handling. Scoped, built, installed, and supported by ECOSIRE.
- `Aramex Settings` single DocType storing account number, credentials (encrypted `Password` fields), pickup addresses, and a sandbox/production toggle
- Live rate shopping via the Aramex Rate Calculator API, callable from the Delivery Note and returned per available service/product group
- One-click Shipment and AWB creation from a submitted `Delivery Note`, with the AWB number written back to the document
- `hooks.py` `doc_events` automation on Delivery Note `on_submit` (auto-create) OR a client-script dispatch button — chosen during scoping