Branded public tracking page in Odoo where customers look up shipment/container status by reference number with a live, dated event timeline. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
Branded public tracking page in Odoo where customers look up shipment/container status by reference number with a live, dated event timeline.
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.
Stop fielding "where's my container?" emails. This is a build-to-order Odoo module, engineered and installed by ECOSIRE, that gives your logistics business a branded, public self-service tracking portal running directly on your Odoo website — no third-party tracking SaaS, no separate login, no data leaving your ERP.
A customer types a shipment or container reference into a public lookup page and instantly sees a clean, dated milestone timeline: booked, gate-in, loaded, vessel departed, in transit, arrived, customs cleared, out for delivery, delivered — with the current status, ETA, carrier, vessel/voyage, and container/carton-level detail. Every event is the same record your ops team already updates inside Odoo, so the customer view is always live and never out of sync.
Under the hood we build this the right Odoo way, not as a bolt-on hack. New models (models.Model) hold shipments, containers, cartons, and dated tracking events, with computed fields (@api.depends) rolling up the latest status and ETA. The public page is a QWeb/website controller rendering only whitelisted, non-sensitive fields — protected by record rules and ir.model.access.csv so a reference lookup can never expose pricing, other customers' data, or internal notes. Milestone changes fire automated actions / server actions that email or notify the customer, and the same shipment data is exposed over Odoo's XML-RPC / JSON-RPC API so your website, carrier EDI feeds, or a mobile app can read and update it.
Because it's native Odoo, it inherits your website theme and branding automatically, supports multi-company and multi-warehouse setups, and works on Odoo Community or Enterprise across versions 17, 18 and 19. ECOSIRE scopes it to your exact workflow, builds it, installs it on your server or Odoo.sh, trains your team, and supports it — typically delivered in 2 to 4 weeks. This is not an instant apps.odoo.com download; it's a made-to-fit module we build for your business.
Wants to give shippers a branded, always-on way to check container status themselves instead of answering status-request emails and calls all day — and wants that portal to live inside the Odoo they already run operations on.
Needs a single source of truth where the ops team updates a shipment once and both internal dashboards and the customer-facing timeline reflect it instantly, with ETA and exception notifications going out automatically.
Wants fewer 'where's my shipment?' tickets and a professional self-service experience with a shareable tracking link per shipment, so clients feel informed without extra manual work from the team.
Needs the tracking feature to be a clean, native module — proper models, record-rule security, and an XML-RPC/JSON-RPC API for feeds — rather than fragile customizations that break on the next Odoo upgrade.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Public self-service tracking page by reference number | Incluído | Suporte parcial | Suporte parcial | |
| Container and carton-level detail on the timeline | Incluído | Suporte parcial | Suporte parcial | |
| Matches your exact milestone workflow and reference format | Incluído | Suporte parcial | Não incluído | |
| Security-reviewed public exposure (record rules + ir.model.access.csv, optional PIN) | Incluído | Suporte parcial | Suporte parcial | |
| Automated ETA / status-change customer notifications | Incluído | Suporte parcial | Suporte parcial | |
| XML-RPC / JSON-RPC API for carrier feeds & apps | Incluído | Suporte parcial | Suporte parcial | |
| Branded to your Odoo website theme automatically | Incluído | Suporte parcial | Suporte parcial | |
| Built, installed, trained, and supported for you | Incluído | Não incluído | Não incluído | |
| Upgrade-safe across Odoo 17 / 18 / 19 | Incluído | Suporte parcial | Suporte parcial |
No. This is a build-to-order module that ECOSIRE designs, builds, installs, and supports specifically for your business and your milestone workflow. You are not buying a pre-existing zip file — you are commissioning a made-to-fit Odoo module tailored to your carriers, reference-number format, notification rules, and branding.
Typical delivery is 2 to 4 weeks depending on scope. We start with a short discovery to lock down your milestone stages, reference format, and notification rules, then build the module, install it on your environment (your server, Odoo.sh, or ECOSIRE-managed hosting), migrate or seed any existing shipment data, run a training session, and hand over documentation. Timeline is confirmed after discovery before work begins.
Every build includes a post-launch support window (default 30 days) for bug fixes and small adjustments. Because the module is written the native Odoo way — clean models, record rules, and standard views — it is designed to survive Odoo upgrades. We also offer ongoing support and version-migration retainers (e.g., moving your module from Odoo 17 to 18 or 19) as a separate optional plan.
We build for Odoo 17, 18, and 19, on both Community and Enterprise. The public website tracking page works on Community — no Enterprise license is required for the core portal. We match the module to your exact version and edition so it installs cleanly on your instance.
Security is designed in, not bolted on. The public controller renders only a whitelisted set of non-sensitive fields, and access is enforced by Odoo record rules and ir.model.access.csv. A reference lookup can never expose pricing, internal notes, or another customer's shipment. We can additionally gate lookups with a per-shipment PIN so only someone with both the reference and the PIN can view a timeline.
Yes. The shipment and event data is exposed over Odoo's standard XML-RPC and JSON-RPC APIs, so your storefront, a mobile app, or carrier EDI/webhook feeds can push new tracking events and read live status. We scope the specific integrations you need during discovery; the tracking model itself is built to be fed programmatically as well as updated by hand.
Branded public tracking page in Odoo where customers look up shipment/container status by reference number with a live, dated event timeline.