howto

Canadian branch and Odoo 19 POS go-live checklist

CanadaOdoo 19Point of SaleBranchesGo-live

1. Choose a pilot branch and define ownership waves

Select a branch with representative products, tax scenarios, payment tenders, hardware and users. Name branch manager, POS lead, accountant, inventory owner, network owner, bank/provider reviewers and the person authorized to pause or reverse go-live. Later waves reuse only evidence that is actually repeatable.

Create a branch template covering entity, warehouse, journal, pricelist, taxes, receipt, user roles, devices and close procedure. Record which settings are common and which require provincial or branch variation. Do not clone a branch before reviewing those differences.

Reviewed 6 November 2026. Revalidation owners: branch manager, POS lead, accountant, network, bank and provider reviewers before subsequent waves.
  • Pilot branch and reason selected: __________
  • Wave owners and go/no-go authority: __________
  • Shared template settings: __________
  • Province/branch variations requiring proof: __________

2. Prove the site network and every physical device

Document router and connection design, expected outage behaviour, workstation/browser version, receipt printer, scanner, cash drawer, payment terminal and any customer display. Record model, firmware, driver, Odoo compatibility evidence, test owner and replacement procedure. A device appearing in a product catalogue is not proof of compatibility with this rollout.

Test a receipt with long English and French item names, barcode scanning, cash-drawer opening, printer recovery and terminal disconnect/reconnect. Label network equipment and preserve configuration backups. Payment terminals and backend-dependent features require connectivity; never infer full offline operation from a local network demo.

  • Site network and backup connectivity: __________
  • Device model, firmware and driver: __________
  • Compatibility and print/scan/drawer result: __________
  • Replacement and support procedure: __________
  • Network recovery evidence: __________

3. Accept the receipt and its tax presentation in both languages

Prepare receipts with business and branch details, customer and item descriptions, taxes, discounts, returns, cash and card tenders, change and reference. Include long mixed-language fields and multi-page output. Verify screen, PDF and printed output along with the order, invoice and accounting entry.

Use the CRA rate table only for general GST/HST/PST/RST/QST rates; item treatment and place of supply are separately reviewed. Taxable, zero-rated and exempt samples must not share a blanket tax rule.

Quebec is not an HST province. QST is calculated on the selling price excluding GST. The combined rate is 14.975% (5% GST plus 9.975% QST), not a 14.975% QST rate. Record the receipt's tax decision in the discovery workbook. Manitoba uses official RST/TVD terminology despite Odoo’s PST label. Retain the official English PST acronym for BC and Saskatchewan in French instructions.

4. Count cash and test final-cash rounding separately

Record opening float by denomination, cash sales, refunds, change, expected cash, counted cash and variance. Use a signed count at open and close with any cash movement between branch and safe or bank. Do not hide a discrepancy in a generic rounding line.

Odoo's CAD record uses Cents and 0.01 rounding; test cash-rounding configuration separately in the discovery workbook. The federal penny-withdrawal guidance applies only to the final cash payment after GST/HST when pennies are unavailable; non-cash payments settle to the cent.

  • Opening float by denomination: __________
  • Cash sales, refunds and change: __________
  • Expected and counted cash: __________
  • Final-cash rounding case and result: __________
  • Variance explanation and owner: __________

5. Test payment settlement and CPA005 bank import as different flows

For each payment provider, record merchant registration, account, terminal, currency, fee, refund, reject, gross sale, net settlement and support contact. Payment-provider documentation does not prove Canadian/CAD eligibility, and Interac e-Transfer is not a native Odoo integration.

Bank synchronization through Plaid Canada/US or Salt Edge depends on institution and Enterprise coverage and is not real-time. Keep manual statement import and reconciliation as a controlled fallback. Never record a net deposit as sales while hiding provider fees.

The separately installed l10n_ca_payment_cpa005 module generates a CPA005 TXT batch of vendor payments. The user downloads the file for subsequent import into the bank system. It is not direct transmission, payroll direct deposit, PAD collection or instant settlement. The Canadian guide says post-import processing may take up to 48 hours, not a guaranteed timeline. Test the bank’s acceptance criteria, cut-off times, fees, rejection handling and correction evidence.

  • Merchant/account/currency and provider approval: __________
  • Gross, fee, net and reference reconciliation: __________
  • CPA005 import result, reject and correction: __________
  • Manual statement fallback and reviewer: __________

