Odoo Functional Certification cheat sheet

A lead is an unqualified contact record; converting it creates an opportunity linked to the same partner and preserves the lead's contact data.

CRM stages are configured per sales team; an opportunity's stage determines its kanban column and default probability.

Won and lost statuses are terminal; lost opportunities require a lost reason if configured on the sales team.

Lead assignment rules route leads by country, industry, tags, or sales team; assignment can be manual, random, or round-robin.

Expected revenue on an opportunity is prorated recurring revenue plus one-time revenue; probability defaults from the stage.

Activities store the next action, due date, and assigned user; completing an activity can schedule the next one.

Email aliases on sales teams or CRM settings create leads or opportunities from incoming messages.

UTM source, medium, and campaign are stored on leads and opportunities and drive campaign reporting.

Confirming a quotation changes it to a sales order and triggers delivery and/or invoicing according to product invoicing policy.

Invoicing policy "Ordered quantities" invoices on sales order confirmation; "Delivered quantities" invoices after delivery validation.

Pricelists compute unit price using fixed price, percentage, formula, or rounding; they can depend on customer, quantity, date, country, or currency.

A down payment is a product line or wizard that creates an invoice before final delivery; it is deducted from later invoices.

Storable products use inventory valuation; consumables and services do not create stock quants in the same way.

Sales order confirmation creates stock moves for storable and consumable products unless the product is a service.

Fiscal positions map taxes and accounts based on customer country or VAT, overriding default product taxes.

Sales teams group orders and salespeople; commissions can be computed on margin or revenue by team configuration.

Confirming an RFQ converts it to a purchase order; receipt and vendor bill can be generated from the confirmed order.

Bill control policy "On ordered quantities" allows billing before receipt; "On received quantities" requires validated receipt.

Vendor pricelists store supplier prices, minimum quantities, lead times, and currency per product and vendor.

Purchase agreements, or blanket orders, allow scheduled RFQs and purchase orders with negotiated prices and quantities.

A purchase order line's planned date is computed from vendor lead time and order date; receipts use that date.

Dropship route sends goods directly from vendor to customer; the purchase order generates a delivery to the customer.

Subcontracting uses a subcontractor bill of materials and a purchase order; components are sent to the subcontractor location.

Three-way matching compares purchase order, receipt, and vendor bill when bill control is set to received quantities.

Vendor bills can be created from purchase order lines; bill quantity is limited by the selected bill control policy.

Stock moves are double-entry operations between locations; validating a move creates or updates quants.

Locations have types: internal, vendor, customer, inventory loss, production, and transit; internal locations are hierarchical.

Reordering rules define minimum and maximum stock and trigger RFQs or manufacturing orders when forecasted quantity falls below the minimum.

Routes combine push and pull rules to automate receipts, deliveries, and manufacturing steps.

Lots track batches; serial numbers track individual units; both can be required by product tracking configuration.

Inventory valuation methods include standard cost, FIFO, and average cost; automated valuation posts journal entries.

Physical inventory adjusts quants to counted quantities; cycle counts can be scheduled by location or product.

Putaway rules direct incoming products to storage locations based on product or product category.

Unit of measure conversions use ratios; Odoo converts quantities between purchase, stock, and sales units of measure.

Every journal entry must balance debits and credits; posting locks the entry from further editing except through reversal.

Journals are typed sale, purchase, bank, cash, or general; each has a sequence and default accounts.

Taxes compute on invoice lines and can be price-included or excluded; tax groups aggregate taxes for reporting.

Fiscal positions remap taxes and accounts for specific customers, countries, or VAT numbers.

Payment terms compute due dates from the invoice date; installments can split the total into multiple due dates.

Bank reconciliation matches statement lines to journal items; unreconciled items affect the computed bank balance.

Multi-currency transactions post at the rate on the invoice date; exchange differences post when payment is reconciled.

Lock dates prevent posting or editing entries before a specified date.

Assets create depreciation entries over time using straight-line or declining balance methods.

A bill of materials lists components and quantities needed to manufacture one product; types include manufacture, kit, and subcontracting.

A manufacturing order consumes components and produces the finished product; confirming the order reserves components.

Operations define work centers and expected duration; work orders are generated per operation.

Work centers have capacity and cost per hour; time tracking records actual duration against work orders.

The MRP scheduler creates procurement proposals from demand, forecasts, and reordering rules.

Kits are not manufactured; delivering a kit explodes into its components as stock moves.

Unbuild orders reverse a manufacturing order, returning components and consuming the finished product.

By-products are additional outputs of a manufacturing order and can carry their own cost share.

Manufacturing lead time affects planned start dates for components and finished goods.

Tasks belong to projects and move through configurable stages; stages can be kanban columns with a folded status.

Timesheets record hours per employee, task, and date; they can be billable or non-billable.

Service products with invoicing policy "Timesheets" invoice delivered hours at the product's price.

A sales order line can create a project and task; the project is linked to the sales order for invoicing.

Planned hours set task budgets; allocated hours compare planned effort against actual timesheets.

Task dependencies enforce order; milestones mark key dates and can trigger billing.

Project visibility can be private, followers, employees, or portal users.

Subtasks inherit the parent project and can have their own assignees and stages.

Timesheet approval can require manager validation before invoicing.

Publishing a product makes it visible on the website; unpublished products remain in the backend catalog.

Product variants are created from attributes and values; each variant can have its own price and stock.

Shipping methods are delivery carriers with price rules based on weight, order total, or destination.

Payment providers such as Stripe or PayPal must be enabled and configured to accept checkout payments.

Checkout can allow guest orders or require customer account sign-in depending on website settings.

Pricelists and currencies on the website determine displayed prices for visitors.

SEO fields include page title, meta description, and keywords; they affect search engine snippets.

Cart abandonment is tracked as an eCommerce order in draft or quotation state before payment.

Multi-language websites translate pages and product names per language.

Employees belong to departments and job positions; the employee's manager drives approval hierarchies.

Contracts define working schedule, wage, and start and end dates; multiple contracts can be sequential.

Time off types define allocation, approval, and validation; allocations can be accrued or fixed.

Attendance records check-in and check-out times; kiosk mode allows badge or PIN entry.

Recruitment uses job positions, applicants, and stages; applicants can be linked to a job position.

Appraisals evaluate employees against skills and goals; skills have levels and types.

Payroll computes payslips from contracts, salary rules, and worked days or leaves.

Expense reports are employee expenses approved and posted to accounting.

Developer mode exposes the Technical menu for views, models, actions, and server actions.

Access rights grant model-level create, read, write, and delete permissions; record rules restrict rows by domain.

Groups combine access rights and record rules; users inherit permissions from all assigned groups.

Multi-company rules limit records to allowed companies; inter-company rules synchronize transactions.

Scheduled actions run server actions on a cron schedule; they can also be executed manually.

Automated actions trigger on create, write, or time conditions and can run Python code.

Email servers configure outgoing and incoming mail; aliases route incoming messages to records.

Sequences define document numbering with prefixes, suffixes, and date ranges.

XML IDs uniquely identify records and views; view inheritance uses xpath or position attributes.