| Discussion Forum: All Replies to Message 1466604 |
|
 |
| | | Author: | dcarmine  | | Posted: | Apr 27, 2024 22:11 | | Subject: | Re: US sellers: Shipping methods update | | Viewed: | 70 times | | Topic: | Administrative | |
|
| I changed to the new API last Wednesday and all orders stopped. I don't
think it's working yet? No way for me to tell exactly, I changed mine back
to a my manual chart. Maybe you can test it on your side.
Thanks
Donna
In Administrative, CE_Anastasia writes:
| | Dear BrickLink sellers in the United States,
We have removed these outdated API-based shipping methods:
• Domestic USPS First-Class Packages (retail),
• Domestic USPS First-Class Packages (commercial).
Starting from today, you will be seeing the following shipping methods in your
Store Settings instead:
• USPS Ground Advantage (commercial),
• USPS Ground Advantage (retail),
• USPS Priority Mail (commercial),
• USPS Priority Mail (retail).
As usual, you can access the new USPS rates for Courier API methods upon selecting
each method in the Rate Chart.
Thank you,
The BrickLink Team
|
|
|
|
| | | | | |
| | | | | Author: | cosmicray | | Posted: | Apr 29, 2024 07:26 | | Subject: | Re: US sellers: Shipping methods update | | Viewed: | 49 times | | Topic: | Administrative | |
|
| In Administrative, dcarmine writes:
| | I changed to the new API last Wednesday and all orders stopped. I don't
think it's working yet? No way for me to tell exactly, I changed mine back
to a my manual chart. Maybe you can test it on your side.
Thanks
Donna
|
An observation, is that orders (without any shipping method changes) went into
a very slow patch for a several days. Do you have a test account ? Might be worth
putting a few things into a shopping cart and see if they calculate correctly,
and based upon the correct zone.
What is not clear (from the announcement) is ... how is BL arriving at the zone
(and the correct postage). The old API method pre-dated when USPS switched to
zone based PM and FCPS. With the new system, you can do it via a API call to
USPS or by loading your own tables and doing a 2-step table lookup (one lookup
for the ZIP-code to zone calculation and one lookup for the actual postage values).
More recently USPS has applied a need for package dimensions, because larger
packages get surcharges. Presumably the API calls also have to supply package
dimensions, else then will generate incorrect results (or possibly refuse to
generate any result). Any table lookup methodology should also need to be sensitive
to package size (because large packages have surcharges).
If BL is using the API calls, then the package dimensions would be a requirement
(just like they are on Pirate Ship). I hope someone from BL can enlighten us
about how this was implemented.
Nita Rae
|
|
|
| | | | | | | | | |
| | | | | | | Author: | dcarmine | | Posted: | May 20, 2024 18:42 | | Subject: | Re: US sellers: Shipping methods update | | Viewed: | 36 times | | Topic: | Administrative | |
|
| Nita,
A buddy tested for me and it is working fine. I guess it was a slow period after
all.
Thanks
Donna
In Administrative, cosmicray writes:
| | In Administrative, dcarmine writes:
| | I changed to the new API last Wednesday and all orders stopped. I don't
think it's working yet? No way for me to tell exactly, I changed mine back
to a my manual chart. Maybe you can test it on your side.
Thanks
Donna
|
An observation, is that orders (without any shipping method changes) went into
a very slow patch for a several days. Do you have a test account ? Might be worth
putting a few things into a shopping cart and see if they calculate correctly,
and based upon the correct zone.
What is not clear (from the announcement) is ... how is BL arriving at the zone
(and the correct postage). The old API method pre-dated when USPS switched to
zone based PM and FCPS. With the new system, you can do it via a API call to
USPS or by loading your own tables and doing a 2-step table lookup (one lookup
for the ZIP-code to zone calculation and one lookup for the actual postage values).
More recently USPS has applied a need for package dimensions, because larger
packages get surcharges. Presumably the API calls also have to supply package
dimensions, else then will generate incorrect results (or possibly refuse to
generate any result). Any table lookup methodology should also need to be sensitive
to package size (because large packages have surcharges).
If BL is using the API calls, then the package dimensions would be a requirement
(just like they are on Pirate Ship). I hope someone from BL can enlighten us
about how this was implemented.
Nita Rae
|
|
|
|
|
|
|
|
USA, Nebraska
