Documentation
Back to website >

Cutbacks

Whenever different systems have to work together, there are limitations. The more systems integrate, the more consideration must be given to each other and the more limitations such a system is subject to.

This primarily concerns the article master data entered and the characteristic tree.

Article Deletion

If in EULANDA articles are deleted or merged that already exist in the SHOP, they must also be deleted in the SHOP. If the SHOP Plug-Ins like eBay or Amazon still contain open auctions or listings, a deletion or merging in EULANDA is absolutely not recommended, because otherwise the open transactions in the SHOP can no longer be executed and retransferred without errors.

Deletion now requires some preparatory work. First such articles may no longer be used externally, then one can delete them in EULANDA and only afterwards in the SHOP. If one would delete these in the SHOP before, a background comparison would create these articles again if necessary.

Article number

The article number may only contain digits 0-9, letters A-Z, minus (-) and underscore (_) as well as the dot (.) as special characters. The article number must be allowed as file names under Windows and Linux.
Neither <>/\+ brackets or similar,
nor must the article number be "FEATURE", as this term plays a special role in the DMS system.

Imagery

Changes to images

Images that are transferred to the shop come as standard from the DMS system (= document management system). These are on the hard disk. A change in the DMS does not change the articles in the EULANDA article master, which means that an automatic export of such articles containing changed images is not possible. Instead, all articles must be exported here.
When uploading to the shop itself, the article data such as texts and prices are uploaded, but images are compared using a checksum and only uploaded if this checksum is new in the shop.

Number of images

A maximum of 15 images per article are supported, these must have the article number as the image name, followed by"-1","-2", etc. If the article number is "4711", valid image names are "4711-1.jpg", "4711-2.jpg", etc. Numbers 1-15 must be complete.

Characteristics tree

Changes to the characteristic tree

Changes to the characteristic tree do not change the articles, which means that automatic export of such articles is not possible. Instead, all articles must be exported here, since the assignment affects the complete structure. The complete export can be forced using the"Forget" parameter.

Name of the characteristic

The names in the characteristic must be allowed as URLs, that is, Internet links. Otherwise, the same restrictions apply as for the article number.

Feature pictures

If the SHOP layout should contain category images in the right area after selecting the category, this can be set in the SHOP via the layout. If this has been done, a category image must also be specified for each category in the properties of the category. The image must be entered there manually and in the DMS folder "Item" and there in the subfolder "FEATURE".

Price lists

In addition to article data, price lists can also be exported. However, if scale prices change, this does not change the article. This means that the interface cannot detect whether such an article has changed and does not automatically export accordingly.
This is done using the"Forget" parameter described in the"Parameters" chapter.

User role

So that the price list can be assigned to a customer in the shop, the name of the price list is expected as a user role in the shop. This role must therefore have been created in the shop with the name of the price list. The scale price is then linked to this role via the interface. Customers who are to receive these prices must also be in this role, which must be done manually once in the shop;
customers who are to receive these prices must also have been assigned the corresponding user role manually in the shop.

Discount groups Customer groups

Instead of price lists, discount and customer groups can also be used for "virtual" calculation of export price lists. These are always based on the net sales price of the article and use the currency"EUR", always an from quantity 1 and always only represent one scale, namely the first. Otherwise, the restrictions for price lists apply.

User role

So that the virtual price list can be assigned to a customer in the shop, the short name of the customer group is expected as the user role in the shop. This role must therefore have been created in the shop beforehand with the name of the customer group. The scale price is then linked to this role via the interface. Customers who are to receive these prices must also be in this role, which must be done manually once in the shop.

Languages

If several languages are to be used, these must also be defined for all articles that have a release. There must also be a translation for each category in the category properties.


An interface to the "Sisulizer" translation system is also available.

Variants

EULANDA supports a total of 5 variants per article. An article can therefore contain one colour, one size, one style, but a maximum of 5 at the same time in one product.
nopCommerce's integrated interface currently only accepts one variant. This is no limit in nopCommerce itself, but the interface of EULANDA to the shop.

Variant attributes

Variant attributes must be unique throughout EULANDA. If this attribute is used, it is valid for all variants. However, if this has different meanings, the individual colors or sizes must be named differently.
Attributes may not contain single quotation marks, as they are often used for the size designation"inches". This restriction does not apply to the dimensions, that is, the respective values.

Complete

Only articles that are complete can be uploaded to the SHOP system. The following points list what must be strictly observed.

A preliminary check can be switched off via various check parameters. These are described in the chapter on the parameters.

Characteristic tree assignment

This includes the assignment in a section of the article in the characteristic tree. Usually from the subpath "\SHOP".

Article picture

At least one article image must exist in the DMS (= document management system). The name of the article picture consists of the article number followed by a hyphen and a number from 1-15. All images must have either".jpg" or".png" as file format and extension. Which extension is to be used is defined in the configuration file. We recommend to use JPG as the image format, because it is about 5 times smaller than PNG files,
if there are several images, they must be numbered without gaps, for
example: "4711-1.jpg", "4711-2.jpg" etc. The file extension must be specified as specified in the configuration file. We recommend to use lower case letters. The SHOP system itself distinguishes between upper and lower case letters,
the image size should be uniform, we recommend 1200x1200 square pixels. Other values are possible, but then the images are shifted especially in juxtapositions. As a result, everything looks uneven and disorderly. In the shop itself, images are transformed into other sizes if required. On the one hand, this costs computing time and space and on the other hand, the image quality suffers.

Unblocking

Every article that is to be transferred to the SHOP must be released. This is done in the EULANDA on the extended index card of the article master.

SHOP Extension

Additional screen masks are also installed with the SHOP interface. These can contain additional information such as META information for search engines or the definition of variants. Each article can represent a certain task. It is a "single article", a "master", a "variant" or a "variant with individual listing". The assignment must always have been made if the article is to be transferred to the SHOP system.