EasyStore checkout testing - shipping and order limit questions

Hello Ziaul,

Thank you for getting back to me.

I have taken a full manual backup of the development site, and our hosting provider also maintains automatic backups.

Login credentials are supplied as requested.

A few notes that may help with your investigation:

1. Product data

We have not yet configured all products with stock quantities and weights, as we are still refining our product catalogue and clearing old stock. Most products do not yet have variants defined, but this will change as the site approaches launch.

2. Test product

While testing the checkout process, I have been using the following product:-

Haflinger - Hawk - Sheepskin - Chestnut

Please see the link pasted in the secure section of this message.

This product has variations and variants. The variants include weights and stock levels. I entered these using the spreadsheet-style variant editor, which works well once the Weight column has been enabled.

3. Shipping configuration

We are using NZ Couriers exclusively for deliveries within New Zealand.

At present, EasyStore does not include NZ Couriers as a shipping carrier, so there is no direct integration for features such as parcel tracking.

As a temporary workaround I have:

• Created a Region Shipping method named NZ Couriers
• Assigned it to New Zealand
• Selected Rate by Weight
• Entered two weight-based shipping rate tables
• Left the Shipping Carrier field blank, as none of the available carriers are applicable

I look forward to hearing your thoughts and recommendations.

Kind regards,

Bruce

Thank you for the suggested solutions.

Firstly, I have corrected the shipping issue. Thanks for the clarification. It makes sense and works well.

I have also enabled Order Quantity and confirmed that the Maximum Order value is enforced correctly for each variant.

However, our business requirement is different. We need to limit the total quantity of shoes in the shopping cart to a maximum of 3, regardless of product or variant.

For example, if a customer adds five pairs of shoes in different size variants, as follows:

Size 41 × 1
Size 42 × 1
Size 43 × 1
Size 44 × 1
Size 45 × 1

or even different products, EasyStore allows the order because each individual variant is within its limit.

This results in five pairs of shoes, but EasyStore allows the order because each variant quantity is only one.

Is there any built-in way to enforce a maximum total cart quantity so that customers cannot proceed with an order exceeding three pairs of shoes?

Hello Ziaul,

Thank you for your clarification regarding the cart quantity limitation.

Your response confirmed that EasyStore currently supports minimum and maximum quantities on individual products or variants, but does not have a built-in option to limit the total quantity of items across the entire cart.

Comfoot Footwear have a specific requirement to limit online orders to a maximum of three pairs of shoes per order. This is mainly due to courier handling and the way they are transitioning from their physical store to an online-only service.

After reviewing the EasyStore checkout process, I have added a small custom validation in the cart checking process. It uses the existing cart weight calculation function and prevents checkout when the total cart weight exceeds 3 kg (our current equivalent of three pairs of shoes).

The change is intentionally small and isolated, and I have documented it so that it can be reapplied after future EasyStore updates if required.

I am currently testing the behaviour to ensure it integrates correctly with the existing checkout error handling.

Thanks again for your assistance.

Kind regards,

Bruce

One additional thought occurred to me while investigating this.

I noticed that EasyStore already uses events such as onBeforePayment, and I wondered whether a Joomla plugin would be the preferred approach for implementing business-specific rules such as a maximum total cart quantity or weight.

As mentioned, I have implemented a small, isolated validation change within the cart checking process so that we can continue testing.

However, from a maintenance perspective, a plugin or event-based solution would obviously be preferable because it would avoid modifying EasyStore core files after future updates.

If EasyStore provides an appropriate event or extension point for this type of validation, I would be interested to know the recommended approach.

Thanks again for your assistance.

Thank you Ziaul.

It's good to know my input is valued.

This is a great way to end the week!

All the best!