Skip to content

[16.0] [ADD] pos_multi_order_payment#1114

Open
etobella wants to merge 1 commit into
OCA:17.0from
dixmit:17.0-multiple-payment
Open

[16.0] [ADD] pos_multi_order_payment#1114
etobella wants to merge 1 commit into
OCA:17.0from
dixmit:17.0-multiple-payment

Conversation

@etobella

Copy link
Copy Markdown
Member

This module will allow you to pay several open point of sale orders at the same time.

The principal order will return the other orders amount and the other orders will be payed with this amount.

@etobella etobella force-pushed the 17.0-multiple-payment branch 2 times, most recently from 01dae43 to de93661 Compare January 3, 2024 21:40
@etobella etobella force-pushed the 17.0-multiple-payment branch from de93661 to af85e16 Compare January 24, 2024 10:31
@etobella etobella force-pushed the 17.0-multiple-payment branch from af85e16 to 4329d9c Compare January 29, 2024 09:22
@legalsylvain legalsylvain added this to the 16.0 milestone Feb 21, 2024
@legalsylvain legalsylvain changed the title [ADD] pos_multi_order_payment [16.0] [ADD] pos_multi_order_payment Feb 21, 2024
@github-actions

github-actions Bot commented Jul 7, 2024

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 7, 2024
@github-actions github-actions Bot closed this Aug 11, 2024
@cvinh

cvinh commented Aug 11, 2024

Copy link
Copy Markdown
Contributor

@legalsylvain can you please reopen and no stale ?
(BTW it's a 17.0 PR)

@etobella etobella reopened this Aug 11, 2024
@legalsylvain

Copy link
Copy Markdown
Contributor

hi @etobella. could you provide a use case ? i don't understand how it can be usefull.

thanks !

@cvinh

cvinh commented Aug 12, 2024

Copy link
Copy Markdown
Contributor

@legalsylvain I'm answering because I'm at the origin of that PR
You're in a bar, you want to pay someone else's drink who is not on your table... ;-)
You are in a store with your family, you want to pay your family's ticket but you want to do it with single payment (check or credit card). At the end, you have 2 tickets and one payment.
For us, it will be used in a vertical use case but we wanted to propose the functionality to the community

@legalsylvain

Copy link
Copy Markdown
Contributor

That makes sense ! coud you add the uses case in the description.rst file. That's allways interesting to understand why a module has been developped concretely.

thanks !

@github-actions github-actions Bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 18, 2024
@github-actions

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 22, 2024
@github-actions github-actions Bot closed this Jan 26, 2025
@cvinh

cvinh commented Feb 26, 2025

Copy link
Copy Markdown
Contributor

@etobella can you please reopen this pr and add no stale tag ?

@etobella etobella reopened this Feb 26, 2025
@etobella etobella added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Feb 26, 2025

@cvinh cvinh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to @legalsylvain we can put the module in development_status = alpha to be merged faster
https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/oca_module_lifecycle_development_status.rst

"version": "17.0.1.0.0",
"license": "AGPL-3",
"author": "Dixmit,INVITU,Odoo Community Association (OCA)",
"website": "https://github.com/OCA/pos",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"website": "https://github.com/OCA/pos",
"website": "https://github.com/OCA/pos",
"development_status": "alpha",

@cvinh

cvinh commented Sep 18, 2025

Copy link
Copy Markdown
Contributor

please rename title and update tag it's a v17 PR

@ivantodorovich

Copy link
Copy Markdown
Contributor

@legalsylvain I'm answering because I'm at the origin of that PR You're in a bar, you want to pay someone else's drink who is not on your table... ;-) You are in a store with your family, you want to pay your family's ticket but you want to do it with single payment (check or credit card). At the end, you have 2 tickets and one payment. For us, it will be used in a vertical use case but we wanted to propose the functionality to the community

Please add this to a readme/CONTEXT.md file

@ivantodorovich ivantodorovich removed the no stale Use this label to prevent the automated stale action from closing this PR/Issue. label Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants