What if in shipmentcostestimate there was a new y/n flag that meant goid_fm/to was a range vice exact?
That makes sense to me. Sent via BlackBerry by AT&T -----Original Message----- From: Paul Foxworthy <[email protected]> Date: Sat, 9 Jun 2012 07:27:36 To: <[email protected]> Reply-To: [email protected] Subject: Re: Shipping Estimates based on ZIP code Ranges Hi Mike, No, quantity break won't work. What you need are Geos for each zip code range, and a new entity that has a minimum and maximum zip code, and the geoId for the corresponding zip code range. Then write a custom service to take sender and destination zip codes, translate to ranges, then do shipping in the usual way. Cheers Paul Foxworthy Mike Z wrote > > Thanks BJ. I was thinking that maybe creating a new QuantityBreakID type > (SHIPMENT_ZIPCODE) where you can enter a zipcode range and update > ShipmentServices.java may work. > > However, the above table shipping combinations (just for USPS) create > about > 5000 different shipping rules, so instead I'm just going to create my own > perl-based SOAP server, create a new custom 3rd party shipment service > that > just passes zip+weight and returns rate. It is probably easier and faster > for what I want to do. > > On Thu, Jun 7, 2012 at 4:18 PM, BJ Freeman <bjfree@> wrote: > >> Geo can be grouped by areas. so you would first query the Area that >> includes the zipcode the marshal all the geos then look uip the cost for >> each cost for each Geo to give you a range. >> it been a while since I did it so don't remember the exact structure. >> >> >> Mike sent the following on 6/7/2012 2:53 PM: >> >>> I supplier ships to customers based on their zip code and weight. They >>> use >>> a table like this for zip code: >>> >>> *ZIP Code Prefix* *Zone* *ZIP Code Prefix* *Zone* *ZIP Code Prefix* >>> *Zone* >>> *ZIP Code Prefix* *Zone* 005 4 349 6 496..497 3 716..722 5 006..009 8 >>> >>> 350..352 4 498..509 4 723..725 4 010..013 4 354 5 510..513 5 726..731 5 >>> 014..034 5 355..359 4 514 4 733 6 035..037 4 360..361 5 515..516 5 >>> 734..741 >>> 5 >>> Etc... >>> >>> And their shipping rates/pound look like this: >>> >>> Weight Postal Zone (lbs) 1 2 3 4 5 6 7 8 1 $5.65 $5.65 $5.65 $5.65 >>> $5.65 $5.65 $5.65 $5.65 2 $5.65 $5.65 $5.90 $6.55 $8.05 $8.40 $8.75 >>> $9.30 >>> 3 $6.25 $6.25 $7.10 $8.10 $9.40 $10.15 $10.65 $11.40 4 $6.95 $6.95 >>> $8.10 >>> $9.10 $10.55 $11.55 $12.25 $13.30 5 $7.80 $7.80 $9.30 $10.35 $11.55 >>> $12.40 >>> $13.05 $14.20 >>> Etc... >>> >>> I wanted to see if I could setup shipping rules to accurately emulate >>> the >>> above in OFBiz, but I was unable to figure out where I could place >>> "ranges" >>> of zip codes in ofbiz. I first thought that it would be possible to use >>> something like this: >>> >>> <QuantityBreak quantityBreakId="90001" quantityBreakTypeId="SHIP_** >>> WEIGHT" >>> fromQuantity="0.00" thruQuantity="1.0"/> >>> <QuantityBreak quantityBreakId="90102" quantityBreakTypeId="SHIP_** >>> WEIGHT" >>> fromQuantity="1.01" thruQuantity="2.0"/> >>> >>> <ShipmentCostEstimate shipmentCostEstimateId="USPS_**STA10001" >>> carrierPartyId="USPS" carrierRoleTypeId="CARRIER" productStoreId="9000" >>> "productStoreShipMethId="9004" orderFlatPrice="5.65" >>> orderPricePercent="0.0" geoIdFrom="00500" geoIdTo="00599" >>> shipmentMethodTypeId="**STANDARD" weightBreakId="90001"/> >>> >>> <ShipmentCostEstimate shipmentCostEstimateId="USPS_**STA10002" >>> carrierPartyId="USPS" carrierRoleTypeId="CARRIER" productStoreId="9000" >>> productStoreShipMethId="9004" orderFlatPrice="6.55" >>> orderPricePercent="0.0" geoIdFrom="00500" geoIdTo="00599" >>> shipmentMethodTypeId="**STANDARD" weightBreakId="90102"/> >>> >>> But then I soon learned that "geoIdFrom" and "geoIdTo" were actual, >>> exact >>> FROM/TO zip codes, and not RANGES, which I initially tried. >>> >>> So I ask: Is it possible to setup shipping rules based on RANGES of ZIP >>> codes? How would you do it? >>> >>> I already know that I can use USPS to lookups, but I wanted to EXACTLY >>> duplicate the shipping rates that the supplier uses, then add my own >>> markup >>> as I see fit. >>> >>> Thanks >>> >>> Mike >>> >>> > ----- -- Coherent Software Australia Pty Ltd http://www.cohsoft.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ -- View this message in context: http://ofbiz.135035.n4.nabble.com/Shipping-Estimates-based-on-ZIP-code-Ranges-tp4633347p4633391.html Sent from the OFBiz - User mailing list archive at Nabble.com.
