TomatoCart

Hello tomato community!

Well first of all i found that open source cart just recently and i am amazed how great it is, i worked with oscommerce for years and installed hundreds of contributions, some of the "have to have" are already all in tomato and i find the system very stable, good looking and 99% ready to go.

I looked a bit deeper in common things customers asks, and that is always regarding to the shipping options, the famous contribution "mzmt" or also called "shipping to multiple Geo Zones using multiple tables" was one on th ebast so far, very flexible.

So i was very happy to find it back natively to tomato by the name of "table rate".

but well either i totally miss somthing either i think it is not complete, we can install it and set it up for a zone but just ONE zone, where in mzmt it was all dynamic and we could add as many zones as we want, i have set up different zones such a "country of shop" "europe" "US" and such... but no way to be able to set up different table rates for the other zones, which is totally missing.

so either i wonder if anybody know how to tweak that module to be able to set up different rates for different zones, or HOW to duplicate this module like "table rate 2" and then set it up for an other zone.

i tried to duplicate it (very easy in oscommerce) but if i do it here the "shipping modules" window is just blank :-/

if any of you could give me som elight s on that that would be awsome

anyway i shall say a big "bravo!" to the tomato team, i am very impressed ^^

Hi, thanks for your feedback.

Unfortunately the osCommerce contribution can not be install on TomatoCart. Can you send us more details so that we can help you to build this module.

Thank you very much for your reply,

well that would be great to be able to do something on that matter, unfortunatly i am not a developer and my php skills are very limited, i can only do small easy tweaks.

But to illustrate a bit better what makes that mzmt contribution i did few screenshots.

so the problem of tomota table rate modle is that it is limited to only one zone, which is very frustratting as we can create multiple zone in tomato in "start > definitions > zone group".
may shops want different fees depending of where they are going to send their good, shipping is off course more expensive when it goes at the other sid eof the world

so tomato has it totally right for one zone:

http://s867.photobucket.com/albums/ab237/lolofora/?action=view&current=tablerate_tomato.jpg

you have all the fonctionalities and you can apply it to a zone, for me being in france, i did setp up as zones "france, europe, rest of the world"
so in my example it has been set up for france.

here are other screenshots from the original oscommerce contribution:

http://s867.photobucket.com/albums/ab237/lolofora/?action=view&current=tablerate_osc01.jpg

a great fonctionality is that in the "configuration" section left hand side bottom "Multigeozone multi tableshipping you can setup how many zones you will use.

To be honest i did a LOT of oscommerce wbeiste and in 95% of the time only 3 zones were doing the job,

anyway once you set up the number of zones that you want to use when you go to configure the module itself

and you see the sames options that you can set up but for differents zones

http://s867.photobucket.com/albums/ab237/lolofora/?action=view&current=tablerate_osc02.jpg

it is even better as as its name indicate you can even setup different table rates.

that module is just great and so versatil, i use it for 90% of my customers.


so either there is something doable to make your original table rates module to work the same way, or as i said in my first post, how hard and simply what to do, to litteraly "duplicate" your existing module.

at the moment if we set it up we assign it to one zone, during the checkout process if we live in a zone that is not the zone used in th emodeul we do not have any otehr shipping methode.

the simplicity to duplicate that module would be to have in the admin panel in the listing of the shipping modules something like "Table rate (zone 1), Table rate (zone 2), Table rate (zone 3)" etc....

then for each modulewe could assign a different zone.
from what i understand during the checkout process only the module with the zone matching the delivery adress would show up.

That could be a great nice and easy trick, rather than (even it it would be better) redevelop your original table rate module.

But how easy it could be to duplicate it?

Tomato is absolutly great but so "pushed" than i doubt that is is easy for anybody to tweak it and develop contribution like in oscommerce.

Hi lolofora ,

The developer's guide about the payment module is completed, the guide about the shipping module is writing, the guide about how to develop a module for the admin panel and how the template engine works in the front end is writing too.After releasing the TomatoCart v1.1 recently, we'll release the developer's guide so that make the developing new module convenient for the developer who is supporting the TomatoCart.

About this issue, We'll consider adding the mutiple zones to be set if it is possible to implement.

jack.yin wrote:

About this issue, We'll consider adding the mutiple zones to be set if it is possible to implement.

any news about this?

d.

Sorry to resurrect an old thread, but i've been battling with this for a few days and think i have a solution / workaround.

I'm no developer but can muddle through with logic and using www.tomatocart.com/wiki/Create_your_own_...#Backend_Development as a reference.

I simply copied the table.php and .xml files and replaced the table identifiers in each file to z1table and renamed the files to the same. Of course you can have z2table, z3, z4.....
This just creates a new shipping module that can have it's own zone associated to it through Definitions > Zone Groups and it's own price table.

If Zones are setup and associated with the table rate the customer will only see the correct shipping for their shipping address.


A very simple 'hack' but I hope it's of some help to people.