A specialty Director Store Ops running fill rate on Looker
A specialty Director Store Ops on Looker should not be hunting for fill rate problems. Ward brings up them every morning.
The full picture: specialty fill rate, Looker data, Store Operations decisions
Managing 800 stores from a spreadsheet is insane. Ward filters to what a Director Store Ops can act on and drops the rest.
Fill Rate Monitoring, in one sentence. Ward monitors on-shelf availability across your entire estate and flags stores or categories dropping below threshold.
In a Specialty Retail fleet the job is 5,000+ SKUs over boutiques. High-consideration purchases, curated assortments, and customer lifetime value. Ward tracks the metrics that matter for margin-rich retail.
Under the hood. Ward tracks expected vs actual on-shelf availability at the store-category level and escalates when fill rate drops below configurable thresholds.
Setup: Ward can query Looker via API or connect directly to the underlying database. Either way, Ward monitors while your team browses.
Capabilities
- Estate-wide fill rate dashboard
- Threshold-based alerting
- Store-vs-estate benchmarking
- Category-level drill-down
Chat
Ask anything. Ward routes to the right agent and returns cited answers.
I pulled traffic against conversion by hour for the four flagships. Traffic is fine. The gap is coverage and depth.
| Signal | Finding |
|---|---|
traffic_conversion | Conversion 18.4% vs. 23.1% chain, all of the gap in 12–2p and 5–7p |
labor.coverage | One associate on the floor through both peaks at 3 of 4 doors |
inventory.depth | Top 20 styles at 1.4 units per size, walk-away rate +9% |
Recommend: add floor coverage to both peak windows, deepen the top 20 styles to three per size at the flagships, and route the walk-away list to clienteling.
traffic_conversion…
Reporting
Pinned views built from saved data-lake queries. Every number re-derivable from its SQL.
| Model | Horizon | MAPE |
|---|---|---|
holt_winters | 4wk | 4.1% |
arima_sarimax | 13wk | 8.9% |
gbm_demand | 1wk | 2.1% |
bayes_hier | new store | 11.4% |
Sources
Connect external systems to the data lake.
| Name | Type | Last sync |
|---|---|---|
shopify_orders_daily | import | 2m ago |
lightspeed_store_sales | import | 2m ago |
netsuite_inventory_snapshot | import | 14m ago |
retail_customer_ltv | import | 1h ago |
retail_traffic_conversion | import | 1h ago |
retail_clienteling_log | import | 1h ago |
retail_ga4_website_daily | import | 1h ago |
Policies
Browse and manage Cedar access policies for your tenant.
| Policy ID | Effect | Resources |
|---|---|---|
ops-read-default | permit | Model::* |
crm-read-ltv | permit | Model::"customer_ltv" |
associate-pii-blocked | forbid | Model::"customer_pii" |
merch-read-assortment | permit | Model::"sales_by_tier" |
Why Fill Rate matters for Specialty retail
A 95% fill rate missing the store's signature item is worse than 85% missing only commodity basics. Ward weights fill rate by item importance, signature products, top sellers, and loyalty drivers get priority, preventing the trap where healthy aggregates mask identity-defining stockouts.
What Ward has eyes on.
Ward reads straight from Looker rather than replacing it. Looker API for query results, underlying database (direct), lookML model metadata come across on a read-only connection, get enriched with contextual data, and come back as insight cards. Your BI is untouched.
Every empty shelf is a lost sale. Ward runs the model continuously rather than on a reporting cycle, which is why a finding lands the morning the pattern starts instead of at the end of the period.
Every one of your boutiques gets its own baseline. Ward tracks CLV, conversion rate, units per transaction against it and surfaces only the deviations that hold up. The two that show up most in specialty retail are assortment curation and customer lifetime value, and both are baseline problems before they are P&L problems.
At the metric level. Ward uses weighted availability scoring (signature items weighted highest, commodity basics lowest), tracks time-of-day availability for high-demand items, and measures the halo effect of signature product availability on overall basket value.
Why this combination
is its own problem.
A generic fill rate model applied to a specialty footprint produces alerts nobody trusts. The thresholds are wrong, because specialty baselines are wrong for it. Ward learns the baseline from your own boutiques instead of importing one.
- 01 Time-of-day availability isn't modeled in standard fill rate dashboards; an item available at 10 AM and gone by 2 PM looks "in stock" on daily snapshots.
- 02 Unweighted fill rate averages mask signature-item gaps; a chain at 95% can routinely run out of the brand-defining product because it represents only 1-3% of SKUs by count.
Benchmarks. Specialty signature-item availability target: 95-98%. Halo effect: signature-item-driven baskets typically run 1.5-2.5x larger than non-anchor baskets, so each signature stockout costs 2-3x its standalone revenue impact.
What the first 90 days
actually look like.
-
01
Week 1: connect
Read-only credentials to Looker / Looker Studio. Ward pulls from looker API for query results, underlying database (direct), lookML model metadata and starts building baselines. First daily cards land inside 48 hours, before baselines are stable, so you can see the shape of the output early.
-
02
Weeks 2 to 3: baselines
Ward needs roughly two weeks of history per store to separate a real deviation from normal variance. During this window the insight cards are directionally right and the thresholds are still moving.
-
03
Weeks 4 to 12: operating rhythm
Findings arrive every morning and get triaged like any other queue. Most teams find the volume settles into something one person clears in ten minutes. What matters is the action rate, not the alert count.
How Ward connects to Looker / Looker Studio
Ward does not replace Looker. Ward watches the same data Looker visualizes and proactively alerts when something changes. Your dashboards stay. Ward adds intelligence.
Setup: Ward can query Looker via API or connect directly to the underlying database. Either way, Ward monitors while your team browses.
Data Ward reads from Looker
Impact metrics with Looker
Data lake enrichment
Ward enriches Looker data with: Looker query results, Underlying database, Weather & events, Competitor data, Customer segments
Managing 800 stores from a spreadsheet is insane.
- ×Morning check-ins rely on phone calls and email chains
- ×No single view of which stores need attention today
- ×Labor scheduling is disconnected from demand signals
- ×Planogram compliance is checked manually, quarterly
- ×Exception management is reactive and inconsistent
- ✓Morning brief delivered at 06:47 with prioritized action list
- ✓Estate-wide heat map of store performance, updated hourly
- ✓Staffing recommendations correlated with predicted traffic
- ✓Planogram compliance anomalies detected and flagged
- ✓Consistent exception handling with recommended actions
Poor labor allocation and inconsistent execution cost multi-store retailers 3–5% in lost sales. Source: RSR Research
Specialty KPI impact
Frequently asked questions
Ward monitors on-shelf availability across your entire estate and flags stores or categories dropping below threshold. For Specialty retail specifically, Ward monitors 5,000+ SKUs across your boutiques and delivers automated insight cards with root cause analysis and recommended actions.
Ward tracks CLV, Conversion rate, Units per transaction, Repeat purchase rate, Sell-through by tier at the store-category level. Ward tracks expected vs actual on-shelf availability at the store-category level and escalates when fill rate drops below configurable thresholds.
Ward can query Looker via API or connect directly to the underlying database. Either way, Ward monitors while your team browses. Data points include: Looker API for query results, Underlying database (direct), LookML model metadata.
Yes. Ward reads Looker data and combines it with contextual signals (weather, events, demographics) to generate Specialty-specific insight cards. No custom development required.
Managing 800 stores from a spreadsheet is insane. Ward solves this with automated insight cards: Morning brief delivered at 06:47 with prioritized action list. Estate-wide heat map of store performance, updated hourly. Staffing recommendations correlated with predicted traffic.
Ward delivers daily insight cards covering CLV, Conversion rate, Units per transaction, tailored for Store Operations decision-making. Each card includes what changed, why it matters, and what to do next.
Ward uses weighted availability scoring (signature items weighted highest, commodity basics lowest), tracks time-of-day availability for high-demand items, and measures the halo effect of signature product availability on overall basket value.
Overall availability looks acceptable, but Ward's weighted metric shows a much lower score. The house-made sourdough, the product customers reference in reviews and social posts, sells out by early afternoon at several locations with higher foot traffic than the production schedule anticipates. Ward recommends adding an afternoon bake at affected stores. Signature product availability recovers, and afternoon revenue climbs as customers who came for the sourdough fill broader baskets.
First insight cards arrive within 48 hours of data connection. Ward needs approximately 2 weeks to establish stable baselines for your specific operation.
No. Ward sits on top of your existing stack. It is the proactive intelligence layer that watches your data continuously and delivers insight cards, so your team acts on findings instead of hunting for them.
Related solutions
See what Specialty fill rate problems Ward catches.
Root causes, not just alerts. See it on your data.
Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly
Find out what your data has been hiding.
Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.