Specialty fill rate from Looker, briefed to merchandising
Every empty shelf is a lost sale. Ward runs it on Looker data over your specialty store base, scoped to merchandising.
How a specialty VP Merchandising runs fill rate on Looker / Looker Studio
Applied to Specialty Retail, the surface area is 5,000+ SKUs across boutiques. High-consideration purchases, curated assortments, and customer lifetime value. Ward tracks the metrics that matter for margin-rich retail.
Your category managers are drowning in spreadsheets. Ward surfaces the indicators that change a merchandising decision.
Here is fill rate monitoring in plain terms. Ward monitors on-shelf availability across your entire estate and flags stores or categories dropping below threshold.
How Ward sends Fill Rate cards: Ward tracks expected vs actual on-shelf availability at the store-category level and escalates when fill rate drops below configurable thresholds.
The connection itself. Ward can query Looker via API or connect directly to the underlying database. Either way, Ward monitors while your team browses.
What you get
- Store-vs-estate benchmarking
- Category-level drill-down
- Estate-wide fill rate dashboard
- Threshold-based alerting
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.
The fill rate model runs each day, not on a reporting calendar. It detects the pattern, explains root cause, and attaches a recommended move before the number reaches a review deck.
Every one of your boutiques gets its own baseline. Ward watches CLV, conversion rate, units per transaction against it and pulls forward 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.
The connection to Looker / Looker Studio is read-only and runs on your schedule. Ward reads straight from looker API for query results, underlying database (direct), and the rest of the feed, then combines it with external context your BI does not carry: weather, local events, competitor pricing.
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.
Fill Rate Monitoring behaves differently in specialty retail than it does anywhere else. The store base shape, the SKU count, and the speed of the category all change what counts as a real signal and what is noise. Ward is tuned to the specialty version.
- 01 Halo basket effects from signature items aren't measured, so the cost of a signature stockout is undercounted by 2-4x because the missed basket-pull revenue is invisible.
- 02 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.
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 reads straight from looker API for query results, underlying database (direct), lookML model metadata and starts building baselines. First insight 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: steady state
Ward returns daily cards each day, each with the cause and a recommended action. Volume settles at a level a single person can read over coffee. The measure of success is not how many findings arrive, it is how many get acted on.
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
Your category managers are drowning in spreadsheets.
- ×Promo planning still runs off last year's playbook
- ×Assortment reviews happen quarterly when they should happen daily
- ×Price changes chase the market a week behind it
- ×No visibility into true cannibalization across categories
- ×Vendor negotiations lack real-time sell-through evidence
- ✓Insight cards flag promo cannibalization the day it happens
- ✓Assortment gaps and whitespace opportunities surface automatically
- ✓Price elasticity shifts detected before margin erosion compounds
- ✓Category-level performance cards replace manual spreadsheet reviews
- ✓Vendor scorecards generated from actual fill rate and quality data
Retailers lose an estimated $300B+ annually to suboptimal assortment and promotional decisions. Source: McKinsey & Company
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.
Your category managers are drowning in spreadsheets. Ward solves this with automated insight cards: Insight cards flag promo cannibalization the day it happens. Assortment gaps and whitespace opportunities surface automatically. Price elasticity shifts detected before margin erosion compounds.
Ward delivers daily insight cards covering CLV, Conversion rate, Units per transaction, tailored for Merchandising 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.