12-step discovery worksheet for grocery chains and multi-store brands.
Brand: StoreTempo · storetempo.com
Answer what you know in everyday language. You do not need to be the IT person.
Basic facts about your brand, website name, and whether all stores share one StoreTempo system or each store stands alone.
Product terms: “shared system” = Chain Starter (one server/database). “Separate system per store” = Store Isolation. DutySeal is optional staff scheduling/checklists.
What brand name should shoppers see?
Preferred short web name for your store finder (letters/numbers, no spaces)
This becomes the public link shoppers use to find your stores, like /g/your-brand/.
/g/your-brand/
How many stores at launch? How many in about 12 months?
Should all stores share one system, or should each store have its own?
Share one system — easiest for comparing stores at head office. Separate per store — each door is more independent (weaker head-office compare).
A = Chain Starter (one VPS / shared database). B = Store Isolation (per-store accounts/databases). Pick “Not sure” if StoreTempo should recommend.
Which public website address(es) will shoppers use?
Email for the first brand-owner admin invite
Do you also need staff shift checklists / schedules / clock-in?
That’s DutySeal (workforce tools). StoreTempo is the shopper + store map product. Many chains use both together (Grocery Ops Bundle).
Who on your side handles website domain settings and server access?
Usually your IT person, agency, or “we need StoreTempo to guide us.” Name a contact if you have one.
DNS/TLS certificates and VPS login ownership — IT can fill this later.
Should this install be private to your brand only (not shared with other brands)?
Most chains say yes — your server is locked to your brand.
Product term: org_lock / single-brand VPS.
What would “success” look like after the first month?
Which doors launch first, who runs each store day to day, and whether new stores copy a template store.
List launch stores (name, address, phone, email)
For store #2 and beyond: start blank, or copy from a template store?
Copy from a template can reuse map layout, look-and-feel, and where products sit — but weekly flyers are not copied (you publish those per store).
How should each store’s web address look?
Path style: brand.com/stores/1042. Subdomain style: 1042.brand.com. Mix is fine if some doors differ.
Where do store hours come from, and who keeps them up to date?
Who runs the app day to day — head office, store managers, or both?
Email that should get “something needs attention” alerts for each store
At first: staff picking orders for shoppers, or shoppers walking their own list with a map?
Any remodel or new floor plan in the next 90 days?
Who owns store time zone and holiday hours?
How product names, prices, and aisle locations get into StoreTempo — usually from a spreadsheet or your cash register system.
At go-live, where will the product list come from?
Spreadsheet is fine to start. Longer term, most chains send products from the cash register (POS) system so prices and stock stay correct.
Does every sellable item have a stable barcode?
Do you already track aisle / side / shelf, or only names and prices today?
Pin popular items on the map, or just use aisle text for now?
Product photos plan, and about how many products at the first store?
Same product list for all stores, or each store sells different items?
Who may mark an item “out of stock” by hand vs trusting the register quantity?
Shoppers and pickers follow walking paths drawn on your floor plan. When you change the floor picture, you choose whether to keep those paths.
Do you have a usable floor-plan picture for each launch store?
Who will place the path points on the map — a store manager or a dedicated map editor?
When the floor plan picture changes, what should happen to the walking paths?
Keep paths — reuse the dots/lines you already set (usual default). Keep paths, stretch to new picture — same points, adjusted to the new image size. Start over — wipe paths and redraw after a big remodel.
Product terms: Copy route nodes / Replace image (IDs kept; coords scale) / Fresh. IT or StoreTempo can confirm the best default for your remodel.
Do stores share the same layout (copy map), or is each map unique?
Launch priority: shopper self-guided paths, staff pick paths, or both?
Confirm map landmarks: entrance, checkout, and pickup / service counter
These three spots make routes and staff-pick handoff work. Someone should verify them before go-live.
Any restricted areas, multi-floor needs, or remodel sign-off notes?
How product prices and stock get from your cash register (POS) into StoreTempo — and whether paid pick-up orders go back to the register.
Inbound = product list / qty into StoreTempo. Outbound = paid staff-pick sales to POS (file outbox or HTTPS webhook). IT usually owns the bridge.
What cash register system do you use (name / version)?
How will you send the product list into StoreTempo?
Think: drop a file on a schedule, secure file transfer, automatic push from the register, or upload by hand for now.
After a shopper pays for a staff-picked order, should that sale go back to the cash register?
Optional at launch. “Later” is fine if you only need maps and lists first.
A = file outbox. B = HTTPS webhook. C = not needed yet.
Who builds/owns the register link? How often should it update?
OK if the register’s regular price wins, and flyer sale prices sit on top?
Can your register export on-hand quantity / in-stock flags?
OK to start with a test feed, then native Square/Clover links later if needed?
Website vs phone app, which journeys matter first, and whether the store finder is open to everyone or invite-only.
At launch, shoppers use…
Which journeys matter most first? (browse → list → map path, flyer → list, and/or staff pick)
Who sends shopper texts/emails (order ready, etc.)?
Brand store finder on? Soft launch (invite-only) or open signup?
If stores use separate web addresses: IT has checked login/cookies across them?
Skip if you’re not sure — this is an IT check so shoppers stay signed in across store sites.
Cookie / CORS settings for store subdomains.
Be honest with shoppers: built-in today is earn points only after a paid order is picked up. Spending points or punch cards needs custom work.
Loyalty for launch
If earn-only: OK that points only add when a paid order is marked picked up (~1 pt per $)?
Do shoppers need to spend/redeem points at checkout? (not built — would be custom)
If custom: which loyalty system is the source of truth, and who owns the link?
Wait on loyalty until staff pick is live? Existing cards to migrate? (no import tool today)
How your weekly circular gets into StoreTempo, who publishes it, and whether every store shares the same flyer.
How do you create the weekly circular today?
Use StoreTempo’s weekly flyer tools? Cover image or PDF on the store home page?
Who publishes each week? Same flyer for all stores, or different per store?
Understood: copying a template store does not copy flyers — OK?
Will the first flyer be ready before public launch?
Whether shoppers walk their own list, staff pick for them, how they pay, and pickup timing. Delivery is not supported.
At launch, shoppers will…
For staff-picked orders, how do shoppers pay?
If card systems fail, Pay at store still queues the order for staff pick. Enterprise buyers often require both.
If the card processor is down, will you still accept Pay at store so pickups continue?
Card payments: one account for the whole chain, or per store? Currency / minimum charge OK?
Pickup timing message OK? Unpaid card orders must not enter the pick queue — agreed?
After pickup: send sale to register? Process for substitutes / not-found items?
Delivery? (not supported — contact info is for pickup only)
Who gets which login: brand owner, store manager, map editor, or floor staff — and how you remove access when someone leaves.
Who should have which role? (owner · manager · map editor · staff)
Who holds the main system admin access — StoreTempo/host, or your IT?
How many pickers per store at peak? Who handles “needs attention” tickets?
Who may Mark a product temporarily out of stock (manager override) when the register feed is wrong or late?
Mark OOS is a short override — it does not invent register quantities. It is audited. POS sync can still update price/qty when the feed returns (unless OOS is forced on).
If using DutySeal too: separate logins OK? Need single sign-on? (email + password today)
How do you remove access when a store manager leaves?
What head office and store managers want to see weekly — searches that failed, routes used, flyer engagement, pick sales, store-to-store compare.
Top numbers for head office (failed searches, routes, flyer, pick sales, store compare)
Who uses head-office reports vs the per-store dashboard?
Need to export data to Excel/BI soon? Advanced heatmaps can wait (roadmap) — OK?
If each store has its own system: OK that head-office store compare is weaker?
Only applies if you chose “each store has its own separate system” in step 1. Shared system = stronger compare.
Weekly business review cadence? Any alerts beyond the ops email?
Final checklist before shoppers go live. Managers can answer dates and “signed off”; IT can tick the technical boxes.
Target go-live date and which store soft-launches first
Setup steps applied as needed (register link, accounts/rewards, domains, DutySeal)
Usually StoreTempo or IT confirms. Managers can note “done / pending.”
Automatic product sync and sales-file jobs scheduled? (IT)
Card payments live + a test payment completed?
Map live with entrance, checkout, and pickup counter checked?
Walk-through signed off: search → shopping list → map path → optional staff pick?
Register product feed + (if used) sales back to register signed off?
First flyer published; brand owner + managers invited?
Website addresses and login across store sites verified? (IT)
Support contacts for shoppers vs staff for the first 30 days
StoreTempo chain onboarding checklist · Fill digitally or print · Source: deploy/docs/onboarding/ · Marketing: https://storetempo.com/onboarding