Summary of enhancements:
- Product attribute value upload in Bulk Product upload
- Audit logs for Product entity
- Image import to file manager from FTP
- Category input config in the product download
- Category input config in Variant value download
- SKU transaction report
- Location-wise stock and price API enhancements
Problem statement: The current way of uploading product attribute values using the “Product attribute” template is complicated and requires significant effort from MIS/merchant users to fill up the “Product attribute” template. On average merchants have 6 product attributes (sg cluster) and giving an option to add/update them through bulk product upload will help do away with a separate upload.
- Product attribute values up to 20 can be added/updated through bulk product upload
- Column names like Attribute Name 1, Attribute Value 1 should be used with their values at the end of the product upload template.
- Attribute name and Predefined attribute values should match as defined in the category attribute creation upload.
- This upload is to add/update product attributes only. It does not support variant attribute value add/update
Reference: To know more about bulk attribute upload, see Bulk product attribute download and upload.
Problem statement: Merchant users or Internal users would want to track the changes in product configurations. Tracking at user level helps identify the user who changed the configuration in case of any unintended change in configuration. It also helps track the change (Previous value vs New value).
- Audit log page is added with an option for a user to search product entity changes in a date range by selecting from and to date. Users can also search by the username to get the changes done by a user.
Image: Audit logs page on the control panel
- Product entity includes the Normal and bundle product information under Basic information, Additional information, Attributes, Images, and Locations.
Image: Illustration showing the changes made by a user (Old and New information)
- Hyperlink to audit logs page will be included in cp in the upcoming sprint release (27). For now, User can access the page using the link: https://sg.ecom.capillary.in/cp/auditlogs
Audit logs for other configurations like price list, Application settings, Locations, etc. will be planned in the JFM quarter.
Reference: To know more about product entity audit logs, see Audit logs.
Problem statement: As part of product creation, Merchants share the imagery content with MIS users so that it can be uploaded to the file manager and subsequently mapped to product SKUs.
Images are typically shared over online cloud storage and MIS users download the same and proceed to upload in the file manager. To simplify this process, a direct transfer option from their FTP storage to the file manager is provided.
- A configuration-based Image import from Merchant FTP to file manager is built
- User needs to configure the settings in the Image settings page of control panel (Settings>Application settings>Image settings)
Image: Configurations for image import from FTP
- Ftp host: Ftp host URL. Eg: data.capillarydata.com
- Source FTP folder: Folder from which images are to be picked for import. It starts with the root folder structure. Eg: CapillaryMainFolder/Subfolder/Images
- Destination folder in the file manager: Folder to which images are to be imported. Starts from the root folder structure Eg: Images/ProductImages/Source
- Ftp login username and password: Provide the login credentials of the Ftp
- Ftp image upload Dashboard monitor: Users can track the status of the upload using a dashboard monitor placed below the configuration section of Image import.
- Image formats supported are png and jpeg
- Imported images will be moved to a folder created by the system in FTP with name “Processed”
- If a user tries to import images with a file name that already exists in the destination folder in a file manager, the system will create a folder called “Skipped” in FTP and move those images into that folder. Users can then choose to delete/rename the existing images from the file manager before attempting the import again.
Reference: To know more about FTP image configuration, see Image settings.
The category reference column in product download will honor the “Category input setting” configured under category management.
Example: If category hierarchy is selected as “Category input setting” and products are downloaded, the category reference column will have category hierarchies
Category reference column in Variant value download will honor the “Category input setting” configured under category management
SKU transaction report helps to find out the changes in stock levels for an SKU at the location level in a given time range.
This report had an issue that is fixed now and users can use this report to know the changes in stock levels for an SKU. This page is available under Products>Stock management>Sku transactions report.
Image showing the stock transaction report screen
[Intended for merchants using API to update stock and price]
We have changed the response schema of Updatelocationwise stock API to include the task id of the price update. The changed schema will have two task ids each for stock and price. This will help track the imports in a better way. You will need to pass the body param TaskDetails=true to get the response in a new format. In all other cases, the response would be returned in the old format.
- In total there would be 3 task ids, Task id, stocktaskid and pricetaskid
- Task id will never be null and will reflect either stocktaskid or pricetaskid. stocktaskid will have precedence in case both task ids are generated for an import. This will also make sure current integrations don't have any problems since the current task id has the value of stock taskid
- MSMQTaskDetails API can be used to further track the status of the task as is the case currently.
Performance improvement: Response times for the LocationwiseStockPrice API are improved by implementing the batch logic. Response times are observed to come down by 72% from 74 sec to 20 sec for an API call with 6000 records.