Icecat Commerce Sprint Review

In this sprint, our main focus was on our ongoing project: transitioning to the new User Interface of Icecat PIM:

• We worked closely with the team to decide on the layout, UI elements, colors, etc. It was especially important to establish standards for our future implementation.
• The future Icecat PIM UX shall be responsive, catering not only to 1920-resolution screens but also to tablets and mobile devices.
• For ongoing Icecat PIM tasks, we incorporated external (Icecat) attribute IDs in product types for each attribute for the interface.
• We also added Icecat attribute IDs, as well as product type’s external (Icecat) IDs, into XML standard exports.
• Implemented checkboxes for all sub-locks when main locks are selected in the product edit for clarity on how the locks work.
• The functionality to retrieve Icecat categories during the Icecat enrichment process has been added. Previously, categories were assigned from Icecat Connect. Now, the user can decide whether to obtain categories from Icecat Connect, Icecat Catalog or to retrieve Icecat categories only for products without Icecat Connect’s categories. This will be particularly useful for plugins that fetch products from shops, enrich them with Icecat, and import them back to the shop.

Icecat connectors updates: 

• WooCommerce: Updated attribute grouping and extra attribute data export.

• Shopify: Provided additional features to help with the web-shop interface of product style content.

• Odoo: Improved product import and enriching steps

Final Thoughts

It’s important to note that our sprints typically last for three weeks. While some features are completed within a single sprint, certain developments may extend beyond one sprint duration. All our functionalities undergo thorough testing to ensure quality. Therefore, finishing a feature/ development in the sprint does not automatically result in immediate availability for our users. Rest assured, we will communicate with all our customers about the new release dates, provide release logs, and offer explanations on what features are inside and how they work via our blog.