Webhooks are a mechanism that allows event information to be sent from one application to another, without the need for constant status checks. With webhooks, applications can exchange data in real time, enabling more efficient integration and process automation.

• The events you have to choose from in the ONe application are:

1. Webhook configuration

• Go to the configurations tab and then Webhooks

• Click on the create webhook button and set the status to "active"

• Set any name and configure the "Calling Event"

• Insert from the external system the Webhook URL to which ONe should send the event information.
• Select authentication type "HTTP_BASIC"

• Complete the input "Username" - "admin"
• Complete the input password - "admin"

• Before creating a webhook, test it by clicking on the "Submit test webhook" button
  

2. Verify the submission of WebHook Cart opened on Backoffice and on customer view.

• Backoffice - follow the steps below:
  

Go to "Customer" tab,
Go to the "Customers" tab,
Click on the name of any of the customers
At the top of the page, press the "Create" button
From the menu of creation options, select "New sale"
Go to the lambda page (sample event)
On the page there should be an event with the id of the customer and the id of the shopping cart

• Customer view - follow the steps below:

Log in to the OFE to the account of one of your clients
Press the shopping cart button located in the upper right corner
Go to the lambda page (sample event)
The page should have an event with the id of the customer and the id of the shopping cart

3. Verify submission of WebHook Client Logged on Backoffice and on Client View. 

• Backoffice - follow the steps below:

Go to "Customer" tab
Go to the "Customers" tab
Click on the name of any of the customers
Go to the lambda page (sample event)
On the page there should be an event with the customer id

• Customer view - follow the steps below:
  

Log in to the OFE to one of your customer accounts
Press account --> account details
Go to the lambda page (sample event)
On the page there should be an event with the customer id

4. Verification of WebHook Offer Opened submission on Backoffice

• Backoffice - follow the steps below:
  

Go to "Customer" tab
Go to the "Customers" tab
Click on the name of any of the customers
Select the "offers" tab
Go to the lambda page (sample event)
On the page there should be an event with the customer id

5. Business examples of using webhooks

1. "Cart opened": The online store can use this event to notify the customer of a discount on the products in their cart and to send push notifications to the customer, informing them of products they may be interested in.

2. "Client logged": The company can use this event to notify customers of new offers or products that may interest them, or to automatically personalize offers based on their behavior and preferences. The company can automatically personalize its websites based on customer preferences.

3. "OfferOpened": The company can use this event to notify the customer of similar offers or products that may be of interest to them, and to send an email notification with special offers for the customer.

These examples show that webhooks can be used in a wide variety of business scenarios to automate and improve processes, as well as enhance the customer experience.

-Using webhooks requires having an external tool to handle the sent events.

Edit price on cable products

1. A function has been created for the cable calculator to add the same product in separate product lines. In the system, we allow you to edit the price on a single product line. Business application: a single piece of a particular product may be damaged and we want to sell it at a lower price.
2. Ability to edit the purchase price: In the price editing modal, we allow the merchant to edit the purchase price on the offer and the shopping cart.
3. In the integration API we return information about the relationship between products. If a product line has a parent line then we provide its ID next to the line. Such a case will occur, for example, for cable products. The parent product will be the cable, while the child will be the drum on which it will be wound. The ID of the product line in which the cable is located will be given next to the product line drum. Endpoint, which is responsible for this to /api/v1/orderpath/integrations/auth-required/offer Get offer

"parentLineId": "1116cba2-499d-4f49-b1bd-4163c1f09fdc"

• When adding a cable product (or any other type of product as needed) to your listing, we allow you to add an appropriate note that it cannot be split. This means that when there is a need to order the product over stock, it will not be split into shipments. It will go from to a shipment sent at a later date, that is, when the stock increases to the level that is needed to make the purchase. At this point, this is possible by changing a flag in the API:/api/v1/orderpath/integrations/auth-required/carts/{cartId}/add-configurable-products

"configurableProducts": [
{
"children": [
{
"allowQuantityChange": true,
"allowQuantitySplitting": true, lub false
"productId": "string",
"quantity": {
"type": "CONTENT_QUANTITY"
},
"removable": true - you can set that the product cannot be deleted