{{ :blocks:logo-apl.png?nolink |}} ===== Back Office: Setting up and Running a Commercial Offer ===== ===== Creating Simple Products ===== ==== Introduction ==== Products are created through the backoffice of your shop catalogue. A simple product is a product that is neither a bundle nor the result of an assembly. ==== Access ==== Go to your shop while logged in, follow the "Go to backoffice" link and follow the "New product" link. :!: Tip: To save time, once you have created a first product, you can duplicate it and modify only the settings needed to manage the second product thus created. Note that the product identification must be unique. {{ :local:shop:setup:menus-backoffice-boutique.png?nolink&800 |}} **After following the "New product" link, fill in the various requested items:** ==== General ==== {{:local:shop:setup:produit-general.png?nolink&600|}} * **Product code:** Must be unique * **Product name:** Free text * **Description:** Free text describing the product, html possible * **Product status:** Choose the state of the created product: planned, available, available (internal), suspended, restocking, sold out. ==== Behaviour ==== {{:local:shop:setup:produit-comportement.png?nolink&500|}} * **Stock:** If you manage stock, enter the quantity in stock at the time the product is created in the catalogue. * **Sales:** If you sell physical products, the quantity sold is incremented and the quantity in stock is decremented. Can serve as an indicator for forecasting or sales objectives. * **Max quantities per transaction:** Choose from the list from 1 to Unlimited. * **Only for users:** This is the choice of visibility and access condition for the product. Products visible on the shop when logged in, indifferent (both possible), or not logged in to Moodle. Choosing the product only for "Customer" users means this product is reserved for users with a customer account on the backoffice interface. //**Example:**// I have a customer account entered in the shop backoffice, and I have the customer role on the shop support space (which means I have a Moodle account elsewhere). I buy a product connected to Moodle, which is reserved for "customers" and which is of type "setting up a training session"; I will not have to designate a manager for the session I acquire, and I will automatically be enrolled as a teacher in the purchased course(s). * **Password:** Optional password for accessing the product. * **Category:** Assignment of the product to the product category or family to display on the shop front. * **Assembly:** Here we check whether the product belongs to a possible group. If the product does not belong to a group, the "No assembly" mode applies. ---- ==== Financial settings ==== * **Unit price excl. tax:** Price of the product excluding tax. Up to 5 prices excl. tax can be entered in total. The first is the one without discount, the following ones are by purchase quantity ranges with an associated price. In all cases you can only enter the price associated with the range (left column) and the end of the range (right column - the start of the range is always either 0, or the end of the previous range + 1) * A range at 0 euros is ignored. * A range starting with 0 or empty is ignored. * A range ending with 0 means "any quantity above the min". The tax-inclusive display is computed for information. * **Tax code:** Tax applied on the product. If the taxes have been created beforehand via the plugin "manage taxes" menu, simply make your choice in the drop-down list. {{:local:shop:setup:unit_prices_fr.jpg|}} ----- ==== Associated resources ==== The product category is created beforehand via the local plugin "manage taxes" menu * **Brochure:** Appears on the shop front through the "download the brochure" link - Example: drop the product brochure pdf there for sale. * **Image:** Product image. GIF, JPG or PNG format. It appears in a lightbox on the shop front when clicking on it. * **Thumbnail:** The thumbnail illustrates the product. It must be 150x150 pixels with a transparent background. Example of thumbnail:{{:local:shop:setup:product-cat2.png?nolink&100|}} * **Sales unit icon:** The icon chosen to display the quantity on the shop front each time an item of the product is added to the cart. Example of sales unit icon: {{:local:shop:setup:01seat.png?nolink&50 |}} * **Terms of sale and use text:** The specific terms of sale of each product will be aggregated with the general terms of sale of the catalogue concerned, just before the order confirmation phase. {{ :local:shop:setup:4-product-assets-fr.png?nolink&800 |}} ----- ==== Automation ==== * **Data to be provided by the customer:** Product that requires information from the customer to be fulfilled. Example: Product renewal: name of the product to renew: Extend the enrolment duration of a training. * **Enable purchase processing:** If a single simple product: Setting up a training session. If the product is made of several different products at the same unit price: Adding unassigned seats. * **Handler parameters:** Here we link the product to the relevant Moodle course(s), specifying where applicable additional parameters such as duration, group. Some generic action handlers take parameters. This field makes it possible to pass specific values depending on the product instance. For example, a generic action handler that gives student access to a course needs to know the id or name of the course concerned. This field makes it possible to specify it product by product. The general form of the parameters is a list of named parameters "URL-style": 'param1=value1¶m2=value2...' Some parameters are common to all standard handlers: 'customersupport=<%courseid%>' Determines the course that will be used to welcome the customer into a support space. If it is not defined, no support space will be set up. === Generic handler: Enrolment in a course === Handler parameters 'coursename=<%course shortname%>' As the course short name is unique in Moodle, there can be no ambiguity. 'role=<%role short name (e.g. student)%>' The short name of the role to assign 'duration=<%duration in days%>' The duration is effective from the handler execution date. === Generic handler: Course creation (pro version) === Handler parameters 'template=<%template shortname%>' As the course short name is unique in Moodle, there can be no ambiguity 'categoryid=<%category id%>' The numeric ID of the category in which the course must be created. The product owner must be Course creator (or have the appropriate capabilities) in this category for the product to be fulfilled. 'duration=<%duration in days%>' The duration is effective from the handler execution. 'groupname=<%group name%>' The group is created from the handler execution. === Generic handler: Category creation (pro version) === Handler parameters 'parentcategory=<%categoryid%>' The parent category where the subcategory in the customer's name will be created. The product owner must have a Manager role or the appropriate capabilities to allow the product to be fulfilled. === Generic handler: Role assignment on a context === Handler parameters 'contextlevel=<%contextlevelID%>' (10 = system, 40 = category, 50 = course, 70 = module, 80 = block) The context level 'instance=<%instanceID%>' The instance ID of the object according to the context level (for example the course id for level 50). The product owner must have appropriate capabilities on the designated context. 'role=<%roleshortname%>' The short name of the role to assign. //**Example of assigning a role that is not the default one in the course (teacher)** &supervisor=teacher2 or another example &supervisor=coursecreator// //**Example for a product sold by 100 whose seats are assigned to learners after the sale of the training product:** packsize=100&courselist=course-short-name&customersupport=support-course-short-name// //**Example for a product made of several different products (always at the same unit price each), the accessible products are separated in courselist by commas:** packsize=10&courselist=course-short-name1,course-short-name2,course-short-name3&customersupport=support-course-short-name// Note: courselist (list of possible items) can be replaced by a MySQL pattern select a% all products that start with a Example: courselist=a% //**Example for a single product and access to the support course:** Short name of the course concerned (shortname), and short name of the customer support course concerned (shortname): coursename=course-short-name&customersupport=support-course-short-name// * **Seat quantity address:** Choose from the drop-down list: No: For a single product - Yes: For several products No: for a bundle because seats are assigned later One seat per purchase order: in case of sale by duration of a product for example. * **Renewable:** Tick the box or not When a product is marked as renewable, it assumes that a product lifetime could be defined, counted from the purchase date (in general). This must be handled by the purchase handler linked to the product, and configured internally through handler parameters. Not all standard handlers necessarily support the notion of duration. When this option is used, the client interfaces will enable product lifecycle notifications, and will allow renewing the purchase of the same product to extend its duration. The customer will then have to provide their product code available in their customer support interface. * **Terms of sale and use:** If specific to the product; otherwise the general terms defined in the plugin settings apply. {{ :local:shop:setup:produit-automation.png?nolink&600 |}} ---- [[:local:shop:userguide:salesadmin|Back to setting up and running a commercial offer]] -[[:local:shop|Back to the Local Shop component summary]] - [[:start|Back to the catalogue]]