MEGURO Docs
Documentation

Task-oriented technical guidance for practice, evidence, automation, and verification.

Reference and troubleshooting

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 jobLook forRepresentative evidence
PricingProducts with margin and demand sensitivityPrice or discount change plus modeled demand and contribution
InventoryLow stock or incoming supplySingle-location adjustment plus modeled stock position
Order cash refundCanonical committed order and priced committed linesLine-item cash refund plus separately labelled return/restocking evidence
FulfillmentOpen fulfillment work or shipping thresholdsFulfillment progress or delivery-profile consequence
RetentionAbandoned checkout or discount pressureBounded offer plus separately labelled modeled cohort or loyalty evidence
CatalogModeled launch pressure, quality gaps, bundles, or plansProduct-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 to verify the call shape separately.