# Store and scenario catalog

Choose by agent job first, then use the store detail to inspect the exact entities and modeled pressure.

## Scope and proof boundaries

Catalog entries declare modeled commerce conditions; they are not forecasts or claims about future customer demand. A template does not redefine the globally supported Admin GraphQL surface. Scenario-only launch-candidate state, carrier-expedite consequences, and variant discontinuation are modeled or reference-only; do not treat them as Shopify read or write capabilities. `productUpdate(status: ARCHIVED)` affects a whole product, not a variant.

## Choose by agent job

| Agent job | Look for | Representative evidence |
| --- | --- | --- |
| Pricing | Products with margin and demand sensitivity | Price or discount change plus modeled demand and contribution |
| Inventory | Low stock or incoming supply | Single-location adjustment plus modeled stock position |
| Order cash refund | Canonical committed order and priced committed lines | Line-item cash refund plus separately labelled return/restocking evidence |
| Fulfillment | Open fulfillment work or shipping thresholds | Fulfillment progress or delivery-profile consequence |
| Retention | Abandoned checkout or discount pressure | Bounded offer plus separately labelled modeled cohort or loyalty evidence |
| Catalog | Modeled launch pressure, quality gaps, bundles, or plans | Product-owned catalog change and accepted call record |

## Inspect the selected store

The store detail is authoritative for its scenario label, seed, starting modeled day, entities, pressure, and suggested meaningful actions. Use [Supported Admin GraphQL surface](/help/admin-api-surface.html#admin-api-surface) to verify the call shape separately.