ozpost shipping module

Hi Rod

Yes Ty Package Tracker comes with direct links to USA carriers for the download and display of tracking information via account, although I have yet to realise the extent of that information.

And these links would need to be changed for Australian carriers eg AusPost, Fastaway.

However whether the Australian carriers provide useful tracking info has yet to be seen by me from previous experience.

If OzPost provides links to the tracking facilities of certain services of the Australian carriers, that could automatically be included in an order confirmation email, this would be sufficient for my current needs without having to bother with Ty Package Tracker.

Cheers

dw08gm:

If OzPost provides links to the tracking facilities of certain services of the Australian carriers, that could automatically be included in an order confirmation email, this would be sufficient for my current needs without having to bother with Ty Package Tracker.

Cheers

Won't happen, unless ozpost.net expands to make bookings as well, because unless/until a booking is made there won't be any reference data to include in the emails... and I really can't see ozpost.net ever evolving into a booking service as well as a quotation service, primarily because Australia Post don't provide a standard booking/tracking service (Eparcel is not the same), and secondly, because most of the courier companies are very difficult to work with in regards to product integration.

Cheers
Rod

Hi Rod

Thanks for the extra clarity.

As a bit of background to my initial query, provision for Ty Package Tracker is being incorporated into the new EditOrders 3.0 and SuperOrders 3.0 mods about to be released. However, these mods do not require the installation of Ty Package Tracker.

QCTechnologies:

I cannot get the TNT part to work.

We have an account number and password but I keep getting the error message "The account number supplied is invalid or not assigned to this login."

You need to contact the tnt helpdesk and ask that the RTT ('Rated Transit Times' service for your account be enabled.
You DON'T need to change/alter your current username/password (these produce a different error message), you'll find it'll just start working as soon as it is activated.

CIT Helpdesk

If you are experiencing difficulties accessing the TNT website or experiencing problems with TNT's online services please send us your enquiry. If you prefer to speak to a member of our CIT Helpdesk please call our Technical Support Team on 1300 851 131.

Cheers
Rod

I have tried these postcodes 0820 0885 0822; not working with V2.2.0 V2.1.1

1.3.8a
ecolitecandles.com.au
paid 3 or 4 days ago; but http://www.ozpost.net/postage.php?flags=expires&host=EcoLite+Candles&fromcode=0885

V2.1.1:
Debugging information Item 1-1Large Faerie with Flower in her Hair ParcelWeight 6100gmsItems 1Weight 6710gmsDimensions 29 x 25 x 2.5 29 x 25 x 2.5 Cube / Weight 1812.5cc / 0.453125Kgs 1812.5cc / 0.453125Kgs
Submitted: Length=29.00cm, Width=25.00cm, Height=2.50cm, Weight=6710gms, NumBoxes=1Server response time 0.45msServer Returned:
Error0.00-1Invalid input Data [Suburb error] 74.55.148.130 Wed Dec 15, 2010 19:07 (SA Server Time) 18:07 (NT Store Time) 0.00 0.00 BAGOT N/A 60

##################################################
p.s.
V2.2.0 on 1.3.8a does not echo shipping module name; I am still using old ozpost update_product.php collect_info.php; and that still seems fine.

nothing is working at the moment (even for the free aust post); no post code are working for any module. but I see the remaining days is fixed. I dont know I will try again tonight.

vandiermen:

I have tried these postcodes 0820 0885 0822; not working with V2.2.0 V2.1.1

I think it would help a LOT if you mention what the actual problem is, before explaining what you have tried in order to fix it. :-)

Each storename/postcode creates a new database entry, each with a new 60 day trial period

vandiermen:

ecolitecandles.com.au
paid 3 or 4 days ago; but http://www.ozpost.net/postage.php?flags=expires&host=EcoLite+Candles&fromcode=0885

This link curently shows 58 days until expiry.

EcoLite Candles/4870 shows 1095 days until expiry.

