POS Split, Merge & Transfer Bills

This is a build-to-order module, not an instant apps.odoo.com download. After a short scoping call to confirm your Odoo version, POS configuration, payment methods, and receipt needs, ECOSIRE develops and tests the module, deploys it to a staging copy of your instance for you to validate, then goes live and trains your team. Typical end-to-end delivery is 2–4 weeks depending on the number of split modes, receipt customizations, and approval rules you need.

Every build ships with a defined post-launch support window covering bug fixes and configuration adjustments, plus a named point of contact. You receive written documentation and a live staff training session. Because Odoo APIs change between major versions, we build against your current release (17, 18, or 19) and can quote a paid compatibility upgrade when you later move to a newer Odoo version — your source and version-tagged release are handed over so nothing is locked to us.

Both. The module extends the standard point_of_sale app that ships in Community and Enterprise alike, using the ORM, OWL POS frontend, ir.model.access.csv security, and QWeb receipts. We confirm your edition and version during scoping and test the build on that exact target across Odoo 17, 18, and 19.

Yes. Every split creates real pos.order records with proper lines, taxes, and payments, and merges/transfers write back to pos.order with a source-order reference and audit metadata. Totals, tax lines, and payment breakdowns flow into your session summary, Z-report, and accounting exactly as native orders do, so cash-up and month-end stay clean.

Native Odoo POS lets you split a payment across tenders but does not cleanly split a bill by person or item into separate receipts, does not merge open tables, and has no first-class order transfer between tables or waiters. This module adds split by item, quantity, equal share, custom amount, and by number of persons — each as its own payable order with its own receipt — plus merge and transfer, all permission-gated.

Absolutely. Access is enforced through ir.model.access.csv and record rules, so you can gate splitting, merging, and transferring by POS role. For higher-risk actions like merging full tables or splitting above a value threshold, we can wire an optional manager-approval step using an automated/server action so a supervisor confirms before the operation commits.