No reviews found
The shopper city in the store header, not only in the checkout
CS-Cart learns the shopper city at the checkout, but until then the shopper neither sees it nor can change it: there is no city in the store header, and the platform neither detects nor remembers it. This add-on puts the city selector into the header, detects the city in the visitor browser, asks for confirmation and keeps the answer, while the city itself is written into the standard location - the one shipping, zones and the checkout read.
Detected in the browser DaData by location or IP, or "Maps and geolocation"
|
A list per storefront its own cities, its own source, its own settings
|
Keeps the choice 30 days by default, the period is a setting
|
CS-Cart 4.17.1+ all editions, tested on 4.21.1 Ultimate and Multi-Vendor
|
Why a store needs it
A shopper arrives from search and looks for one answer first: "do you work in my city?". In CS-Cart that answer waits until the checkout - the city is asked for in the delivery address, and before that the shopper sees a storefront that looks the same for the whole country.
The add-on closes that gap. The city stands in the header, is detected on its own and is changed in a single click, while the store gets it in the standard location that shipping and zones are calculated from. The shopper no longer has to reach the cart to find out whether their city is served.
The city is visible at once
The city line stands in the store header next to the language and the currency, where shoppers look for it. |
Detected automatically
The city is found in the visitor browser: by location when it is allowed, by the IP address otherwise. |
Confirmed in one click
The "Your city is Kazan?" bar is shown once: the shopper agrees or picks another city. |
One city for the whole store
The choice goes into the standard location, so shipping, zones and the checkout see the same city as the header. |

How it looks to the shopper
- • Step 1. The shopper opens the storefront - the add-on detects the city and shows it in the header.
- • Step 2. A bar appears under the city: "Yes, that is right" or "Choose another". Once answered, it does not come back.
- • Step 3. The selection window holds popular cities as tiles, the list of cities of presence and a search over the directory: a city outside the list can be picked as well.
- • Step 4. The choice is remembered: on the next visit the shopper sees their city straight away, and the store sees their location.


How the city is detected
- • DaData. For Russian addresses. The add-on asks the browser for the location and finds the city by coordinates; if the visitor refuses or does not answer within 10 seconds, it uses the IP address of the browser. A DaData API key is needed: your own or the one from the Cart-Power "DaData" add-on.
- • Yandex or Google. Detection goes through the stock "Maps and geolocation" add-on and its map service key - the same way the stock location block works.
- • Do not detect. The visitor always picks the city: the add-on shows the default city and the selection window.
- • The detection status is visible right in the settings: the add-on checks the key and says whether the chosen source works on this storefront.

Cities of presence in the administration panel
- • A section of its own. "Settings - Cities of presence": the list of the storefront cities with the region, the "Popular" mark, the position and the status.
- • Cities come from the directory. The add-on keeps no catalogue of its own: names, regions and postal codes live in the stock Cities directory.
- • Search instead of a list of 22 thousand rows. Cities are added by searching the directory, several at a time; larger cities come first.
- • Popular cities are shown as tiles in the selection window - usually the four to eight cities most orders come from.
- • Access rights. The section has its own "Can view" and "Can manage" privileges that can be granted to a separate group of administrators.


What can be set up
- • A city outside the list. "Allow" - the list works as a quick choice: the detected city is shown as it is and the search covers the whole directory. "Restrict" - only the cities of the list: a visitor from elsewhere is offered the default city.
- • The default city. It is set when nothing is known about the visitor and offered with the "Your city is ...?" question.
- • The confirmation bar. It can be turned off: then the city is simply shown in the header.
- • How long the choice is kept. The number of days the shopper choice is remembered, 30 by default.
- • Search in the window. It can be turned on and off, and the number of suggestions is a setting.
- • The region under the name. It is shown on the second line so that cities with the same name are not mixed up.

Storefronts, editions and updates
- • Every storefront keeps its own list. The cities, the detection source and all the settings belong to the storefront - both in Ultimate and in Multi-Vendor. The storefront is chosen with the stock switcher in the panel.
- • A block in any grid. The city selector is an ordinary block: it is placed into the top panel or into the header of the layout, like other store blocks.
- • Standard location storage. The city is written by the functions of the "Maps and geolocation" add-on, so shipping, zones and the checkout see it.
- • Updates go through the CS-Cart upgrade centre and the "Cart-Power: Add-ons manager" add-on.

