Implementation Mode

Overview

Implementation Mode is used for functional Odoo setup, guided configuration, data import, task planning, and controlled execution in a connected Odoo database.

This mode is best for standard Odoo implementation work such as creating master data, setting up workflows, preparing import templates, validating files, and executing approved configuration steps.

Implementation Mode is needed to connect to the Odoo database in the project; otherwise, Odoo Pilot will not allow the use of this mode.

When to Use Implementation Mode

Use Implementation Mode when the task is related to standard Odoo setup or implementation.

Common examples include:

• Setting up CRM stages, tags, leads, and opportunities

• Creating customers, vendors, and contacts

• Creating products, product variants, categories, and pricelists

• Setting up warehouses, locations, operation types, and routes

• Preparing sales, purchase, inventory, or accounting demo flows

• Generating CSV or Excel import templates

What Implementation Mode Can Do

Implementation Mode can help with:

• Installing or checking standard Odoo apps where supported
• Creating implementation task plans
• Setting up master data
• Creating customers, vendors, products, warehouses, pricelists, and other records
• Generating CSV or Excel import templates
• Validating uploaded import files
• Importing approved data into Odoo
• Configuring workflows
• Avoiding duplicate records where possible
• Tracking task status
• Showing execution footprints
• Asking for missing information before continuing
• Retrying or reimplementing failed tasks
• Supporting rollback where available
• Allowing the user to mark tasks as reviewed after verification

Task Planning

When a requirement is submitted, Odoo Pilot may split it into tasks and subtasks.

Tasks may include:

• Required apps
• Required configuration
• Master data creation
• Import steps
• Record creation or update
• Validation checks
• Missing information
• Failed or pending actions
• User review steps

Missing Information Handling

If required information is missing or unclear, Odoo Pilot asks for the missing details before continuing.

Missing information may include:

• accounting_localization_and_tax_policy

• posting_policy

• online_payment_provider

• delivery_pricing_policy

• salary_amounts

• commission_overtime_allowance_policy

• payroll_accounting_policy

In some cases, Odoo Pilot may show an Add required/missing information popup in Re-implement button before allowing the user to proceed.

Safe Execution

Before changing records, Odoo Pilot perform checks such as:

These checks may include:

• Confirming the required Odoo app is available
• Confirming the required model exists
• Confirming required fields are available
• Searching for existing records to avoid duplicates
• Validating required values
• Checking dependencies between tasks
• Checking whether the connected user has permission
• Showing skipped, failed, or blocked steps
• Recording the result in execution footprints
• Allowing retry, reimplement, or continuation where possible

Task Panel and Execution Controls

Overview

This section explains common task actions in Implementation Mode, such as creating tasks, editing tasks, adding follow-up work, reviewing footprints, using rollback, and understanding how approval and execution work.

How to Create a Task

Users can create a task in Implementation Mode in two ways.

First, Odoo Pilot may automatically create tasks after the user submits an implementation requirement. These tasks are generated from the original prompt and may include app checks, configuration steps, master data creation, imports, validations, and review steps. In Implementation Mode, Odoo Pilot may create a task panel on the right side of the workspace. This panel helps users track the implementation flow, review task status, open execution details and add follow-up tasks.

The task panel may show:

• Total number of tasks

• Completed tasks

• Failed tasks

• Pending tasks

• Subtasks

• Task preview

• Proceed action

• Add Task option

Users can click View Tasks to open the implementation task panel when it is hidden.

Second, users can manually create a task by clicking Add Task from the task panel. 

This is useful when the user wants to extend the implementation flow after the original task plan was generated or add a follow-up task for missing, failed, or additional work.

When the user clicks Add Task, Odoo Pilot opens the Add implementation task popup.

Users can add:

• Title
  A short name for the task.
• Instructions
  The full requirement or action that Odoo Pilot should perform.
• Spreadsheet attachment
  Users can attach one CSV or XLSX file. 
• Dependencies
  Users can select prerequisite tasks that should be completed before this new task runs. This is useful when the new task depends on earlier setup, such as apps installation, customer creation, product creation, or sales order confirmation.
• Required inputs
  Users can list missing information needed for the task. Each missing item should be added on a separate line.

For example, users may add a task to:

• Create additional records
• Fix missing configuration
• Add another import step
• Verify existing records
• Continue a failed process
• Add a follow-up implementation requirement
• Run a task only after selected prerequisite tasks are completed

The Add task button becomes available after the required task details are entered.

Added tasks should be clear and specific so Odoo Pilot can execute or guide them correctly. If the task depends on earlier work, users should select the correct dependency from the prerequisite task list.

How to Edit a Task

A task should be reviewed before execution. If a task needs correction, the user can update the instruction where the interface allows editing.

This keeps the original task history clear and creates a proper follow-up record.

How to Add Subtasks

Odoo Pilot may create subtasks automatically when a task needs follow-up work, missing information, or reimplementation.

Users can also add a new related task through Add Task and select prerequisite tasks in the Dependencies field. This helps Odoo Pilot understand which earlier task must be completed before the new task runs.

