Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $249.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
bpost Shipping Connector for ERPNext
A build-to-order bpost shipping integration for ERPNext that generates national and international labels, supports parcel-locker and pickup-point delivery, syncs live tracking, and handles COD directly from your Delivery Notes. ECOSIRE scopes, builds, installs, and supports it.
$249.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
`bpost Settings` single DocType storing API user, passphrase and account ID encrypted in site config, with a built-in Test Connection action against the bpost Shipping Manager API
Whitelisted server methods (e.g. `create_label`, `void_label`, `get_tracking`) exposed over the Frappe REST API so labels can be generated from the desk or from external systems
National and international label generation returning the bpost PDF/PNG, auto-attached to the Delivery Note via the File DocType for in-app printing
`hooks.py` `on_submit` doc event on `Delivery Note` that requests the label and writes back the bpost barcode, tracking number and tracking URL
Hourly `scheduler_events` job that polls open shipments and updates a `Tracking Status` field plus the document timeline with live bpost delivery events
Parcel-locker and pickup-point selection via a client script that fetches nearby bpost pickup points and stores the chosen point on the sales document
COD support that maps the ERPNext outstanding invoice amount into the bpost cash-on-delivery product and reconciles the collected amount
Custom fields added cleanly via fixtures for service product, parcel type, weight, insured value and delivery method on `Delivery Note` and `Shipment`
Dedicated bpost role and Role Profile so only authorized shipping staff can generate labels or edit carrier credentials
Idempotent label creation guarded against double-submit so re-submitting a Delivery Note never buys a second label
Structured API error handling that surfaces bpost validation errors (bad postcode, weight, unsupported product) back to the user with a readable message and Error Log entry
Weight and dimension validation before the API call so rejected shipments are caught in ERPNext rather than at the carrier
Multi-language address and print support suitable for NL/FR/EN Belgian operations
Tested and packaged for both Frappe/ERPNext v15 and v16 with a documented upgrade path
Bu Ürün Hakkında
Belgian ERPNext merchants shipping with bpost usually end up in one of two bad places: staff re-key every order into the bpost Shipping Manager web portal, or they buy a generic multi-carrier plugin that treats bpost as an afterthought and never surfaces parcel-locker choices, Belgian pickup points, or COD reconciliation. ERPNext core gives you a Shipment DocType and a Delivery Note, but it has no bpost Shipping Manager API client, no label PDF retrieval, no barcode/tracking storage, and no way to push a status back to the customer. That gap is exactly where hours leak and where mis-shipments and untracked parcels start costing money.
Neden bpost Shipping Connector for ERPNext
`bpost Settings` single DocType storing API user, passphrase and account ID encrypted in site config, with a built-in Test Connection action against the bpost Shipping Manager API
Whitelisted server methods (e.g. `create_label`, `void_label`, `get_tracking`) exposed over the Frappe REST API so labels can be generated from the desk or from external systems
National and international label generation returning the bpost PDF/PNG, auto-attached to the Delivery Note via the File DocType for in-app printing
`hooks.py` `on_submit` doc event on `Delivery Note` that requests the label and writes back the bpost barcode, tracking number and tracking URL
Hourly `scheduler_events` job that polls open shipments and updates a `Tracking Status` field plus the document timeline with live bpost delivery events
Parcel-locker and pickup-point selection via a client script that fetches nearby bpost pickup points and stores the chosen point on the sales document
ECOSIRE builds a proper Frappe app, ecosire_bpost, installed on your own bench alongside ERPNext — not a fragile set of pasted server scripts. It ships a bpost Settings single DocType (API user, passphrase, account ID, default product configuration) with credentials stored encrypted in the site config, plus per-shipment fields extended onto Delivery Note and Shipment for service product, parcel type, weight, insurance, and delivery method. Whitelisted methods exposed over the Frappe REST API — for example ecosire_bpost.api.create_label and ecosire_bpost.api.get_tracking — call the bpost Shipping Manager API, receive the label, and attach the returned PDF/PNG straight to the document via the File DocType so warehouse staff print from inside ERPNext.
Technically the automation is wired through hooks.py doc events and scheduler events rather than manual button-mashing. A Delivery Note on_submit handler can request a label and write back the bpost barcode and tracking URL; a scheduler_events hourly job polls open shipments and updates a Tracking Status field and timeline so customer-service sees live delivery progress without opening the bpost portal. Parcel-locker and pickup-point delivery is handled with a client script that lets the user pick a bpost pickup point (Cyclone/parcel-locker network) on the sales document before the label is generated. COD is supported by mapping the ERPNext outstanding amount into the bpost cash-on-delivery product and reconciling the collected amount back against the invoice. Access is governed by a dedicated Role and Role Profile so only shipping staff can generate labels or edit bpost credentials.
Because this is build-to-order, nothing is a pre-packaged download. We start with a short scoping call to confirm your bpost contract products (national, international, pickup points, COD), your Delivery Note workflow, and your Frappe/ERPNext version — the app targets and is tested on both v15 and v16. You approve a fixed scope, we build against a staging copy of your instance, run UAT there, and only then install on production with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the full source in a git repository so you are never locked to us.
Ne elde edeceksin
- Installable source for the `ecosire_bpost` Frappe app, pinned to your Frappe/ERPNext v15 or v16 version
- Installation and configuration on your bench, including bpost Settings, custom fields, roles and scheduler wiring
- Technical documentation: DocType reference, whitelisted API methods, hooks and scheduler events, and configuration guide
- End-user guide plus a live training session for your shipping and customer-service staff
- Post-go-live support window for bug fixes and questions after production install
- UAT on a staging copy of your instance with a documented, tested rollback plan
- Full git repository handover so you own and can extend the code
- Handover notes covering bpost contract product mapping and future ERPNext upgrade considerations
Bu kimin için
Belgian ERPNext e-commerce merchant
Ships domestic and cross-border parcels with a bpost contract and wants labels, pickup-point choice and tracking generated straight from the Delivery Note instead of re-keying orders into the bpost portal.
Warehouse / logistics lead
Needs one-click label printing, correct parcel type and weight validation, and reliable barcode capture so packers move faster and mis-shipments drop.
Customer-service manager
Wants live bpost tracking status visible inside ERPNext and on the timeline so agents can answer 'where is my parcel' without logging into a separate carrier tool.
ERP administrator / integrator
Responsible for the bench and upgrades; wants a clean installable app with encrypted credentials, proper roles, and source in git rather than undocumented server scripts.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden bpost Shipping Connector for ERPNext uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
bpost Shipping Connector for ERPNext yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
bpost Shipping Connector for ERPNext Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| bpost feature depth | Purpose-built for bpost: pickup points, COD, national and international products | Whatever you spec and can afford to build | Often generic multi-carrier with shallow bpost support | |
| Label generation | One-click from Delivery Note, PDF attached in ERPNext | Possible but built from scratch | Usually yes, but limited product options | |
| Live tracking sync | Hourly scheduler job updates status and timeline | Only if you build the polling job | Varies; sometimes tracking link only | |
| Fit to your workflow | Scoped to your Delivery Note process and roles | Fully bespoke but you manage the whole build | Fixed to the vendor's assumptions | |
| Code ownership | Full source in a git repo handed over to you | You own it if built in-house | Closed or vendor-locked in many cases | |
| Version support | Built and tested for v15 and v16 | Depends on your team's coverage | May lag behind ERPNext releases | |
| Time to live | 2 to 4 weeks from confirmed scope | Often months with in-house resourcing | Fast to install but slow to adapt | |
| Support and updates | Post-go-live window plus optional maintenance | Your team maintains it | Vendor SLA, quality varies |
bpost Shipping Connector for ERPNext hakkında Sıkça Sorulan Sorular
How long does delivery take?
This is build-to-order. After a scoping call to confirm your bpost products, Delivery Note workflow and ERPNext version, typical delivery is 2 to 4 weeks from confirmed scope. We build against a staging copy, run UAT, then install on production with a rollback plan.
Is this an existing app I can download and install today?
No. It is not a Frappe Cloud Marketplace download. ECOSIRE builds the `ecosire_bpost` app specifically for your instance and bpost contract, then installs and supports it. You receive the full source in a git repository at handover.
Which ERPNext versions are supported?
The app is built and tested for both Frappe/ERPNext v15 and v16. We confirm your exact version on the scoping call and pin the build to it, and we document the upgrade path for future major versions.
How do updates and support work after go-live?
Every build includes a post-go-live support window for bug fixes and questions. Because you own the git repository, your team or ours can extend the app later; ongoing maintenance or new features beyond the window are available as a separate engagement.
Do I need my own bpost account?
Yes. You provide your bpost Shipping Manager API credentials (API user, passphrase and account ID) and your contract products. We store the credentials encrypted in the site config and map your contract products into ERPNext during configuration.
Does it handle parcel lockers, pickup points and COD?
Yes. Users can select a bpost pickup point or parcel locker on the sales document before generating the label, and cash-on-delivery is supported by mapping the ERPNext outstanding amount into the bpost COD product with reconciliation back to the invoice.
Will it interfere with my existing ERPNext customizations?
No. It installs as a separate Frappe app using fixtures, hooks and whitelisted methods rather than overwriting core files, so it coexists with your other apps and survives migrations. We validate against your customizations during UAT on staging.
Teklif isteyin
bpost Shipping Connector for ERPNext
A build-to-order bpost shipping integration for ERPNext that generates national and international labels, supports parcel-locker and pickup-point delivery, syncs live tracking, and handles COD directly from your Delivery Notes. ECOSIRE scopes, builds, installs, and supports it.
- `bpost Settings` single DocType storing API user, passphrase and account ID encrypted in site config, with a built-in Test Connection action against the bpost Shipping Manager API
- Whitelisted server methods (e.g. `create_label`, `void_label`, `get_tracking`) exposed over the Frappe REST API so labels can be generated from the desk or from external systems
- National and international label generation returning the bpost PDF/PNG, auto-attached to the Delivery Note via the File DocType for in-app printing
- `hooks.py` `on_submit` doc event on `Delivery Note` that requests the label and writes back the bpost barcode, tracking number and tracking URL