Shipping Label & Manifest Designer for Odoo

Typical lead time is 2 to 4 weeks from confirmed scope. Week one is discovery — we confirm your carriers, printer models, label sizes, manifest formats and access rules. We then build the module, deliver it in a staging environment for your review, apply revisions, and finally deploy to production with go-live verification. Simple single-carrier setups land closer to two weeks; multi-carrier or RPC-integrated builds toward four. This is a custom build-to-order engagement, not an instant apps.odoo.com download.

Every engagement includes a post-go-live support and bug-fix window during which we resolve any defects and fine-tune templates at no extra charge. Because we hand over the full module source, your team can maintain and extend it freely afterward. We also offer an optional ongoing support and Odoo-version-upgrade retainer — for example carrying the module forward from Odoo 17 to 18 to 19, or adding new carriers and label formats as your operation grows.

Yes. The module outputs native ZPL for Zebra and compatible thermal printers (TSC, Godex and others that speak ZPL), and QWeb-generated PDF for any A4/office printer. During discovery we build a template per carrier and printer size to match each courier's label and AWB specification. If a carrier requires a particular barcode symbology, field layout or manifest format, we configure it as part of the build.

It works on both Community and Enterprise, across Odoo 17, 18 and 19. It builds on the standard Inventory (stock) app that ships with Community, so you do not need Enterprise-only apps. If you already run official carrier connectors, this module complements them by giving you full control over label and manifest design where their fixed formats fall short.

The module is written to Odoo best practice — proper __manifest__.py dependencies, standard ORM models, QWeb reports and ir.model.access.csv security — which keeps it upgrade-friendly. We hand over the complete source, so you own it. You (or we, under a retainer) can add carriers, tweak templates, or migrate it to the next Odoo version. Nothing is locked behind a subscription or an opaque binary.

Yes. We expose the print and manifest actions over Odoo's XML-RPC and JSON-RPC API, so a scan station, WMS, or courier-desk application can request a label or generate the end-of-day manifest headlessly. We deliver sample calls and integration notes as part of the handover so your developers can wire it into existing floor tooling.