End-to-end demo of Salesforce Commerce Cloud starter kit

Transcript

Alright, it’s demo time. In the previous videos, we have configured everything we need in order for our SFCC Commerce Optimizer Starter Kit to keep data in sync between Salesforce Commerce and Commerce Optimizer.

When you run the aio-app-deploy command, you will see a URL when it finishes to experience.aw.com custom apps. Let’s navigate to this URL.

We should now see the Sync panel, which controls the synchronization from our SFCC instance to Commerce Optimizer.

These are triggers that allow us to execute actions in our App Builder application.

Let’s go to the bottom and first check the connectivity. When this page loads, connectivity to SFCC as well as to Commerce Optimizer will be checked. We can also recheck these at any time. Now that we know that we have connectivity from our App Builder application to our source and our destination systems, let’s execute the full sync action to kick things off. Alright, we have successfully requested this asynchronous action. This action will run in the background synchronizing data from SFCC into Commerce Optimizer.

Let’s go check the status. Let’s go back to our terminal and use the aio-cli one more time. Type aio rt for runtime activation list. This will give us a list of all of the runtime actions that we have executed so far.

You can see this is our full back office sync that we just kicked off from our UI.

Let’s copy this activation ID, aio rt logs, and this activation ID. Alright, and here we can see all of the logs from our full synchronization and see that it was executed successfully. We can also see this event call from our back office full sync. By clicking into the back office full sync event in our dev console, we can use debug tracing in the event browser to get some visibility into what happens in these events.

We can see that we’ve triggered our SFCC full sync event, and here we have the same activation ID that we saw from the aio rt command, so we can also get this ID here. This means that this event was successfully received by the runtime action and was subsequently executed. By clicking into the event browser tab, we can also see journaling. We can see request and response information for every event that was received by our app builder application. Now that we have verified via the runtime action logs that our full sync runtime action completed successfully, let’s verify this using our storefront. I’ve navigated over to my EDS storefront, which uses the commerce optimizer.

Using our Carvelo dataset, I’m going to search for some parts. Let’s look at the Bolt brand, and then let’s look for breaks.

I’m going to click into these Man with Premium breaks, and I can see that our storefront is fully working. The search and pdp pages loaded from commerce optimizer with data synchronized from SFCC.

Now let’s make some changes to some product details and pricing in SFCC and see how our app builder connectors delta sync action picks up these changes and synchronizes them to commerce optimizer.

Let’s head over to our business manager. In the Carvelo site, let’s look at our product catalog, and let’s find the SKU data.

Let’s look at this same SKU here, which is Bolt Man with Premium breaks. I’m going to copy the SKU and search for it in our SFCC catalog. Alright, let’s make some changes.

As an example, let’s remove the year from the product name, since we have this already in an attribute. Next, let’s add some content to the description. Let’s just add a simple text, and let’s say, keys are the best breaks money can buy for the most adventurous of off-roaders.

Okay? Let’s apply these changes. Alright, in addition, let’s make a price change. Let’s head over to price books. Let’s head to our VIP West Coasting price book. And let’s look for our SKU. Alright, we see this is $1,750. Let’s say that we want to have a light sale. We’re going to lower this to $1,550. Now let’s click apply. Now that we’ve made these changes in the SOCC catalog, all we have to do is wait for our configured jobs to automatically pick up these changes and synchronize them to Commerce Optimizer. They will then be immediately available on your EDS storefront.

Heading back over to our storefront, we can refresh the page and see that our changes have already been picked up. The year has been removed from the product name. Our new line has been added to the product description. And our price has been lowered.

Throughout this video series, we have completed all the steps necessary to synchronize a Salesforce Commerce B2C or SOCC catalog with Commerce Optimizer. We have installed and configured all of the necessary items to enable the SOCC instance to communicate with Commerce Optimizer via our Commerce Optimizer SOCC connector in App Builder. We have successfully run a full site sync and then made changes to the SOCC catalog and allowed our delta site sync process to pick up those changes and synchronize them to Commerce Optimizer. We were then able to see those changes immediately on our storefront.

Thanks for watching!