The website says "check your local store." The local store pages don't say anything useful.

The situation

Six stores, six sets of rules, one website that ignores all of them

The chain runs six locations: two downtown, one in a suburban mall, two strip-mall anchors, and one outlet store. Each has different hours — the mall location follows mall hours and is open Sundays, the outlet closes at 6 PM on weekdays, the downtown flagship is open until 9 PM Thursday through Saturday. The website lists "Mon-Sat 10-7, Sun Closed" on a single "Our Stores" page and leaves it at that.

Return policies vary by location too, but nobody wrote it down. The mall store accepts returns on online orders because its lease requires a customer-service desk. The outlet store does not accept returns at all — everything is final sale. The other four accept returns within 30 days with a receipt, but two of them won't process exchanges on clearance items. The website's return policy page is a single paragraph that says "returns accepted within 30 days" with no mention of location exceptions, online-to-store rules, or final-sale categories.

Stock visibility is the third gap. Customers search online, see "available in store," and drive twenty minutes to find the item is only stocked at two of the six locations. The website has no per-store inventory indicator — just a global "in stock" badge that reflects warehouse availability. When Google's shopping assistant or an AI chatbot tries to answer "does the Elm Street store have this in stock?" there is nothing on the site to source an answer from.

The work

What Taz actually does with this location data

Taz audits every store page, policy page, FAQ, and location mention across the site. The audit covers what is published, what is missing, and what contradicts reality.

• Per-location hours audit: Every store's actual hours are documented — regular hours, holiday exceptions, seasonal changes, early-close days. Each location gets a structured hours record with machine-readable opening/closing times and exception dates. "Mall hours" becomes "Mon-Sat 10 AM-9 PM, Sun 11 AM-6 PM, closed Thanksgiving and Christmas Day."
• Location-specific policy mapping: Return, exchange, and warranty policies are mapped per store. Each location gets its own policy record that answers the actual questions: "Can I return an online order at this store?", "Is clearance final sale here?", "Do I need the original receipt or will an email confirmation work?" Contradictions between the website and store-level reality are flagged.
• Stock visibility assessment: Taz documents which product categories are stocked at which locations, the current state of any inventory feed, and what information the site could realistically display. If the POS system can export per-store stock counts, the audit notes the feed format and what would need to change to surface it.
• Store page rewrite: Each location page is rewritten with structured data — hours, address, phone, services offered (gift wrapping, alterations, curbside pickup), parking notes, and return-policy summary. Written to be parsed by AI agents and rendered by Google Business Profile.
• Agent answer pack: A structured JSON file with every location fact, policy answer, and hours record — sourced only from verified data. This is what an AI assistant would use to answer "is the outlet store open Sunday?" without guessing.

The deliverable

What the chain receives

• Location data audit spreadsheet — Every store in one sheet: current published hours vs. actual hours, services offered, policy exceptions, stock category coverage, and a gap-severity ranking by customer impact.
• Rewritten store pages — Six location pages with structured hours, policy summaries, service lists, and LocalBusiness schema markup. Ready to drop into the CMS.
• Unified policy document with location branches — One returns/exchange policy rewritten with clear conditional logic: "If you purchased online AND are returning at the Mall location, then..." Each branch traces to a verified source.
• Implementation ticket list — Prioritized CMS changes with exact copy, schema markup snippets, and Google Business Profile update notes. The chain's web team can work through the list without interpretation.
• Agent answer pack (JSON) — Machine-readable location records, policy answers, and hours data. Every answer traces back to a source document or confirmed store manager input.