We are pleased to inform you about important new features in our system that will significantly improve the use of our platform. In this article, you will find detailed information about the following significant updates:

1. Adding products without prices to the cart and cart offers in the Backoffice.

To enable the addition of products to the Backoffice cart without a specified price, the implementer must perform certain configurations. As part of these changes, you need to set the flag:

"can_add_product_without_price_to_cart" to "true" for a specific customer. This flag is available in the internal order path API settings.

Enabling this flag activates support for products without a specified price, allowing for:

a) Adding to the cart products that are active but do not have a set price.

b) Adding both active products and work-in-progress products without a specified price to the offer.

c) Before assigning a price to a product, it is possible to add products to the offer or cart. However, accepting the offer and placing an order for these products will be unavailable until a price is assigned.

d) After assigning a price to the product, you can continue processing the order and offer without any restrictions.

e) Offers without a specified price can be printed and sent to the customer via email.

f) A cart containing products without a specified price can be assigned to a specific user and made available on our online store

2. Addition of a new type of permissions.

The new permission allows for filtering the view and managing orders based on assigning a customer to a specific branch. By adding a branch reference condition in the "Customer Service" and "Customer Documents" sections, we gain the ability to restrict visibility and order creation only for customers assigned to that specific branch.

{OPERATOR_DEFAULT} / branchId (branch ID)

3. Displaying a new menu in the customer context in BO.

The horizontal menu on the customer card has been replaced with a vertical menu. You can select the same options as before; only the presentation style has changed. The menu presentation has been adapted for mobile views.

4. Adding the ability to assign multiple branches to one operator.

The assignment of branches to operators has been implemented in such a way that it is divided into two types: the main branch and additional branches. An operator must be assigned a main branch and can have multiple additional branches assigned. In cases where only an additional branch is assigned without a main branch, it becomes the main branch. With these changes, permissions have also been adjusted. They can be configured so that an operator with the {OPERATOR_DEFAULT} condition (meaning fetch branch information from the operator's card) can work on additional branches as well.

5. Establishment of a new permission area for warehouse documents such as DZ and DZK.

In upcoming updates, more actions and translations for the entire area will be added.

6. Product addition queue message

If there is a queue when adding a product to the cart or offer, the user on the product list view will be informed about how many products are currently being added. A new blue-colored message will appear on the product listing.

7. Customer search from my branch.

In the ONe system, the ability to assign additional branches has been introduced. When searching for customers in the main search (at the top of the window), in the 'My Branch' tab, customers assigned to the main branch as well as additional branches of the operator will appear

8. Adding the ability to retrieve events related to invoice corrections from the integration API:

The ability to retrieve events related to invoice corrections, including their addition, update (common event), and deletion, has been added to the integration API. You can use the following endpoint for this purpose: link to the API endpoint

Here is a sample response after adding a correction (Newer Invoice):

{
  "nextId": 3,
  "events": [
    {
      "invoiceNumber": "Faktura Katowice",
      "type": "InvoiceCreated"
    },
    {
      "correctionNumber": "Faktura NOWSZA",
      "type": "AccountingDocumentCorrectionUpdated"
    }
  ]
}

9. Splitting the current pricing lists into two separate pricing lists: 'purchase' and 'markup'.

https://api-prod.onecommerce.shop/swagger/pricing/swagger-ui.html?urls.primaryName=pricing%20integration%20v1#/pricing

There have been changes made in the integrative API for pricing:

a) The endpoints related to 'purchase' pricing have been grayed out. Instead, two new endpoints have been added: 'purchase-price' and 'markup'. This change addresses the limitation of not being able to add additional markups to an existing purchase price list. With this modification, you can create a markup price list (in the pricing section) and add multiple markups to it (in the markup section).

b) Naming conventions have been introduced for the main price lists. This allows integrators to use the provided name instead of a fixed UUID as the ID for a particular price list:

• Main Catalog Price List (MAIN_CATALOG)
• Main Purchase Price List (MAIN_PURCHASE)
• Main Markup Price List (MAIN_MARKUP)

c) These names have been reflected in the 'explain pricing' graph, improving its clarity.

10. Disabling the option to send a work-in-progress product for activation from the line level.

By default, the ability to send work-in-progress products for activation from the product line level has been disabled for every tenant. Products will be sent for activation automatically when the offer status is changed to 'WON_WITH_DRAFT_PRODUCTS', which happens after it's been accepted by the customer.

The option for manual sending of work-in-progress products for activation can be enabled in the settings (orderpath section). To do this, an operator must have the appropriate permissions for the settings section.