Track Shipments in Odoo
with GoComet

The module connects Odoo to GoComet through its REST APIs. Administrators configure the GoComet account credentials used to generate the API access token. Once configured, the connection can be reused for subsequent data exchange between both platforms.

The module stores the GoComet credentials and access token securely, with access restricted to authorized administrators. It tracks the token expiry date returned by GoComet and regenerates the token before it expires, following GoComet’s authentication process. If a token becomes invalid or authentication fails, the connector notifies the administrator and records the failure. To avoid account lockout, the connector stops retrying after a failed login attempt.

A connection testing option allows administrators to verify whether Odoo can successfully authenticate with GoComet by generating an access token. It displays a success or failure message and provides relevant diagnostic information, such as the error returned by GoComet, to help identify credential or authorization issues.

The connector allows users to create shipment tracking records from Odoo using supported tracking identifiers. Supported modes are ocean, air, road, and courier, and supported identifiers include container numbers, master bills of lading, booking numbers, air waybill numbers, courier tracking numbers, and road references such as PRO or load numbers. The carrier code, ports, and other details can be provided where required by the API.

Odoo purchase orders, vendor shipments, or configured logistics records can be linked to their corresponding GoComet tracking records. The Odoo document reference is stored in GoComet’s reference number field, and the GoComet tracking ID is stored in Odoo, so users can identify the related goods across both systems.

The connector retrieves tracking information from GoComet and updates the corresponding Odoo records. This includes shipment status, carrier details, tracking identifiers, ports of loading and discharge, estimated arrival dates, and shipment events.

The module displays shipment events in Odoo as a chronological tracking history, including planned and actual dates. When GoComet marks an event as delayed or provides an updated estimated arrival date, the connector highlights the change to help logistics teams identify delayed shipments and take appropriate action.

Scheduled synchronization allows Odoo to retrieve updated tracking information from GoComet automatically. The system periodically checks eligible shipment records and updates the corresponding Odoo entries without requiring users to initiate each synchronization manually.

A centralized dashboard provides an overview of the integration process. It can display successfully synchronized shipments, pending tracking requests, failed synchronization attempts, connection status, and the latest synchronization time. Users can also manually refresh tracking data or retry failed operations when required.

The module maintains logs of synchronization activities between Odoo and GoComet. These logs include the related Odoo record, operation type, timestamp, synchronization status, and relevant error details. Access tokens are masked in the logs. The logs help administrators investigate authentication failures, invalid tracking information, API errors, and temporary connection issues.

Tracking records can be created automatically when a configured event occurs in Odoo, such as confirming a purchase order or preparing a related shipment. This reduces manual work and ensures tracking begins when the required shipping details are available.

The connector can display GoComet’s tracking link on the related purchase order or shipment record. Users can open the tracking details in GoComet without searching for the shipment separately.

The system can generate Odoo activities or email notifications when tracking updates indicate a shipment delay, a change in the estimated arrival date, or another configured exception. Notification rules and recipients can be customized.

Administrators can configure which Odoo document types are eligible for tracking, how Odoo references map to GoComet shipment references, which tracking modes are enabled, and which fields are synchronized between the platforms.

The connector can use GoComet tracking IDs, tracking numbers, and Odoo document references to prevent duplicate records and match tracking updates to the correct shipment. If GoComet reports that a tracking number already exists, the connector links the existing tracking instead of creating a duplicate. Ambiguous matches can be flagged for manual review.

Temporary API failures can be retried automatically after a configured delay. The connector distinguishes temporary failures from authentication or validation errors, does not retry failed logins, and records the outcome in the synchronization logs.

Each Odoo company can maintain its own GoComet connection, credentials, and synchronization settings. A GoComet team code can be specified where the customer uses multiple teams in their GoComet account. Access rules ensure that company-specific records remain separated.

A comparison report can identify Odoo shipments without tracking records, missing references, duplicate matches, or records that have not been updated recently. This helps administrators identify discrepancies and maintain consistent shipment information.

Administrators can choose eligible records and set synchronization intervals. The connector sends tracking requests from Odoo to GoComet and retrieves tracking data from GoComet into Odoo.