[MERGE][REF] delivery: extract stock logic in separate module #110686
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
vava-odoo
force-pushed
the
master-delivery_split_from_sale_and_stock-vava
branch
12 times, most recently
from
83d1956 to
771d608
Compare
vava-odoo
force-pushed
the
master-delivery_split_from_sale_and_stock-vava
branch
16 times, most recently
from
8d5d9a0 to
5fbadfa
Compare
It's currently impossible to set fixed delivery costs in eCommerce without installing Inventory. This is a problem for one-app free instances on our SaaS, which would need to pay for a feature that should be part of the basic eCommerce features bundle. This commit makes it possible to define fixed-cost delivery methods in eCommerce without installing Inventory by adding a direct dependency of `website_sale` on `delivery`. The bridge between those two modules is therefore included in the former.
*: mondialrelay, stock_picking_batch **: delivery_mondialrelay, loyalty_delivery, picking Adapt dependency to `website_sale` directly instead of `website_sale_delivery`.
In ecommerce, the form vue of shipping methods should be improved to easily set up fixed delivery costs. This commit improves the user-experience and solves bugs on the fields displayed. task-3203210
Feyensv
force-pushed
the
master-delivery_split_from_sale_and_stock-vava
branch
from
5317a2c to
28799be
Compare
|
@robodoo r+ |
|
@vava-odoo @Feyensv linked pull request(s) odoo/enterprise#36609 not ready. Linked PRs are not staged until all of them are ready. |
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
Extract the Inventory logic from the `delivery` module into a new `stock_delivery` module. This will allow to integrate the basic delivery features into the website_sale app in a one-app free database. task-3074497 Part-of: #110686
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
It's currently impossible to set fixed delivery costs in eCommerce without installing Inventory. This is a problem for one-app free instances on our SaaS, which would need to pay for a feature that should be part of the basic eCommerce features bundle. This commit makes it possible to define fixed-cost delivery methods in eCommerce without installing Inventory by adding a direct dependency of `website_sale` on `delivery`. The bridge between those two modules is therefore included in the former. Part-of: #110686
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
*: mondialrelay, stock_picking_batch **: delivery_mondialrelay, loyalty_delivery, picking Adapt dependency to `website_sale` directly instead of `website_sale_delivery`. Part-of: #110686
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
In ecommerce, the form vue of shipping methods should be improved to easily set up fixed delivery costs. This commit improves the user-experience and solves bugs on the fields displayed. task-3203210 Part-of: #110686
robodoo
pushed a commit
that referenced
this pull request
Mar 14, 2023
robodoo
added a commit
that referenced
this pull request
Mar 14, 2023
It's currently impossible to set fixed delivery costs in eCommerce without installing Inventory. This is a problem for one-app free instances on our SaaS, which would need to pay for a feature that should be part of the basic eCommerce features bundle. Delivery is now split from inventory/stock module to allow for a soft free integration into website_sale. This PR makes it possible to define fixed-cost delivery methods in eCommerce without installing Inventory by adding a direct dependency of `website_sale` on `delivery`. The bridge between those two modules is therefore included in the former. Steps are: - extract the Inventory logic from the `delivery` module into a new `stock_delivery` module; - move `website_sale_delivery` into `website_sale`; - adapt dependencies to `delivery` and `website_sale_delivery`; - remove bridge module with loyalty directly in `website_sale_loyalty`; - move `website_sale_delivery_mondialrelay` to `website_sale_mondialrelay`. task-3074497 task-3203210 See also: - odoo/enterprise#36609 - odoo/upgrade#4362 closes #110686 Related: odoo/upgrade#4362 Related: odoo/enterprise#36609 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
99 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's currently impossible to set fixed delivery costs in eCommerce without installing Inventory. This is a problem for one-app free instances on our SaaS, which would need to pay for a feature that should be part of the basic eCommerce features bundle.
Delivery is now split from inventory/stock module to allow for a soft free integration into website_sale. This PR makes it possible to define fixed-cost delivery methods in eCommerce without installing Inventory by adding a direct dependency of
website_saleondelivery. The bridge between those two modules is therefore included in the former.Steps are:
deliverymodule into a newstock_deliverymodule;website_sale_deliveryintowebsite_sale;deliveryandwebsite_sale_delivery;website_sale_loyalty;website_sale_delivery_mondialrelaytowebsite_sale_mondialrelay.task-3074497
task-3203210
See also: