A store directory: keeping head office and the field on the same page

Chain businesses have one data set everyone needs and nobody owns: the store list. How many stores are there, in which region, who works there, what's the phone number? That information usually lives in three separate places — HR's spreadsheet, operations' list and marketing's map — and none of them agree.

Why a separate directory?

A store doesn't behave like a department. It has its own address, opening hours, format (high street, shopping centre, outlet), region and manager. Squeezed into the org chart, most of that is lost.

A separate directory solves three things at once: one correct list, the foundation for content targeting and the address book for field operations.

The store as a targeting foundation

The directory's real value isn't in being a list but in other modules being able to build on it. An announcement can go to "stores in the western region", a field task to "shopping-centre format stores", a shift plan to a single branch.

When those relationships aren't set up, every module starts keeping its own list and six months later none of them is current. We cover the general logic of targeting in our announcements article.

Which fields should be kept?

Few, and genuinely used. The set that works in practice: store code, name, address, city, region, format, phone, opening date and the responsible manager.

Adding operational metrics such as monthly revenue is tempting but creates two problems. That data already exists in another system and will conflict when kept in two places; and revenue information shouldn't sit in a directory open to everyone.

Bulk import

Entering a hundred stores by hand isn't realistic. Bulk import via Excel or CSV is a precondition for this module being usable at all.

Two details decide the import experience: the store code as a unique key (so re-uploading the same file doesn't create duplicates) and reporting bad rows rather than rejecting the whole operation. A 500-row file refused entirely because of an error on row three is the most frustrating setup experience there is.

Who will keep it updated?

A store directory goes stale faster than an employee directory: openings, closures, relocations and manager changes happen continuously.

The sustainable answer is giving update rights to regional managers. The head-office team shouldn't be expected to track the whole chain; the person who knows their own store best should maintain it. We detail the ownership principle in our operations article.

Maps and visual presentation

A clickable map looks good but its real value is limited; most employees find stores by searching, not by map. There are two situations where a map genuinely helps: showing newly opened stores and presenting regional distribution to leadership.

Spending the energy on filters rather than the map gives better results: region, format and city filters cover most daily use.

The store page

Each store's own page acts as a small homepage for the people who work there: the team list, contact details, tasks assigned to that store and the shift plan.

It also has an outward benefit: an employee calling from another branch knows who to speak to. In chains, "who works at which branch" is asked more often than the head-office equivalent.

Franchise and dealer structures

In companies that run franchises alongside their own stores, a permissions question arises: which content should franchise staff see?

The practical approach is to mark franchises as a separate group and target content accordingly. Internal cost information and personnel processes stay closed while operational instructions and training can be opened. That distinction must be defined in the data layer; a forgotten targeting rule carries internal information outside.

Measurement

• Data currency — the number of store records untouched in the last 90 days.
• Page usage — which store pages get viewed, which are never opened?
• Targeting usage — the share of announcements and tasks sent by region or format.

The last shows whether the directory is actually working: if everything is still sent "to the whole company", the directory hasn't moved beyond being a list. We cover sending work to the field in our field tasks article.