What is new in version 1.0
- • City selection in the storefront header: the current city, a selection window with popular cities, the list of presence and a directory search.
- • City detection in the visitor browser - "Maps and geolocation" (Yandex or Google) or DaData by location and by IP.
- • The "Your city is ...?" confirmation bar answered in one click.
- • The "Cities of presence" section with a directory search, popular cities, order and statuses.
- • A separate list of cities and separate settings for every storefront - in Ultimate and in Multi-Vendor.
- • A setting for a city outside the list: a quick choice or the cities of the list only.
- • The choice is remembered for a given period and written into the standard customer location.
Frequently asked questions
Is a key needed for the add-on to detect the city?
Yes, with either source. DaData needs an API key from the dadata.ru account (the key of the Cart-Power "DaData" add-on works too); "Yandex or Google" needs the map service key in the settings of the "Maps and geolocation" add-on. Without a key detection can be turned off - the shopper picks the city themselves.
What does the shopper see when the city could not be detected?
The default city from the settings and the "Your city is ...?" question. If there is no default city and the choice is restricted to the list, the selection window opens by itself.
Does the add-on work for a shopper from a city we do not serve?
Yes. With the "Allow" setting the city is shown as it is even when it is not in the list, and the list stays a quick choice. With "Restrict" the shopper is offered the default city.
Does the chosen city affect shipping and the checkout?
Yes. The city is written into the standard customer location, so shipping rates, zones and the address fields of the checkout see it.
Does the add-on keep a cities catalogue of its own?
No. It works with the stock Cities directory and only decides which cities belong to the storefront list, which of them are popular and in what order they are shown.
What happens to the shopper choice after the add-on is updated?
It stays: the choice lives in the browser cookie and in the standard location, and the storefront list of cities lives in the add-on table.
- Store Builder
- Store Builder Plus
- Store Builder Ultimate
- Multi-Vendor
- Multi-Vendor Plus
- Multi-Vendor Ultimate
- 4.21.1
- 4.20.1
- 4.19.1.SP2
- 4.19.1.SP1
- 4.19.1
- 4.18.4
- 4.18.3
- 4.18.2.SP1
- 4.18.2
- 4.18.1.SP1
- 4.18.1
- 4.17.2.SP3
- 4.17.2.SP2
- 4.17.2.SP1
- 4.17.2
- 4.17.1
- English
- Русский
|
CS-Cart development · in-house team · since 2013 We build, upgrade and speed up CS-Cart stores and marketplacesAnalysts, developers, designers, QA and support under one roof — no subcontractors. We ship add-ons you can buy on this page today, and we take on the work that no ready-made add-on covers. |
|
2013 Working with |
4.98 Rating from |
200+ Solutions on this |
500+ E-commerce projects |
Flagship products
Two add-ons that change how a store performs
Everything else we publish improves one screen. These two change the numbers: how customers find products, and how often they come back.
|
Add-on · Search & merchandising Smart SearchElasticsearch-powered search for large catalogues. The customer types two letters, sees products with images and prices, and buys from the dropdown — even after a typo or with the wrong keyboard layout. Visitors who use the search bar are 24% of traffic and 44% of revenue, and convert about 2.5× better than people who only browse categories. If search returns nothing, up to 80% of them leave. | ||||||||
| ||||||||
Try it on a live catalogue: open the demo store and search with a deliberate typo. |
|
Add-on · Mobile commerce PowerApp — mobile app for your storeA native iOS and Android app running on your CS-Cart data: the same products, prices, stock, promotions, reward points and orders. There is no second catalogue to maintain — everything stays in the admin panel you already use. A mobile site brings a customer in once; an app brings them back for free. Push notifications replace the retargeting budget you spend to buy the same customer a second time. | ||||||||
| ||||||||
Screens, block types and pricing tiers: see how the app is built. |
Services
When no add-on solves it, we do the work
Fixed scope, written specification, a named project manager and a warranty on what we ship.
|
Custom CS-Cart development Functionality the platform does not have: add-ons, marketplace mechanics, integrations with 1C, CRM, ERP, payment and delivery providers. We start from a written specification, not from an estimate on a phone call. Details → |
|
CS-Cart upgrade Move to the current version without losing data, custom code or add-ons. We audit every modification first, upgrade on a staging copy, adapt what breaks and switch over with little or no downtime. Details → |
|
Speed and performance optimisation Conversion falls by about 4.4% for every extra second of load time. We profile the server, the database and the front-end, then fix what actually costs the seconds — and show you the before-and-after numbers. Details → |
|
Design for CS-Cart Mobile-first storefront design built on CS-Cart's own template structure, so the layout survives the next platform upgrade instead of becoming a migration problem. Details → |
|
SEO for CS-Cart A technical audit of indexing, duplicates, redirects, structured data and Core Web Vitals — delivered as a prioritised fix list your developers can act on, or that we implement ourselves. Details → |
How we work
What you get besides the code
|
Before we start We discuss the goal, offer options and write the specification. You approve scope and price before development begins. |
While we build A named project manager reports progress on a fixed schedule. You always know what is in work and what is next. |
|
Before release A separate QA pass on every release — the developer who wrote the code is not the person who signs it off. |
After handover Documentation for everything we ship, plus a warranty on the modifications and the project. |
Tell us what the store needs to doDescribe the task in a couple of sentences and we will come back with options, a scope and a price. The consultation is free, and we will say plainly if a ready-made add-on already solves it.
|
Client cases, our full add-on catalogue and 184 customer reviews are in the tabs above.