Catalog Foundations
When sending data, a catalog refers to the collective data describing products, related attributes and assets, and the taxonomy which organises it.
Data Processing Formats
A data file or table will be a List format unless specifically mentioning the Build format in it's name. Some are supported in either format, so this offers the choice of either format when suppling that data to FusionPlus.
Build File Format
The Build file is a multi-column format where related attriubtes are presented in columns and data is related on one row only. The Build File will be processed by FusionPlus to a List Format.
List File Format
The FusionPlus tooling can translate Build Files into List File format. The List File produces data in many related files with related product attributes stored in rows. It uses columns only where attributes relate to each other in a one to one relationship in that row. For example, the Attribute File would include columns of Attribute Label and Attribute value and rows of values, such as brand label and brand value related to a specific product.
Taxonomy vs Group data
Taxonomy data is preferred way to categorize product data. Any number of taxonomy leves is possible but ecommerce data is recommended to three levels. Group data is an legacy format which is provided as an option but not preferred. Group data has no defined structure other than what is inferred by the names of the groups.
Data formated for sending to FusionPlus
Preparing data for sending to FusionPlus can be done in a Build or List Format (see above). If not defined in the name then the list format is being used.
You can request sample file schema, field types, and sample data from FusionPlus staff. Just request a zip file of example formats and if you know you need specific file support then let us know based on the list below.
Commonly Used Data Tables
To supply catalog data for use by ERPs and Ecommerce stores, these tables are the most commonly supplied.
Product Data Files
Catalogue List — transactional product data including base selling unit of measure
Att Build/List — attribute label and attribute value for filterable and standard attributes
Images List — additional images (the primary image is in the Catalog List file)
Bullets Build — known as highlights on the API
Category Data
Taxonomy Data Files
Taxonomy Build/List — provides the structure of categories and their parents but the build format supports up to six levels only
Taxonomy Products List — links products to categoies and types
Group Data (Legacy) Files
Group Build/List
Enhanced Content Files
Additional content about products can be provided in list format for the following tables.
Alternatives
Environmental — Recycleable, Made from Recycled Materials, etc.
Synonyms
Documents — SDS (safety data sheets), Hazardous Material sheets, and others.
Linked Products
Videos
Configurable Products for EvolutionX
Product Line Variations Build — a row per finished product listing in colums the attributes and values defining the product
Product Lines Build — defines a Product Line as a row which groups the finished products defined in the Product Line Variations Build
Swatch ID list — defines a swatch as referenced in the Product Line Variations Build
Product Lines Order list — defines the sort order of product line variations within a product line
Data Not Natively Supported
Prop 65 — defines Californial Prop 65 data
Uom — alternate selling units of measure, base selling unit of measure is in the catalog table/file
Uom Waste — disposal units of measure