Odoo Changelog — 2025-07-01

Tuesday, July 1, 2025

3 changes · 18.0

Improvements(3)

Enhancements to existing features

[IMP] l10n_tr_nilvera: log info to avoid CI failing

Core18.0l10n_tr_nilvera

The Turkish Nilvera integration now records connection issues as informational logs instead of errors. This keeps diagnostic details available while preventing automated upgrade checks from failing when internet access is blocked.

Original PR description

In 3b5cb63 we silenced Nilvera connection errors to prevent upgrade CI failures due to blocked internet access. However, using `logger.error` still caused CI to fail when triggered. This commit changes the log level to info to ensure the error is recorded without impacting the CI. Also, we're now printing the stack trace for easier debugging.

runbot-227039

Forward-Port-Of: odoo/odoo#215791

#turkey#nilvera#logging#ci

[IMP] delivery_starshipit: reliability improvements & asynchronous fetch of shipping costs

PR #86383

Enterprise18.0delivery_starshipitMEDIUM

Starshipit deliveries no longer block when the final shipping cost is not immediately available. Odoo now records a temporary zero cost and later updates the delivery and sales order with the correct price automatically, improving checkout and fulfillment reliability.

Original PR description

**Description of the issue/feature this PR addresses:** This PR enhances the Starshipit integration to reliably handle scenarios where the exact shipping cost is not immediately available from…

**Current behavior before PR:**
When confirming a picking with a Starshipit Delivery method, the exact Shipping cost was not instantly available. The previous code had 3 attempts to retrieve it, before stopping the process, asking the user to try at a later time.

**Desired behavior after PR is merged:**
The price fetching becomes non-blocking. If Starshipit did not return an immediate `total_shipping_price`, a temporary price of 0.0 will be used. A Cron job will then run on all pickings with a 0.0 carrier price in order to fetch the exact price from Starshipit, and update the SO delivery lines.

opw-4748113

When merging on `master`, further improvement might be to introduce a `starshipit_pending_price` boolean field instead of running the CRON job on all 0.0 carrier price pickings.

With the new view `view_picking_form_inherit_stock` being introduced, runbot tests fail when migrating to saas-18.1. (Because view is not yet present in the saas-18.1 codebase)

**How to test?**
- On a runbot DB, install the `delivery_starshipit` module
- Configure the DB to interact with the connector
- Place a Sales Order with a delivery method configured to use Starshipit.
- Confirm the Delivery. The shipping price, if not available, will be temporarily set to 0.0.
- Run the Cron Job manually. You can check and activate the Cron by navigating to Settings > Technical > Automation > Scheduled Actions.
- Check that the SO has been updated with the actual shipping price from Starshipit.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#starshipit#shipping#delivery#automation

[IMP] sign: polishing of the sign.item.type model and its form and list views

PR #89154

Enterprise18.0signMEDIUM

The Sign app’s signature field configuration screens are easier to understand, with clearer labels, better layout, and an option to archive unused field types. Text field sizing is simplified into practical size choices, helping administrators configure signing templates faster and with fewer errors.

Original PR description

Changes include:
    
    - Change of the model name text in form and list views from "Signature
      Item Type" to "Signature fields".
    - Addition of "active" field in the sign.item.type model to add the
      option to archive/unarchive records.
    - Capitalized default value of "tip" field from "fill in" to "Fill in".
    - Removed "default_width" and "default_height" fields from the form view
      and substituted them with a new field "field_size" which allows for 3
      values (short, normal, long) and, on change, updates the two height and width fields accordingly. This new field is only displayed when the "field_type" is set to Text.
    - Restructuring of the form view to have on the left normal fields and
      on the right autocompleted ones.
    - Change of the names of two columns on the list view: from "Specific
      Model Linked" to "Linked to" and from "Auto-fill Field" to "Linked field".

#sign#signature fields#usability#configuration

In 3b5cb63 we silenced Nilvera connection errors to prevent upgrade CI failures due to blocked internet access. However, using `logger.error` still caused CI to fail when triggered. This commit changes the log level to info to ensure the error is recorded without impacting the CI. Also, we're now printing the stack trace for easier debugging. runbot-227039 Forward-Port-Of: odoo/odoo#215791

**Description of the issue/feature this PR addresses:** This PR enhances the Starshipit integration to reliably handle scenarios where the exact shipping cost is not immediately available from Starshipit after label creation. Cost is fetched via a cron job and correctly applied to both the stock.picking's carrier_price and, crucially, the corresponding Sales Order delivery line. First commit removes the 3-tries loop, and was already reviewed on this [PR](https://github.com/odoo/enterprise/pull/85088). **Current behavior before PR:** When confirming a picking with a Starshipit Delivery method, the exact Shipping cost was not instantly available. The previous code had 3 attempts to retrieve it, before stopping the process, asking the user to try at a later time. **Desired behavior after PR is merged:** The price fetching becomes non-blocking. If Starshipit did not return an immediate `total_shipping_price`, a temporary price of 0.0 will be used. A Cron job will then run on all pickings with a 0.0 carrier price in order to fetch the exact price from Starshipit, and update the SO delivery lines. opw-4748113 When merging on `master`, further improvement might be to introduce a `starshipit_pending_price` boolean field instead of running the CRON job on all 0.0 carrier price pickings. With the new view `view_picking_form_inherit_stock` being introduced, runbot tests fail when migrating to saas-18.1. (Because view is not yet present in the saas-18.1 codebase) **How to test?** - On a runbot DB, install the `delivery_starshipit` module - Configure the DB to interact with the connector - Place a Sales Order with a delivery method configured to use Starshipit. - Confirm the Delivery. The shipping price, if not available, will be temporarily set to 0.0. - Run the Cron Job manually. You can check and activate the Cron by navigating to Settings > Technical > Automation > Scheduled Actions. - Check that the SO has been updated with the actual shipping price from Starshipit. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Changes include: - Change of the model name text in form and list views from "Signature Item Type" to "Signature fields". - Addition of "active" field in the sign.item.type model to add the option to archive/unarchive records. - Capitalized default value of "tip" field from "fill in" to "Fill in". - Removed "default_width" and "default_height" fields from the form view and substituted them with a new field "field_size" which allows for 3 values (short, normal, long) and, on change, updates the two height and width fields accordingly. This new field is only displayed when the "field_type" is set to Text. - Restructuring of the form view to have on the left normal fields and on the right autocompleted ones. - Change of the names of two columns on the list view: from "Specific Model Linked" to "Linked to" and from "Auto-fill Field" to "Linked field".