[Skip to main content](#vessel-content)

#   Semantics of shipment method filtering.

##

- **[vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")**
- [![vittorio.zambon's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar17262.png)](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile") Topic Author
- [ Offline](/forum/user/17262-vittorio-zambon)

Less More

- Posts: 9
- Thank you received: 1
-
-

8 years 1 week ago [\#299553](#299553) by [vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")  *[Semantics of shipment method filtering.](/forum/28-shipping-methods/896045-semantics-of-shipment-method-filtering#299553 "-- url of the page with the problem -- :   www.ruedusansgluten.com  -- HikaShop version -- : 4  While the HikaShop-manual says that the configured plugins (I refer only to the manual type) are evaluated as if they were filters, nevertheless this implied semantics is not quite true. They seem to be applied to the shipment instance in a sequential manner. I might as well think they are implemented using various SQL SELECTs. In fact I get responses like this one: ITEMS&#95;WEIGHT&#95;TOO&#95;SMALL&#95;FOR&#95;SHIPPING&#95;METHODS = S=&quot;The cart items combined weight is too small for all the possible shipping methods&quot; when it is not true for ALL the methods I configured but only for a subset of them. This may be a clue to the fact that a query gets issued having a WHERE ZONE = &quot;somewhere&quot; clause.  I beg the authors (or anyone who knows) to disclose the exect evaluation semantics (or trivially the algorithm) of the configured shipment rules.  THNX al lot!")* was created by *[vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")*

-- url of the page with the problem -- : [ www.ruedusansgluten.com](https://www.ruedusansgluten.com)
-- HikaShop version -- : 4

While the HikaShop-manual says that the configured plugins (I refer only to the manual type) are evaluated as if they were filters, nevertheless this implied semantics is not quite true. They seem to be applied to the shipment instance in a sequential manner.
I might as well think they are implemented using various SQL SELECTs.
In fact I get responses like this one: ITEMS_WEIGHT_TOO_SMALL_FOR_SHIPPING_METHODS = S="The cart items combined weight is too small for all the possible shipping methods" **when it is not true** for ALL the methods I configured but only for a subset of them.
This may be a clue to the fact that a query gets issued having a WHERE ZONE = "somewhere" clause.

I beg the authors (or anyone who knows) to disclose the exect evaluation semantics (or trivially the algorithm) of the configured shipment rules.

THNX al lot!

Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzI4LXNoaXBwaW5nLW1ldGhvZHMvODk2MDQ1LXNlbWFudGljcy1vZi1zaGlwbWVudC1tZXRob2QtZmlsdGVyaW5nP3RtcGw9bWFya2Rvd24=) or [Create an account](/component/users/registration?Itemid=101) to join the conversation.

- **[nicolas](/forum/user/63-nicolas "View nicolas's Profile")**
- [![nicolas's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar63.png?1793428657)](/forum/user/63-nicolas "View nicolas's Profile")
- [ Offline](/forum/user/63-nicolas)

Less More

- Posts: 86320
- Thank you received: 14279
-
-

8 years 1 week ago [\#299558](#299558) by [nicolas](/forum/user/63-nicolas "View nicolas's Profile")  Replied by *[nicolas](/forum/user/63-nicolas "View nicolas's Profile")* on topic *[Semantics of shipment method filtering.](/forum/28-shipping-methods/896045-semantics-of-shipment-method-filtering#299558 "-- url of the page with the problem -- :   www.ruedusansgluten.com  -- HikaShop version -- : 4  While the HikaShop-manual says that the configured plugins (I refer only to the manual type) are evaluated as if they were filters, nevertheless this implied semantics is not quite true. They seem to be applied to the shipment instance in a sequential manner. I might as well think they are implemented using various SQL SELECTs. In fact I get responses like this one: ITEMS&#95;WEIGHT&#95;TOO&#95;SMALL&#95;FOR&#95;SHIPPING&#95;METHODS = S=&quot;The cart items combined weight is too small for all the possible shipping methods&quot; when it is not true for ALL the methods I configured but only for a subset of them. This may be a clue to the fact that a query gets issued having a WHERE ZONE = &quot;somewhere&quot; clause.  I beg the authors (or anyone who knows) to disclose the exect evaluation semantics (or trivially the algorithm) of the configured shipment rules.  THNX al lot!")*

Hi,

First the shipping methods are loaded with restrictions that can be applied through SQL:
- access level
- published or not
If no method is found the generic "no shipping method is found" message is displayed.
Then, the restriction on the zone, as well as the zip code restrictions, is applied on all the shipping methods left.
If no method is left after that, the "no shipping method found for your zone" message is displayed.
Then, for each shipping method left, the different restrictions (weight, volume, price, etc) are applied at the same time. Each time a shipping method is discarded at that point the reason for which it was discarded is stored. And if no shipping method is left and there is at least one reason stored, the first reason is displayed (as to not display several different error messages to the customer which would make it quite confusing).

The following user(s) said Thank You: [vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")

Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzI4LXNoaXBwaW5nLW1ldGhvZHMvODk2MDQ1LXNlbWFudGljcy1vZi1zaGlwbWVudC1tZXRob2QtZmlsdGVyaW5nP3RtcGw9bWFya2Rvd24=) or [Create an account](/component/users/registration?Itemid=101) to join the conversation.

- **[vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")**
- [![vittorio.zambon's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar17262.png)](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile") Topic Author
- [ Offline](/forum/user/17262-vittorio-zambon)

Less More

- Posts: 9
- Thank you received: 1
-
-

8 years 1 week ago [\#299611](#299611) by [vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")  Replied by *[vittorio.zambon](/forum/user/17262-vittorio-zambon "View vittorio.zambon's Profile")* on topic *[Semantics of shipment method filtering.](/forum/28-shipping-methods/896045-semantics-of-shipment-method-filtering#299611 "-- url of the page with the problem -- :   www.ruedusansgluten.com  -- HikaShop version -- : 4  While the HikaShop-manual says that the configured plugins (I refer only to the manual type) are evaluated as if they were filters, nevertheless this implied semantics is not quite true. They seem to be applied to the shipment instance in a sequential manner. I might as well think they are implemented using various SQL SELECTs. In fact I get responses like this one: ITEMS&#95;WEIGHT&#95;TOO&#95;SMALL&#95;FOR&#95;SHIPPING&#95;METHODS = S=&quot;The cart items combined weight is too small for all the possible shipping methods&quot; when it is not true for ALL the methods I configured but only for a subset of them. This may be a clue to the fact that a query gets issued having a WHERE ZONE = &quot;somewhere&quot; clause.  I beg the authors (or anyone who knows) to disclose the exect evaluation semantics (or trivially the algorithm) of the configured shipment rules.  THNX al lot!")*

your timeliness, kindness and expertise are exceptional! Thank you!

Please [Log in](/login?return=aHR0cHM6Ly93d3cuaGlrYXNob3AuY29tL2ZvcnVtLzI4LXNoaXBwaW5nLW1ldGhvZHMvODk2MDQ1LXNlbWFudGljcy1vZi1zaGlwbWVudC1tZXRob2QtZmlsdGVyaW5nP3RtcGw9bWFya2Rvd24=) or [Create an account](/component/users/registration?Itemid=101) to join the conversation.

Board Categories HikaShop Install &amp; Update Product &amp; Category Display Content Creation Sales and Orders Orders management Reports &amp; Statistics Customers Checkout Payment Methods Shipping Methods Import &amp; Export (CSV, XLS…) Specific Features Affilation Taxes Wishlist Vote Carousel &amp; Slider Mass Actions Filters &amp; Search Discount &amp; Coupon Feature Request Integrations Showcase General Talk about HikaShop Development HikaShop 3.0 Beta Translation Commercial Jobs HikaShop Components HikaMarket Market: Feature requests Market: How to? Market: Bug Report HikaSerial General talk about HikaSerial Serial: Bug Report Serial: How to? Support en Français de HikaSerial (French Support) HikaSubscription HikaAuction Auction: Feature requests Auction: How to? Auction: Bug report Hikashop around the world Support en Français (French Support) Russian FAQ. Курс выживания с Hikashop. Частые вопросы и о Расширения Hikashop Наши сайты на Hikashop 日本語版サポート(Japanese Support) Thai German Archives Bug Report How to?

[](/forum/topics/feed/mode-topics?format=feed&type=rss)

Time to create page: 0.046 seconds

[Powered by](/forum/credits) [Kunena Forum](https://www.kunena.org)

[](#top)
