Where do I start in my first 30 minutes?

where do i start in my first 30 minutes? use this page if you are a new pricing manager deciding whether to orient on the dashboard, understand pricing governance, or validate proposed prices before taking action which screen should i open first? start with yieldigo platform documentation hub docid\ p0rrr5rq3qtsyycngkmuu unless you already have a specific pricing question use the dashboard to find the area that needs review, then choose price management docid\ rs0z8lfkdpage86wko0qc to understand or change governance, or price reports docid\ cudlursgmvcrrubq3grud to validate a proposed price with product and sales evidence do not begin in exports docid\ ayu6zunb35nqkubun3bpf on your first login an export is the outbound handoff of price changes to store systems, erp, or downstream integrations; review the proposed prices and their governance first compare the three starting points attribute dashboard overview price management price reports best first question what needs attention now? why is this new price being proposed? does this recommendation make commercial sense? start here when you are orienting after first login a governance setting, rule, or pricing structure needs review you need evidence for a category, product, or zone primary decision which area should i investigate next? should the applicable pricing governance change? should this proposed price be investigated further? useful signals alerts, pending standard export status, impact of new regular prices, and summaries price rules, price strategy, locked products, product architecture, and model insight new price, current price, difference, cost, margin, reference price, and sales history do not use first for editing rules or validating an individual product in detail a quick operational scan of all pending work changing price rules or releasing an export use this 30 minute path 0–5 minutes orient in dashboard overview open yieldigo platform documentation hub docid\ p0rrr5rq3qtsyycngkmuu at the top level check these areas in order alerts summary — identify products or families requiring attention, especially negative margin expectations, competitor reference deviations, missing computable new prices, and product architecture violations standard export status — see whether a standard export is scheduled and how many new, adjusted, and deleted price rows are pending impact of new regular prices — understand the projected direction of profit, revenue, volume, margin, and reference price index if the current new regular prices are applied families summary and multibuy summary — note whether coverage or attention counts point to a structural issue rather than an individual product issue rule of thumb use the dashboard to prioritize, not to diagnose an alert tells you where to look next; it is not, by itself, a reason to change a price 5–15 minutes choose price management when the question is “why?” open price management docid\ rs0z8lfkdpage86wko0qc when the dashboard indicates a governance exception or when you need to understand the source of a recommendation review the selected scope before taking action selecting a category re scopes the module from the top level to that part of the assortment, including its applicable inherited or exception settings check the relevant area price settings when you need to see the applicable price rules and price strategy regular prices when you need to compare current price and new price by zone before export locked products when a product should not be automatically repriced a locked product is excluded from automatic regular repricing; its baseline price stays fixed until manually changed product architecture when related products must preserve a value ladder when enabled, product architecture overrides generic price rules model insight when demand patterns may explain the proposal the optimization algorithm uses model insight signals alongside price rules, reference prices, cost, and sales data to generate new regular prices rule of thumb investigate the applicable price rule before creating a manual price a manual price overrides algorithmic output for a specific product and should be used sparingly 15–25 minutes choose price reports when the question is “is it credible?” open price reports docid\ cudlursgmvcrrubq3grud when you need to test a recommendation against commercial evidence without changing governance start with product list or category list compare current price with new price and use difference to find material proposed movements switch to a by zone view when a product can have different new/current prices per zone filter for alerts, price change criteria, brand, supplier, or product class to focus the review open a product and use product regular prices to review cost, margin, reference price indexes, and planned promo price information by zone use sales history to separate regular sales, standard promo, and multibuy sales before interpreting demand or margin movement rule of thumb do not judge a regular price recommendation from promotional sales alone promo price activity and multibuy sales are separate from regular price performance 25–30 minutes decide the next click, not the final price at the end of the first 30 minutes, classify each issue no exception and credible impact continue monitoring from yieldigo platform documentation hub docid\ p0rrr5rq3qtsyycngkmuu rule, strategy, lock, or architecture question continue in price management docid\ rs0z8lfkdpage86wko0qc product, category, zone, margin, or market position question continue in price reports docid\ cudlursgmvcrrubq3grud ready for governed outbound review move to exports docid\ ayu6zunb35nqkubun3bpf , where export content and export impacts support review before release common pitfalls treating new price as already effective current price is the price currently in stores; new price is proposed and not yet exported reviewing only the aggregated view when zones have different pricing or reference prices changing a price rule before checking whether a locked product, product architecture, or another applicable rule explains the result using a manual price as the default response to an alert instead of investigating the underlying data or governance constraint opening an export before checking alerts and the projected impact of new regular prices