Saturday, February 3, 2024
2 changes · 17.0
New functionality added to Odoo
Adds Ecuador-specific checkout and portal fields so online orders can collect the identification details needed for electronic invoicing. It also connects eCommerce payment methods to the required SRI payment information and removes the ZIP code requirement for Ecuadorian invoices, reducing checkout friction and invoice errors.
Original PR description
This PR provides a localization for the eCommerce workflow in Ecuador. Changes * A new localization module l10n_ec_website_sale adapting the eCommerce workflow for Ecuadorr * Make zip code not…
This PR provides a localization for the eCommerce workflow in Ecuador.
Changes
* A new localization module l10n_ec_website_sale adapting the eCommerce workflow for Ecuadorr
* Make zip code not required
* Provide access to latam identifaction types to "public users" (non-portal / non-internal shop users) so that it can be used in the checkout process of the eCommerce (billing information)
### l10n_ec_website_sale details
main adaptions:
* Identification type and number in the checkout process (in the billing address)
* SRI Payment Method in the eCommerce Payment Method
SRI Payment Method
* The SRI Payment Method value is required for the EDI
* In the payment method form view the SRI Payment Method field is hidden
if the list of fiscal countries of the selected companies does not include Ecuador.
* Payment methods which do not have an associated SRI Payment Method cannot be used in the eCommerce of an Ecuadorian company.
* When creating an invoice from a sales order we try to compute the SRI Payment Method as follows:
We consider all the SRI Payment Methods of the payment methods of the payment transactions associated with the sales order.
If there is exactly 1 such SRI Payment Method we use this on the invoice.
This should ensures that we can always set the SRI Payment Method on invoices created through the eCommerce flow.
### task info
task-3585823Resolved issues and error corrections
This fix prevents users from accidentally adding website design elements (like badges) inside payment forms, which was causing payment processing failures. The payment form is now protected from website editing to ensure payments work reliably for customers.
Original PR description
Before this commit, it was possible for users to drop website snippets (e.g., the "Badge" block) inside the inline form of payment acquirers. At least for Adyen, it would prevent payments because the payment inputs within the inline form wouldn't load anymore. As inline forms are part of the payment form widget, which itself is not customizable by users, this commit blocks the website editor inside the entire payment form and its children elements. opw-3607719 Forward-Port-Of: odoo/odoo#152403 Forward-Port-Of: odoo/odoo#152306