Try our new AI assistant by clicking the chat icon in the lower right corner.

• Miva Docs
• Reference Guide
• Miva 10.03.00 | Release Notes

Miva 10.03 Features Overview

On this Page

• Last Updated - Customer and Orders
• Subscription Improvemenets
• First and Last Name Search on Batch List
• Improved Handling of Changes to Shipping Method Names
• Review Baskets Updates
• Combination Facets Now Support Variant-Level Data
• Variant Support for Pre-Calculated Discount Prices Scheduled Task
• Template Feed Changes
• Address Validation Improvements
• Edit Baskets Update

Last Updated - Customer and Orders

The 10.03 update to the Miva admin allows you to see the last updated time for orders and customers was updated.

To view the last updated information for a customer, click the Customers heading, and make sure you are in the Customers tab.

Once there, click the plus sign in the far right to add a column to the batch list.



In the drop down, click the box next to Last Updated. Click outside the dropdown box to close it.

Now in the list, the date and time of the customer’s last update is displayed.



Note

The last updated information for orders works the exact same way in the orders batch list.

The following order actions will cause the last order update data value to be updated:

• Customer Information (Bill To/Ship To) Updates
• Order Item: Add, Updated, Delete
• Backorder item. Cancel item.
• Change value of an Order Custom Field
• Shipment created. Items removed from shipment
• Assign/Unassign Price Group to an Order
• Assign/Unassign coupon to an order
• Tax is recalculated
• Order charges updated
• Subscription: Added, Updated, Deleted from Order
• Item split into multiple line items
• Return created/received
• Order archived
• Order added to a batch
• Void, authorize, capture, refund payment
• Delete payment record

Notes

The last updated values are also available in the JSON API when pulling orders or customers from Miva. This allows you to get all updated orders or customers since the last time the external system queried Miva.

Not all of these actions are available in the notifications module API for use in things the Order Workflow triggers, but may be added in a future release.

For stores upgrading to 10.03, the field Order Last Updated will be set to 0. This means that until an order is updated it will remain at 0.

Subscription Improvements

Improvements to the way the Miva admin handles subscriptions are included in the 10.03 release.

Subscriptions now have a subsection for Subscription Shipping Rules within Shipping Settings.

To access these new rules, click Settings, then Shipping Settings from the pop out menu. Once on the Shipping Settings page, click the Settings tab.



You will see a Subscription Shipping Rules box under the Shipping Rules box.

In the box there are several options to choose from.

Ignore Shipping Method Restrictions - This the default behavior and is checked by default for both new and upgraded stores (10.03).

Under Invalid Shipping Method Handling, there are new options available when it comes to subscription shipping issues.

• Error – This is the default state and behavior, and did not change with the update.
• Use Highest Priority Available Shipping Method – When the new order is created from the subscription, if there is a shipping error the highest priority shipping method will be used.
• Use Lowest Priority Available Shipping Method – When the new order is created from the subscription, if there is a shipping error the lowest priority shipping method will be used.
• Force Specific Method – You can choose from a drop down list of available shipping methods to use when there is a shipping error.
• Use Fallback Shipping Method – You must have “Use Fallback Shipping Method” selected under Shipping Rules in order to use this option. If both are selected, whatever shipping method you have set for fallback will be used for the order.
• Automatically Update Subscription with Replacement Method When Original Method is Invalid – With this selected, the subscription record will be updated with whatever shipping method you have selected above. If it is not selected the shipping method replacement will still occur, but it will happen each time the subscription order is set to renew and occurs at the order level, not the subscription level.

Note

If you forced the shipping method on error to get updated to UPS overnight, the cost of overnight shipping will be charged to the customer, so be aware that changing the shipping method to a more (or less) expensive method, will change what the customer pays for that order.

In addition, the Miva admin gives you greater flexibility when it comes to managing subscriptions that are in an error state. Often a subscription goes into an error state when the credit card used to pay the subscription becomes invalid, like after an expiration date.

To access the settings, click Settings, then Store Settings from the pop out menu. Once on the Store Settings click the Subscription Settings tab.



On this tab you can set how frequently, in days, the admin tries to retry the authorization of the subscription. You can also establish when the system will cancel the subscription based on the number of failed authorizations.

The new update also addresses an issue where the customer browser time and the admin server time were not in sync, which caused issues with how the subscription renewals were run during scheduled tasks.

Now the subscriptions batch list will display a date and time, but it will include notation of the actual date and time in relation to Coordinated Universal Time, or UTC.



First and Last Name Search on Batch Lists

The Miva admin 10.03 update includes improvements to the search functionality of batch lists.

Previously, users could only search by either just first name, or just last name. Now users can search batch lists with a person’s full name; both first and last.

Note

On upgrade for existing stores, if a customer has not saved any preferences for these two lists (i.e., shown/hidden other columns or made width adjustments), then the default column assignment will be made and they won't have to do anything to view the new joined columns. If they have made any preference changes, then they will have to manually change the visibility of those columns to see the new behavior.

