To clone or not to clone?

[earmsby]

Before I go ahead and make a bunch of cloned shipping modules I thought I'd see if what I am doing makes sense.

I have 3 shipping methods (Ground, 2-day and Next day). Each of these has a different matrix of prices depending on number of items ordered. In addition, I have additional separate matrices for same three methods for USA, Europe, Asia and Rest of World.

So...

am i right in thinking that what I need to do is make clones of the table module for each of these? So that would be something like:

usagroundtable
usa2daytable
usanextdaytable
europegroundtable
europe2daytable
europenextdaytable
etc...

Ellie

[earmsby]

Answering my own question. This seemed to work fine and cloning the additional modules was easy after the first one.

My next problem is that setting the zones for these does not seem to work even though I'm pretty sure I have the zones set up ok.

The new modules work fine if zone is set to none but if I set zone to existing zone they do not show up for test customer located in that zone.

I notice that the module status icon is yellow if the zone is set. The same is true for the zone itself, although I assumed this was just because I had not set tax for the zone.

Hmmm???

Ellie

[earmsby]

One further thing I just checked...

A flat rate module works with the zones without a problem, so it seems like it's an issue with the table module itself not the zone?

Ellie

[Ajeh]

Each clone would have its own settings if you cloned everything correctly ...

So, each clone could use its own Zone that you built or share a Zone as needed ...

Check that you have replaced all table with newclonename and TABLE with NEWCLONENAME and be careful that the actual calls for TABLE_something where that is a database table name are not touched ...