| Age | Commit message (Collapse) | Author |
|---|
|
Because the `receiptHtml` was taken from a component which was mounted outside of the DOM, it was hardly ever destroyed for some unknown reasons and the `el.outerHTML` could not be taken to create the receipt.
closes odoo/odoo#71087
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
Before, when using the manage order, if a payment method was used and then removed from the pos.config,
we couldn't load the old order anymore because of unknow reference.
To fix this, we load all methods at the opening of the pos but when we display the payment methods we only show those in the pos.config.
closes odoo/odoo#71263
Task-id: 2541708
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
This tasks allow to see serial numbers or lot numbers for each products on the order.
It also add the same information on an invoice generated by the POS if the option is ticked in the pos config.
closes odoo/odoo#42410
closes odoo/odoo#69932
Task-id: 2154835
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
When a pos user combines payment methods with and without rounding, we
must be sure that the rounding is made by payment method and not only on
the total amount of the order.
As the total may change depending on the combination of payment method
used, we had to adapt the methods that checks that an order is paid, and
also propagate the new rounding made on the invoice.
We also don't allow anymore a user to validate an order with a payment
badly rounded.
closes odoo/odoo#69544
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
When a pricelist is set to display a discount, it also display the price
difference when the price is increased for a reason.
To avoid such an anoying behavior, that'll show that the price of a
product as been increased by aplying a discount, we only show the old
price when it has been decreased.
closes odoo/odoo#69569
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
The terms in the search bar of the ticket screen are not translated.
This commit fixes this issue by passing the translated form of the
terms to the search bar component.
closes odoo/odoo#65038
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
|
|
To reproduce:
1. Start an odoo instance without demo with point_of_sale module.
2. Install a generic fiscal local if not automatically installed.
3. Create a product.
4. Open a pos session.
5. BUG: no search bar
This is because the search bar is rendered inside ProductsWidgetControlPanel
which is only rendered when there are categories. Instead, we render it
always but we pass the hasNoCategory information to selectively render
it's part. This now always show the search bar.
closes odoo/odoo#63517
Opw: 2418858
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
When you are configuring the picking type used in the point of sale to
not use existing lots and not create lots, the POS still ask you to
encode a lot for product tracked, and the picking created don't use
existing lots in stock because no reservation is made when a picking is
valaidated from point of sale.
As we want to reserve only in this specific case, we are now checking
the options on the picking type to reserve or not product tracked.
We are also not asking anymore for lot or serial number if picking type
is configured that way.
OPW-2377008
closes odoo/odoo#62734
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
- Activate debug mode
- Go to Settings > Translations > Languages
- Activate and switch to a language that does not use dot (.) as decimal separator (i.e. French)
- Go to a POS session
- Select a Product, edit the price with a decimal via the Numpad widget
The decimal is not taken into account.
This is due to the fact that the entered input ('.') is not considered as the decimal point
in this language (i.e. ',') and is skipped.
The same issue happens for quantity and discount.
The dot in the Numpad widget has been replaced by the decimal separator of the language.
Also "field_utils.parse.float" has to be used instead of "parseFloat" because "parseFloat" only
recognizes a dot as separator. (i.e. "parseFloat" returns 12.00 for "12,99")
Howerver "parseFloat" is still useful for checking values as "field_utils.parse.float" returns
an error if its parameter is not a string or if the parsed result is not a number.
opw-2357848
closes odoo/odoo#59665
Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
|
|
- Set the company country to India
- Open th POS, make a sale
- Print the receipt
The label for the VAT is 'VAT' while it should be 'GSTIN'.
The `VAT:` label is hardcoded in the receipt template. It is expected to
be adapted to the localization thanks to the translation. However, in
this case it doesn't work: since we keep the English language, there is
no translation applied.
We use the country `vat_label` and fall back on the `VAT` string.
opw-2343652
closes odoo/odoo#58831
X-original-commit: 652e240901a052ed612f91620bdab3cbd5608e3f
Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
|
|
Improve usability of open tabs in the POS.
closes odoo/odoo#56728
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
As long as the payment is not validated, the cashier can add products
to the order, even if the payment has been completed. The amount
authorized can be adjusted if the payment interface implements the
canBeAdjusted method.
closes odoo/odoo#56639
Taskid: 2117032
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
Before this commit, mode value can be different to what is shown in the screen
because of async rendering. To make sure that the mode value is properly synced
with with view, we couple the numpad mode value to the component.
|
|
Aside from new look, we also move the email option from payment
screen to receipt screen. This allows emailing the receipt to a
customer that is not in the contact list.
We also removed invoicing in the receipt screen during failed invoicing
from payment screen as it is removed in here: bc48e0033e2166728ae72739b72076ea67e86e74
closes odoo/odoo#55868
Related: odoo/enterprise#12395
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
This commit switch the cash control opening mangement from the backend to the front end of the point of sale.
task_id: 2258817
closes odoo/odoo#55741
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
The following changes are made in this task:
1. Remove order tabs and replace with ticket list.
2. Top bar color change.
3. Search bar in the product screen is moved in the top bar.
4. List of sub-categories are now in the same line as the category
breadcrumbs.
closes odoo/odoo#55100
Task-id: 2276678
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
Configure products with create_variants = 'never' from the POS
closes odoo/odoo#54956
Taskid: 208205
Related: odoo/upgrade#1522
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
Issue
- Install "Point of Sale" module
- Edit POS (e.g.: Shop) settings
- Enable "Header & Footer" feature
- Add a footer with multiple breaklines and save
- Start a session with the current POS
- Make an order
Receipt footer not well formated
Solution
Add 'white-space:pre-line' style to avoid escaping breaklines;
inspired on text-field css class.
opw-2300889
closes odoo/odoo#55182
X-original-commit: 85de8418ae9b152fc0f4c300b71249440f381224
Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
|
|
Improve the flow of the customer list and edit to fit better with odoo.
closes odoo/odoo#54571
Task-id: 2294251
Related: odoo/enterprise#11891
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
Add an option in the pos config to disallow the use of manual discount per order line.
closes odoo/odoo#51172
Task-id: 2082140
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
We now allow invoicing of finalized orders in an open session in this first
iteration of order management in the pos frontend. Additionally, receipt
reprinting is also introduced. With this feature, we can now reprint the
receipt of old orders.
closes odoo/odoo#51141
Task-id: 1981354
Related: odoo/enterprise#11690
Related: odoo/upgrade#1472
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
The primary goal of disableRubberbanding is to disable scrolling during
touch event by default and to allow only selected descendants to have scrolling
active during touchstart+touchmove event. Only elements with class="touch-scrollable"
are allowed for touch scrolling. This restriction can be a good idea but it
results to bug-ridden explicitness which is not necessary because scrolling
should be allowed automatic by default in the first place. In this commit, we
allowed scrolling by default by:
1. We remove disableRubberbanding.
2. We set the position property of .pos to fixed. This is to accomplish the
original goal of disableRubberbanding (fixing the root element in its position).
3. We remove the touch-scrollable class as they are not needed anymore and
no style associated to it.
Removing the disableRubberbanding method also fixes the Intervention error during
touch scrolling event. The reason for that error is we are calling preventDefault
in the event that is passive. touchmove and touchstart events are passive by default
- which means that preventDefault won't work.
X-original-commit: 54f7fb49dae3aab6a005402a1ac60262bbd15edc
|
|
TASK-ID: 2230195
|
|
Electronic payment lines were not displayed correctly. We resize the
text and button and hide the delete button when a payment is done.
X-original-commit: a9c87c141459e947ccef068226f301e390536bfe
|
|
closes odoo/odoo#52871
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
The point of sale user interface has been adapted to work on mobile
devices.
We modified the design of payment lines to look like payment methods and
stack them together in the mobile view.
When you had a cash method, the amount was not preffilled during
payment, now we always prefill the amount to keep it more simple.
closes odoo/odoo#51891
Task-id: 1887609
Related: odoo/upgrade#1334
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
|
|
|
