Transcript
KIBO offers unrivaled flexibility for product management and easy to use UI, bulk editing tools, and publishing workflows.
With an API first platform, KIBO can easily integrate with leading PIM solutions. But because of KIBO’s robust product catalog capabilities, over ninety percent of KIBO’s customers can leverage KIBO’s out of the box catalog to meet all of their PIM needs.
Prebuilt integrations from PIMS, as well as custom built integrations to clients back office, product masters, or other PIMS, map the product data and structure from the PIMS to the product types, attributes, and individual product structures available in KIBO system, dynamically generating new product types, attributes, values, and products as they’re defined in the PIM. Product types are templates of settings and attributes created for a specific set of products. Every product in the catalog has a single product type associated to it.
As we look at our product catalog, we will see how this is managed.
Inside of the product catalog, I can search, filter, and sort to find the product that I’m looking for. Let’s look at an existing product.
When we land on the product page, you’ll notice that it’s easy to navigate with text areas for all of our inputs. One thing I’d like to point out is that for each product, multiple locales can be enabled for a single master or child catalog. This allows you to easily localize the same product information across different languages.
We also support multi currency on this same product to keep everything consistent.
Let’s head back to the main page. This product is configurable with options. So if we scroll down, you can see we have images mapped to those options.
Full pricing section, manage what happens if we encounter a stock out, the section where we define options like size, color, or whatever option is required for the product, custom property attributes like brand or rating or whatever information we need to track for this product, extras like gift wrapping, warranties, monogramming, or whatever we’d like to offer to go with the product, shipping designations, and SEO information.
If I make any changes to the product, say, I update the price, I’ll come up and save the changes, and we will see that the product gets saved in a draft status.
I could choose to publish the product now, leave it in a draft status, or move it to a published set for later. If I leave it in draft or put it in a published set, I can go out and view the product in a staging environment.
Within the staging environment, a merchant can view the whole website and shop just as a consumer does. The merchant can also view the website based on a specific date to see what the content or the website is going to look like on that day or type in a price list to see what specific price or discount scenarios will look like for customers or segments of customers.
For this situation, rather than publish it now or leave it in a draft status, I can move it into a published set.
Some merchants choose to push their products and content through a workflow of their own liking. Users can create the products and pass them to a product review team who can then pass it to a manager to review and publish.
Published sets can also be scheduled to go live at a particular date and time and have multiple different assets stored inside of them. These workloads are fully configurable and can be defined by individual retailers.
We have just walked through editing and publishing a product in the admin. There are four primary ways changes can be made inside of KIBO. The first is through the admin console, as you have just seen. The second is through the API.
KIBO offers one hundred percent API coverage of the platform. The administrative console we’ve been using today is built on KIBO’s API, meaning everything we have done and will do can also be done through the same API. The third is quick edit, which is an admin tool that allows merchants to make changes on products in bulk. And lastly is KIBO’s import export tool.
This enables merchants to make changes in bulk by exporting out data from the platform, making required updates, and importing the updated data back into the platform.
First, let’s look at quick edit.
In this example, I want to update all of My North Face products by assigning them The North Face brand under the properties attribute of brand.
I could save these changes as a draft or publish them instantly.
When we go back into the product record, we will see that the attribute of brand now has been changed to The North Face.
As mentioned earlier, the other option available for bulk editing is through the import export tool. This tool allows me to export data from all aspects of the platform, including products, through an Excel or CSV document.
Within the tool, I can export out the whole catalog or a subset of the catalog, make my changes in bulk in an Excel or CSV document, and import them back into the platform and have those changes reflected.