Not being able to use dimensions is no problem. Just do your own quick Dim Weight calculation and enter the weight accordingly in Magento. Dimensional weight is simply length x width x height (in cm) divided by 4000. Ausie Post (all couriers for that matter) charge on the greater of the two. Example below.
Not to hijack this thread but since its related heres another challenge if anyone can point in the right direction.
We use Couriers Please Satchells and Aus Post Satchels.
Using Matric Rate ext we set it up like so:
If Post Code is a designated Couriers Please Zone then show Couriers Please else show Aus Post . This took me a long time to put together as we needed to determine the NON CP areas and fill the voids with Aus Post.
Then there is the issue where CP do not ship to PO BOXES, there is information and ranges available for PO BOXES, so we took it one step further and started breaking down the CP Zones with exclusion for the PO BOX Post Codes, now this took an awfully long time and we have a about 700 rows in the table.
So now the problem is where a POST CODE can be a Couriers Please zone and a PO BOX , but not a dedicated PO BOX Post Code.
For example NSW 2192 is Belmore and is a Couriers Please zone, Belmore however has PO BOXES too which are 2192.
So they are given a Couriers Please option but go on to enter a PO BOX!
Short of modifying it somehow with an override to detect PO BOX in the address line and then present a different set of options, which I think is the only way to do this - has anyone else face this issue , have a suggestion or know of an extension that will handle the lot?
I run a similar setup, but with Fastway satchels (also no PO boxes).
I get away with simply labelling the shipping option: “Fastway (no PO Boxes)” in the checkout. I get very few false orders that way, but perhaps I’m just lucky!
There is no extension that can handle this, but if you were prepared to pay for the development, Webshopapps (matrix rates author) could probably take their Fastway extension and adapt it for Couriers Please (assuming CP have an API available), and then parse the address for PO Box addresses. I would *think* that is a reasonable option - with those caveats.
Contact Karen at www.webshopapps.com and I’m sure she will give you an assessment and quote for the work.
That could work except we also plot the Satchel Type and Delivery ETA in the description to make it easier when processing orders, for example it will say:
Coruiers Please - 3KG (1-3 Days)
This works in managing customer expecations (they dont all visit the FAQ page) and also ensure the person packing isnt mucking around trying to figure out what box will fit in what satchel (this has all been worked out prior).
Will contact Karen, they have been very helpful in the past.
The commercial Matrix ext does the trick from WebShopApps, right now its a tad pricey and going to give it a crack first, if that fails then ...
Some of us a destined to learn the hard way!
I did find this http://www.fontis.com.au/blog/magento/preventing-po-box-shipping-addresses perhaps a good starting point, ideally though we don\’t want the restriction applies fully, only where the criteria returned contain \’Couriers Ple...\’
Hi All, my store is on an old version 220.127.116.11 as I haven’t got around to updating it yet. Yesterday my Australia post Integration just stopped working. When trying to estimate shipping I get no options displayed at all, I have actually had to add flat postage to allow customers to continue placing orders. Does anyone know if Australia Post has changed something on their side to break this? How could I debug this, or is it better to bite the bullet and upgrade.