Improved Handling of Changes to Shipping Method Names

With the updated 10.03 Miva admin, the following shipping modules now have a Shipping Method Code field, in addition to Method name field.

• Base + Weight Shipping
• Flat Rate Shipping
• Minimum or Weight Shipping
• Price Table Based Shipping
• Quantity Based Shipping
• Weight Table Shipping


This allows you to change the name of the shipping method without having to update other references such as shipping method rules, subscription shipping references or order shipping references. When your store is updated to 10.03, the field will be automatically populated with the current hipping method name value.

Review Baskets Updates

Arriving with the 10.03 update, the product inventory is now correctly added or removed when an item is added or removed from a basket using Review Baskets (when Inventory at Checkout is not being used).

Now, converting a basket to an order in the admin using Review Baskets now processes the following automatically:

• Update Order Status
• Generate Digital Downloads
• Generate Gift Certificates
• Update Wish List
• Update Product Inventory

In addition, the new “Price_Changed” event can determine if a product’s price has changed. This is called regardless if variants are being used or not.

Combination Facets Now Support Variant-Level Data

The Combination Facets module, new in version 10.03, allows you to use the part products as the variant source, rather than the master product.

In Utilities Settings, on the Combination Facets tab, there is a new Variant Source column in the batch list. When you select the Part Products source, the admin will pull the data from the part products as selected.



This allows for a customer to apply a combination facet to find a specific variant product. For example, if a customer is seeking a specific part for a vehicle, they are able to apply a Year, Make and Model combination facet to find a part specific to that vehicle.

When a customer chooses their facets on the webpage, the available attributes are limited on the product's page, based on the facets chosen. In our example below, the customer is shopping for a transmission for their 2002 Honda Civic. By entering those facets, their only choice for a transmission is the "small" transmission.



Variant Support for Pre-Calculated Discount Prices Scheduled Task

With the release of 10.03, the Miva admin now supports the ability to pre-calculate discount prices at the variant level.



Now, in the Pre-Calculate Discount Prices function in Scheduled Tasks, you can have the admin pre-calculate discounts and, once the prices are calculated, they are cached and can be used in feeds and other areas of the software. This leads to performance gains for your site.

In addition, there is a time limitation setting which prevents the task from using the entire 60 minutes of processing time available to a scheduled task process, which also aids in performance. This gives you better controls to prevent this task from using all of the alloted 60 minutes and allows other tasks to run before a timeout occurs.

Template Feed Changes

The 10.03 update enables Template Based Feeds to calculate discounted variant prices dynmically to be used in feed templates.

This also includes making use of any pre-calculated variant prices, when available, which would be created as part of the "Pre-Calculate Discounted Prices" Scheduled Task.

As part of the changes in 10.03.00, the output for variant records has been standardized as follows:

• record:price, record:cost, record:weight will always refer to the aggregate variant price/cost/weight, taking into account sNN_ProductVariantPricing and the sNN_ProductVariantParts quantity multiplier [note: both of these were not taken into account pre 10.03.00)
• record:variant:price, record:variant:cost, record:variant:weight will always refer to the individual part product price/cost/weight

In addition, two new output fields have been added:

• record:variant_id, which will mirror record:variant:variant_id (which has beenretained for backwards compatibility)
• record:variant:quantity, reflecting the sNN_ProductVariantParts quantity field

Address Validation Improvements

The 10.03 admin update includes improvements to the Address Validation function. Previously, address validation would run each time at checkout.

Now, when a single address is returned and it matches the address the customer entered, the Address Validation dialog will not be displayed.

In addition, if a customer has already validated their address during a particular basket session, the admin will bypass address validation, even if the customer abandons the checkout process and returns later. However, because it only tracks the current basket session, if the customer comes back a week later, they would need to validate their address again.



Edit Baskets Update

With the 10.03 update, customers can now edit items in their basket/shopping cart as long as the item has attributes.

When an item with attributes is in the basket, it will show a link to “Edit” the item.



Note

Edit Baskets is also possible when a subscription item is in the basket.

If the customer clicks the link, a popup box opens and allows them to update the item. In this example, the customer could change the size of the shirts they wanted to order, as well as the number of shirts.

When the customer clicks Update Item, the cart updates, including changing the price of the item or the total price of the cart if required.



Note

The item’s image will not update within the edit basket pop up box, but it will update in the shopping cart if, for example, the color changes from black or red.

The Template Code changes for the Edit Baskets functionality can be found here: https://github.com/mivaecommerce/readytheme-shadows/issues/127

Template Feed Changes

The 10.03 update enables Template Based Feeds to calculate discounted variant prices dynmically to be used in feed templates.

This also includes making use of any pre-calculated variant prices, when available, which would be created as part of the "Pre-Calculate Discounted Prices Scheduled Task.