E-Commerce Localization

Our Web Scraper API offers localization options to retrieve e-commerce data customized to specific delivery and store locations. This page explains how to use the geo_location and store_id and other parameters to align results with local availability and preferences.

Parameter	Description
geo_location	Specify a location to customize results based on the desired delivery area.
context: store_id	Specify a store ID to receive data specific to that store. (Exception: Context parameter is not required for Kroger. See example.)

Website-Specific Localization Support

Domain	Geo Location / Delivery	Store ID	Fulfillment type
Amazon	ZIP code or 2-letter country code	-	-
Walmart	ZIP code or country	Supported	-
The Home Depot	ZIP code or country	Supported	-
Kroger	ZIP code	Supported	Supported

Amazon

Using the geo_location parameter customizes Amazon results based on delivery preferences, as shown in the screenshots below:

For most Amazon domains, you can set geo_location with either a zip/postal code or a 2-letter country code. Except for a few cases, this approach covers two main localization scenarios:

• Use a zip/postal code for locations within the marketplace’s country. Example pairs:

  • { "domain": "com", "geo_location": "90210" }

  • { "domain": "co.uk", "geo_location": "W105LT" }

• Use a 2-letter country code for locations outside the marketplace’s country. Example pairs:

  • { "domain": "com", "geo_location": "LT" }

  • { "domain": "de", "geo_location": "US" }

Exceptions

• Unsupported domains: cn, com.tr, com.be, and nl do not support custom delivery locations.

• Special Cases:

  • Australia (com.au): Only accepts Australian postcodes.

  • UAE (.ae): Accepts UAE city names as geo_location, e.g., "geo_location": "Abu Dhabi", or 2-letter country codes.

You can also use domain and locale parameters when scraping Amazon. Learn more here.

Walmart

Use the geo_location parameter to specify Walmart delivery locations based on zip code.

You can also add store_id in the context parameter for store-specific data. Find the list of Walmart Store IDs here.

...
"geo_location": "60805",
"context": [
    {
        "key": "store_id",
        "value": "5485"
    }
]
...  

The Home Depot

Use the geo_location parameter to set the delivery location by zip code or country.

You can also add store_id in the context parameter for store-specific data. The Store ID must be a 4-digit number. For example, if the Store ID is a 3-digit number, prefix it with one zero (e.g., 618 -> 0618). Find the list of Home Depot Store IDs here.

...
"geo_location": "29576",
"context": [
    {
        "key": "store_id",
        "value": "2214"
    }
]
...  

Kroger

Parameter	Description	Default Value	Dependencies
store_id	Specify a store. See the available values here. The ID must start with '0'.	-	Required when fulfillment_type is set to pickup or in_store.
delivery_zip	Specify delivery location ZIP code.	-	Required when fulfillment_type is set to delivery or ship.
fulfillment_type	Specify order fulfillment method. Available values: ship, pickup, delivery, in_store.	pickup (if only store_id is provided)	Requires store_id for pickup and in_store, or delivery_zip for delivery and ship.

Dependecies explained:

• pickup and in_store values use the store_id parameter to determine the correct store.

• delivery and ship use the delivery_zip parameter to specify the delivery location.

• If only store_id is provided, and fulfillment_type is not specified, the default type is pickup.

If the fulfillment_type and store_id/delivery_zip combination is invalid (unsupported by Kroger), the scraped page will return with a 404 status.

Please note that the contextual parameter is not required to set the store ID with Kroger sources, unlike with other sources.