Friday, March 10, 2023
2 changes · master
Enhancements to existing features
Point-of-sale orders can now be accessed across trusted cashier desks, making it easier to handle returns in different shops and manage restaurant orders with multiple checkout points. Restaurants can also share floor plans across several desks, supporting smoother waiter, cashier, and self-service workflows.
Original PR description
Currently the below use-cases are hardly supportable, though quite common:
Retail: Sell product in one shop and return it in another one
Restaurant: Managing payment when having multiple checkout desks, and multiple waiters (only taking orders)
This because currently:
PoS orders are only known by the cashier desk (pos.config) they were created from
One floor map can only be linked to one cashier desk at a time
More over, with the Self-Service coming along the way (where kiosk orders must be accessible from a cashier desk), this need must be supported.
For restaurant, floor plans can be linked to multiple cashier desks, ongoing orders are shared between trusted PoS config (through floors for restaurant and according to the setting "Trusted PoS config" for the retails), and past orders can be accessible from any desks within a same DB.
Task-id: 3090565
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prSubscription records now use one clear status field instead of several overlapping stage and renewal fields. This simplifies day-to-day subscription tracking, makes subscription screens more consistent with sales views, and removes the old renewal flag behavior ahead of a future replacement.
Original PR description
To simplify the subscription logic, this PR aims at removing the subscription's stage model and anything that depends on it to replace if by a simpler selection field called `subscription_state`.…
To simplify the subscription logic, this PR aims at removing the
subscription's stage model and anything that depends on it to replace
if by a simpler selection field called `subscription_state`.
This field will merge the usage of the follwing fields :
-stage_id
-stage_category
-subscription_management
-renew_state
For clarity sake's these fields are now represented by the 7
state of `subscription_state` :
-'Quotation', Quotation for a new subscription
-'Renewal Quotation', Renewal Quotation for existing subscription
-'In Progress', Active Subscription or confirmed renewal for active subscription
-'Paused', Active subscription with paused invoicing
-'Renewed', Active or ended subscription that has been renewed
-'Churned', Closed or ended subscription
-'Upsell', Quotation or SO upselling a subscription,
upsells are not subscriptions
Following theses changes, massive overhaul have been made
to the different subscription views to enhance the
usability as well as the onboarding of this app.
One of the main focus of these change was to make
the subscription view more closely act like the sale's
view.
Additionally, the old `to_renew` behaviour has been removed
as it wasn't fitting the new plan for subscription and will
be replaced in the future.
task-id : 3190077