Odoo Changelog — 2026-03-14

Saturday, March 14, 2026

1 change · saas-19.2

Improvements(1)

Enhancements to existing features

[IMP] l10n_tr_nilvera_edispatch: allow flexible sequence codes and compute GIB prefix

Coresaas-19.2l10n_tr_nilvera_edispatchMedium

This update removes a restriction on outgoing stock sequence codes for Turkish companies, allowing users to include warehouse identifiers. This change ensures compatibility with Nilvera's e-Dispatch requirements while retaining operational flexibility. Additionally, the UI has been slightly improved for easier Nilvera status viewing.

Original PR description

# Description of the issue/feature this PR addresses:
Previously, the `sequence_code` of `stock.picking.type` was restricted to exactly 3 characters for outgoing pickings of Turkish companies. This was introduced because Nilvera requires a 3-character prefix when sending e-Dispatch documents.

However, enforcing a 3-character sequence code prevents users from including warehouse identifiers in the prefix (e.g. `WH/OUT`). Odoo normally relies on this structure to help users filter and distinguish warehouses. With the restriction in place, this functionality was lost.

# Desired behavior after PR is merged:
This commit removes the 3-character restriction on the sequence code and introduces a computed field that extracts the required 3-character GIB prefix from the sequence code. The computed prefix is used when sending documents to Nilvera, while users can keep meaningful sequence codes for operational use.

Additional improvements:
- Move the e-Dispatch tab next to "Operations" in `view_picking_form`
- Reduce the spacing between the text and reload button for the "Nilvera Status" field in `view_picking_form`

task-5964505
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#e-dispatch#nilvera#turkish#stock

# Description of the issue/feature this PR addresses: Previously, the `sequence_code` of `stock.picking.type` was restricted to exactly 3 characters for outgoing pickings of Turkish companies. This was introduced because Nilvera requires a 3-character prefix when sending e-Dispatch documents. However, enforcing a 3-character sequence code prevents users from including warehouse identifiers in the prefix (e.g. `WH/OUT`). Odoo normally relies on this structure to help users filter and distinguish warehouses. With the restriction in place, this functionality was lost. # Desired behavior after PR is merged: This commit removes the 3-character restriction on the sequence code and introduces a computed field that extracts the required 3-character GIB prefix from the sequence code. The computed prefix is used when sending documents to Nilvera, while users can keep meaningful sequence codes for operational use. Additional improvements: - Move the e-Dispatch tab next to "Operations" in `view_picking_form` - Reduce the spacing between the text and reload button for the "Nilvera Status" field in `view_picking_form` task-5964505 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr