Local Delivery: Postal Code Validation
Configure postal code validation to ensure you only accept delivery orders from supported areas. Choose between Exact match, Partial (wildcard) match, or Advanced pattern match.
Table of Contents
- How Postal Code Validation Works
- Step 1: Set the Global Matching Mode
- Step 2: Add Codes to Locations
- Matching Modes Guide
- Testing Your Configuration
How Postal Code Validation Works
Postal code validation is a two-part configuration:
- Global Matching Mode: You select one validation logic (e.g., "Exact" vs "Partial") that applies to your entire store in the Validation settings.
- Location-Specific Lists: You enter the specific list of accepted postal codes for each individual location.
When a customer enters their address, the widget compares their input against the list for their selected location, using the logic defined by your Global Matching Mode.
Step 1: Set the Global Matching Mode
First, define how the system should interpret postal codes for your store.
- Go to Bird Settings > Delivery.
- In the Delivery Validation Settings section, select your Distance Validation Mode:
- Exact postal code match: Strict 1-to-1 matching. (Best for US Zip Codes).
- Partial postal code match: Allows wildcards. (Best for UK, Canada, regional clusters).
- Advanced postal code match: Uses Advanced Expressions. (For complex pattern matching).
- Click Save.

Step 2: Add Codes to Locations
Now that the mode is set, add the actual postal codes to your locations.
Default Mode: Configure Locations
For most users configuring specific settings per location.
- Go to Bird Settings > Configure Locations.
- Click on the location you want to set up.
- Click Edit Settings (located beside the "Local Delivery is Enabled" text).
- Scroll down to the Local Delivery Pincodes section.
- In the Zip / Postal codes field, enter your allowed codes separated by commas.
- The format depends on your chosen mode (see Matching Modes Guide below).
- Click Save.

Legacy Mode: Same Schedule
Only for users on the legacy "Same schedule for all locations" plan.
- Go to Bird Settings > Delivery.
- In the Delivery Validation Settings section, find Postal codes field.
- Enter your codes separated by commas.
- Click Save.

Matching Modes Guide
Exact Match
Best for: Specific lists of zip codes where precision is key (e.g., US 5-digit zips).
- How it works: The customer's input must match one of your entries character-for-character.
- Example List:
90210, 90001, 90002 - Behavior:
- Input
90210-> ✅ Match - Input
90210-1234-> ❌ Fail (because-1234is not in your list)
- Input
- Tip: If your customers often use the full ZIP+4 format, consider using Partial Match or adding the specific ZIP+4 codes to your list.
Partial Match (Wildcards)
Best for: Defining broader regions, districts, or handling variable formats (e.g., UK, Canada, Netherlands).
- How it works: Use the asterisk
*as a wildcard to represent "any sequence of characters". - Example List:
SW1*, M1*, M2* - Behavior:
- Entry
sw1*matches:SW1,SW1A,SW1 2AA,SW19.
- Entry
- Strategy: This prevents you from having to list every single full postal code in a district. Instead of listing
M1 1AA,M1 1AB,M1 1AC, you can simply listM1*.
Advanced Match (Patterns)
Best for: Complex scenarios where simple wildcards are too broad (e.g., distinguishing "M1" from "M12").
- How it works: Interprets entries as Advanced Expressions, supports
*for wildcard and_for space. - Example List:
M1_A*, M2* - Behavior:
-
M1_A*would allowM1 A234,M1 A2345,M1 A23456, etc. -
M1_A*would not allowM12 A234,M1 B234,M1A234, etc. -
M2would behave the same as partial matchM2*.
-
Testing Your Configuration
Always verify your setup before going live.
- Go to Bird Settings > Widget Design.
- Use the Widget Preview on the right side.
- Select Delivery mode.
- Enter a postal code that is in your list.
- Expected: You should see the date picker.
- Enter a postal code that is NOT in your list.
- Expected: You should see an error message

Related Articles
Updated on: 01/18/2026
Thank you!
