---
name: store-studio
description: Use when the user wants to build or edit a storefront, products, inventory, customers, orders, discounts, delivery, or sales reports in Store Studio. Discover the current App from https://goalmatic.io/apps.
---

# Store Studio

Store Studio combines a merchant storefront with products, stock, orders, customers,
promotions, delivery, pickup, and sales reporting.

## Intake

Ask whether the user wants to configure the storefront, create a product, update stock, manage
an order, change delivery, review customers, or inspect reports. Confirm the active merchant
workspace, storefront scope, product or order, and whether this is Demo or Live.

Reuse the task details and authorization already supplied; ask only for missing information or
a consequential action outside that scope.

Open Store Studio from the Apps directory. Discover current commerce, media, guest storefront,
and template actions through the installed App session; use connected tools rather than invented
routes or operation names.

## Workflow

1. Inspect the current store, product, stock, order, or template before editing.
2. For products, confirm title, description, price, variants, inventory, media, and digital or
   physical fulfillment details.
3. For templates, preview the design and preserve the merchant's existing customizations.
4. For orders, verify customer, line items, fulfillment, payment state, and permitted status.
5. For guest storefronts, check that the public scope exposes only intended catalog and checkout
   actions.
6. Reread the visible result and report the exact changed state after each write.

Completion means the intended merchant record, storefront preview, guest route, or report is
visible in the correct workspace. A local Demo, preview, or private test does not prove a live
storefront or payment outcome.

## Guardrails

Goalmatic owns identity, commerce transactions, sessions, media transport, and provider
credentials. Keep customer and merchant data scoped to the active installation and workspace.

The user separately authorizes product, inventory, order, discount, delivery, publication, and
payment actions. Never collect card details, process a payment, or claim settlement unless the
current App explicitly reports that provider state.

Treat store template publication and the App's own release as separate actions. Do not publish
or activate a storefront because a preview rendered successfully.

## Evidence

Report the changed merchant record, preview or live state, order/fulfillment status, customer
scope, and any provider or payment state shown by the App.

For inventory, verify the product variant and stock location before changing quantities. For
orders, keep fulfillment and payment state distinct. For digital products, verify entitlement
or delivery state through the App before telling a customer that access is ready.

When the App reports Demo, Live, private test, or unavailable state, carry that label into the
handoff. A customer storefront link and the merchant's App release are different artifacts.