Table des matières

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.

After following the “New product” link, fill in the various requested items:

General

Behaviour

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).


Financial settings

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)

The tax-inclusive display is computed for information.


Associated resources

The product category is created beforehand via the local plugin “manage taxes” menu

Example of thumbnail:

Example of sales unit icon:

* 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.


Automation

Example: Product renewal: name of the product to renew: Extend the enrolment duration of a training.

If the product is made of several different products at the same unit price: Adding unassigned seats.

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&param2=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

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.

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.


Back to setting up and running a commercial offer -Back to the Local Shop component summary - Back to the catalogue