This means at the time of registration I identified EcoLite Candles/4870 as being the actively used store rather than the specified EcoLite Candles/0885 ... (Actually, that would have been the only active one at the time, because if I'd identified multiple combos for the same store I would have updated both records, which I have now done).

In any case, this doesn't explain what the problem is, because with 60 days or 1000+ days subscription this aspect of things isn't going to make any difference.

vandiermen:

Server Returned:
Error0.00-1Invalid input Data [Suburb error]
74.55.148.130
Wed Dec 15, 2010 19:07 (SA Server Time)
18:07 (NT Store Time)
0.00 0.00
BAGOT N/A
60

I've reformatted the relevent part of your debug (above) to help make it a little easier to read:

Firstly the error:
Invalid input Data [Suburb error]
This can be either the store origin suburb, or the destination suburb..

The "74.55.148.130" indicates the server IP address (prep work for multiple servers rather than simple redundant servers)

**Wed Dec 15, 2010 19:07 (SA Server Time)
18:07 (NT Store Time) **
These lines are pretty obvious :-)

The servertime is used for logging purposes, the Storetime is used to ensure next day delivery deadlines match the store timezone
**
BAGOT N/A**
These are the origin suburb and destination suburb (ok, not exactly obviious until informed). In this case a destination suburb cannot be found** (N/A)**, this can be caused be a lack of a destination postcode, or an invalid postcode.
EcoLite Candles/820 (BAGOT) was the store origin used with this particular test.

The final entry "**60" **is the subscription remaining days, in this case it was the same day you started using this particular storename/postcode combo.
SO, if the destination suburb is your problem you'll need to ensure that you are testing with valid destination postcodes. This has gotten a lot stricter over the last couple of versions due to inaccuracies with single postcodes covering multiple suburbs.
If you find valid postcodes that still don't seem to work please let me know which ones and I'll take another look.

As for the store/origin postcode, sooner or later you'll settle on one or another (most people don't get this choice), and sooner or later I'll match whatever is settled upon with the data from the records that were subscribed with.

vandiermen:

V2.2.0 on 1.3.8a does not echo shipping module name; I am still using old ozpost update_product.php collect_info.php; and that still seems fine.

Where is it that you are not seeing this? (a screenshot may be helpful.. or not.. ). LOL

vandiermen:

I am still using old ozpost update_product.php collect_info.php; and that still seems fine.

