NOGL
Interactive platform demo5/7

Protect margin

Price & Promote

Hold the floor when the market gets noisy.

BrandAlpine Atelier
Productsage merino zip knit
MarketDACH

Scenario

One signal across the full merchandising lifecycle

Market markdowns

-12%

Your price

Hold

Trigger

<68%

Modeled demo

Floor protected

Market markdown pressure hits -12%, but the sage knit should hold price until wk 14 unless sell-through drops below 68%.

Hold EUR 85, reserve promo only for late sizes, and review exceptions twice weekly.

Continue the chain: Customer Care

Base

EUR 85

Keep premium framing while signal remains healthy.

Promo

Late sizes

Use markdown only where size curve breaks.

Review

2x weekly

Exceptions, not spreadsheets.

Signal chain
1Read market-12%
2Check floor22%
3Decisionhold
What this is based on

Modeled from market markdowns, inventory, sell-through target, and margin floor.

Methodology: Pricing scenario. It is a recommendation, not automated repricing.

Alpine Atelier keeps the same product signal across all seven pages so the demo feels like one operating system, not seven unrelated widgets.

Price & Promote · Protect the decision boundary

Review the reason before changing the price.

A competitor move is an input, not an instruction. Compare the offer, check your constraints and make the proposed response understandable to the person who approves it.

Turn a price observation into a reviewable proposal.

Explore the existing pricing scenario
  • 01Is this really a comparable offer?
  • 02Which cost, stock and margin rules matter here?
  • 03Why hold, test or revise the proposed price?

Illustrative price review sheet

A response to review, not a live price change

01 · Example observation

€74

Catalog B · zip layer

01 Oct 2026 · EUR · synthetic comparison price, excluding VAT

Match unresolved: check material, size and delivery. This is not a current observed offer.

02 · Business constraints

Example cost
€29.00
Price floor
€70
Target contribution
≥ 55%
Tax basis
All prices exclude VAT

03 · Compare a scenario

Proposal

€79

Simple contribution

63.3%

(Price − €29 example cost) / price. Excludes VAT, overhead, discounts, returns and demand effects. Not a margin forecast.

04 · Approval boundary

For review, not publication.

Both example prices meet the displayed arithmetic rules. The match and actual cost remain unverified. An accountable person confirms the next step.

Selection is local. No storefront price changes.

05 · Read the test result

A measured difference, shown with its limits.

Compare a prepared price or promotion test against its control. The example shows the measured result and whether it is strong enough to act on.

Fictional example: one prepared test. The values are invented.
05 · Read the test resultControlVariant
Conversion rate3.1%3.6%
Order value€68.00€71.00

Significance: Significant at the agreed level

Traffic split: 50% control, 50% variant (fictional)

No storefront traffic is split and no price changes. A person decides whether a result is acted on.

06 · Competitor capture (example)

Where the offer was seen, and when.

Each example observation keeps its channel, dates and creative, so a reviewer can see where an offer came from before comparing it.

Dated captures for this offer
  1. Channel: Email

    First and last seen: –

    Creative format: Text banner with discount code

  2. Channel: SMS

    First and last seen: –

    Creative format: Short video, six seconds

  3. Channel: Ad creative

    First and last seen: –

    Creative format: Static square image

Fictional example: three captures for one invented competitor offer.

No inbox, contact list, ad library or scraper is connected. The captures are invented for this layout.

Storefront placement · fixture

Which products a shopper sees, and why.

Boost and bury rules: Boost · Bury

  1. Rank 1Zip layer, darkBoost
  2. Rank 2Crew layer, sandBoostBuryTwo rules conflict on one product; the margin floor applies and the conflict is listed.
  3. Rank 3Fleece vestBury
  4. Rank 4Shell jacket

Fixture products and sample scores only. No shopper data is read or stored.

Campaign spend check, fixture example

Illustrative campaigns and stock cover. No ad account is connected and no bid or budget changes are made.

Review threshold: 14 days of stock cover
CampaignDaily spend (example)Stock cover (days)Proposal
Retail media€420.0022Keep spend
Paid search€180.009Reduce spend for review
Paid social€140.0012Hold spend for review

Creator video (fictional)

Suggested product match

ZIP-01 · 84%

A suggested match is not a confirmed product tag.

Conversion potential (illustrative): Medium, illustrative only

