Accepting payments from within Salesforce and recalculating taxes in Salesforce are some of the new features in our March 2023 release.

Here is a summary of our new features for March ‘23:

• Accept payments from within Salesforce
• Recalculate Taxes in Salesforce
• Customise the time before a Cart is marked as abandoned
• Allow PO number to be optional on Pay by Account
• Enable New Order Save Behavior

Accept payments from within Salesforce

Note: Requires Store version 13.3 or higher

Just landed is the ability to accept payments from within Salesforce, using the payment providers you have configured for StoreConnect. This allows you to create a new order (or modify an existing one) while on the phone with a customer, and have them give you their card details for payment processing.

On any Order, use the ‘Take Payment’ button to enter the card details and process the payment. Please refer to our documentation for this feature for more details.

Recalculate Taxes in Salesforce

Taxes can now be calculated and re-calculated from within Salesforce. If you create a new order, or modify an existing one, you can (re)calculate the taxes as they would have been on the webstore. Please refer to our documentation for this feature for more details.

Support for Liquid caching

Note: This is an advanced feature

We have introduced a way to cache content in liquid templates.

As of now the objects that can be cached is limited, but we will expand it over the coming releases. Please read our documentation to find out more details of how and when to use liquid caching.

Customise the time before a Cart is marked as abandoned

By default, without any configuration, Carts are processed as abandoned after 10 hours. Using configuration via Store Variables, this can be extended or reduced. Previously the maximum extension was capped at 7 days. This has been increased to 45 days. This allows your customers to keep items in their cart for extended periods before placing an order.

Default price format has changed with regards to stripping zeroes

Previously, all insignificant zeroes were stripped from the price after the decimal point. This resulted in prices like $27.5 or $42. With this change, zeroes are only stripped if the price has all zeroes after the decimal point, now giving $27.50 and $42. We feel this is a better default behaviour. However you can still configure the output to achieve the previous result. See the money filter documentation for more details

Allow PO number to be optional on Pay by Account

The PO number has been a required field when a customer is paying by account. This will remain the default, however you can now configure your Store to make it optional. See the Pay by Account documentation for more details.

Enable New Order Save Behaviour

With the upcoming change to the Order Save Behaviour in Salesforce, our package now supports both the old and new behaviours in the transition period before it becomes mandatory. This is just informational - you do not need to do anything.

Deprecated StoreConnect Page Layouts

Many of our Page Layouts were inconsistently named. In this release we have renamed some of our layouts more consistently starting with the layouts for Standard objects. This will make it easier to identify StoreConnect layouts. Renaming layouts has the effect of deprecating (removing) the old layout. Any old layouts that are assigned will remain. To use the new layouts, simply assign them.

Replaced Promotion.Code with Promotion.Promotion_Code

We have removed the field ‘Code__c’ from the `Promotion__c’object. The replacement field (Promotion_Code__c) has already been use for some time. This completes the move from ‘Code’ to ‘Promotion_Code’, which allows the same promo code to be used on different Stores. ‘Code’ was unique to the Org, ‘Promotion_Code’ is unique to a Store.

Fixes

Default theme: Account Summary page: Most Recent Order

The item was previously showing the oldest order instead of the newest order.

Incorrect amount charged when deposit was more than total payable

If the Order’s total payable amount was less than the deposit amount, the deposit amount was still being charged.

Out of Stock Product could be added to Cart

In certain cases a Product could be added to Cart when it should have been marked as Out of Stock. This could happen when the product was not back-orderable, and there was at least 1 stock location that had a stock level, but the sum of stock levels across all stock locations was zero or negative. In this case, even though the item could be added to Cart, the Cart validation immediately removes it and shows an Out of Stock message. Now, the item cannot be added to Cart in the first place.