The update_product.php collect_info.php and other files under /admin never need updating between ozpost module versions. They may require updates with zencart versions though (but to be perfectly honest, I don't recall when I last updated them).

Oh, and please remember that when switching between versions it is imperitive that you click the remove/install button sequence in order to keep the database syncronised with the files.

Cheers
Rod

vandiermen:

nothing is working at the moment (even for the free aust post); no post code are working for any module. but I see the remaining days is fixed. I dont know I will try again tonight.

I've absolutely no explanation for any of this.. I've been away from the computer until shortly before replying to your first posting.

Cheers
Rod

RodG:

I've absolutely no explanation for any of this.. I've been away from the computer until shortly before replying to your first posting.

Cheers
Rod

problem seems to have been V2.1.1 tpl_modules_shipping_estimator.php is not compatable with V2.2.0 or aust post module

its all fixed now.

Hi Rod,

So it's Christmas and I am over people saying they have not received their parcel! I was wondering how difficult it would be to make every order over $50 registered and insured. I can't seem to figure out the settings to get that to happen. Also it doesn't allow for satchels to be registered, which you can do. Any advice would be greatly appreciated, how many claims can you have with Australia Post at the same time?

Hi Rod, Ok I have upgraded before, but I find it a bit tricky and now need to go to your newer version. For the illiterate of us could you advise what files we need to change / process to follow to upgrade?

I am sure lots of us would appreciate it!

Thanks
Jazzah

(Fully paid up subscriber!)

jazzah:

Hi Rod, Ok I have upgraded before, but I find it a bit tricky and now need to go to your newer version. For the illiterate of us could you advise what files we need to change / process to follow to upgrade?

I am sure lots of us would appreciate it!

..... V2.2.0 UPGRADE.txt ....................
As a GENERAL RULE upgrading from an older version of ozpost will require that you simply replace the following two files

/includes/modules/shipping/ozpost.php
/includes/languages/english/modules/shipping/ozpost.php.

Also check for any new icons. Anytime a new method is added there should also be corresponding icons for them.

After upgrading you should ALWAYS log in as admin, then 'REMOVE' and 'INSTALL' the ozpost module. Please take note of your settings before doing this because they will be returned back to the instalation defaults as a result of this NECESSARY action.

V2.1.1 to V2.2.0
If upgrading from V2.1.1 to V2.20 you only need to replace the file
/includes/modules/shipping/ozpost.php
(you still need to perform the remove/install process though)

Cheers
Rod

jazzah:

I was wondering how difficult it would be to make every order over $50 registered and insured. I can't seem to figure out the settings to get that to happen.

You'll need to do some custom editing for this because the code doesn't have the functionality to enable/disable methods based on price.

It shouldn't be difficult... in the /modules/shipping/ozpost.php file, seek out the "CASE" statements (there are lots of them)

For example:

case "RPP";
            if(in_array("Regular", $this->allowed_methods))   $handlingFee = MODULE_SHIPPING_OZPOST_RPP_HANDLING ;
        break ;

This is the entry for regular parcels.. and the entry is "set" if "Regular" parcels are in the $this->allowed_methods array.

If you wish this entry to NOT show (because the ordercost is over $50) then you'll just need to expand the test so it reads:

case "RPP";
            if ((in_array("Regular", $this->allowed_methods)) && ($ordercost < 50 ) ) $handlingFee = MODULE_SHIPPING_OZPOST_RPP_HANDLING ;
        break ;

You'll need to repeat this with each "CASE" that is normally enabled, but you wish to conditionally disable.

You may find it easier to simply dissallow regular parcels, which means all order regardless of cost must be sent either registered or insured.

jazzah:

Also it doesn't allow for satchels to be registered, which you can do.

I do realise that this is possible, and one day I might add it as another valid option (my how this has grown since its initial inception), but the reason it isn't supported is mainly because of the fact that satchels are prepaid, which makes them more of a convenience rather than a cost effective method of mailing.. The convenience being that most merchants will have them on-hand and will not need to enter a post office in order to post them.
This convenience gets lost if you need to enter the post office in order to add registration, and if you are going to do that, you are best off packing the item(s) in a reguar box which will often be a cheaper and better packaged option anyway. (In other words, disable the satchels)

jazzah:

how many claims can you have with Australia Post at the same time?

As far as I know there are no limits.

Cheers
Rod

Hi Rod

Thanks for all your past help.

As promised I up-graded from V1.0.1 to V2.2.0 and everything seemed to go quite well.

However, I must have made a couple of mistakes with the settings or mis-interpretted the logic.

I operate from 4012 (Brisbane suburban) and mostly use 5kg Express satchels.

I tried to set up using walk in, registered parcel post, normal express parcel, Pre-Paid 3 and 5kg satchels and ego.

For some reason I can't get a quote for the Satchels at all and the Express parcel claims I am sending outside the express network from 4012 to 3000.

http://charcool.com/shop/index.php?main_page=product_info&cPath=18&products_id=34

I have debugged baseded on the product above and this is the server response

<?xml version='1.0' encoding='ISO-8859-1'?><quotes>

<quote><id>EGO</id><cost>8.80</cost><days>3</days><description>E-go Parcel</description></quote><quote><id>RPP</id><cost>11.90</cost><days>3</days><description>Parcel over 500gm</description></quote><quote><id>PPSE3XL</id><cost>14.60</cost><days>1 (Outside Express network - fastest possible delivery)</days><description>3kg XL Express Satchel</description></quote><quote><id>REG</id><cost>14.85</cost><days>4</days><description>Registered Parcel over 500gm</description></quote><quote><id>RPPi</id><cost>14.85</cost><days>4</days><description>Insured Parcel over 500gm</description></quote><quote><id>EXP</id><cost>22.25</cost><days>1 (Outside Express network - fastest possible delivery)</days><description>Express Parcel over 500gm</description></quote><quote><id>COD</id><cost>22.40</cost><days>4</days><description>Cash On Delivery </description></quote><quote><id>EXPi</id><cost>25.20</cost><days>1 (Outside Express network - fastest possible delivery)</days><description>Insured Express Parcel over 500gm</description></quote><quote><id>PLT</id><cost>27.00</cost><days>1 (Outside Express network - fastest possible delivery)</days><description>Platinum Parcel over 500gm</description></quote><quote><id>PLTi</id><cost>29.95</cost><days>1 (Outside Express network - fastest possible delivery)</days><description>Insured Platinum Parcel over 500gm</description></quote><information>
<server>74.55.148.130</server>
<timestamp>Tue Dec 28, 2010 11:34 (SA Server Time)</timestamp>
<requesttime>11:04 (QLD Store Time)</requesttime>
<postdate>Wed 29th of Dec</postdate>
<insurance>2.95</insurance>
<registration>2.95</registration>
<fromsuburb>NUNDAH</fromsuburb>
<destsuburb>MELBOURNE</destsuburb>
<expires>337</expires>
</information>
</quotes>

In addition I also seem to be getting 2 sets of quotes one from V 2.2 with images and an earlier version (maybe???) without. Ego comes up after the first 2 which is what makes me think I am getting 2 sets of quotes.

Available Shipping Methods. For your protection, all regular parcel rates include registration Rates
Australia PostRegistered Parcel Post - 4 days Estimated Delivery Time)

