5.7.4.3

Issue key

Summary

Description

Issue Type

Components

V5-7600

Enhanced UI/UX for businesses signing up and converting to paid customers of CRM.COM

Enhanced UI/UX for businesses signing up and converting to paid customers of CRM.COM.

BN - USER EXPERIENCE AND TECHNICAL

Improvement

V5-7541

List locations Web API returns duplicate records

List locations Web API returns duplicate records for the same merchant. Also, ensure that the 'address' is returned by this Web API.

BN - BUSINESS NETWORK

Bug

V5-7601

Self-service Web API issues

1. List contact services

   1. Returns null in 'scheduled_actions'. This should be 'false' if there are no scheduled actions and 'true' when there are scheduled actions (as in BO Web API)

2. Sharing devices in communities

   1. When a member views the devices shared by their community owner, the device’s characteristics are not returned (even though 'include_characteristics' is set to 'true')

BN - USER EXPERIENCE AND TECHNICAL

Bug

V5-7544

Devices remain in the ownership of the business even after being stocked out and invoiced

Devices remain in the ownership of the business even after being stocked out and invoiced

SC - INVENTORY

Bug

V5-7573

UI issue: Unable to edit an order for a variant product

An order has been placed for a variant product with modifiers. The user wants to edit the order while keeping the same variant but changing its modifiers, which should be supported.

Issue 1:
In production, when editing the variant, the Service Recommendation API is triggered, even though the variant is a traceable physical good.

Issue 2:
No API is triggered to load the ordered variant's information. As a result, when the modal opens, the variant appears unselected/available for selection, instead of reflecting the existing order. Because of this, the user cannot remove the included modifier and replace it with another one, even though this flow is supported when placing the order.

SC - ORDERS

Bug

V5-7378

Ability for merchants to manage their product pricing

Allow merchant users to set up and manage the prices of products they sell on behalf of the business.

SC - PRODUCT CATALOGUE

Improvement

V5-7421

Ability to support  Quantity-Based and Multi-Line-Based Services

Provide businesses with the ability to configure subscription services as either 'quantity-based' or 'multiline-based'.

• Quantity-based: A single service SKU is added to the subscription, with the quantity adjustable to represent multiple units of the same service.

• Multiline-based: Each subscribed service creates a separate line item, representing a unique instance that can be managed independently within the subscription.

SC - SUBSCRIPTIONS

New Feature

V5-7540

Issue when deleting a contact

Contact cannot be deleted because a validation error indicates an invalid account state, even though the contact has no account.

WP - ACCOUNTS

Bug

V5-7405

Pass redemption issue

When redeeming the pass, a contact was created, and the pass value was transferred to the contact’s wallet. However, the pass state was not changed to 'Redeemed' because incorrect data was passed in the custom fields, and no error was thrown. As a result, the pass was redeemed again, which created another contact.

WP - PASSES

Bug

V5-7510

Enhanced Automations to generate Achievement Events

Enhanced the 'New Purchase' and 'Award Contact' automations to generate Achievement Events. This enables businesses to configure additional Reward Offers for their contacts, encouraging them to achieve more milestones and earn additional awards.

WP - REWARDS CORE

Improvement

V5-7571

Issue when setting up Auto Top-up and Termed Top-up rules for the wallet

1) An unhandled error occurs when configuring wallet rules because the user hasn’t selected one of the contact’s payment methods (e.g. a card). A validation message should be shown instead.

2) Backend users cannot configure auto top-up or termed wallet rules if the wallet’s funding source payment method type is not enabled by the business.

Example:
The only enabled payment method for the business is the CRM.COM Wallet. A contact has added a card as the wallet’s funding source. When the backend user attempts to configure the rule, the card cannot be selected because the UI filters payment methods by enabled payment method types, and card is not enabled.

The UI should instead display all payment methods associated with the contact, regardless of their payment method type, allowing the backend user to select the appropriate funding source.

WP - WALLET

Bug

V5-7562

Wallet exists Web API issue and gap

1) Wallet Exists API – Deleted Contact Scenario

A contact with a wallet was deleted, and a new contact was created using the same email address.
When the Wallet Exists Web API is called, it returns true, even though the wallet belongs to the deleted contact.

2) Wallet Exists API – Incorrect Identifier Type

The business has enabled both Email/OTP and Phone/OTP authentication methods.
However, the Wallet Exists Web API request includes type=phone and the contact’s email address.

WP - WALLET

Bug

V5-7494

Ability to view blocked wallet funds for an order

Ability to view the wallet’s funds that are blocked because of an Order. When the Order is placed (and according to order queue settings), funds are blocked and used to pay it off upon completion. This feature allows backend users to view the amount blocked per Order and the total amount blocked within the contact’s Financials.

WP - WALLET

Improvement

V5-7491

Ability to support wallet Top-ups and Pass redemption by merchants 

Ability for Merchants of a Business to perform wallet top-ups and redeem pass actions.

WP - WALLET

Improvement

V5-7649

Concurrent Payout API Calls Cause Duplicate Deduction

An issue occurs when the payout API is invoked multiple times simultaneously by the same user. If two payout requests are triggered at the exact same moment, each request is processed independently because neither request is aware of the other.

As a result, when the second request is processed, the first payout transaction has not yet been completed. Since there is no concurrency control mechanism in place, both requests proceed, and the system deducts the funds twice, resulting in duplicate payouts.

BN - USER EXPERIENCE AND TECHNICAL

Bug

V5-7644

Edit order issues involving variants and components

The Edit Order screen does not properly load variants, component sets, mandatory products, or pricing for composite products, while the same configuration works correctly during new order creation.

SC - ORDERS

Bug

V5-7624

Add Reward Offer Performance endpoint to Backoffice API

Added the ability to retrieve a contact's reward offer performance via the backoffice API

New Backoffice Endpoint: GET /backoffice/v2/reward_offers/{id}/performance?contact_id={contact_id}

WP - REWAD OFFERS

Improvement

V5-7547

Ability to display reduced product price compared to original price with unit price attributes

Introduces an additional product pricing option that allows configuring compare-at pricing for physical products, enabling the display of the original price alongside the discounted price, with associated unit pricing information.

SC - PRODUCT CATALOGUE

Improvement

V5-7537

New dedicated API to update Product custom fields

The new API Update Product Custom Fields (/backoffice/v2/orders/{id}/custom_fields) allows custom fields to be updated for a single product.

SC - PRODUCT CATALOGUE

Improvement

V5-7379

Ability to allow placing of orders outside operating hours

Ability to allow placing of orders outside operating hours and contact to select a delivery slot for the order to be delivered to them.
Back-end changes only.

SC - ORDERS

New Feature