Waiting for review before the video goes live

No social account is connected and no creator is contacted.

Fictional example: one fixed budget, three channels, two scenarios.

Budget scenarios with outcome and channel detail

Compare allocations of one fixed budget. For each scenario, see the change against the current mix, an outcome estimate with its range, and the channel return behind it. Fixture values only; nothing is recommended or applied.

  • Each scenario keeps the total budget fixed and shows the change per channel against the current mix.
  • An outcome estimate with an uncertainty range, labelled as a model estimate and not as a forecast.
  • Channel return (ROAS) bands and a saturation note, so a channel near its ceiling is visible.

Fixed budget (fixture): EUR 120,000 per quarter

Budget change per channel against the current mix, for one fixed total budget.

Optimised plan: the scenario with the highest fictional outcome for the fixed budget.

Fictional example: one fixed budget, three channels, two scenarios.
ScenarioSearchSocialRetail mediaEstimated outcome effectUncertainty range
A: more search+€7,200-€6,000-€1,200+2.1%+0.6% to +3.4%
B: more social-€4,800+€6,000Above saturation note-€1,200+0.9%-0.4% to +2.2%
Fixture plan+€7,200-€6,000-€1,200+2.1%+0.6% to +3.4%

Fixture plan for illustration. It is not a recommendation, and no budget is changed.

Return by channel

Return by channel
ChannelCurrent shareReturn band (ROAS)
Search40%3.1 to 4.2
Social35%1.8 to 2.6Social response flattens above about 38% of the budget (fixture).
Retail media25%2.2 to 2.9

All values are fictional and illustrative. The panel does not change any budget, does not recommend a plan and does not show an observed result. An accountable person reviews any scenario before use.

Fictional example: four creators, six posts, thirty days of fixture sales.

Creator sales attribution

See which creator posts and affiliate links lead to sales, and what each creator earns after commission. This panel uses fixture values and connects to no store, affiliate network or creator account.

  • Sales attributed to each post or link, with the signal used: tracked link, promo code or survey answer.
  • Commission rate and earnings per creator, set against the cost of the content.
  • A 30-day earnings trend for each creator, so a drop is visible before the next payout cycle.
Attributed sales by post
PostCreatorAttribution signalSalesCommission rate
P-01CR-01Tracked link4612%
P-02CR-01Promo codeOverlaps another signal: shown on its own, not added up1912%
P-03CR-02Survey answerNo attributed sales10%
P-04CR-03Signal not supplied815%
P-05CR-03Tracked link2715%
P-06CR-04Promo code129%

30-day earnings trend

  • CR-01: €210.00 in 30 days, +8% on the prior 30 days
  • CR-02: €96.00 in 30 days, -4% on the prior 30 days
  • CR-03: €143.00 in 30 days, +2% on the prior 30 days
  • CR-04: €58.00 in 30 days, -11% on the prior 30 days

All values are fictional. The panel shows a layout only and reads no store, affiliate network or creator account. Figures are not a payout statement and not a forecast.

Fictional example: four channels, two campaigns each, one fixture refresh date.

Channel attribution across touchpoints

See how revenue is credited across the channels and campaigns a shopper touched before buying, with the refresh cadence stated. Fixture values only; the attribution model is named beside every figure.

  • Attributed revenue by channel and campaign, with the attribution model and lookback window shown beside the table.
  • A refresh date and cadence on every view, so a figure is never read as live when it is not.
  • Profit per channel set beside attributed revenue, so spend that drives sales but loses money is visible.

Last refreshed (fixture): · Refresh cadence: Weekly

Attribution model: Last touch · Lookback window: 28 days
ChannelAttributed revenueProfit per channel
Search2 campaigns€96,400.00€31,200.00
Social media2 campaigns€71,800.00€14,600.00
Retail media2 campaigns€58,200.00€9,100.00
Affiliate2 campaigns€42,600.00€7,300.00

Switching the model relabels the table. No figure is recalculated here.

All values are fictional. The panel reads no ad account, pixel or order feed. Attributed revenue is credit, not proof of additional sales; check it against the MMM view and against tests.

Evidence and review boundaries

