Q. What are the file formats you can upload your catalog in?

A. Unbxd supports catalog in CSV, JSON, and XML formats.

The schema should be uploaded separately in JSON format before uploading the catalog in CSV or XML format. The uploads in CSV and XML via SFTP are converted to JSON format by Unbxd and then uploaded via the feed API.

Q. What is the maximum feed size supported by Unbxd?

A. Unbxd systems are designed to handle extremely large catalog sizes. However, large catalogs require certain custom optimizations to offer the best results.

Unbxd feed system has supported feed files meeting the following specifications in the past:

• File size: 50GB+
• Product SKUs : 150Mn+
• Fields per product: 25000+
• Variants per product: 5000+

Q. What happens when a new schema file is sent with some new fields?

A. Schema file uploads are handled on the Unbxd end in the following manner :

• If the new schema file has fields that already existed in the schema, but values corresponding to them are modified, then the schema is updated with the modified values of the field
• If the new schema file has new fields, then the new fields are added to the previously existing schema

Q. Can we delete a deprecated field from the Schema file?

A. No, currently there is no mechanism to delete a field from the schema. However, presence of deprecated fields in the schema doesn’t affect the search results anyway.

Deletion of a field from the schema can lead to corruption of the search & category index resulting in downtimes. Unbxd team can delete the deprecated fields from the schema from the backend if it’s extremely necessary. However, these requests can take some time.

Q. Can schema upload fail because ‘Autosuggest’ parameter wasn’t specified in the schema file?

A. Yes. The Autosuggest parameter is marked as ‘Required’. It is mandatory to specify the Autosuggest parameter in the schema file for all the fields. These are the mandatory and optional parameters:

• fieldname (required)
• datatype (required)
• multiValue (required)
• Autosuggest (required)
• isVariant (Optional)
• id (Optional)

Q. What are the type of feed uploads?

A. Unbxd supports three types of feed uploads:

• Full Feed Upload: When you upload your entire catalog. *(Recommended frequency is once a day)
• Delta Upload: When you want to upload only a few modified fields (like price changes or color additions) of your catalog, use the delta feed upload.
• Single Feed Upload: When you want to update a single attribute of your feed, use single feed upload.

Q. We accept JSON, XML, and CSV but is JSON the only format that can be uploaded by the customer through feed API?

A. Yes. We only support JSON via feed API. Also, XML and CSV via SFTP won’t be self serve. Unbxd will anyway need to transform these files to JSON, and then call our feed API internally. Eventually, everything needs to pass via the feed API.

Q. How do we show variants of a product?

A. Variants are properties of a product with different values. Suppose, a product is available in five different colors then that means the product has five different variants.

To integrate variant functionality we have to set variants=true (to enable variants).

Our Search API returns parent products with variants, and never just the variants. Some of the variant properties are:

• By using variants.count, we can define how many variants of a product need to be returned.
• We also have a predefined attribute (relevantDoc) in our API response that informs the customer if the parent product should be displayed or variant – given we send both back in the response.