Cashier
Products, buttons, categories, prices, taxes, customer data, permissions, and POS configuration determine what the cashier can sell.
Odoo 19 POS and Kitchen Guided Plan
Keep the Customer, Cashier, Kitchen, Stock, and Accounting in One Flow.
A successful POS transaction depends on more than taking an order. Products, taxes, sessions, payment methods, restaurant configuration, kitchen preparation, stock movements, refunds, customer invoices, cash control, and Accounting must continue working after the cashier presses the payment button.
Connect cashier to kitchen
Validate payments and stock
Close sessions with clearer control
One restaurant order — one connected flow
01
Customer & Cashier
Table, products, quantities, price, taxes, notes, and order
Order
02
Kitchen Preparation
Preparation area, product routing, status, and handoff
Prepare
03
Payment & Stock
Payment method, receipt, invoice when required, and inventory effect
Settle
04
Session & Accounting
Cash difference, closing, sales data, and financial handoff
Validate
Where the visible problem may really begin
The customer sees one transaction. Odoo may be coordinating several workflows behind it.
A missing kitchen item, wrong total, unavailable payment method, incorrect stock quantity, failed refund, or unexplained session difference may originate in product data, POS settings, preparation configuration, Inventory, payment setup, permissions, session control, or Accounting.
Kitchen
Preparation areas, product routing, restaurant order changes, status, and handoff determine whether the kitchen receives the right work at the right time.
Products
Shared product settings can influence sale price, tax, POS availability, preparation routing, stock movement, revenue, and other connected applications.
Payment
Cash, card, bank-linked or other configured payment methods determine how the order is settled and how session totals are interpreted.
Stock
POS sales may affect inventory quantities, replenishment needs, locations, returns, and product availability for other channels.
Accounting & Closing
Taxes, payment methods, customer invoices, session totals, cash differences, journals, and financial configuration determine the downstream accounting result.
Fixing the cashier screen alone may not fix the transaction. The correct test follows the order from customer entry through preparation, payment, stock movement, refund behavior, session closing, and financial handoff.
Six guided POS and Kitchen outcomes
Build the POS around the service flow your operation actually needs.
The guided plan organizes POS and restaurant operations into practical outcome groups so cashier setup, restaurant service, kitchen preparation, payment, refunds, stock, closing, and accounting can be tested together.
POS configuration, products, categories, taxes, cashier experience, and devices
Configure the sales screen around the products and operating model cashiers actually use while keeping the shared product and tax data consistent.
- POS configuration and operational settings
- Available products and POS categories
- Prices and applicable taxes
- Cashier usability and permissions
- Relevant supported device dependencies
Intended result: a cashier flow that is easier to operate and validate.
Payment methods, cash control, receipts, customer invoices, and collection
Define how customers settle orders and how cash, configured payment methods, receipts, invoicing, and session totals should behave together.
- Cash and configured payment methods
- Payment-method responsibilities
- Receipts and customer information
- Customer invoicing where required
- Cash-control and settlement awareness
Intended result: payment handling that is easier to reconcile with the order and session.
Restaurant floors, tables, orders, transfer, splitting, and service flow
Structure the restaurant experience from seating and table order entry through order changes, movement, splitting, customer service, and final settlement.
- Restaurant floors and tables
- Table-based order entry
- Order transfer where applicable
- Split-bill or split-order scenarios
- Service handoff and customer settlement
Intended result: a restaurant flow that follows the real customer journey.
Kitchen display, preparation areas, product routing, status, and handoff
Connect ordered products to the preparation process so kitchen or preparation teams can receive the relevant items, update progress, and hand completed work back to service.
- Preparation or kitchen-display setup where used
- Preparation areas and product assignment
- Order-item routing
- Preparation status
- Kitchen-to-service handoff
Intended result: preparation work that is easier to organize and follow.
Refunds, returns, sessions, cash differences, and closing
Prepare the operation for exceptions and end-of-shift control rather than designing only the ideal sale.
- Refund and return workflows
- POS session control
- Opening and closing procedures
- Cash counts and differences
- Exception review before closing
Intended result: session closing that is easier to review and explain.
Inventory movement, accounting entries, sales data, and reporting integration
Validate what the POS transaction creates outside the front counter, including stock effects, financial handoff, sales information, and management visibility.
- Inventory movement and returns
- Sales and payment data
- Tax and accounting dependencies
- Session and order reporting
- Cross-application validation
Intended result: stronger visibility from POS activity into operational and financial results.
Practical restaurant scenario
Move a restaurant order from table to kitchen preparation, payment, stock update, and session closing without losing a step.
The guided approach separates activation, configuration, execution, connected dependencies, and validation so the restaurant order can be tested as a complete operational cycle rather than as a cashier-only transaction.
Activation
Confirm the POS and restaurant capabilities required by the operating model.
Review the settings needed for restaurant operation, floors and tables, preparation or kitchen display where used, payment methods, customer invoices, cash control, stock behavior, and other supported POS features before changing the live order flow.
Configuration
Configure the POS, restaurant layout, products, taxes, preparation routing, and payments.
Confirm the POS configuration, available products, categories, sale prices, taxes, floors, tables, preparation areas, product preparation assignment, payment methods, customer-invoice behavior, permissions, and session responsibilities.
Execution
Run the real table-to-kitchen-to-payment transaction.
Open the POS session, select the table, add the products, confirm that relevant items reach preparation, update preparation status, complete the customer service flow, collect payment through the intended method, and issue the appropriate receipt or invoice.
Dependencies
Check product, Inventory, Accounting, Purchase, Manufacturing, Sales, and Expense dependencies.
Confirm whether the sale changes stock quantities, whether replenishment or purchasing is required, whether prepared products depend on manufacturing logic, whether shared Sales product data is affected, and whether taxes, payment methods, customer invoices, or operating expenses require additional financial review.
Validation
Test the completed order, a refund or return, payment totals, stock result, and session closing.
Verify the order value, taxes, preparation status, payment method, receipt or invoice, inventory effect, refund behavior where relevant, cash or payment totals, session difference, closing result, sales reporting, and connected Accounting outcome before relying on the setup.
Intended POS and restaurant outcomes
The goal is a smoother service cycle from customer order through operational and financial closing.
These are intended outcomes of a well-designed and validated POS workflow. Actual results still depend on product data, configuration, devices, payment setup, staff permissions, operating discipline, Inventory, Accounting, and other connected applications.
Faster service
A clearer cashier and restaurant workflow can reduce unnecessary steps between order entry, preparation, service, and settlement.
Organized kitchen
Preparation items can be routed and followed more deliberately when products, preparation areas, and statuses are aligned.
Clearer closing
Payment totals, cash differences, refunds, sessions, and closing responsibilities become easier to review.
Stronger integration
POS activity can be validated against Inventory, Accounting, Sales data, replenishment, and other operating workflows.
The advisor method
From the service result you need to the screen, dependency, transaction, refund, and close that prove it works.
ERP Workflow Advisor separates configuration from execution, identifies screen-level paths, checks product and payment dependencies, considers permissions and connected applications, then turns the setup into a complete POS test cycle.
Screen-level paths
App → Configuration → Screen → Record → Operational Session
Identify where the relevant POS or restaurant setting is configured and distinguish it from the live POS screen used by cashiers and service staff.
Product and preparation dependencies
Product → POS → Preparation → Service
Review shared product data, POS availability, category, tax, pricing, and preparation behavior before duplicating products or compensating for an upstream setup problem.
Payment and accounting dependencies
Payment Method → Session → Closing → Accounting
Connect cash and other configured payment methods to session totals, customer invoices where used, closing controls, and financial handoff.
Permission awareness
Cashier → Manager → Refund → Close
Consider which users can open or close sessions, change prices or discounts, process refunds, manage cash, edit configuration, or review operational results.
Full test order
Open → Order → Prepare → Pay → Stock → Review
Test the operating configuration with a representative customer order so service, preparation, taxes, payment, receipts, inventory effects, and reporting can be reviewed together.
Refund and closing test
Refund / Return → Payment Impact → Session Close → Validate
Test an exception as well as a normal sale. Review refund or return behavior, payment totals, stock movement, cash differences, session closing, and the connected accounting result.
Connected applications
POS may be the front counter, but the transaction continues across the ERP.
The customer sees one order while Odoo may be updating stock, creating financial results, consuming or replenishing products, sharing sales data, and interacting with several other business processes.
Financial connection
Accounting
POS taxes, payment methods, customer invoices,
session totals, journals, cash differences, and closing
can create financial results that Accounting must reflect correctly.
Open Accounting Guided Plan →
Stock connection
Inventory
POS sales and returns can affect available stock,
locations, replenishment, product availability,
reservations, and other sales or operating channels.
Open Inventory Guided Plan →
Production connection
Manufacturing
Prepared or manufactured products may depend on BOMs,
ingredients, finished-goods availability, production timing,
and replenishment before the POS can continue selling reliably.
Open Manufacturing Guided Plan →
Supply connection
Purchase
Fast-moving products and ingredients may require regular replenishment.
Vendor lead times, incoming stock, receipt timing,
and purchasing rules can affect POS availability.
Open Purchase Guided Plan →
Commercial connection
Sales
POS and Sales may share products, prices, taxes,
customers, stock, and commercial data even though
the transaction experience is different.
Open Sales Guided Plan →
Operating-cost connection
Expenses
Restaurant and retail operating expenses,
employee spending, reimbursements, and supporting costs
should remain distinguishable from POS revenue and payment flows.
Open Expenses Guided Plan →
Access options
Choose how long you want ERP Workflow Advisor available.
Use the same advisor while configuring POS, restaurant service, kitchen preparation, payment methods, refunds, stock behavior, session closing, or following dependencies into Accounting, Inventory, Manufacturing, Purchase, Sales, Expenses, and other supported Odoo areas.
30-Day Membership
$8.99
30-day ERP guidance access period
Suitable for a focused POS or restaurant setup, implementation phase, workflow review, training period, or short-term Odoo project.
- Access to ERP Workflow Advisor
- POS, Kitchen, and supported application guidance
- Private working area and workflow continuity
- Configuration, execution, refund, and closing guidance
Unlimited Access
$149
One-time payment for unlimited access under the service terms
Designed for Odoo professionals, business owners, implementation teams, restaurant operators, and service providers who expect to return to the advisor across multiple applications and projects.
- One-time payment for this access product
- No monthly renewal for this product
- The same ERP Workflow Advisor workspace
- Long-term use across supported guided-plan topics
Need to compare the available access options first? View ERP Workflow Advisor pricing.
Start with the required service result
Do not begin with the POS menu you assume is correct.
Start with the result you need: configure a cashier station, build the restaurant floor, send the right products to preparation, organize kitchen handoff, configure payments, issue a customer invoice, process a refund, update stock correctly, explain a cash difference, close the session, or understand the Accounting result. Then configure the relevant screens, run a complete test order, test an exception, and validate the operational and financial cycle.
Odoo 19 POS and Kitchen Guided Plan
Keep the Customer, Cashier, Kitchen, Stock, and Accounting in One Flow.
A successful POS transaction depends on more than taking an order. Products, taxes, sessions, payment methods, restaurant configuration, kitchen preparation, stock movements, refunds, customer invoices, cash control, and Accounting must continue working after the cashier presses the payment button.
Connect cashier to kitchen
Validate payments and stock
Close sessions with clearer control
One restaurant order — one connected flow
01
Customer & Cashier
Table, products, quantities, price, taxes, notes, and order
Order
02
Kitchen Preparation
Preparation area, product routing, status, and handoff
Prepare
03
Payment & Stock
Payment method, receipt, invoice when required, and inventory effect
Settle
04
Session & Accounting
Cash difference, closing, sales data, and financial handoff
Validate
Where the visible problem may really begin
The customer sees one transaction. Odoo may be coordinating several workflows behind it.
A missing kitchen item, wrong total, unavailable payment method, incorrect stock quantity, failed refund, or unexplained session difference may originate in product data, POS settings, preparation configuration, Inventory, payment setup, permissions, session control, or Accounting.
Cashier
Products, buttons, categories, prices, taxes, customer data, permissions, and POS configuration determine what the cashier can sell.
Kitchen
Preparation areas, product routing, restaurant order changes, status, and handoff determine whether the kitchen receives the right work at the right time.
Products
Shared product settings can influence sale price, tax, POS availability, preparation routing, stock movement, revenue, and other connected applications.
Payment
Cash, card, bank-linked or other configured payment methods determine how the order is settled and how session totals are interpreted.
Stock
POS sales may affect inventory quantities, replenishment needs, locations, returns, and product availability for other channels.
Accounting & Closing
Taxes, payment methods, customer invoices, session totals, cash differences, journals, and financial configuration determine the downstream accounting result.
Fixing the cashier screen alone may not fix the transaction. The correct test follows the order from customer entry through preparation, payment, stock movement, refund behavior, session closing, and financial handoff.
Six guided POS and Kitchen outcomes
Build the POS around the service flow your operation actually needs.
The guided plan organizes POS and restaurant operations into practical outcome groups so cashier setup, restaurant service, kitchen preparation, payment, refunds, stock, closing, and accounting can be tested together.
POS configuration, products, categories, taxes, cashier experience, and devices
Configure the sales screen around the products and operating model cashiers actually use while keeping the shared product and tax data consistent.
- POS configuration and operational settings
- Available products and POS categories
- Prices and applicable taxes
- Cashier usability and permissions
- Relevant supported device dependencies
Intended result: a cashier flow that is easier to operate and validate.
Payment methods, cash control, receipts, customer invoices, and collection
Define how customers settle orders and how cash, configured payment methods, receipts, invoicing, and session totals should behave together.
- Cash and configured payment methods
- Payment-method responsibilities
- Receipts and customer information
- Customer invoicing where required
- Cash-control and settlement awareness
Intended result: payment handling that is easier to reconcile with the order and session.
Restaurant floors, tables, orders, transfer, splitting, and service flow
Structure the restaurant experience from seating and table order entry through order changes, movement, splitting, customer service, and final settlement.
- Restaurant floors and tables
- Table-based order entry
- Order transfer where applicable
- Split-bill or split-order scenarios
- Service handoff and customer settlement
Intended result: a restaurant flow that follows the real customer journey.
Kitchen display, preparation areas, product routing, status, and handoff
Connect ordered products to the preparation process so kitchen or preparation teams can receive the relevant items, update progress, and hand completed work back to service.
- Preparation or kitchen-display setup where used
- Preparation areas and product assignment
- Order-item routing
- Preparation status
- Kitchen-to-service handoff
Intended result: preparation work that is easier to organize and follow.
Refunds, returns, sessions, cash differences, and closing
Prepare the operation for exceptions and end-of-shift control rather than designing only the ideal sale.
- Refund and return workflows
- POS session control
- Opening and closing procedures
- Cash counts and differences
- Exception review before closing
Intended result: session closing that is easier to review and explain.
Inventory movement, accounting entries, sales data, and reporting integration
Validate what the POS transaction creates outside the front counter, including stock effects, financial handoff, sales information, and management visibility.
- Inventory movement and returns
- Sales and payment data
- Tax and accounting dependencies
- Session and order reporting
- Cross-application validation
Intended result: stronger visibility from POS activity into operational and financial results.
Practical restaurant scenario
Move a restaurant order from table to kitchen preparation, payment, stock update, and session closing without losing a step.
The guided approach separates activation, configuration, execution, connected dependencies, and validation so the restaurant order can be tested as a complete operational cycle rather than as a cashier-only transaction.
Activation
Confirm the POS and restaurant capabilities required by the operating model.
Review the settings needed for restaurant operation, floors and tables, preparation or kitchen display where used, payment methods, customer invoices, cash control, stock behavior, and other supported POS features before changing the live order flow.
Configuration
Configure the POS, restaurant layout, products, taxes, preparation routing, and payments.
Confirm the POS configuration, available products, categories, sale prices, taxes, floors, tables, preparation areas, product preparation assignment, payment methods, customer-invoice behavior, permissions, and session responsibilities.
Execution
Run the real table-to-kitchen-to-payment transaction.
Open the POS session, select the table, add the products, confirm that relevant items reach preparation, update preparation status, complete the customer service flow, collect payment through the intended method, and issue the appropriate receipt or invoice.
Dependencies
Check product, Inventory, Accounting, Purchase, Manufacturing, Sales, and Expense dependencies.
Confirm whether the sale changes stock quantities, whether replenishment or purchasing is required, whether prepared products depend on manufacturing logic, whether shared Sales product data is affected, and whether taxes, payment methods, customer invoices, or operating expenses require additional financial review.
Validation
Test the completed order, a refund or return, payment totals, stock result, and session closing.
Verify the order value, taxes, preparation status, payment method, receipt or invoice, inventory effect, refund behavior where relevant, cash or payment totals, session difference, closing result, sales reporting, and connected Accounting outcome before relying on the setup.
Intended POS and restaurant outcomes
The goal is a smoother service cycle from customer order through operational and financial closing.
These are intended outcomes of a well-designed and validated POS workflow. Actual results still depend on product data, configuration, devices, payment setup, staff permissions, operating discipline, Inventory, Accounting, and other connected applications.
Faster service
A clearer cashier and restaurant workflow can reduce unnecessary steps between order entry, preparation, service, and settlement.
Organized kitchen
Preparation items can be routed and followed more deliberately when products, preparation areas, and statuses are aligned.
Clearer closing
Payment totals, cash differences, refunds, sessions, and closing responsibilities become easier to review.
Stronger integration
POS activity can be validated against Inventory, Accounting, Sales data, replenishment, and other operating workflows.
The advisor method
From the service result you need to the screen, dependency, transaction, refund, and close that prove it works.
ERP Workflow Advisor separates configuration from execution, identifies screen-level paths, checks product and payment dependencies, considers permissions and connected applications, then turns the setup into a complete POS test cycle.
Screen-level paths
App → Configuration → Screen → Record → Operational Session
Identify where the relevant POS or restaurant setting is configured and distinguish it from the live POS screen used by cashiers and service staff.
Product and preparation dependencies
Product → POS → Preparation → Service
Review shared product data, POS availability, category, tax, pricing, and preparation behavior before duplicating products or compensating for an upstream setup problem.
Payment and accounting dependencies
Payment Method → Session → Closing → Accounting
Connect cash and other configured payment methods to session totals, customer invoices where used, closing controls, and financial handoff.
Permission awareness
Cashier → Manager → Refund → Close
Consider which users can open or close sessions, change prices or discounts, process refunds, manage cash, edit configuration, or review operational results.
Full test order
Open → Order → Prepare → Pay → Stock → Review
Test the operating configuration with a representative customer order so service, preparation, taxes, payment, receipts, inventory effects, and reporting can be reviewed together.
Refund and closing test
Refund / Return → Payment Impact → Session Close → Validate
Test an exception as well as a normal sale. Review refund or return behavior, payment totals, stock movement, cash differences, session closing, and the connected accounting result.
Connected applications
POS may be the front counter, but the transaction continues across the ERP.
The customer sees one order while Odoo may be updating stock, creating financial results, consuming or replenishing products, sharing sales data, and interacting with several other business processes.
Financial connection
Accounting
POS taxes, payment methods, customer invoices,
session totals, journals, cash differences, and closing
can create financial results that Accounting must reflect correctly.
Open Accounting Guided Plan →
Stock connection
Inventory
POS sales and returns can affect available stock,
locations, replenishment, product availability,
reservations, and other sales or operating channels.
Open Inventory Guided Plan →
Production connection
Manufacturing
Prepared or manufactured products may depend on BOMs,
ingredients, finished-goods availability, production timing,
and replenishment before the POS can continue selling reliably.
Open Manufacturing Guided Plan →
Supply connection
Purchase
Fast-moving products and ingredients may require regular replenishment.
Vendor lead times, incoming stock, receipt timing,
and purchasing rules can affect POS availability.
Open Purchase Guided Plan →
Commercial connection
Sales
POS and Sales may share products, prices, taxes,
customers, stock, and commercial data even though
the transaction experience is different.
Open Sales Guided Plan →
Operating-cost connection
Expenses
Restaurant and retail operating expenses,
employee spending, reimbursements, and supporting costs
should remain distinguishable from POS revenue and payment flows.
Open Expenses Guided Plan →
Access options
Choose how long you want ERP Workflow Advisor available.
Use the same advisor while configuring POS, restaurant service, kitchen preparation, payment methods, refunds, stock behavior, session closing, or following dependencies into Accounting, Inventory, Manufacturing, Purchase, Sales, Expenses, and other supported Odoo areas.
30-Day Membership
$8.99
30-day ERP guidance access period
Suitable for a focused POS or restaurant setup, implementation phase, workflow review, training period, or short-term Odoo project.
- Access to ERP Workflow Advisor
- POS, Kitchen, and supported application guidance
- Private working area and workflow continuity
- Configuration, execution, refund, and closing guidance
Unlimited Access
$149
One-time payment for unlimited access under the service terms
Designed for Odoo professionals, business owners, implementation teams, restaurant operators, and service providers who expect to return to the advisor across multiple applications and projects.
- One-time payment for this access product
- No monthly renewal for this product
- The same ERP Workflow Advisor workspace
- Long-term use across supported guided-plan topics
Need to compare the available access options first? View ERP Workflow Advisor pricing.
Start with the required service result
Do not begin with the POS menu you assume is correct.
Start with the result you need: configure a cashier station, build the restaurant floor, send the right products to preparation, organize kitchen handoff, configure payments, issue a customer invoice, process a refund, update stock correctly, explain a cash difference, close the session, or understand the Accounting result. Then configure the relevant screens, run a complete test order, test an exception, and validate the operational and financial cycle.