• Includes $5.00 Packaging & Handling. $2.95 Registered. $19.85
  Australia PostExpress Parcel Post (1 days Estimated Delivery Time)
• Includes $5.00 Packaging & Handling. $27.25
  E-go Parcel Mon 3rd of Jan
  Includes $5.00 Packaging & Handling.
  $13.80
  Australia Post Registered Parcel over 500gm Tue 4th of Jan
  Includes $5.00 Packaging & Handling. +$2.95 fee
  $19.85
  Australia Post Express Parcel over 500gm Thu 30th of Dec (Outside Express network - fastest possible delivery)
  Includes $5.00 Packaging & Handling.
  $27.25
  Store PickupWalk In $0.00

I have uninstalled and re-installed but still come up with the same result.

You may have seen this level of incompetence before ???

thanks

PS: Subscription the subscription is cheap. Accurate shipping costs are very complex. Hope it's working out.

Arliss61:

I operate from 4012 (Brisbane suburban) and mostly use 5kg Express satchels.

For some reason I can't get a quote for the Satchels at all and the Express parcel claims I am sending outside the express network from 4012 to 3000

The debug output you posted indicates that satchel quotes were returned from the server, in this case, the 3kg XL sized, which implies that these are being disabled by your local settings. Yes, I know logic dicates that in this instance a quote should probably be given for a 5Kg Stachel instead, but the server doesn't know what you have disabled.
I'm not really sure what to do about this. Suggestions?

As for being outside the express network, this was true according to the postcode list(s) available when I added the tests and checks. Since then new, much more comprehensive lists have been published, which I shall be incorporating into the server code early in the new year. Meanwhile I've just manually added 4012, so this should be fixed for you now (let me know if not).
The added tests/checks are to enable accurate predictions of overnight deliveries.

Arliss61:

In addition I also seem to be getting 2 sets of quotes one from V 2.2 with images and an earlier version (maybe???) without. Ego comes up after the first 2 which is what makes me think I am getting 2 sets of quotes.

With DEBUG enabled you will/should see two sets iof quotes.. The first messy looking set is what is returend by the server, the second set is what is displayed to the customer. Usually these will match, but if you have disabled some methods these will be missing from the customer view.

Arliss61:

You may have seen this level of incompetence before ???

I refuse to answer this on the grounds that I will incriminate myself :-)

Cheers
Rod.

Hi again Rod

Thanks for adding 4012. We're small but very important :).

Regarding the satchels quote:

satchel quotes were returned from the server, in this case, the 3kg XL sized, which implies that these are being disabled by your local settings. Yes, I know logic dicates that in this instance a quote should probably be given for a 5Kg Stachel instead, but the server doesn't know what you have disabled.
I'm not really sure what to do about this. Suggestions?

I understand and it does seem a conundrum. The server is just trying to fit the board in the cheapest satchel it can find, to the buyers benefit. It doesn't know I am too lazy and cheap to keep an entire range of Pre-Paids on hand. Clearly it doesn't know me as well as you do!

Here's my thought for what it's worth.

The satchels cost the same no matter where you are or where you are posting even outside the express network so you don't really need a server quote. They are more like a fixed price option.

Perhaps if you could have any of the four satchels selected optionally with the merchant inputting their own pricing.

Thus if I select 5kg satchels in the menu (all I stock) at $22.00 (including handling) the price could be displayed whenever a product within the dimensions was being quoted.

