Understanding your projects is the first step to starting to use the Connecteed feed manager. You can start to think of projects as a categorization of your tasks.
Before choosing how to use projects to separate your feeds and your sales activities, it is good to specify that each project defines a series of flow behaviors that are specific to the specific project, and cannot be shared between different projects.
In fact, the separation between projects allows you to generate completely different import/export behaviors and so we will see some good examples in this guide that will help you choose how to set up Connecteed for your purposes.
contains a database (and only one), in which you can configure infinite fields and import infinite price lists to populate your database, depending on the type of export you want to configure for the sale;
contains database correction rules internal to the project (example: percentage mark-ups on sales prices) and cannot be shared between different projects;
it can contain an unlimited number of outgoing channels towards the marketplaces or exporting textual formats (JSON, XML, CSV, TXT) with distinct rules between each channel, but always internal to the individual project.
Given these assumptions therefore, it might be useful to evaluate the following types of separation.
separate supplier lists into different projects which, although they must be sold on the same marketplaces, require configurations of rules and exclusions that are very different from each other;
separate feeds that are very different from each other in terms of database or where the combined imports cannot work because they differ both in the unique keys and in the mapping rules into separate projects;
Most Connecteed users choose to separate projects by adopting a project for each input channel (data supplier) so that it is possible to operate in a capillary manner by applying extremely precise and contextualized rules based on the database obtained from the import processes.
In fact, the separation between projects allows you to generate completely different import/export behaviors and so we will see some good examples in this guide that will help you choose how to set up Connecteed for your purposes.
In particular, each project:
contains a database (and only one), in which you can configure infinite fields and import infinite price lists to populate your database, depending on the type of export you want to configure for the sale;
contains database correction rules internal to the project (example: percentage mark-ups on sales prices) and cannot be shared between different projects;
it can contain an unlimited number of outgoing channels towards the marketplaces or exporting textual formats (JSON, XML, CSV, TXT) with distinct rules between each channel, but always internal to the individual project.
Given these assumptions therefore, it might be useful to evaluate the following types of separation.
separate supplier lists into different projects which, although they must be sold on the same marketplaces, require configurations of rules and exclusions that are very different from each other;
separate feeds that are very different from each other in terms of database or where the combined imports cannot work because they differ both in the unique keys and in the mapping rules into separate projects;
Most Connecteed users choose to separate projects by adopting a project for each input channel (data supplier) so that it is possible to operate in a capillary manner by applying extremely precise and contextualized rules based on the database obtained from the import processes.