Observed offer
Example public offer · source, observation date and currency need confirmation.
Matching caveat
Check variant, pack size, tax, delivery and promotion terms before comparing prices.
Proposed scenario
An illustrative hold-or-revise decision; no storefront price is changed.
Retailer constraints
Authorized cost, margin, stock and channel rules are required to test the proposal.
Reason & reviewer
Record the constraint and rationale; a merchant approves any next action.

Three checks before a price decision.

  1. 01 · Verify the offer

    Confirm the match and observation context. A missing price or stale page is not a reliable competitive signal.

  2. 02 · Check the constraints

    Use agreed cost, margin and stock information. A lower competitor offer need not justify reducing your own price.

  3. 03 · Review the proposal

    Keep the reason and applicable rules visible. Approval and execution are separate from this illustrative comparison.

Connect the economics to the evidence.

Public offer observations do not contain your costs, inventory or channel policies. Agree authorized inputs and review rules for a pilot. Marketing-budget scenarios are a separate MMM conversation, not a promised pricing or ROI outcome.

Social signals that could become a shoppable moment

Customer posts and live-shopping events from social channels are listed as signals. Each one names its product, shows the stock state and suggests a next step. A merchant reviews the step; nothing is posted, boosted or restocked from this page.

  • Each social signal names one product and one event type: post, comment, live view or share.
  • A shoppable moment links a customer photo to a product SKU and shows its stock state.
  • A suggested step (promote, hold or restock review) stays a proposal until a merchant accepts it.

Fictional example: three social signals for one product line, with one size out of stock.

  1. Post

    Product: ZIP-01

    Stock state: In stock

    Suggested step, for review: Promote

  2. Comment

    Product: ZIP-01

    Stock state: In stock

    Suggested step, for review: Hold

  3. Live view

    Product: ZIP-01

    Stock state: Size M out of stock

    Suggested step, for review: Restock review

The example is fictional. No social post, live session, stock level or ad budget is read or changed on this page.

When price rules disagree, keep the disagreement visible.

Choose a prepared rule set and a proposed price. Inspect each comparison before deciding which input needs review.

Fictional local rule check · no price is changed

Supplied example inputs

Rule-set ID: PR-01

Minimum price · supplied rule
€70.00
Source ID: EX-PR-01-lowerCents
authored fictional input
Maximum price · supplied rule
€90.00
Source ID: EX-PR-01-upperCents
authored fictional input
Purchase cost · supplied record
€50.00
Source ID: EX-PR-01-purchaseCostCents
authored fictional input
Currency
EUR
Source ID: EX-PR-01-currency
authored fictional input
Example source date
Source ID: EX-PR-01-sourceDate
authored fictional input
Rule version
v1
Source ID: EX-PR-01-ruleVersion
authored fictional input

Proposed example price: €80.00

  • At or above the minimum

    €80.00 ≥ €70.00

    Comparison met

  • At or below the maximum

    €80.00 ≤ €90.00

    Comparison met

  • Above the supplied purchase cost

    €80.00 > €50.00

    Comparison met

PR-01 · P80 · €80.00

All three comparisons are met. This is not approval or evidence of profit.

Merchant approval: not established

Feed-quality review

Inspect supplied feed evidence beside the price-rule example. This local review does not connect to a channel or change a price.

Bounded feed-quality evidence review · reviewer assessment only

Source feedEvidence state: Known
Catalog export · 2026-10-01
Source ID: EX-PR-01-feed
authored fictional input
Normalized categoryEvidence state: Known
Apparel / Tops / T-shirts
Source ID: EX-PR-01-category
authored fictional input
Missing attributesEvidence state: Known
None recorded
Source ID: EX-PR-01-missing-attributes
authored fictional input
Channel readinessEvidence state: Known
Ready for reviewer check
Source ID: EX-PR-01-channel-readiness
reviewer assessment in supplied fixture
Failed attemptEvidence state: Failed
Channel rejection · fixture: Rejected: material attribute missing
Routed back to enrichment; not resubmitted
Source ID: EX-PR-01-channel-rejection
channel rejection in supplied fixture
Human note
No local note prepared.
Local only · not saved or sent

Channel readiness is a reviewer assessment; no channel result is established.

Compare all prepared proposals