Of course this might be a bit of a nightmare (?) to program.

Otherwise, I guess I would need to see if AP were willing to sell me, a humble retailer, some of their very important and special 3kg and 5kg XL satchels which apparently are only available to "contract/account" customers who have slept with an independent member of the Commonwealth parliament
http://auspost.com.au/business/express-post-products.html#satchels

Leave you with that horrible thought.

Regarding the 2 quotes, after turning off debug this is what I got (with 3kg XL satchel) enabled:

6 quotes and still outside the Express Network (probably update overnight I guess).

Thanks again. At least I now understand what I didn't know.

cheers

cheers

Arliss61:

Hi again Rod

Thanks for adding 4012. We're small but very important :).

I agree :)

Arliss61:

Regarding the satchels quote:

I understand and it does seem a conundrum. The server is just trying to fit the board in the cheapest satchel it can find, to the buyers benefit. It doesn't know I am too lazy and cheap to keep an entire range of Pre-Paids on hand. Clearly it doesn't know me as well as you do!
Well, not yet, but as with anything I code, I try to make the program as clever as I am (which equates to being as cheap and as lazy as everyone else) <grin> .

Arliss61:

Here's my thought for what it's worth.

The satchels cost the same no matter where you are or where you are posting even outside the express network so you don't really need a server quote. They are more like a fixed price option.

This is true, up until the time Australia Post increases their fees, at which time everyone will need to manually update their prices, which negates the benefits of using a server. Beleive it or not, some merchants are so 'out of touch' they still offer economy air as an overseas shipping method (Australia Post dropped this about 3 years ago).

Arliss61:

Perhaps if you could have any of the four satchels selected optionally with the merchant inputting their own pricing.

Thus if I select 5kg satchels in the menu (all I stock) at $22.00 (including handling) the price could be displayed whenever a product within the dimensions was being quoted.

Of course this might be a bit of a nightmare (?) to program.

Not really a 'nightmare', but it does place more dependance on the client code, which out of necessity I need to keep as simple as possible for portability purposes).

Nonetherless, it IS an option to be considered.

Another option (easy to implement, but I'm not convinced that there isn't a better way) is for the server to provide quotes for all satchels (that are suitable), and leave it for the client to filter the ones they don't need. This is much like the current method, but it will have the 'bad' side effect of offering (say) the 3kg and the 500gm stachels instead of just the 500gm ones, if suitible. IOW, it will present the customer an option that they don't really need. It WILL solve the current problems though.. but it is a matter of choosing the lesser of two evils, in my opinion.

My 'other' solution is to update the client code (again), to include another setting to tell the server to continue to work the way it is, or to return all satchel quotes as indicated above, thus making it a user choice.. This is the 'near ideal' solution, other than it does introduce yet another setting that would probably confuse most people as to its purpose.

As you can see, several possible silutions, but so far nothing I'm 100% happy with. (Which is why I seek other ideas and inputs).

Arliss61:

Otherwise, I guess I would need to see if AP were willing to sell me, a humble retailer, some of their very important and special 3kg and 5kg XL satchels which apparently are only available to "contract/account" customers who have slept with an independent member of the Commonwealth parliament
http://auspost.com.au/business/express-post-products.html#satchels

LOL.

Have you asked at your local PO recently? As of last May the 5kg XL satchels were made available to most outlets for general use.

Arliss61:

6 quotes and still outside the Express Network (probably update overnight I guess).

I may need to take another look into the outside express network (my update should have taken immediate effect)... as for the duplicate quotes, it appears that you have more than one 'australia post' module installed/activated.. This is probably because you needed to make such a large jump in versions, and in the change from V1.x.x to V2.x.x I needed to keep the code entirely separate for developement purposes, therefore is is/was possible to have two versions running at the same time. Just disable the older version.

Cheers
Rod

Thanks again. At least I now understand what I didn't know.

cheers

cheers[/quote]

Rod

Yep had the old Aust Post module running in tandem.

Looking better now - although 4012 still seems to be outside the Next Day network.

A possibility for overcoming the satchels issues (which ones do you have/offer) is to clone the Store Pick Up "Walk In" module so that the text you input in > includes/languages/english/modules/shipping/storepickup.php shows your satchel. The price can be controlled from Admin - Modules - Shipping.

