USPS Plugin generating errors for Belgian 4 digit zipcodes

Either this is a problem with the USPS API - ShippingAPI.dll or the NopCommerce 1.3 USPS plugin that comes with NopCommerce 3.9 pre-installed. I've had problems before with Canadian addresses being charged $0 for an order (Likely the USPS problem), but this time for a Belgian order with a 4 digit zipcode, the USPS API errors with - USPS Error returned: Error Desc: OriginZip is invalid. Please make sure OriginZip is 5 numeric characters.USPS Help Context: .

Both the Estimate shipping and the checkout process generate this error. Inputs are Belgium, Other non US, and 1850. I tried 01850 and have the same error.

If NopCommerce is not preserving the leading zero in this case then the USPS Plugin needs a fix. Otherwise I will have to take it up with the USPS, and they aren't as responsive as you guys are. I suspect that they made a change on their side in Feb that broke the plugin. Can someone there take a look at the source code of the plugin and run a shipping test for Belgium with 1850 zipcode?

Thanks

Well, it appears that the problem is that NopCommerce 3.9 or the USPS can't handle an origin ZipCode of Zip+4 so the NNNNN-NNNN origin zipcode format is not supported. I guess that's OK since the +4 only helps with bulk mail and has no impact on First Class.

After reviewing some of the source code for the USPS 1.3 Plug In, I was a bit concerned that they fudged the dimensions of the package to 12x12x12. USPS rules say if any dimension is over 36 or the Length + girth is over 45 inches is must ship Priority Mail - and up to 4lbs for international first class packages.

Sometimes I ship maps that are 36 inches and the tube or box they ship in makes them 37. It would be nice to see an update to the USPS 1.3 Plugin that actually uses the maximum dimensions gleaned from the items ordered - since those numbers are on the Product pages and I enter them with the weight. Then NopCommerce could disable the first class international option automatically on check out.

Two thirds of the orders I get are to Europe, and customers are constantly getting charged first class rates instead of required Priority Mail - which is usually 3x the cost. A $35 map with $14 first class vs $52 Priority can be a deciding factor for the customer.

RE: "...fudged the dimensions of the package
The USPS plugin was not updated like the UPS and FedEx which offer, in the configuration page, a "Packing Type". (E.g. "Pack by Volume",  "Pack by one item per package")

RE: "...Then NopCommerce could disable the first class international option automatically on check out. "
The core nopCommerce does not have any such conditional capability.  If a shipping method is configured/selected by the store owner and it gets returned by shipping plugin, then it will display to the customer.


Shipping Director can deal with these issues. It has better "Packing" (by volume, but items that don't fit the specified box size get their own package) and it can remove methods - example here; in your case, the Name Expression (which can remove methods when the expression evaluates to blank "", could be:

[$Name].Contains("First Class") and Items.Any(Product.Length > 12) ? "" : [$Name]

That doesn't change the fact that the standard USPS plugin doesn't implement the US postal rules adequately. Granted the USPS shipping regs are a pretty thick book, but I would think the plugin that has been in use for all these years would better implement box size and international stuff. It doesen't even support Zip+4 for origin zipcode. Lots of custom coding shouldn't be the standard answer. So my only choice is to put up with its limited abilities or write a bunch of custom code. Maybe they should spend less time writing glitzy new versions of NopCommerce that we constantly have to upgrade to, and address some of these very basic plugin issues. It would appear that the USPS API is pretty robust, maybe a second look at interfacing with all its functionality properly is in order. Sorry its a free plugin.