Proposed example priceAt or above the minimumAt or below the maximumAbove the supplied purchase cost
€60.00P60 · EX-P60At least one supplied rule is not met. The price remains a proposal.Comparison not metComparison metComparison met
€80.00P80 · EX-P80Proposed example priceAll three comparisons are met. This is not approval or evidence of profit.Comparison metComparison metComparison met
€100.00P100 · EX-P100At least one supplied rule is not met. The price remains a proposal.Comparison metComparison not metComparison met

The three amounts are authored proposals, not recommended prices.

These are three explicit comparisons, not a pricing optimizer. Taxes, channel fees, demand, stock, contractual authority and merchant approval are not established. A price above purchase cost is not proof of profit.

Price & Promote · local feed review

Trace a feed row before it reaches a channel.

Inspect one fixture row from source through normalization, taxonomy review, channel mapping and an unsent export preview. Every value is local and editable for review; no feed, connector or publish action is connected.

Fixture only · no source feed, upload, API, connector, persistence or publish action

  1. 01

    Ingest

    Ready to inspect

  2. Image evidence

    A fictional product photo is read for colour, neckline and occasion. Attributes stay unconfirmed until a reviewer checks them.

    PHOTO-01 · Source: image (fictional)

    Colour (hex)
    #2F4F4F · Unconfirmed attribute
    Neckline
    V-neck · Unconfirmed attribute
    Occasion
    Not in the photo · Unconfirmed attributeSuggested value for a missing field: Everyday · Unconfirmed attribute

    Attributes read from an image are suggestions for review, not confirmed product facts.

  3. 02

    Normalize

    Ready to inspect

  4. 03

    Taxonomy review

    Needs review

  5. 04

    Human decision

    Needs review

  6. 05

    Channel mapping

    Blocked by missing evidence

  7. 06

    Export preview

    Blocked by missing evidence

  8. 07

    Protect

    Local safeguard

Review the category before a product reaches a channel

Each product gets a category suggestion, a confidence value and a review state. Products below the confidence threshold, or without a channel mapping, wait in one review queue. Nothing is exported until a person resolves the category.

  • Each product shows its suggested category and a confidence value.
  • Products below the threshold, or without a channel mapping, wait in one queue.
  • The export preview stays blocked until the review decision is recorded.

Fictional example: three products in the review queue, one below the confidence threshold.

Review threshold (example value)
75 %
Products in the queue
2

Review queue

  1. CAT-001

    Confidence
    91 %
    Category state
    Accepted for local preview
    Review state
    Accepted for local preview
  2. CAT-002

    Confidence
    62 %
    Category state
    Below the confidence threshold
    Review state
    Needs review
  3. CAT-003

    Confidence
    88 %
    Category state
    No channel mapping
    Review state
    Needs review

Feed errors

Channel mapping missing
Count: 2
Required attribute missing
Count: 1

Export preview unsent: the review decision is not recorded. The example is fictional. The confidence values and the threshold are example settings, not model output. No product, feed or channel is read or changed.

Source row

Record ID
CAT-001
Source
Supplier CSV fixture · no feed connected
Supplied title
Crew-neck T-shirt
Description
Short sleeves; supplier calls the item a T-shirt. Blue.

Edit this local value to see the unsent preview change. It is not saved or sent.

Taxonomy review

No confidence score is supplied. A reviewer must resolve the category before export preview can be ready.

Review decision
Unreviewed
Channel mapping
Blocked · resolve and accept a category first

Target taxonomy tree

Target taxonomy tree
NOGL fixture target tree · example only
Confidence
Not supplied
Model / source
Not supplied / Not supplied

Destination mapping matrix

DestinationMapping state
Fictional example channelCH > TSHIRT
ShopifyNot supplied in this fixture
Google Merchant CenterNot supplied in this fixture
AmazonNot supplied in this fixture

The fictional example-channel mapping is shown for review; Shopify, Google Merchant Center, and Amazon mappings remain unsupplied and no connector is connected.

Attribute gap · fixture

CAT-001 · material: Required attribute material is empty

Suggested value, not applied: cotton blend

The suggestion waits for reviewer approval

Channel rule · fixture

One parent with two child variants; the rule is applied to each child

PARENT-01 → CHILD-01, CHILD-02

Local review history

No local decision event yet.

Local fixture decision event · not persisted · not an authenticated backend audit log

Export preview

Preview blocked · unresolved category or mapping

Protect

  • • No network request
  • • No persistence
  • • No publish status
  • • Human review remains required