6. Reconcile stock movements, landed costs and branch valuation

Test receiving, sale, return, transfer, adjustment and stock count for every representative item. Record quantity and value before and after, warehouse, lot or serial where used, accounts and expected inventory/ledger result. Do not let a service item acquire a stock balance through an incorrect mapping.

Odoo 19 landed costs can allocate eligible freight, insurance, duty and other charges. Verify AVCO/FIFO prerequisites where required and use a separate Standard Price path. Rehearse a late freight bill after a partial sale and another sale afterwards.

Record allocation basis, quantity sold and remaining, cost and value before/after, entry, inventory report and ledger. A late cost without a reviewer or a quantity without value prevents branch acceptance.

7. Test invoices, returns, credits and uninvoiced orders

Run identified and walk-in sales, partial and full returns, credit notes, discounts, tax-exempt and zero-rated cases, and a foreign-currency payment where relevant. Match each order to invoice, payment, stock movement, journal entry and report. Preserve the reason and approval for every correction.

Open and uninvoiced orders need an explicit state and owner. Tax-return documentation and “Mark as Submitted” do not transmit a return. Odoo was absent from the CRA certified software list dated 4 November 2026; record report preparation and external filing responsibility in the discovery workbook.

  • Order, invoice, payment and stock references: __________
  • Return/credit-note reason and approval: __________
  • Uninvoiced order state and owner: __________
  • Report preparation and external filing responsibility: __________

8. Rehearse offline work within the documented limits

Odoo 19 offline POS can create and manage orders during a temporary outage and synchronize later. Payment terminals, customer registration and real-time stock require connectivity, and requested invoices are generated after reconnection. Do not promise offline card acceptance, authority filing or complete branch operation.

Users must not close or reload the browser or clear site data before synchronization finishes. Run the outage with synthetic orders in a controlled environment using version-matched sandbox screens and task cards; never use production records for a restart or data-loss drill.

  • Outage scenario and synthetic order IDs: __________
  • Functions available and deferred: __________
  • Browser warning acknowledged by each user: __________
  • Reconnect start/end and synchronization state: __________

9. Recover, reconcile and close with signed evidence

After reconnection, wait for synchronization and compare local and server order counts, references and states. Then reconcile payments, stock, invoices, uninvoiced orders, processor gross/net settlement and back-office entries. Investigate duplicates before any close.

Close the POS session first: opening and counted cash, tenders, sales, returns, invoices, uninvoiced orders and differences. Then close the branch day after all sessions, bank and inventory are reconciled. Branch manager and accountant sign remaining differences with owner and due date.

Use Payments Canada wire guidance and the Bank of Canada oversight register for payment-system context, not as proof of a connector or settlement result.

  • Local/server order parity and duplicate review: __________
  • Payment, stock, invoice and entry reconciliation: __________
  • POS session close and branch-day close: __________
  • Residual owner and resolution due date: __________

10. Train, support and link the rollout to the other workbooks

Train each role on its assigned routine and exception cases. Cashiers practise sales, returns and cash control; branch managers approve closes; receivers practise stock movements; accountants reconcile; network owners lead recovery; tax and provider reviewers decide within their mandates. Cross-functional scenarios involve the relevant process owners rather than every role performing every task, with English/French instructions and useful English Odoo labels. Access is granted only after practical assessment.

Hypercare exit requires adoption evidence, clean branch closes and resolved blocking defects, not a fixed calendar promise. Provider and hardware changes trigger document and acceptance review. Keep the tax and bilingual discovery workbook, CAD reconciliation workbook and role-based training/document acceptance plan beside the branch template.

Use the QuickBooks and Zoho Books paths to prepare source evidence, then record each branch decision and acceptance owner in the workbook. Oakland is an official Odoo Gold Partner delivering remotely from the UAE; the next action is to rehearse the agreed scenarios with your process owners.

Ready to get started with Odoo?

Tell us about your business — one of our experts will get back to you within one business day.

Free consultation · No obligation