Find the gap
Scan a competitor and surface the one gap worth acting on.
Scenario
One signal across the full merchandising lifecycle
Competitors expanding
3
Your comparable SKUs
0
Signal confidence
82%
White space found
Open a chase concept for the sage merino zip knit and validate demand before the buy window closes.
Color
Sage
Muted green is rising inside training layers, not across the whole market.
Assortment
Gap
Competitors added breadth while your catalog has no near match.
Timing
Open
The opportunity is still pre-markdown and pre-peak search.
Pre-seeded sales scenario built to demonstrate the complete signal-to-decision flow.
Methodology: Sample data only. Run a competitor scan to replace it with verified public-catalog evidence.
Alpine Atelier keeps the same product signal across all seven pages so the demo feels like one operating system, not seven unrelated widgets.
Market Sense · Evidence before action
A crowded catalog is not the same as a growing market. Start with a specific question, inspect what the source supports and choose what deserves a closer look.
Illustrative evidence card
Example source · catalog A + B
DACH · Training layers ·
Catalog A
Crew layer
€59 · Sample offer
Catalog B
Zip layer
€79 · Sample offer
Observation → next question
Catalog B includes a zip layer and catalog A does not. Check variants and capture coverage, then test the concept.
Every value in this comparison is synthetic. Run the catalog scan above for current public evidence.
Scan a public catalogAgree category, market and comparable attributes. A price difference without product context can mislead.
Keep source, observation date and coverage together. Missing items or incomplete pages are a limitation, not proof of absence.
Take a supported observation into Design Studio. Validate the demand hypothesis before treating a visible assortment gap as a buy signal.
A storefront can support catalog, price and attribute observations when those fields are available. Search, social, sales and customer data each require their own source and access. The demo labels its sample and public-scan evidence separately.
Compare capture time, item identity and offer terms before treating a difference as a market change.
Fictional review example. No live monitoring or price action.
Choose an evidence caseUnknown is not zero.
Capture time records when this fictional capture was attempted. The source's publication or update time is not supplied.
Comparable stated terms
−€8.00
The later captured offer is €8.00 lower in this fictional pair. The source's publication or update time and the reason for the difference are not supplied.
E01 · E02
A public offer does not establish demand, a completed sale or a launch date.
Review the limits first.
Review owner: unassigned. No approval or external handoff has occurred.
No example note prepared.
Local example only; not saved or sent.
Bounded external observations categorized into commercial signal classes. Signals inform human merchandising reviews without executing automated pricing or inventory changes.
Monitored shift in competitor shelf pricing across equivalent variants
Abrupt removal or introduction of variant sizes or colorways on public shelves
Aggregate review and feedback topic sentiment divergence over rolling windows
Competitor seasonal sale initiation, badge attachment, or coupon cadence
Algorithmic anomaly detection isolates unexpected shifts in shelf dynamics, articulating what was observed alongside strict boundary disclaimers.
Observed competitor lowered displayed price from €80.00 to €72.00 (-10.0%) across size M/L variants. Inventory status remains unobserved; sale volume is not established.
Evidence Boundary: Observation does not establish promotional cause, margin concession, or competitor stock levels.
Human Review Gate: Merchandising review required before evaluating price match or campaign response.
Competitor listing removed size XL and XXL variants from navigation. Unknown whether discontinued or temporarily out of stock.
Evidence Boundary: A missing web listing does not establish factory discontinuation or permanent de-listing.
Human Review Gate: Verify own-stock depth in XL/XXL before adjusting category marketing spend.
Review sentiment index shifted from +0.62 to +0.28 over 30 days based on 42 public reviews mentioning shoulder seam tightness.
Evidence Boundary: Public review sentiment reflects voluntary self-reporting with inherent selection bias.
Alert threshold: The fall in the 30-day index that opened this alert. In a live setup the threshold is set per topic or learned from a baseline.
Human Review Gate: Product development review recommended to inspect tech pack measurements before design freeze.
Brand mention watch
Public mentions of the brand in news and social channels, counted by region and period. The example is fictional; no live feed is read.
| Region | Mentions in the observation window | Compared with the prior 14 days | Volume spike flag |
|---|---|---|---|
| North | 320 | 210 | Volume spike flag |
| South | 140 | 150 | No spike in this window |
| Source channel | Mentions in the observation window |
|---|---|
| news | 80 |
| social | 240 |
| forum | 12 · Too few mentions to read a sentiment |
| review | No data for this channel |
Mention counts show public talk, not sales, demand or market share. A flag is a prompt for review, not a finding.
Brand mention feed
Public mentions of the brand, one row each, with the source, the sentiment label and the time. The rows are fictional; no live feed is connected.
Fixture data; not refreshed live
Source: news · Sentiment: Positive · Observed:
@fictional_editor
Fictional coverage of the new knit range.
Source: social · Sentiment: Neutral · Observed:
@fictional_user_1
Fictional question about sizing.
Source: forum · Sentiment: Negative · Observed:
@fictional_user_2
Fictional complaint about a loose button.
Source: social · Sentiment: Positive · Observed:
@fictional_user_3
Fictional praise for the colour.
Source: Source not recorded · Sentiment: Neutral · Observed:
@fictional_user_4
Fictional mention without a recorded source.
Source: news · Sentiment: Negative · Observed:
@fictional_editor_2
Fictional note on delivery delays.
Read-only example: replies and other actions are not available on this page.
Verified scrape records tracking stated competitor shelf prices over time. Observations exclude private sales quantities and profit margins.
Comp-Jacket-01
Displayed web price reduced by €21.00. Free shipping threshold remains unchanged at €50.00.
Comp-Shirt-02
Promotional banner badge 'Mid-Season Special' attached. Price reduction limited to selected colorways.
Competitor media signal, fixture example
Illustrative records. No live monitoring and no bid or price action.
CM-1
fictional rain jacket
Advertising spend direction: Up
Capture date (example):
| Paid | Organic |
|---|---|
| 24% | 31% |
CM-2
fictional knit cardigan
Advertising spend direction: Flat
Capture date (example):
| Paid | Organic |
|---|---|
| Share of voice not supplied | 19% |
Ad creatives over time
Dated ad creatives from one competitor across channels, with format, placement and a labelled estimate of spend. The records are fictional and show the layout only.
Format: video
First and last seen: 2026-08-02 – 2026-08-20
Fictional spring capsule, new colourways
Shop the edit
Estimated spend and impressions
EUR 5k to 10k (estimate)
200k to 400k (estimate)
A model estimate, not a reported figure. Use it to compare ranges, not to set a budget.
Format: text
First and last seen: 2026-08-10 – 2026-09-01
Fictional knitwear sale line
View knitwear
Estimated spend and impressions
EUR 2k to 5k (estimate)
Not supplied
A model estimate, not a reported figure. Use it to compare ranges, not to set a budget.
Format: video
First and last seen: 2026-09-05 – 2026-09-18
Fictional outerwear story
Explore outerwear
Estimated spend and impressions
Not supplied
100k to 250k (estimate)
A model estimate, not a reported figure. Use it to compare ranges, not to set a budget.
Format: image
First and last seen: 2026-09-12 – 2026-09-19
Fictional tailoring reminder
See tailoring
Estimated spend and impressions
EUR 1k to 2k (estimate)
50k to 120k (estimate)
A model estimate, not a reported figure. Use it to compare ranges, not to set a budget.
A creative seen on a channel shows presence in that window, not reach, conversion or sales.
Topic-clustered sentiment indicators derived from public reviews. Indicators highlight potential design and sizing questions prior to range planning.
Alert flag: No flag: score at or above the threshold (Threshold 0.30)
True-to-size consensus across 82% of responses. Minimal return friction reported.
Sample represents verified purchase review submissions; excludes offline store buyers.
Alert flag: No flag: score at or above the threshold (Threshold 0.30)
Heavier fabric than anticipated for transitional spring wear noted in 18 comments.
Subjective sensory perception; does not represent physical fabric GSM variance.
Alert flag: No flag: score at or above the threshold (Threshold 0.30)
Colour matched the listing in most comments; photo lighting was named in a smaller group.
The sample covers verified purchases only; photos and in-store colour are not compared.
Alert flag: Flag set: score below the threshold (Threshold 0.30)
Window 2026-08-01 to 2026-08-14: +0.52
Two windows disagree; both values are shown and none is merged.
Delivery times were praised in most comments; a smaller group reported delays at weekend peaks.
Delivery reviews mix the carrier and the buyer's address; the sample does not separate them.
Brand Mentions by Channel
Illustrative mention records show how one brand's public mentions score across channels. Each row keeps its channel and observation time.
| Channel | Mention sentiment |
|---|---|
| Social posts · MN-1 | +0.42 · · Fictional post, public |
| Social posts · MN-2 | -0.35 · · Fictional post, public |
| Reviews · MN-3 | +0.60 · · Fictional verified review |
| News · MN-4 | +0.10 · · Fictional trade article |
A mention score describes wording. It does not show demand or sales.
Mention volume and spikes
Counts of public mentions for one brand over fixed windows, with the sentiment split and any spike flag. The figures are fictional and show the layout only.
Fictional example: one brand, one window, fixed records.
| Window | Mentions | Sentiment split |
|---|---|---|
| 7d | 412 | Positive 52% · Neutral 30% · Negative 18% |
| 30d | 1860 | Positive 49% · Neutral 30% · Negative 21% |
Spike flag: 7d
Flag when mentions rise above the rolling baseline by the set threshold.
Spike flag: 1.8 / 1.5 · Human review is needed before any reply or campaign step.
Spike flag: 30d
Flag when mentions rise above the rolling baseline by the set threshold.
No spike in this window.
Counts show public mentions, not sales or demand. A spike shows a change in attention, not its cause.
Sentiment by market and city
Public sentiment for one brand, split by country or city, with the number of mentions behind each row. The records are fictional.
Fictional example: four markets, one window, fixed records.
The table shows the rows for the chosen country.
| Market or city | Mentions | Average sentiment | Negative share | Source basis |
|---|---|---|---|---|
| Berlin | 240 | 0.31 | 22 % | Public reviews, inferred city |
| Hamburg | 180 | 0.27 | 26 % | Public posts, inferred city |
| Vienna | 22Fewer than 30 mentions: read with care. | 0.40 | 14 % | Public posts, inferred city |
| Not supplied | 95 | 0.18 | 31 % | Public reviews, no city inferred |
Geo labels are inferred from the source and can be wrong. A city with few mentions is not a trend.
Use Market Sense to frame a question for Design Studio. Review pricing constraints separately before any price decision.
No. A failed or partial capture cannot establish removal. Check the source and coverage before making that claim.
No. These fixed examples explain evidence review. They do not schedule scans, save decisions or change prices.
Fictional fixed example — no live answer collection
Read one fictional answer sample beside its dated source. A mention, a citation and a supported product statement are different kinds of evidence.
Explore the fixed example →Select a fixed sample and a review question. These controls change only this example; they do not query an answer engine.
Preparing the local example
Human review required
Brand mentioned; one fictional URL cited.
Check the prompt, language, market and collection time. An unknown engine version or unavailable response stays unknown.
A brand can appear without a cited product page. A cited URL does not by itself verify the product statement or identify the exact variant.
Read the supplied catalog field and its version beside the answer. Conflicting values, missing source contents and unmatched variants need review.
Check what was captured, what the source supports and what remains missing. This example does not approve a claim or publish a correction.
Visibility across answer engines
Check whether a brand is mentioned and cited for one keyword set across several answer engines. Share of voice compares the sample brand with named competitors over dated runs, and the cited-domain table shows which sources the answers rely on. This panel uses fixture values only and queries no engine.
Fictional example: one keyword set, six engine rows, four dated runs.
| Named rival | Collection date: 2026-09-01 | Collection date: 2026-09-15 | Collection date: 2026-10-01 |
|---|---|---|---|
| Sample brand | 31% | 28% | 35% |
| Fictional rival X | 27% | 30% | 22% |
| Fictional rival Y | 18% | 19% | 20% |
Fictional counts for one fixed prompt set. Each row shows how many sample answers name the brand or a named rival. An unavailable answer counts as unknown, not as absence.
| Answer engines (fictional letters) | Sample brand | Fictional rival X | Fictional rival Y |
|---|---|---|---|
| Fictional engine A | 40% | 30% | 20% |
| Fictional engine B | 10% | 50% | 20% |
| Fictional engine C | 30% | 30% | 10% |
| Fictional engine D | 20% | 20% | 30% |
| Fictional engine E | 0% | 10% | 10% |
| Fictional engine F | No answers recorded in this fixture run. | ||
| Cited domains (fixture) | Own-URL citations |
|---|---|
| Fictional publisher 1 | 14 |
| Fictional review site 2 | 9 |
| Fictional retailer 3 | 4 |
Prompts where a rival is named and the brand is not
Ranked by how often the gap appears in the fixed set. A gap is a visibility question, not a demand or sales finding.
Change notice (example)
Visibility for one engine moved past the threshold. This notice is an example and sends nothing.
All values are fictional. The panel shows the layout only, queries no answer engine, and makes no claim about demand, sales or rankings. Fixed fictional counts. No engine is queried and no brand is measured. Every value here is fixture data. No answer engine was queried.
Use product discovery and product information to review the underlying catalog context. Answer visibility does not establish demand, conversion, stock or delivery readiness.
Fixed fictional example — no live runway analysis
A seasonal label and a photographed look describe a source. They do not establish demand for your assortment. Explore three fixed fictional records.
Example →Browse a season before you read a look
Seasons and designers are labels on a source record. This fixed example shows the path from a season to a designer to a show, with no live search.
Fictional example: not a real season, designer or show.
NOGL does not hold editorial rights to runway archives or images. This block shows labels and structure only.
Change the example or the review question. This local exercise does not search collections, analyze an image or contact a supplier.
R01 · Dated observation
Human review required
One dated source note identifies a look and a supplied attribute; the season is not the capture date.
Read the supplied look reference, attribute and source version together. A source note is not an independently verified description.
No comparison source supplied
Field reference: T25:R01:comparisonMissing; no evidence provenance
Tags on this look
The named fashion season, show date and capture date answer different questions. Keep missing dates visible and do not substitute one date for another.
Supplied source
Comparison source
No comparison source supplied
Compare only the supplied scope. Different seasons or incomplete look sets do not support a growth claim. An unknown population stays unknown.
Supplied source
Comparison source
No comparison source supplied
Attribute momentum against the same season last year
Compare how far one fictional attribute moved in its share of looks against the same season a year earlier. Each row names its season scope, its designer count and its rank among the example risers.
Fictional example: three attributes, one season scope, one fictional sample.
| Attribute | Share of looks, this season | Share of looks, same season last year | Change, percentage points | Designers | Momentum label | Rank among risers |
|---|---|---|---|---|---|---|
| Sheer layering | 34% | 27% | +7 | 9 | Rising | 1 |
| Oversized tailoring | 22% | 24% | -2 | 7 | Holding | — |
| Metallic trim | 5% | 12% | -7 | 4 | Fading | — |
Rising when the share grows by at least 10 percent of its prior-season value, fading when it falls by at least 10 percent, holding otherwise. Example rule, not a published index.
Momentum uses only the supplied looks. Social and search signals, peak and end-of-life stages, and live runway collections are not connected in this example.
Check source identity, timing, coverage and usage permission before reusing an observation. This example neither grants image rights nor approves a buying decision.
Use the unresolved question in product planning or design review. Keep supplier evidence and actual customer demand separate from runway observations.