> ## Documentation Index > Fetch the complete documentation index at: https://storekit.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # What You Can Ask > Prompts that work well with the storekit AI assistant, grouped by job: sales, what sold, refunds, bills, snoozes, menus, discounts and payment links. Your assistant works out which storekit tools to call from what you ask. These prompts are a starting point; adapt the stores, dates and amounts to your own. Three habits make answers more reliable: * **Name the store** when you have more than one ("at Soho", "for the Brighton kiosk"). Without it, sales figures are added up across the account, which is refused when your stores use different currencies. * **Say the period** ("yesterday", "last week", "1 to 15 March"). The default is the last 7 days, or 30 days for sales stats and top products. The longest single period is 90 days. * **Ask for one thing at a time** for the first few questions, then chain ("now compare that with the week before"). ## Yesterday's Numbers ```text theme={null} How many orders did we take yesterday at Soho, and what was the total? ``` ```text theme={null} Compare this week's sales at Soho with the same days last week. ``` ```text theme={null} What was our average order value for delivery orders in August? ``` Totals exclude rejected and cancelled orders (cash and pay-later orders are included). They are gross of refunds — ask for refunds separately (below) if you want a net figure. Figures for one store use that store's local time; account-wide figures use UTC unless you specify a timezone. ## What Sold ```text theme={null} What were the ten best-selling products at Soho last month? ``` ```text theme={null} Which items sold fewer than 5 units in the last 30 days? ``` Prices shown alongside are the current menu prices, not what each unit sold for at the time. ## Orders ```text theme={null} Show me yesterday's orders that were rejected. ``` ```text theme={null} What happened to order KX7D2? Give me the full timeline. ``` ```text theme={null} List delivery orders scheduled for tomorrow. ``` By default orders are listed by when they are due (their scheduled time, or creation time if there is no slot). Say "placed on" or "created" if you mean when the customer ordered. Rejected and cancelled orders only appear when you ask for them. ## Refunds ```text theme={null} How much did we refund at Soho last week, and on which orders? ``` ```text theme={null} List refunds for orders that were placed in July. ``` Refunds are shown by the date the refund was issued unless you ask by the order date. ## Pay at Table ```text theme={null} Which bills are still open at Brighton right now? ``` ```text theme={null} How many covers did we do on bills yesterday? ``` ## Snoozing ```text theme={null} Which items were snoozed at Soho this week, and for how long in total? ``` ```text theme={null} Were any items snoozed by the POS rather than by staff in the last 7 days? ``` Snooze reports cover the whole period you ask for. If you want the individual on/off events for an item, ask for them and keep the period short — a busy week can exceed the 100-event cap per item. ## Menus and Stores ```text theme={null} Which menus does Brighton have, and which are live? ``` ```text theme={null} List every product on the Brunch menu with its price and whether it is available. ``` ```text theme={null} What are Soho's delivery hours and delivery fees? ``` ## Discount Codes This section includes a **write**. Most clients ask before creating the code, but only if you have not auto-allowed the tool — see [permissions](/docs/guides/ai/permissions-and-privacy). Check the code, amount, stores and dates before you approve, then confirm under **Marketing** → **Discounts**. ```text theme={null} Which discount codes are active, and how many times has each been used? ``` ```text theme={null} Create a discount code WELCOME10 for 10% off at Soho and Brighton, one use per customer, valid until the end of next month. ``` Types the assistant can create are: a fixed amount off, a percentage off, buy one get one free, and free delivery. It can set a minimum spend, a total or per-customer usage cap, a start and end date, and restrict the code to delivery, pickup or in-store. It cannot edit or archive a code once created — do that in the dashboard. ## Payment Links This section includes a **write**. Most clients ask before creating the link, but only if you have not auto-allowed the tool. Check the store, amount and expiry before you approve. A created link is live immediately and can take money. ```text theme={null} Create a one-off payment link for £150 at Soho titled "Private dining deposit — Patel, 14 Oct", expiring in 7 days. ``` ```text theme={null} Create a reusable payment link at Brighton where the customer chooses the amount, between £5 and £500, titled "Gift voucher". ``` ```text theme={null} Show me the QR code for payment link plink_… so I can print it. ``` ```text theme={null} Which payment links have taken payments this month, and how much? ``` A **one-off** link becomes **Completed** after one payment; a **reusable** link stays active (optionally up to a maximum number of payments). A **fixed** link has a set amount; a **variable** link lets the payer choose within optional bounds. The assistant can also set a description, an internal reference, an image, a thank-you message or a redirect after payment, and whether to collect the payer's name, email, phone or business name. See [Payment Links](/docs/payment-links/overview) for how they behave once created. ## When the Assistant Says No Some answers are refusals by design: | The assistant says | Why | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | It needs you to pick a store | Your stores use more than one currency, so an account-wide total would be meaningless | | The period is too long | The limit is 90 days in one question — split it | | It cannot find an order, store or link | It belongs to another account, or the ID is wrong. Order IDs are short codes like `KX7D2`; payment link IDs start with `plink_` | | It cannot change a menu, order or setting | There is no tool for that. See [What It Cannot Do](/docs/guides/ai/overview#what-it-cannot-do) | Anything else that looks wrong is covered in [Troubleshooting](/docs/guides/ai/troubleshooting). ## Related topics - [Connect Your AI Agent](/docs/guides/ai/overview.md) - [Connect Claude](/docs/guides/ai/connect/claude.md) - [Connect ChatGPT](/docs/guides/ai/connect/chatgpt.md) - [Connect Claude Code](/docs/guides/ai/connect/claude-code.md) - [Connect Other Clients](/docs/guides/ai/connect/other-clients.md)