イメージプレビューBranded public tracking page in Odoo where customers look up shipment/container status by reference number with a live, dated event timeline.
Container & Shipment Tracking Portal for Odooとは？
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 $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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 one working week. This is not an instant apps.odoo.com download; it's a made-to-fit module we build for your business.
得られるもの
- Complete, installable Odoo module (properly structured __manifest__.py, models/, views/, security/, controllers/, data/) targeted to your Odoo 17, 18 or 19 version and Community/Enterprise edition
- Discovery + scope document capturing your milestone stages, carriers, reference-number format, and notification rules before a line of code is written
- Public tracking page and backend ops views built and styled to match your existing Odoo website branding
- Security configuration: ir.model.access.csv access rights and record rules reviewed with you so public exposure is provably safe
- Installation and deployment on your server, Odoo.sh, or ECOSIRE-managed hosting, including data migration/seed of existing shipments if provided
- Configuration of notification email templates, automated actions, and the shipment reference sequence to your business rules
- Admin + operations training session (live walkthrough) plus written user documentation and a technical README for your team
- Included post-launch support and bug-fix window (two weeks) with a clear channel for issues and small adjustments
これは誰のためのものですか
Freight forwarder / logistics provider
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.
Head of operations / logistics manager
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.
Customer experience / account manager
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.
IT / Odoo administrator
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.
Container & Shipment Tracking Portal for Odoo の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Public self-service tracking page by reference number | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Container and carton-level detail on the timeline | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Matches your exact milestone workflow and reference format | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Security-reviewed public exposure (record rules + ir.model.access.csv, optional PIN) | 付属 | 部分的なサポート | 部分的なサポート | 部分的なサポート |
| Automated ETA / status-change customer notifications | 付属 | 部分的なサポート | 部分的なサポート | 部分的なサポート |
| XML-RPC / JSON-RPC API for carrier feeds & apps | 付属 | 部分的なサポート | 部分的なサポート | 付属 |
| Branded to your Odoo website theme automatically | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Built, installed, trained, and supported for you | 付属 | 含まれていない | 含まれていない | 含まれていない |
| Upgrade-safe across Odoo 17 / 18 / 19 | 付属 | 部分的なサポート | 部分的なサポート | 付属 |
Container & Shipment Tracking Portal に関するよくある質問
Is this an instant download from the Odoo app store?
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.
How long does delivery take, and what's the process?
Typical delivery is one working week 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.
What happens after launch — support and updates?
Every build includes a post-launch support window (two weeks) 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.
Which Odoo versions and editions does it support?
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.
Is the public tracking page secure? Can customers see other people's data?
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.
Can it connect to carriers, our website, or a mobile app?
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.
関連モジュール
Container & Shipment Tracking Portal
Branded public tracking page in Odoo where customers look up shipment/container status by reference number with a live, dated event timeline.
- Public website tracking lookup page (QWeb + website controller) where anyone can search by shipment or container reference — no Odoo login required
- Auto-generated, human-readable shipment reference numbers using ir.sequence, with an optional customer-friendly PIN check to gate access
- Dated milestone/event timeline model (one2many tracking events) showing every status change with timestamp, location, and note
- Container-level and carton-level detail: multiple containers per shipment, cartons/packages per container, with dimensions, weight, seal number and quantity