Version 18.03.2024

SECTION I. TERMS AND CONDITIONS

This Onboarding Project Plan also  is also subject to:

     (a) the Agreement including the GTCU, the STCU and their appendices;

     (b) the terms and conditions of this Project Plan; and

     (c) the provisions of any appendix, or exhibits, schedules, or attachments to, or other documents incorporated by reference in this Project Plan.

In this Project Plan, the capitalized terms used but not defined have the respective meaning attributed to those terms in the Agreement. 

The Project Plan starts within 30 (thirty) days at the latest after the effective date of the Agreement (see obligations of each party in section II and III)

LENGOW makes the HelpCenter available online. The CLIENT acknowledges it has to check the Documentation provided in the HelpCenter in order to help it through implementation and the use of the Lengow Solution.

SECTION II. CLIENT OBLIGATIONS AND SERVICE SCOPE

Based on Lengow’s vast experience with clients, we offer an efficient working methodology with one clear objective: help clients increase profitable growth.

However, for this efficient methodology to work, the CLIENT acknowledges that its close collaboration with Lengow is a key factor for the success of the Implementation.

  • CLIENT Obligations

Therefore, here is a list of the obligations for which the CLIENT is responsible, necessary conditions on Lengow’s performance :

  • The CLIENT holds primary responsibility for data quality to achieve channel requirements.
  • The CLIENT will provide all source data, in the required format, and must ensure accessibility for Lengow to perform its obligations and stability of his data during the setup phase. All source data required to support the scope is assumed to be available during the first three weeks. If additional services are asked to Lengow to support non-native data integration or data manipulation, then this may increase the project fees and timeline.
  • The CLIENT  will provide a resource(s) that is knowledgeable of their data, data mapping, and data flow. 
  • The CLIENT  holds primary responsibility to manage order actions on Marketplaces
  • The scope of this engagement will be no longer than the estimated weeks outlined in Section III of this Project Plan and activities will occur as described. In the event the CLIENT causes or creates any variance to the Project that requires additional on Lengow’s efforts such as extended timeline or additional project phase(s), section IV. “extra services & out of scope” applies.

If any CLIENT Obligations are unfulfilled or inaccurate, changing orders, pausing the process and/or increasing fees may be required to proceed with the Project.

  • Services Scope of the Standard Project Plan

The Catalogue will be implemented in Lengow (source will come from plugin, e-commerce site, manual import…) to go on a selected channel  (supported by Lengow) defined in the Statement of work that shall be completed before signature and reviewed in the Kickoff Call.

A standard project plan includes the setup of  1 catalogue with max. 10k products (skus) on 1 dedicated channel in 1 country (for example: 1 catalogue to go on Amazon FR)

To that end, Lengow will set up one Feed in the Lengow Solution for and with the CLIENT.

SECTION III. STANDARD PROJECT PLAN

Below the stages of our current standard onboarding plan for the clients first catalogue in the first channel for one country:

 

* Prior to kick-off, Lengow will share all preparation work resources

** see options here

*** see here 

**** Except for Channels Zalando and El Corte Inglés and/or Shopify CMS

***** see here

 

(1) Catalog Set-up:

  • +2 weeks in case of Zalando/Yoox/La Redoute as additional sources must be created
  • +1 week if CMS is Shopify (as additional source is required; see here) or WordPress/Woocommerce (as other Woocommerce plugins may get in conflict with Lengow connectors; see here)
  • +1 week in case of Salesforce Commerce Cloud because the client has to install a cartridge and host the data in an sFTP More info here. SFCC doesn’t allow to retrieve orders
  • In case of the Akeneo connector, it’s mandatory to define the scope, locals and currency in order to easily parse the Catalogue in Lengow (no more than 300 attributes, assets included) Parent products do not exist (see here).
  • In case of missing catalogue data according to the channel’s requirements, the CLIENT will provide the information in an additional source.
  • +1/2 weeks respectively for a Lengow FTP or SFTP Opening (just if additionally purchased)
  • Proprietary solution the project plan might be susceptible to changes
  • Catalogues with >10k Products (skus) might be susceptible to changes in the timeline

(2) Channel Set up & Publication:

  • +2/3 weeks for: Ali Express, Amazon Fashion, El Corte Inglés, Joom, Kaufland, La Redoute, Otto, Ubaldi and Zalando. These channels take a longer time to create and review products prior to publication. 

SECTION IV. EXTRA SERVICES & OUT OF SCOPE

The list of the following services are considered extra services : 

  • Cleaning or enrichment of Data via a reprocessing other than through functions available 
  • Data hosting Services
  • Providing a catalogue via developing an API connection on the CLIENT’s environment
  • Adding extra Channels (marketplaces or Marketing Channels other than the first channel in one country).
  • Extra Training other than the 3h session included.

The fees for the Standard Project set forth on the Contract are based on high-level design decisions agreed upon with the CLIENT. Any additional system functions, business processes, source systems, developments, etc. (extra services) identified between the Parties during the Implementation phase may increase the overall fees and/or timeline, which the CLIENT expressly acknowledges. Changes to the fees must be agreed upon by both Parties in an addendum to the Agreement. In this case, Lengow reserves the right to pause the Implementation until the addendum is signed by both Parties.

The list of the  following services are considered out of scope : 

  • No changes in Data Sources during the implementation phase will be considered.
  • The API to manage orders will be set up by the client following the API Documentation 
  • Distributors are responsible for account opening in the desired channels. Lengow is not responsible for delays due to third parties (developers, agency, marketplaces requirements, etc.)
  • Plugins and connectors: installation, configuration or customization of our plugins or connectors 
  • Onsite services
  • PreProduction environment has limited actions 
  • Images hosting services

SECTION V. LIABILITY

For the avoidance of any doubt, each Party’s liability however caused arising out of or in connection with this Project Plan shall be subject to the limitations of liability set out in the GTCU. 

 

SECTION VI. COMPLETION CRITERIA

  • The catalogue setup (phase I)  is complete when the Catalogue is uploaded in the Lengow Solution and the first channel is created.
  • Lengow Solution Configuration is complete when the export rate is at least over ~90% of the products selection (defined right after the catalogue setup phase) and is exported to the CHANNEL, provided that the data is present and usable in the Catalogue. Lengow and the CLIENT have to sign an acceptance report acknowledging that the configuration is complete under the criteria defined in the Project Plan between the Parties.
  • The solving of external platform errors through Lengow is limited to content related errors. Missing content must be provided by the CLIENT.
  • Training Session is completed once 3 hours sessions are done , on a maximum 4 weeks period

Once these criteria are completed, the services relating to the Implementation process of the Lengow Solution shall be deemed delivered and accepted by the CLIENT.

SECTION VII. PROJECT PLAN MODIFICATION

LENGOW reserves the right to update or amend the Project Plan on its website.