Build-to-order Odoo module for custom shipping labels, AWBs and end-of-day manifests across any carrier and printer. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
ایپ مینی فیسٹ
آپ کے ورک فلو کے مطابق تیار کردہ
Build-to-order Odoo module for custom shipping labels, AWBs and end-of-day manifests across any carrier and printer.
خود سیٹ اپ کی ضرورت نہیں — ایک کام کرنے والی ایپ جو ECOSIRE بناتا، انسٹال اور سپورٹ کرتا ہے۔
ایک بار کی تعمیر کی قیمت سے آغاز کریں۔ آغاز پر ہم آپ کے ساتھ مل کر دائرہ کار طے کرتے ہیں۔
ECOSIRE اسے آپ کے Odoo پر بناتا، ترتیب دیتا اور انسٹال کرتا ہے۔
آپ تقریباً 2–4 ہفتوں میں لائیو ہو جاتے ہیں، لانچ کے بعد معاونت کی مدت کے ساتھ۔
Odoo's stock module prints a basic delivery slip, and carrier connectors give you their own fixed label format — but the moment you need a branded 4x6 thermal label, a combined AWB layout, a compliant end-of-day handover manifest, or want to bulk-print a whole wave of picked orders to a Zebra printer, you hit a wall. The Shipping Label & Manifest Designer for Odoo is a net-new module that ECOSIRE designs, builds and installs on your Odoo 17, 18 or 19 database to close exactly that gap.
This is a build-to-order engagement, not an instant download from apps.odoo.com. After you order, our Odoo engineers scope your carriers, printers and label rules, then deliver a fully custom module: new models (models.Model) for label templates, manifest documents and print jobs; computed fields (@api.depends) that pull sender, recipient, weight, package count, order reference and tracking numbers straight from stock.picking and sale.order; QWeb report templates for pixel-accurate PDF labels; and a raw ZPL rendering engine for native thermal output. A designer-style template editor lets you place barcodes, QR codes, carrier logos and text blocks at exact millimetre coordinates, so a label matches carrier spec and your brand at the same time.
Everything is wired into Odoo the right way. Access is governed by ir.model.access.csv plus record rules so warehouse operators can print but only managers edit templates. A "Print Labels" action appears on delivery orders and can bulk-generate labels for every picked/packed order in a batch. An automated action (or scheduled ir.cron) can build the end-of-day manifest, number it, and mark shipments as handed over. Views are delivered in XML with OWL widgets for the live template preview, and a JSON-RPC/XML-RPC endpoint lets external WMS, scan stations or courier-desk apps request a label or manifest without opening the Odoo UI.
The result: your team designs labels once, prints them to thermal or A4 from anywhere in the pick-pack-ship flow, hands the driver a clean signed manifest, and never again exports data to a third-party label tool. Works on Community and Enterprise, and we hand over the source so it is yours to keep, extend and migrate forward.
Runs the pick-pack-ship floor and needs labels that print fast to thermal printers, plus a compliant end-of-day manifest to hand each driver — without exporting order data to a separate label tool.
Ships through several couriers whose native Odoo connectors each impose a different fixed label. Wants one designer where any carrier's label and AWB can be built to spec and printed from Odoo.
Owns the Odoo instance and wants a maintainable, upgrade-safe module with proper access rules and source handover — not a fragile Studio hack or an opaque third-party black box.
Prints on behalf of many clients and carriers, needing per-carrier templates, per-client branding, bulk waves and manifests, ideally driven headlessly via RPC from a WMS or scan station.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Custom label design (4x6 thermal, A4, AWB) matched to your brand and carrier spec | Included | Partial support | Partial support | |
| Native ZPL output for direct thermal printing | Included | Partial support | Partial support | |
| End-of-day manifest / driver handover sheet | Included | Partial support | Not included | |
| Bulk-print a wave of picked/packed orders in one action | Included | Partial support | Partial support | |
| Carrier-agnostic — works across any courier, not one vendor's fixed format | Included | Included | Not included | |
| Role-based access via ir.model.access.csv + record rules | Included | Partial support | Partial support | |
| XML-RPC / JSON-RPC headless printing for scan stations & WMS | Included | Partial support | Not included | |
| Full source handover — you own and can extend it | Included | Included | Not included | |
| Built, installed, supported and version-upgraded by an Odoo team | Included | Not included | Not included |
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.
Build-to-order Odoo module for custom shipping labels, AWBs and end-of-day manifests across any carrier and printer.