odoo manifest file

Hello Odooers, Odoogig and Odoo Lovers,

In this Odoo Technical Tutorial, I would like to explain about Odoo __manifest__ file  in detail.

The manifest file serves to declare a python package as an odoo module and to specify module metadata.

A manifest file  contains a single Python dictionary, where each key specifies module metadatum.A key such as  module name, version, category, description, summary, associate views, demo, data files and also the author details


__openerp__.py  filename in odoo 9.0, 8.0 and earair version

__manifest__.py filename in odoo 10.0, 11.0, 12.0 and latest version

Brief details of odoo manifest file each keys :

name : –  name of your module which may different or same from technical name

version:-   A version of your module, when you create first time your module it will be  1.0 but after make some changes  it will be 1.2 or 1.3.

You can also write module version based on odoo version like below

odoo 8.0 =  Module version ,

odoo 12.0 =  Module version ,

sequence :-  it will represented your module position into module list.  based on sequence module will show top , bottle or in middle

category:- you need to mentioned in which category or  exiting application your module belongs. if you do not wan’t to specify the category then you can use “hidden

Here below exiting application and it’s category in odoo

  • CRM :-  Sales Management
  • Sales:-  Sales Management
  • Purchase:-  Purchase Management
  • Stock:-  Warehouse
  • Accouting:- Accounting
  • HR:- Human Resources
  • Project:-  Project Management
  • MRP:- Manufacturing
  • Point of Sale:–  Point of Sale
  • Marketing:- Tools

summary:- Short introduction about your odoo module functionality

description:-  Long introduction description about your odoo module functionality.

depends:-  Mentioned all dependent module require to develop your module. If you developing any module which is inheriting exiting module then you can specify the module name in depends.

data:- you can specify all  your odoo views file . A file like below

  • views file
  • data file
  • security file
  • access rights csv file

demo:- All demo data xml file will be listed here, while  creating database  if you mark “Load demo data” true then this demo xml file will be loaded into system

test:-  All test yml file will listed here. it wiill run based on server parameter when you start the odoo server

application:-  it will be True/False, if it’s false then application will be not show into module list.

auto_install:-  it will be True/False,  it it’s true then  your module will install automatic when  you install depends  module.

author:-  here you can specify company name or individual person name who writing the odoo module

website:- you can specify company name or individual person website name who writing the odoo module

support:- A company or individual person who will support for the odoo module

live_test_url:- You can specify test url of your server, or  youtube video link



We’d Love to Hear from You! We are happy to answer any questions, you have regarding My Training.

Mail : getodootraining@gmail.com

Skype : mayur_maheshwari1

What’s app : +919924542042

1 thought on “Odoo __manifest__.py or __openerp__.py File

  1. Paulo Matos Reply

    Great post.
    Can you please tell if there is any order for the files references we add on the “data” section?
    I am asking you that because I had some problems with the order of the files on this section.
    Perhaps it was something I did wrong but, recently I had a problem on a custom module which uses several .xml files.
    After some problems with “External id’s not found…”, I have discovered that changing the order of the xml files on the “data” section solved my problem…
    Any comments on this?
    Keep the great job.


Leave a Reply

Your email address will not be published. Required fields are marked *