GLS Shipping Connector for ERPNext

Key Features

Per-country GLS API credentials, contract IDs, and default service flags stored in a `GLS Settings` single DocType, keeping each depot (DE/FR/NL/etc.) isolated

`GLS Shipment` DocType linked to ERPNext `Delivery Note` and `Shipment`, holding parcel number, tracking URL, chosen service, and the returned label PDF

Live GLS rate and service lookup at quotation/sales-order time via whitelisted server methods, so users select the correct product before confirming

Label generation on `Delivery Note` `on_submit` (or an explicit button) that writes the GLS PDF back as a document attachment

ParcelShop delivery support, including recipient ParcelShop selection and the corresponding GLS product code

Express and standard doorstep services exposed as fields and passed through to the GLS API

COD service flag with amount and currency passed to GLS, and collection status reconciled back onto the shipment

Scheduler event (configurable interval via `scheduler_events` in `hooks.py`) that polls GLS track-and-trace and updates status, timestamps, and delivery state

`hooks.py` doc-event handlers on `Delivery Note`/`Shipment` for label, cancel, and status sync — no core file patching

Client script that renders the GLS action buttons and validates required address/weight fields before an API call

Dedicated role and role profile so only shipping/warehouse staff can generate labels or view credentials

Full request/response logging of GLS API calls for audit and support debugging

Frappe REST API-exposed whitelisted methods so external systems (WMS, portals) can trigger rating and labels

Idempotent label creation and cancel/void handling so re-submitting a Delivery Note does not double-charge parcels

Built and tested for Frappe/ERPNext v15 and v16

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

EU distributors and merchants running ERPNext on GLS hit the same wall: ERPNext core has a Shipment DocType and a delivery workflow, but no native connection to a carrier API. That means warehouse staff re-key every consignment into the GLS web portal, copy tracking numbers back by hand, guess at freight cost on the sales order, and reconcile COD collections in a spreadsheet. There is no live rate at quotation time, no automated label on Delivery Note submit, and no status feedback once a parcel leaves the dock. As order volume grows across multiple GLS country depots, this manual bridge becomes the bottleneck and the error source.

ECOSIRE builds a dedicated GLS Shipping Connector as a proper Frappe app installed on your own bench. At its core is a GLS Settings single DocType that stores per-country API credentials, contract IDs, and default service flags — so a group running through GLS Germany, France, and the Netherlands keeps each depot's authentication and product codes isolated. A GLS Shipment DocType links to the ERPNext Delivery Note and Shipment, capturing the parcel number, tracking URL, service used, and returned label. Whitelisted server methods call the GLS REST/SOAP endpoints for rating, label creation (ParcelShop delivery, express, and standard doorstep), and status polling, with all requests logged for auditability.

Technically, the connector wires into ERPNext through hooks.py document events and the Frappe scheduler. A Delivery Note on_submit hook (or an explicit button rendered by a client script) triggers label generation, writes the returned PDF back to the document as an attachment, and stamps the parcel number onto the record. A quotation-time server call returns live GLS rates and available services so sales users pick the right product before the order is confirmed. A scheduled event polls GLS track-and-trace on a configurable interval and updates shipment status, delivery timestamps, and — for COD parcels — collection state, so ERPNext reflects the carrier's truth without anyone opening the GLS portal. COD and express service flags are surfaced as fields on the shipment and passed through to the API. Access is governed by a dedicated role and role profile, so only shipping and warehouse users can generate labels or edit credentials.

Because every GLS contract, product catalogue, and country depot differs, this is a build-to-order engagement, not a one-click marketplace download. We start from a short scoping call to confirm your GLS country accounts, the services you actually ship (standard, express, ParcelShop, COD), your ERPNext version, and any print/label-format requirements. We then build and unit-test against your exact GLS credentials, deliver on a staging bench for UAT, and cut over to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, and you receive the full source in a Git repository you own — no black box, no per-parcel SaaS fee.

What you get

Installable source code for the GLS Shipping Connector app, built for your ERPNext version (v15 or v16)

Installation and configuration on your bench, including GLS per-country credential and service setup

UAT on a staging site with your real GLS test credentials, plus a documented rollback plan before production cutover

Technical documentation: DocType reference, `hooks.py` events, whitelisted methods, and scheduler configuration

End-user guide plus a live training session for your shipping and warehouse team

Post-go-live support window for bug fixes and adjustments

Handover of the complete Git repository, owned by you with full commit history

