Do you have to make data available for electronic catalogs in many different formats such as BMECAT and other XML formats, Excel, CSV formats, other text formats and formats that are completely customer-specific? Is product data going to be structured according to standard classification systems such as eCL@ss, UNSPSC or are separate product hierarchies going to be used? In practice, even with standards such as BMECAT you are faced with several variants and not just one and the structure and content of these vary, some more than others. Do you have to prepare foreign-language catalogs in these very different versions?

If some parts of your customers’ target systems cannot cope with special characters, a plain text conversion is required. In the case of other target systems which process special characters, these are supposed to be provided as entities or numerical entities in decimal or hexadecimal notation. The target system may possibly work with a certain character set and expects the data to be coded for precisely this character set.

If these are problems you experience, you should look at the benefits offered by the system from FinalCatalogs.

Electronic catalogs

FinalCatalogs allows data for electronic catalogs to be made available in all conceivable export formats. Control documents are produced in XML format to define the structure and content of the electronic catalog. The control documents are used as a basis to export data in one step, without the need for manual intervention or any other preparation.

The control documents can be produced and edited by your employees. No external programming whatsoever is required to prepare a new export format. An interface is available that can also be integrated with the Visual Basic Scripts of the company producing the catalog, thus ensuring that even the most elaborate customer requirements can be solved.

Print Version

Home  |  FC System features  |  System comparison  |  Electronic catalogs  |  Legal information  |  Contact  |  Email
German Version