Copy orders on point of sale view.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Lets Point of Sale users duplicate an existing order directly from the POS screen, creating a new draft order with the same products and details so it can be adjusted and paid.
This module adds a "Duplicate Order" button to the Point of Sale interface. Cashiers can copy the order currently open on the product screen, or select an existing order in the ticket list and duplicate it from there.
When an order is duplicated, a new draft order is created with the same order lines and copied field values. The new order gets a fresh sequence number, a new access token, a new ticket code, a new unique identifier, and the current date and time. The original order is left untouched.
- On the product screen, a "Duplicate Order" control button appears next to the other POS buttons.
- In the ticket screen, a "Duplicate Order" button is added both in the order action area and next to the invoice button.
- The module controls which fields are copied by loading the list of copyable fields from
pos.orderandpos.order.linewhen the POS session starts. - Several fields on
pos.orderare explicitly marked as not copied, includingdate_order,user_id,session_id,sequence_number,shipping_date,is_tipped,tip_amount, andticket_code.
The feature works entirely in the POS frontend and does not add new menus or backend screens.
Depends on
Models and fields (1)
- pos.order · extends an existing modeluser_id, is_tipped, date_order, session_id, tip_amount, ticket_code, shipping_date, sequence_number, last_order_preparation_change
Text generated by AI (DeepSeek) from reading the Odoo 17.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/pos.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.