FAQ
-
How do I know what are the active SupplierXM attributes for a specific product category?
Go to the Attributes documentation page. From there you will be able to select a specific product category and view all its active attributes. Active attributes for all children product categories are also displayed so you do not have to go to every product category to see all attributes that you can handle using SupplierXM. When no specific product category is selected in this page, all active attributes are listed regardless for which product categories they are active. -
Some text and string attributes are language declinable, meaning those attributes can be provided in different languages (ex : product description in French and English). If I am interested in only one language how I get only this information?
There is a specific parameter in SupplierXM Products API to get only the language declinable attribute in the language(s) in which you are interested: filter_product_languages. -
How does SupplierXM map GDSN attributes into its own set of attributes?
Every time an SupplierXM attribute is mapped with a GDSN attribute, we indicate the GDSN attribute name in the description on the Attributes documentation page. Regarding product pictures exchanged through GDSN, you can find all necessary information on Media assets. -
In SupplierXM' data model, code list entities are composed of two different attributes : code and label, which one should I integrate into my system?
We recommend you to integrate codes as they are immutable. Labels can be displayed to the users of your system but shouldn't be used as the key element for integration. There is a specific parameter in SupplierXM Products API to display the label in your preferred language : Accept-language. -
Are the exportable formats generated for every product picture?
For every product picture, we generate a different exportable picture format with different resolutions, so you can integrate the resolution in which you are interested. We generate following resolutions (1024x1024, 512x512, 256x256, 128x128, 64x64). To limit, the size of the picture, all exportable pictures are converted to jpg.
When initial picture resolution is less than the SupplierXM resolution, we add white margin to reach the expected picture resolution. -
What are the differences between SupplierXM XML and JSON formats?
Attributes' type and structure are not different in SupplierXM XML and JSON formats. The only difference relies in the native differences between XML and JSON languages. XML is a markup language when JSON consists of attribute-value pairs. -
Do you have an XML schema to validate the SupplierXM XML format?
Currently we do not have such an XML schema. -
Do you have a JSON schema to validate the SupplierXM JSON format?
Currently we do not have such a JSON schema.
Updated about 1 year ago