Changes in bulk upload of variant values

Problem statement : In the current system, User has to select multiple categories one at a time to map a variant value to those categories. There was no option to map multiple categories in one go. This was time consuming and needed simplification.

a. Variant value mapping through Control panel UI : A variant value can now be mapped to all categories in one-click. User can also map a value to multiple categories by selecting the root/leaf categories.

● The category selection process under variant value-category mapping is changed to achieve this. Under Masters>Add/Edit variant value, you will see the new category tree which can be used to map variant values to categories.

Image showing the new configuration to map variant value to categories

Variant value mapping through Bulk upload: User can also map a variant value to multiple categories through bulk upload. To achieve this, use the following identifiers in Category reference column of the upload.

All- To map all categories to the variant value 

Category ref code of a root category. This will map the value to all the leaf categories under the root category.

b. Variant property rank and Variant value rank is non-mandatory:

Problem statement: Property rank and value rank are mandatory in current system. These values can be auto-incremented and user need not spend time making a unique sequence of ranks.

● Both the ranks are now non-mandatory in control panel UI and bulk uploads. If a user is not giving these values, they would be auto-incremented based on the existing highest rank.

● The ranks can be modified. Validations are in place to avoid duplicate ranks. 

Out of scope:

● Variant value mapping download sheet will not reflect the identifiers like ALL, Category root reference.

Reference: http://wiki.martjack.com/doku.php/help:products:product%20list:create%20product%20variants 

Brand Configuration to make brand-id Non-Mandatory

Problem statement: In the current system, brand is mandatory. However, most merchants create a custom brand and use it just for the purpose of product upload. Making brand non-mandatory would simplify product upload for most merchants.

● The config to make Brand Mandatory or not is given under Products>Masters>Brands

Image showing the brand configuration for a merchant

● The default setting for “Brand not mandatory” is false. You can set this to true to make Brand input optional as part of product upload.

● The setting will be applied to both add/edit single product and bulk creation/edit of products

● If you make the brand non-mandatory, you can still use brand-ids. The setting only makes the brand-id input optional.

Reference: http://wiki.martjack.com/doku.php/help%3Bproducts%3Bmasters%3Bbrands 

Bulk upload for locations

Problem statement: Merchants did not have an option to create multiple locations in one go during the merchant on-boarding. Each location had to be created through UI which was time consuming.

● Users can upload locations in bulk under under Products>Bulk tools >Bulk uploads

● Select the upload type as location and proceed to download the default template. You can then upload the updated file to create multiple locations in one go.

● Validations and data types for various fields that are part of the upload are given here

● This enhancement will greatly help QSR merchants since they have hundreds of locations.

Reference: Create anew article under product > Bulk tools > Merchant data import.

Merchant and Product level config for returns

● Merchants can now restrict the return window for products. Return window can be

configured at product level.

● To enable returns for a merchant, the merchant level config and product level config has

to be enabled. Merchant level config is given under order settings. Product level config

can be given after enabling merchant config using product upload.

Image showing the merchant level return configuration

● Once the Merchant setting is enabled, returns can be processed if the product level flag is true.

● To vary the return window at product level, User has to set “Is Returnable” flag to true and configure the “Returnable Within Days” at product level . Both these configs can be done through bulk product upload/Single product add UI.

● If at the product level, “Returnable Within Days” is set to 0 but “Is Returnable” flag is true, system will use the number of days given at Merchant level.

● The configs do not work retrospectively for order processing i.e the system considers configs at the time of order placement for skus in a order.

Reference: Add a new article Product > Add new product, but first look for an existing or relevant article. http://ecom-support.capillarytech.com/en/support/solutions/articles/4000151028-add-bundle-product 

Delete (Archive) Product

Problem statement: Merchants wanted an option to remove junk skus used for testing or any other skus which are no more being used by the merchant. We are restoring the archive functionality to achieve this.

● Once a product is deleted, it will stop showing up in Cp product search, bulk downloads, storefront search.

● User will not be able to create a product again with archived sku. The archived product can be restored by raising a request to tech support in exceptional cases.

● Only products can be archived. Variants of a product cannot be archived.

● Deleting a bundle product sku will only archive the product sku and bundle items will not be archived.

Image showing delete product option

Reference: product > Product list

Category reference config for uploads

Problem statement: In the current system, Category reference code is used to identify the category of a sku. Category reference code is a system identifier and it would be a better experience for the user to deal with identifiers like category name or category hierarchy. Client can now share data with category name or category hierarchy and the same can be used by MIS users for upload purposes without the additional step of figuring out category reference code.