Subtasks or follow-up tasks are useful when:

• A task failed
• A step was skipped
• Extra data needs to be imported
• A previous task needs verification
• A correction is required after execution

What Execution Footprints Are

The Footprints panel shows a broader execution history for the current task or chat.

It may include tabs such as:

• All

• Success

• Failed

• Rollback

They may show:

• Odoo model used
• Action type such as search, create, update, or read
• Success or failure status
• Database name
• What happened during the step
• Technical response where available
• Rollback availability where supported

Footprints help users audit the work performed by Odoo Pilot and verify whether the task actually touched the expected Odoo records.

Footprints can be opened from the Execution log button or Footprints button in the top bar or from execution-related task actions.

What Rollback Means

The Rollback button is used when Odoo Pilot can reverse a supported execution step.

Which Actions Support Rollback

Rollback may be available when Odoo Pilot incorrectly creates or updates records in a way that can safely be undone.

Rollback is useful when:

• Wrong records were created

• A task was executed with incorrect details

• The user wants to undo a recent supported change

• A test execution needs to be reverted

Rollback is not always available. Some actions, such as read-only searches, verification steps, already-existing records, or complex business flows, may not support rollback.

If rollback is not available, Odoo Pilot clearly shows that the step cannot be rolled back.

How Users Can Perform a Rollback

To perform a rollback:

1. Open the task result.
2. Click Execution log or open Footprints.
3. Check whether rollback is available for the step.
4. Click Rollback button where available.
5. Review the result after rollback.
6. Verify the record inside Odoo.

Users should only use rollback when they are sure the executed change should be undone.

How Task Approval and Execution Work

Implementation Mode usually follows a controlled execution flow.

First, Odoo Pilot prepares the task plan. The user reviews the tasks and confirms whether the plan is correct. After that, the user can proceed with execution.

During execution, Odoo Pilot checks apps, fields, records, dependencies, and required information. If something is missing, it may ask for more details before continuing.

After execution, the user should review the task summary, execution log, and footprints. The task should only be marked as reviewed after the user verifies the result inside Odoo.

What Re-Implement Means and When to Use It

The Re-implement button is used when a task needs to be run again with corrected details, missing information, or a new follow-up instruction.

It does not always mean starting from zero. It may create a follow-up subtask to complete only the missing, skipped, failed, or corrected part of the original task.

When users click Re-implement, Odoo Pilot may show a popup where they can add:

• Optional notes

• Supporting details

• Corrections

• Clarifications

• Uploaded files such as CSV, Excel, documents, or screenshots

After the user clicks Create and run, Odoo Pilot creates a reimplementation subtask and attempts the task again using the updated information.

Use Re-implement when:

• A task failed

• Required information was missing

• A task was partially completed

• Odoo Pilot skipped something important

• The result exists but needs correction

Before reimplementing, users should check the task result, execution log, and footprints to understand what was already created or updated in Odoo.

How Users Provide Master Data Files for Import

Users can provide master data files by uploading a CSV file in Implementation Mode.

Users can upload files in two common ways:

1. From the chat input
   Use this when the file is related to the current prompt or task.

2. From Add Task or Re-implement popup
   Use this when the file belongs to a specific implementation task, follow-up task, or import correction.

Before importing, Odoo Pilot should inspect the file, check the headers, validate required fields, detect missing values, and confirm whether the file is ready for Odoo import.

If the file has issues, Odoo Pilot should explain what needs to be fixed before execution.

Users should make sure the file has clean column names, correct data format, no duplicate rows, and Odoo-compatible values before asking Odoo Pilot to import it.

Data Import Workflow

A typical import flow:

1. User uploads the file in the same task.
2. Odoo Pilot validates the file.
3. Odoo Pilot imports the data if validation passes.
4. User verifies the records inside Odoo.
5. User marks the task as reviewed only after verification.

This workflow is useful for importing products, contacts, vendors, customers, pricelists, inventory data, and other master data.

Marking Tasks as Reviewed

A task should be marked as reviewed only after the user verifies the result inside Odoo.

Before marking a task as reviewed, check:

• The expected records exist in Odoo

• The correct values were created or updated

• No duplicate records were created

• The workflow works as expected

• Failed steps are either fixed or accepted

• Footprints match the actual result

If the task says completed but the record is not visible in Odoo, do not mark it as reviewed until the issue is checked.

Best Practices

Use Implementation Mode with a clear and complete requirement so Odoo Pilot can prepare better tasks, avoid unnecessary follow-up questions, and reduce repeated execution.

• Providing complete details helps Odoo Pilot understand the requirement in the first attempt. This can reduce credit usage because fewer follow-up prompts, retries, reimplementations, and corrections are needed.
• A short or unclear prompt may still work, but it can create general tasks, ask for missing information, or require multiple follow-up runs.
• A complete prompt saves time, improves accuracy, and helps avoid wasted credits.

This helps avoid duplicate records, incomplete implementation, and unnecessary repeated execution.