User Tools
local:shop:structure:classes:shop
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
local:shop:structure:classes:shop [2016/12/29 00:07] admin |
local:shop:structure:classes:shop [2024/05/14 15:39] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== the Shop Class ===== | + | <html><!-- nomoodle --></html>{{ :logo-apl.png?nolink |}}<html><!-- /nomoodle --></html> |
| - | ===== Moodle Integrated Shop : Structural elements ===== | + | =====Shop concept : the Shop Class ===== |
| + | ===== Moodle Shop structure documentation ===== | ||
| - | The shop denotes a scope where some customers will interact with some product lines under some commercial modalities to buy Moodle assets. | ||
| - | You will be able to create several shop instances in Moodle, having distinct product lines and distinct behaviour or seliing rules. Each Shop will be assigned a unique master Catalog. Several instances of a Shop may use the same product line (Catalog) but using distinct settings. | + | ====Introduction==== |
| The Shop class is the object counter part of a "Shop front office instance". | The Shop class is the object counter part of a "Shop front office instance". | ||
| + | The shop is basically a framework within which customers interact with certain product lines under certain conditions of sale to buy Moodle assets. | ||
| + | You will be able to create several shop instances in Moodle, that have distinct product lines as well as distinct behaviours and terms of sale. Each shop will be assigned a unique master catalogue. Several instances of a shop can use the same product line (Catalogue) but with distinct settings. | ||
| + | The shop class is the object counter part of a “Shop front office instance”. | ||
| ==== Shop properties ==== | ==== Shop properties ==== | ||
| - | Common attributes to a Shop are: | + | Common shop attributes are: |
| - | === the Catalog ID === | + | === Catalogue ID === |
| - | the ID of the master instance of a Catalog that will contain the product lines. A Shop can be assigned to only one catalog, but may use several instances of Catalogs if the master catalog is bound to slave instances. | + | The ID of the master instance of a Catalog that will contain the product lines. |
| + | A Shop can be assigned to one catalog, but may use several catalogue instances if the master catalog is linked to slave instances. | ||
| === Default currency === | === Default currency === | ||
| - | The default currency applied to the whole Shop. May be overriden at lower stage. | + | The default currency applied to the whole Shop. Can be overriden at lower stage. |
| === Front-office browsing order === | === Front-office browsing order === | ||
| - | Though most of the common shop engines are provideing a very common scenario to drive a customer from the entrance to the order confirmation, some steps may be reordered for convenience. the scenario must follow essential rules for the selling process being consistant. | + | Also most common shop engines provide a very common scenario to lead a customer from the entrance to the order confirmation, some steps can be reordered for convenience. |
| + | The scenario must follow essential rules for the sales process to remain consistent. | ||
| === Customer information options === | === Customer information options === | ||
| - | Three options allow altering what information is collected for physical persons. | + | There are three options to change what information is collected for physical persons. |
| * Ask customers for an institution (professional customers) | * Ask customers for an institution (professional customers) | ||
| - | * Ask institution for the participants when collecting participant data | + | * Ask institutions for the participants when collecting participant data |
| - | * Ask mobile phone of the participants | + | * Ask participants for mobile phone numberr |
| - | === Front-office layout options : tabbing the categories === | + | === Front-office layout options : tab categories === |
| - | A shop may choose to stack the categories of products one over the other on a single page, or tab the categories. | + | A shop can choose to stack products categories one on top of the other on a single page, or tab the categories. |
| === Default customer support course === | === Default customer support course === | ||
| - | A course can be designated to serve as customer support workspace. | + | A course can be designated to serve as customer support space. |
| - | === Force downloading the attached documents === | + | === Force download of attached documents === |
| - | Shop settings can force users to download and locally store the attached documents such as leaflets, etc. If this option is not enabled, then the document may be displayed directly in the browser if the document type is supported. | + | Shop settings can force users to download and locally store the attached documents, such as leaflets, etc. If this option is not enabled, then the document can be displayed directly in the browser if the document type is supported. |
| - | === enable taxes calculation === | + | === Enable taxes calculation === |
| - | In some cases and countries, training and course providing can be completely free of taxes. | + | In some cases and countries, training and providing course can be completely tax-free. |
| - | [[:local:shop:structure|Return to the structure summary]] | + | ---------- |
| + | <html><!-- nomoodle --></html> | ||
| + | |||
| + | [[:local:shop:structure|Back to the Moodle Shop structure documentation summary]] - [[local:shop:userguide:salesadmin|Go to Configuration and implementation of a commercial offer]] - [[:local:shop|Back to Local Shop componant ]] - [[:start|Back to catalogue]] | ||
| + | |||
| + | <html><!-- /nomoodle --></html> | ||
local/shop/structure/classes/shop.1482966423.txt.gz · Last modified: 2024/04/04 15:50 (external edit)
