Module installation and activation
To understand the data flow in OXID eShop functionality, have a look at the following state diagram:
![@startuml
top to bottom direction
state "Non Existing" as NonExisting : State where module\nin OXID eShop does \nnot exist yet.
state Installed: Module assets and \nconfiguration \nin place.
state Configured: State where the OXID \neShop administrator \nalready configured a \nmodule via OXID eShop \nadmin, or by editing \nconfiguration files.
state Active : At this module becomes \nactive.
[*] --> NonExisting
NonExisting --> Installed: **Installation**\nvia <i> composer install</i>
Installed --> Configured: Configure module \nvia eShop admin \nor configuration files
Configured --> Active : Module activation \nvia eShop admin \nweb interface\nor CLI command
@enduml](../_images/plantuml-ffa3262f6aadd12c86953d5e6d14355b264e97fe.png)
For more information about module installation and configuration, see Module preparation and deployment.
To understand the data flow in OXID eShop functionality, have a look at the following state diagram:
For more information about module installation and configuration, see Module preparation and deployment.