Good morning!
I have two shipping policies, both containing the same ZIP code, but one of them is set up as a pickup point.
The problem is that some ZIP codes work under the shipping policy for delivery, but don’t work for pickup, a
and it’s not just ZIP code 85900-001 that isn’t working — there are a few others within the range as well.
This is my shipping policy range:
As an example, ZIP code 85900-010 works and is recognized by the policy, whereas 85900-011 is not recognized.
What should I do in this case?
Good morning, Carlos!
I believe some adjustment is needed in the spacing of the pickup points on this page:
Karina Mota
Field Software Engineer | VTEX
So Karina, the change has already been made and the error persists. I’m coming to the conclusion that the ZIP codes that don’t show up are general ZIP codes, which is why the shipping policies like pickup don’t appear for them.
I ran the test and checked the pickup point option within the shipping policy, and it shows up correctly.
Is there any chance that a general ZIP code doesn’t work with the shipping policy as a pickup option? Because in the image below, when I run the simulation with the ZIP code that doesn’t work, it doesn’t return the address.
Hi Carlos!
I checked here and ZIP code 859000-01 does not exist according to Correios. If you’d like to verify: https://buscacepinter.correios.com.br/app/endereco/index.php
Since the ZIP code cannot be found in the database, we don’t have the coordinates to look up the eligible pickup point.
You might be wondering why pickup doesn’t work, but home delivery does, even with a non-existent ZIP code.
This happens because nearby pickup points are searched by the VTEX platform based on the geographic coordinates of the ZIP code, while home delivery is based on a ZIP code spreadsheet.
Unfortunately, it is not possible to create this ZIP code in the database to reflect on your site for the pickup point, as our policy is to only include ZIP codes that exist in the official Correios database.
Got it, thank you very much!