PrestaShop Services Implementation Guide

PrestaShop assessment

Services Implementation of the whole three level hierachy of the EGI service catalogue specified in D3.7 (only "external" services). This requires the implementation of a specific form for each service type. The specification for this is quite complete (see the deliverable) but we still need to define the service options for some services functionality can be implemented until the end of nov (for chosen for exemplary services and service options) difficulties: specific, customed form for each service type additional dev needed: no additional plug in needed: http://addons.prestashop.com/pl/20201-additional- product-attributes-custom-product-fields.html price: 62 Euro

Common attributes Prestashop cart customised to allow the customer to specify a set of "common" attributes (e.g. "quote") functionality can be implemented until the end of nov difficulties: common attributes for all service options additional dev needed: no additional plug in needed: http://addons.prestashop.com/pl/20201- additional-product-attributes-custom-product-fields.html price: 62 Euro

Workflows Implementing simple custom workflow to manage access requests. Customers need to be notified by mail after they request an access to a service. At this stage, we need to agree on simple workflow such us: 1) send an mail to training.egi.eu if a customer requests access to a training; 2) register the request of cloud resources on e-grant or in some other places, etc. These are only example, we need to agree on that. The basic idea is having something very simple that could be replaced when all the workflows are well-defined. functionality can partly be implemented by the end of Nov. Customer notifications and standard Administrator e-mail alerts are already a part of Prestashop functions. difficulties: e-mail notifications about new order can be send always on the same e- mail address (or several adressess). There is no functionality to send e-mail with notification to different e-mails (providers) due to different orders. additional dev needed: no

Providers Registration of the providers in the system. Each provider should be linked to a set of products. Providers should be visibile in the product pages. functionality can be implemented until the end of Nov difficulties: we need to add information about provider on product page. We will try to add a provider logo too. additional dev needed: yes

AAI Integration with the EGI Checkin service (AAI). Documentation on how to integrate this service is available at https://wiki.egi.eu/wiki/AAI#Documentation functionality can be implemented until the end of Nov difficulties: we need to create integration module. We will try to create it basing on Google Accounts login-in module for PrestaShop. additional dev needed: yes

PfU Basic support for pay-for-use. To be further discussed functionality can be implemented until the end of Nov difficulties: need to know which specific payment system is chosen to implement. additional dev needed: yes

Other we need to check if it is possible in Prestashop delegating the registration of new services in the system to third parties. This is a key feature that the marketplace must have when operational. There is a possibility to add user profile with permission only to add and edit products in catalogue (it is a standard feature). We think that it will be possible to create also in future a special tool which will let third-party providers to add new products to Marketplace data-base from standing-alone instance (not Prestashop backoffice). Those new products will be not active until Marketplace admin does it.

Other Adding services and manage backoffice Services will be added by one or more admins. They will have special level of access that will mage possible adding new items. There also is possible to create special profiles for providers that will only have possibility to edit informations about services and/or add new ones.

PrestaShop modifications 1. Because we sell services instead classic products we need to implement some modifications - we will try to hide all informations about shipping. In checkout we will hide section with select shipping option, we will remove information about shipping costs in cart summary and e-mail notifications. Services will be added as classic products - not virtual products. 2. On the Shipping step in checkout procedure we will put possibility of adding some extra fields to define order details by customer. 3. We will add this module: http://addons.prestashop.com/pl/20201- additional-product-attributes-custom-product-fields.html It will allow us to put limitless number of special fields where customer can specify service terms and dates (when customer wants to use service).

PrestaShop modifications 4. Also we will install this module: http://addons.prestashop.com/pl/19736- custom-checkout-and-customer-and-address-fields-manager.html - this allows us to freely add special fields on checkout procedure (details about order - for example dates of service usage). All this data will be present in backoffice and also in e-mail notifications. 5. We will implement new function where service price will be hidden if price will be set to 0.00. 6. In our opinion it will be better not to implement on-line payment system. After making order customer will see information that Customer Service will contact to confirm final cost of order. Of course it is possible to add PayPal service or any other if you wish.