Build-to-order GLS parcel integration for Odoo: labels, live rates, tracking sync, returns and multi-parcel — built and installed by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $199.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
Build-to-order GLS parcel integration for Odoo: labels, live rates, tracking sync, returns and multi-parcel — built and installed by ECOSIRE.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
The GLS Shipping Connector is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your specific GLS contract and warehouse workflow. This is not an off-the-shelf apps.odoo.com download — after purchase, our Odoo engineers develop the module against your GLS API credentials and country pack, then deliver a tested, production-ready delivery-carrier integration to your instance within a typical 2–4 week lead time.
It plugs GLS directly into Odoo's native delivery.carrier framework so your team keeps working inside the standard Inventory and Sales screens. When a picking is validated, the module calls the GLS API to register the consignment, generate the parcel labels (PDF or thermal ZPL from a QWeb report), write back the tracking number, and update the delivery status — no copy-pasting into a separate GLS portal. Live rate retrieval surfaces GLS shipping options and prices at the sale-order and website-checkout stage, so quoted freight matches what you are actually billed.
Under the hood the module is built the Odoo-correct way: a proper __manifest__.py declaring dependencies (stock, delivery, sale), new/extended models via models.Model with typed fields and @api.depends computed values (weight, parcel count, rate), access control through ir.model.access.csv plus record rules so only shipping and warehouse roles touch carrier data, XML/OWL views for the GLS configuration and label actions, and QWeb report templates for the labels and consignment manifest. GLS credentials and depot settings live in encrypted config parameters, and every API call is logged for traceability. Automated actions (server actions / scheduled ir.cron) poll GLS for tracking events and sync parcel status back onto the delivery order and the customer portal.
Because we build it to your exact GLS country service (GLS operates across Germany, France, Italy, Spain, Benelux, Poland and the wider EU), your product mix and your Community or Enterprise edition, you avoid the compromises of a generic connector: correct service codes, your negotiated rate table, the right label format for your printers, and clean handling of multi-parcel consignments. You own the source code, and ECOSIRE stands behind it with a support window and version compatibility across Odoo 17, 18 and 19.
Runs an online store shipping parcels across the EU with GLS as a primary carrier. Needs live rates at checkout, one-click labels on picking validation and automatic tracking so customers self-serve status without support tickets.
Owns daily dispatch out of one or more warehouses. Wants GLS labels printed directly from Odoo, multi-parcel consignments handled cleanly and dispatch throughput that does not depend on re-keying orders into the GLS web portal.
Responsible for the Odoo instance and its integrations. Needs a maintainable, source-available module with proper security roles, logging and version support across Odoo 17/18/19 rather than a black-box connector they cannot audit.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Fit to your exact GLS contract, services and country pack | Built to your negotiated GLS services, rate table and country pack | Achievable but you specify and maintain every detail yourself | Generic service codes; may not match your contract | |
| Live GLS rates at sale order and checkout | Yes — live rates matched to your tariff | Only if you build the rating call correctly | Sometimes; often flat or estimated rates | |
| Label printing (PDF and thermal ZPL) from Odoo | Yes — QWeb labels tuned to your printers | You build the report and format yourself | Usually PDF only; ZPL varies | |
| Multi-parcel consignments and GLS return labels | Yes — both, mapped to your GLS service | Requires significant extra development | Partial; returns/multi-parcel often missing | |
| Source code ownership and auditability | You own the source; proper security roles and logging | You own it, but carry full build cost and risk | Usually closed-source, vendor-locked | |
| Delivery time to a working integration | 2–4 weeks, installed and UAT-signed by ECOSIRE | Months of in-house development and testing | Instant install but then self-integration and fixes | |
| Version support and post-delivery support window | Odoo 17/18/19 with a defined support/bug-fix window | You maintain it across every Odoo upgrade | Depends on the third-party vendor's roadmap |
No. This is a build-to-order module. After you purchase, ECOSIRE's Odoo engineers develop the GLS connector against your specific GLS contract, country service, printers and Odoo edition, then install it on your instance. It is not an existing apps.odoo.com download, so there is no instant zip to self-install.
Typical lead time is 2–4 weeks from when we receive your GLS API credentials and shipping requirements. Timing depends on scope — number of GLS services, label formats, warehouses and any marketplace or WMS integration. We confirm a firm schedule during kickoff and validate everything on staging before production go-live.
Every build includes a post-delivery support and bug-fix window plus version-compatibility maintenance so the module keeps working across Odoo 17, 18 and 19. During the window we fix defects and help your team. After it ends, we offer ongoing support and update plans, and because you receive the source code you are never locked to a single vendor.
We build for Odoo 17, 18 and 19, on Community or Enterprise. The module uses Odoo's native delivery.carrier framework and standard Inventory/Sales screens, so it fits your existing setup rather than replacing it. We target your exact version and edition so there are no surprises on upgrade.
Yes. The connector supports GLS ShopReturn / return labels generated from the original shipment or a return picking, and it handles multi-parcel consignments where one delivery is split into several parcels, each with its own weight, label and tracking number. Both are configured to match your GLS service agreement.
You receive the module source and own it. It is built the Odoo-correct way with access control via ir.model.access.csv and record rules restricting carrier configuration and label actions to shipping/warehouse roles, encrypted storage of GLS credentials in system parameters, and full logging of API calls for traceability.
Yes. Because the module lives inside standard Odoo models, an external WMS, ERP or marketplace can create shipments and pull labels/tracking via Odoo's XML-RPC/JSON-RPC API. We can scope this integration as part of the build if you need programmatic dispatch.
Build-to-order GLS parcel integration for Odoo: labels, live rates, tracking sync, returns and multi-parcel — built and installed by ECOSIRE.