● The config is given under category management and has 3 options (Category reference code, Category hierarchy, Category name ). For category hierarchy, user can input one of the three separators (>, :, /)

Image showing Category reference config for uploads

● This is a Merchant level config and will be applicable to all uploads. Currently, it is applicable to variant value upload only. Support for other uploads will be extended in subsequent release.

Out of scope

Downloads will not reflect the selected category config. This support will be extended in future releases.

Reference: Product > Category management.


Bulk upload for Geo fencing

Problem statement: In the current system, Geo-fences for stores cannot be created on bulk basis. This is time consuming and bulk upload option would help cut down on the time spent on creating geo-fences.

● Bulk upload for geo-fences is given under Products>Bulk tools >Bulk uploads.

● Select the geo-fencing as the upload type and proceed to download>update>upload the file. Any validations will be shown on Error logs page upon clicking “View log” under


● Area code field is added which uniquely identifies a geo-fence. Three actions are allowed for the upload (Add, update, delete) Following validations are in place for this upload

● This enhancement will ease the process of creating/editing geo-fences for QSR merchants.

  • By default, the action is to add the values (null in action column).
  • For updating the geo-fences, user has to give geo-fencing code and either of set1 (delivery mode-start time-end time) or set2(latitude- longitude). For updating the geo-fences, Location code is optional and if not given, the existing value will be retained.
  • For deleting, geo-fence code and delete action is mandatory and it will delete the complete geo fence details i.e set 1 and set 2.
  • For adding geo-fences, all fields are mandatory.
  • For adding and updating the lat-long pairs, at least 3 pairs are mandatory.
  • In a single upload, adding and update is not possible for the same geo-fencing code.
  • In a single upload, you can add a geo-fencing code and update another geo-fencing code.

Reference: Create anew article under product > Bulk tools > Merchant data import.

Bulk Language translation upload for Locations

Problem statement: In the current system, Translation for locations has to be done one at a time. To simplify this, Bulk upload option is provided.

● Bulk upload for geo-fences is given under Products>Bulk tools >Bulk uploads.

● Select the geo-fencing as the upload type and proceed to download>update>upload the file. Any validations will be shown on Error logs page upon clicking “View log” under Action.

Reference: Create anew article under product > Bulk tools > Merchant data import.

Bulk Imagery content changes

Problem statement: In the current system, the image sequence is unique at product sku level. When the merchants share the image file with the sequence set at variant sku level, MIS users had to transform the sequence to make it unique at sku level.

● Bulk imagery content upload sequence rules have been changed to accommodate the uniqueness of the sequence at variant sku level.

● The system will continue to support the current way of sequencing at product sku level since that implicitly also makes the sequence unique at variant sku level.

Reference: Product > Bulk tools > Bulk imaginary content upload 

Import Notifications

Problem statement: Merchants with integrations use our Dev APIs to push stock, price, tags etc into the system automatically. If a upload is validated due to some errors, Merchant has no knowledge of the validations unless they check the task history. Notifications have been enabled for imports to intimate the users on validations so that they can take appropriate actions immediately.

● Configuration for import notifications is under Bulk tools>Import notifications

● When the configured minimum percentage limit for validation errors is breached,configured users will get a notification with task id and link to the error report.

Image showing the import notifications configuration

Note: Notifications will be triggered for stock, product tag uploads and price engine v 1.

Notification for price uploads using v 2 price engine are not supported currently.

Reference:  Product > Bulk tools > Import notification

Multi-language Feed enhancements

● Multi Language support is extended to attributes of Merchant.

● Similar to categories, attribute selection also has two options. Include means user has to select all attributes explicitly. Using Exclude, user only needs to exclude few categories and all other, including ones that get added in future will be included in feed.

● Google category field support : In all multi-language feeds, google category feed field will have values from English language. This is in compliance with GMC guidelines.

Reference: Marketing > 

Default currency change option in Admin panel (Feature Intended for Tech support only)

Problem statement: Change of default currency for a sub-domain site was involved a DB action. There was no config available for this in admin panel

● Option to change the default currency of a merchant is included in the admin panel. Tech support can make these changes from admin panel.

● This change can only be made for sub-domain sites (.martjack.com). Changing default currency will also change the default culture of the merchant.

● In case of multiple cultures for a currency, user can select the culture from drop-down before proceeding to save the currency configuration.

Image showing the admin panel configuration to change the default currency