You can see that the product base is $85. One interesting note for this client, you don't see any sales prices, that's because all sales prices are set in WooCommerce, while all base costs are set in Syspro. We'll go ahead and adjust the $85 base price to $79 and close and save that as the new product price. Let's go fire off that sync and connect by selecting the process products from Syspro to WooCommerce job and triggering it now.
For this client, we've built the workflow differently as they've split the product management with some fields being controlled within WooCommerce and others within Syspro CRM. So with this custom workflow, we load every product first from Syspro—which you can see down here—then compare the data we've pulled from Syspro to see what needs to be updated. It could be adding or deleting products, updating the inventory for many products. As you can see with our scenario, just updating the price for one product.
Once back in WooCommerce on the product page, we'll go ahead and click refresh and see that it updated the base price to $79. Even though the price was lower, it's still on sale for less, so let's go ahead and buy one. I've added one to the cart, we'll speed up the checkout process a little. Once ordered, you can see that our WooCommerce order ID is 298777. Now we'll fire off the process sales order, sync job, and we'll watch it process, noting that order 298777 was processed and that as it was processed into Syspro, an ID of 406470 was assigned as the Syspro ID. Moving into Syspro, we'll navigate to sales orders and search for the order 406470. Here's the order and drilling in, we can see that it's our order and it's broken out the order details with the part and the shipping costs separated. It's associated the order with our newly created demo Johnson account.