Configuration workbook mapping your GLS products/services to ERPNext service selections

Who this is for

EU distributor / merchant on ERPNext using GLS

Ships high parcel volume across one or more GLS country depots and needs rating, labels, and tracking inside ERPNext instead of the GLS portal, without re-keying every consignment.

Warehouse / logistics manager

Owns dispatch throughput and label accuracy; wants a one-click label on Delivery Note submit, automatic tracking sync, and COD reconciliation so staff stop copy-pasting parcel numbers.

ERPNext system administrator / Frappe developer

Maintains the bench and cares that the integration is a clean Frappe app using hooks and whitelisted methods — not core patches — with source they own and can extend on v15/v16.

Finance / COD reconciliation lead

Needs COD collection status and amounts flowing back into ERPNext against the right shipment so cash-on-delivery is reconciled without a side spreadsheet.

How GLS Shipping Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
GLS API rating & labels	Live rating, label generation, ParcelShop, express, and COD built to your contract	Possible but you specify and build every endpoint yourself	Generic mapping that rarely fits your exact GLS products	None — no carrier API in ERPNext core
ERPNext integration	Clean Frappe app via `hooks.py` events and whitelisted methods, no core patches	Depends entirely on your team's discipline	Varies; some patch core or override DocTypes	Manual `Shipment` DocType with no carrier link
Per-country GLS accounts	Isolated credentials and service flags per depot in `GLS Settings`	Build it yourself if you need it	Often single-account only	Not applicable
Track & trace sync	Scheduled polling updates status, timestamps, and COD collection	You design and schedule it	Sometimes; often manual refresh	None
Version support	Built and tested for v15 and v16, targeted to your bench	Whatever you validate	Depends on maintainer's update cadence	Ships with ERPNext but no GLS features
Code ownership	Full Git repository handed over, yours to extend	You own it because you wrote it	Usually closed or license-restricted	Open source but no connector
Delivery & support	2-4 weeks build-to-order, UAT + rollback, post-go-live support window	Your internal timeline and backlog	Instant download, self-support or forum	Immediate but nothing to configure
Total cost profile	One-time build, no per-parcel fee	Developer time plus ongoing maintenance you carry	Low upfront, possible per-seat or SaaS fees	Free but staff absorb the manual labour

Frequently Asked Questions about GLS Shipping Connector for ERPNext

How long does delivery take?

This is a build-to-order engagement. Typical delivery is 2-4 weeks from confirmed scope — that is, after our scoping call fixes your GLS country accounts, services, ERPNext version, and label requirements. Simpler single-country builds land toward the shorter end; multi-depot or COD-heavy setups toward the longer end. You get a firm timeline in the quotation.

Is this an instant download from the Frappe marketplace?

No. It is not an existing marketplace app you download and self-install. ECOSIRE builds it against your specific GLS contract and ERPNext bench, tests it on staging with your credentials, installs it on production, and hands over the source. Because every GLS contract and product catalogue differs, a one-size download would not reliably rate or label your parcels.

Which ERPNext and Frappe versions are supported?

We build and test for Frappe/ERPNext v15 and v16. Tell us your exact version and bench setup on the scoping call and we target it precisely. The app is a standard Frappe app installed on your bench — no core files are patched, so it survives normal `bench update` cycles.

What happens with support and updates after go-live?

Every engagement includes a post-go-live support window for bug fixes and adjustments to what we delivered. Because you receive the full Git repository, your own team can also extend it. Beyond the included window we offer optional support/maintenance retainers covering GLS API changes and new ERPNext version compatibility.

Do you handle GLS COD and express services?

Yes. COD is passed to GLS with amount and currency and the collection status is reconciled back onto the shipment record; express and ParcelShop are selectable services on the shipment and passed through to the API with the correct GLS product codes. We confirm exactly which services your contract enables during scoping.

Can multiple GLS country accounts run from one ERPNext instance?

Yes. The `GLS Settings` DocType holds per-country credentials, contract IDs, and default service flags, so a group shipping through GLS Germany, France, the Netherlands, and others keeps each depot's authentication and product codes isolated while sharing one ERPNext install.

Do we own the code, and can external systems trigger it?

You own the complete source in a Git repository handed to you at go-live — no black box and no per-parcel SaaS fee. Rating and label generation are exposed as whitelisted methods reachable through the Frappe REST API, so a WMS, storefront, or portal can trigger them programmatically with the appropriate role permissions.