Downside is that it will still be offered for everything - very small products (overkill) and very large (won't fit).

I am aware from http://shop.vcsweb.com/ that there are only a small number of sites using the paid Ozpost solution, so my problem is probably pretty rare.

If I was oo.com.au I'd pay a programmer to make a more elegant fix but for now this will probably do:

Arliss61:

Looking better now - although 4012 still seems to be outside the Next Day network.

I've just (re)checked, and 4012 is definitely now identified as being inside the next day delivery network, so I can only guess that it was the destination postcode that was outside (apparently).

For my tests, I used postcodes 3000 (Melbourne) and 5555 (Ashford).
Only the quote to 5555 indicated that it was outside the express network.

Arliss61:

A possibility for overcoming the satchels issues (which ones do you have/offer) is to clone the Store Pick Up "Walk In" module so that the text you input in shows your satchel. The price can be controlled from Admin - Modules - Shipping.
Downside is that it will still be offered for everything - very small products (overkill) and very large (won't fit).

This is also an alternatve for those merchants that don't wish to support the ozpost project.
For me, this would have an even bigger impact in that I'd need to replicate this same functionality for each of the different softwares. Admittedly, this is currently only ZenCart and OsCommerce, but I have a version almost ready for OpenCart, and hopefully several others by the end of 2011

Arliss61:

I am aware from http://shop.vcsweb.com/ that there are only a small number of sites using the paid Ozpost solution, so my problem is probably pretty rare.

Just to clarify, it isn't just a small number of sites using the ozpost method, it is more a matter of the small number of (active) Australian zencart merchants period (which is why I need to bring other sofwares on board, because I suspect that all the other ecommerce solutions will also be small in number, but the combination of them all will produce positive gains for all of us.

As for your problem being pretty rare, I can't really say for sure. I became aware of what I consider to be my screwup (lack of foresight) in this regard a few minutes after releasing the initial V2.x.x code (Actually the 'problem' goes way back to V1, but it has become more troublesome with V2 with the additional 'hide' functions.
Other than yourself I have had one other person report that it caused a problem (same reasons as yourself), which actually makes it unrare considering the total number of users.

Arliss61:

If I was oo.com.au I'd pay a programmer to make a more elegant fix but for now this will probably do:

A more elegant fix will be forthcoming because this 'hole' does bug me in that it can and does cause unexpected behaviour, not to mention the fact that It is in my best interests to make the module work in ways that the users would like and expect, so in this regard, I am the 'paid programmer'. :smile:

Cheers
Rod

RodG:

Another option (easy to implement, but I'm not convinced that there isn't a better way) is for the server to provide quotes for all satchels (that are suitable), and leave it for the client to filter the ones they don't need. This is much like the current method, but it will have the 'bad' side effect of offering (say) the 3kg and the 500gm stachels instead of just the 500gm ones, if suitible. IOW, it will present the customer an option that they don't really need. It WILL solve the current problems though.. but it is a matter of choosing the lesser of two evils, in my opinion.

My 'other' solution is to update the client code (again), to include another setting to tell the server to continue to work the way it is, or to return all satchel quotes as indicated above, thus making it a user choice.. This is the 'near ideal' solution, other than it does introduce yet another setting that would probably confuse most people as to its purpose.

OK, I think I've figured out the best way to do this.

1. By default, have the server returning quotes as it currently does (less chance of causing issues with older versions).

2. Update the client code with the following tests/checks
   a) Are ALL satchel sizes enabled? If so, no changes needed
   b) Are ALL satchel sizes disabled? If so, no changes needed.
   c) Are only some satchel sizes enabled? If so, send additional data to the server so that either ALL suitable satchel quotes are returned (IOW, the smallest sachel possible, plus those that are larger, if any).

The downside being if the client only disables the XL satchels (the most likely case) and the item/parcel is 500gm suitable, the customer will still be presented with the 3kg satchels as well.

The other option for part 'c' would be to send enough data to the server (based on what is enabled/disabled) to enable the server to return quotes based on client selection and what is possible (as opposed to what is optimum).

Hmmmm.... probably not to hard after all.... Stay tuned...

Cheers
Rod