​

Configuring Odoo as a Source

​

1. Add account access

• API URL: The base URL of your Odoo instance (e.g., https://mycompany.odoo.com). This is the root URL where your Odoo instance is hosted.
• API Key: The API key (bearer token) to authenticate against the Odoo API. This token grants access to your Odoo instance and must have the necessary permissions to read the data you want to extract.
• Database: (Optional) The name of the database to connect to. This is only required when a single Odoo server hosts multiple databases. If your instance uses a single database or the database name is determined automatically, you can leave this field empty.

​

2. Select streams

Tip: The stream can be found more easily by typing its name.

​

3. Configure data streams

• Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
• Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
• Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
• Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
  • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
  • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.

​

4. Configure data source

• Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
• Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

​

5. Check your new source

​

Streams and Fields

​

Data Model

​

Use Cases for Data Analysis

​

1. Payment Analysis Overview

• Monitor payment transactions and cash flow
• Analyze payment methods and patterns
• Track outstanding payments and reconciliation status
• Generate financial reports based on payment data

SELECT
   DATE(payment_date) AS payment_date,
   payment_method,
   state,
   currency_id,
   SUM(amount) AS total_amount,
   COUNT(*) AS payment_count,
   COUNT(DISTINCT partner_id) AS unique_partners
FROM
   nekt_raw.odoo_payment
WHERE
   payment_date >= CURRENT_DATE - INTERVAL '30' DAY
GROUP BY
   DATE(payment_date),
   payment_method,
   state,
   currency_id
ORDER BY
   payment_date DESC,
   total_amount DESC

SELECT
   DATE(payment_date) AS payment_date,
   payment_method,
   state,
   currency_id,
   SUM(amount) AS total_amount,
   COUNT(*) AS payment_count,
   COUNT(DISTINCT partner_id) AS unique_partners
FROM
   `nekt_raw.odoo_payment`
WHERE
   DATE(payment_date) >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
GROUP BY
   DATE(payment_date),
   payment_method,
   state,
   currency_id
ORDER BY
   payment_date DESC,
   total_amount DESC

​

2. Insurance Quotation Tracking

• Track quotation creation and conversion rates
• Identify trends in quotation volume over time
• Analyze customer segments and quotation performance
• Monitor quotation status and workflow progression

SELECT
   DATE(create_date) AS quotation_date,
   state,
   product_id,
   COUNT(*) AS quotation_count,
   COUNT(DISTINCT partner_id) AS unique_customers,
   AVG(amount_total) AS avg_quotation_value,
   SUM(CASE WHEN state = 'sale' THEN 1 ELSE 0 END) AS converted_count,
   ROUND(
      SUM(CASE WHEN state = 'sale' THEN 1 ELSE 0 END)::NUMERIC / 
      NULLIF(COUNT(*), 0) * 100, 
      2
   ) AS conversion_rate_percent
FROM
   nekt_raw.odoo_insurance_quotation
WHERE
   create_date >= CURRENT_DATE - INTERVAL '30' DAY
GROUP BY
   DATE(create_date),
   state,
   product_id
ORDER BY
   quotation_date DESC,
   quotation_count DESC

SELECT
   DATE(create_date) AS quotation_date,
   state,
   product_id,
   COUNT(*) AS quotation_count,
   COUNT(DISTINCT partner_id) AS unique_customers,
   AVG(amount_total) AS avg_quotation_value,
   SUM(CASE WHEN state = 'sale' THEN 1 ELSE 0 END) AS converted_count,
   ROUND(
      SAFE_DIVIDE(
         SUM(CASE WHEN state = 'sale' THEN 1 ELSE 0 END),
         COUNT(*)
      ) * 100,
      2
   ) AS conversion_rate_percent
FROM
   `nekt_raw.odoo_insurance_quotation`
WHERE
   DATE(create_date) >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
GROUP BY
   DATE(create_date),
   state,
   product_id
ORDER BY
   quotation_date DESC,
   quotation_count DESC

​

Implementation Notes

​

Dynamic Schema Discovery

• The Odoo connector uses dynamic schema discovery by calling the fields_get method on each Odoo model
• This means the exact fields available may vary based on:
  • Your Odoo version
  • Installed modules and apps
  • Custom fields and configurations
  • Model-specific customizations
• If schema discovery fails, the connector falls back to a basic schema with only the id field

​

Data Quality Considerations

• Odoo model fields may include relationships (many2one, one2many, many2many) that are represented as integer IDs or arrays
• Date and datetime fields are automatically converted to appropriate types
• Monetary fields are handled as numeric types
• Binary fields are represented as strings
• Fields defined as string in the stream schema (e.g. vehicle_cc) are coerced from numeric values (e.g. 0) to string when the API returns numbers, so targets receive schema-compliant types

​

API Limits & Performance

• The connector uses pagination with a default page size to efficiently extract large datasets
• For faster extractions, select only the streams necessary for your analysis
• Odoo API rate limits may apply depending on your instance configuration
• Ensure your API key has appropriate read permissions for the models you want to extract

​

Multi-Database Support

• If your Odoo instance hosts multiple databases, specify the database name in the configuration
• The database name is sent as the X-Odoo-Database header in API requests
• Leave the database field empty if your instance uses a single database or auto-detection