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 one working week from confirmed scope, and you receive the full source in a Git repository you own — no black box, no per-parcel SaaS fee.