---
title: Store Operations
description: Set up and run your store's catalog, orders, customers, promotions, sourcing, and reviews.
---

Use Store Operations to manage the day-to-day information and activity behind your Runner store.

## Why and when to use Store Operations

Open this area after Runner has created your store. It is the practical control center for store details, shipping rules, products, orders, customers, and promotions. Some work, such as supplier sourcing or review moderation, appears only when the corresponding capability is available.

## Availability and prerequisites

- Sign in and open a Runner project that includes a store.
- Wait if Runner shows **Please wait, the store admin is deploying...**. The pages load when the store backend is ready.
- Your workspace role and the store's state can limit which controls are shown.
- Connected payment, shipping, fulfillment, booking, and supplier services can add status-specific controls.

## Open Store Operations

1. Open **Workspace**.
2. Choose the store you want to manage.
3. Select **Store Operations** in the project navigation.
4. Choose a section from the Store Operations menu.

## Ask Runner to help from chat

**Entry path:** Open the project → choose **New Chat** or an existing conversation.

You can ask Runner to inspect or update approved store records without finding every admin page
yourself. This includes common work with products and variants, customers, inventory, shipping,
fulfillment, orders, returns, promotions, and related records.

1. Name the record and the exact result you want.
2. Ask Runner to inspect the current state first when the change depends on an order, inventory, or
   fulfillment status.
3. Explicitly authorize the exact effect before a destructive or order-lifecycle action. A general
   request is not permission to delete a record, cancel an order, or advance fulfillment.
4. Wait for Runner's result, then refresh the relevant Store Operations page and verify the updated
   state before retrying or starting another change.

Account access, store-system settings, payments, and tax administration are not available through
this chat capability. Product imports and other file uploads still use their dedicated flows.

## Choose the right section

| Section | Use it for | What selecting it shows |
| --- | --- | --- |
| **General** | Store visibility, identity, markets, stock locations, shipping, and review availability | Opens the shared settings page. Most fields use the page **Save**; the **Product reviews** switch saves immediately. |
| **Orders** | Customer purchases and fulfillment progress | Opens the order list; selecting a row opens the full order record. |
| **Products** | Catalog items, prices, images, variants, inventory, and SEO | Opens the product list; **Add** starts a new product and a row opens editing. |
| **Customers** | Customer contact details, addresses, and order history | Opens the customer list; selecting a row opens the customer record. |
| **Promotions** | Automatic discounts and promotion codes | Opens the promotion list. Use **Create**, or **Add First Promotion** in an empty list, to choose a discount type. |
| **Dropshipping** | Conditional supplier catalog browsing | Opens search and filter controls when supplier data is available. |
| **Reviews** | Conditional review moderation | Appears after product reviews are enabled and supported by the store. |
| **Advanced Admin** | Conditional access to the full store backend | A floating desktop entry opens the backend admin in a new browser tab when the feature is available. |

## Recommended setup order

1. Complete [onboarding and General settings](./onboarding-and-general-settings.mdx).
2. Add a stock location and configure [shipping](./shipping.mdx).
3. Create [products](./products.mdx) and check [variants and inventory](./inventory-and-variants.mdx).
4. Connect a payment service from **Apps** before testing checkout.
5. Use [orders](./orders.mdx), [customers](./customers.mdx), and [promotions](./promotions.mdx) as activity begins.
6. Use [dropshipping](./dropshipping.mdx), [reviews, or Advanced Admin](./reviews-and-advanced-admin.mdx) only when those entries and prerequisites are available.

## Common states and limits

- **No data yet** is a valid state. Products, orders, customers, promotions, and reviews show an empty message until records exist.
- **Loading is not success.** Wait for a list, saved confirmation, or updated status before assuming an action finished.
- **Unsaved changes stay on the page.** Use **Save** where shown; if Runner warns about leaving, choose whether to remain, save, or exit without saving.
- **Destructive actions require confirmation.** Deleting a product, customer, or promotion cannot be assumed recoverable.
- **Chat results still need verification.** After Runner changes a store record, refresh the relevant page and confirm the new state before retrying.
- **Conditional entries can be absent.** Do not use a copied URL as proof that your store supports a hidden feature.

## If Store Operations does not load

1. Confirm that you opened the intended project.
2. Wait for the deployment message to clear, then refresh the page.
3. Return to the project and select **Store Operations** again.
4. If only one section fails, try its **Refresh** control when available.
5. If the issue continues, keep the project name, section name, visible error, and approximate time for support.

## Related guides

- [Welcome to Runner AI](../product-guide.mdx)
- [General settings and onboarding](./onboarding-and-general-settings.mdx)
- [Products](./products.mdx)
- [Orders](./orders.mdx)