> ## 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. # Build Your Own Tools on storekit > Point storekit webhooks at a small app you build with Lovable, Bolt or Replit to add custom kitchen tickets, order screens, alerts and reports. Describe the tool you want, paste one of our prompts into an AI app builder, and point a storekit webhook at what it builds. Most of the recipes in this section go from idea to a working tool in an afternoon, without hiring a developer. ## How It Works Every recipe here has the same three parts: 1. **Something happens in your store** — an order comes in, a printer drops offline, an order fails to reach your till, a payout lands. 2. **storekit sends that event to your app** as a webhook: a small JSON message delivered to a web address you choose, within seconds. 3. **Your app does something with it** — prints a ticket, shows it on a screen, sends a text, adds a row to a spreadsheet. You build part 3. storekit handles parts 1 and 2. You never need to ask storekit for API access: webhooks are enabled from your own dashboard. ## What You Need * Webhooks on your storekit plan. Webhooks are a paid add-on. Under **Settings** → **Developers**, the **Webhooks** panel shows **Enable Webhooks** if your plan includes them, or **Upgrade to enable webhooks** if it does not — in which case [contact support](/docs/getting-started/contact-support). * An account with an AI app builder. The recipes are written for [Replit](https://replit.com), [Lovable](https://lovable.dev), [Bolt](https://bolt.new) and [v0](https://v0.dev). Any builder that can deploy a small web app to a public URL and hold a secret for you will do. For tools that need to receive webhooks or run on a schedule, we lean towards Replit; for screen-only tools, any of them. * An hour or two, mostly spent testing. You are building software that will run in your business. It is yours: storekit supports the webhook reaching your app, and the builder supports its platform, but nobody at storekit can see or fix the app itself. Keep the tools small and single-purpose, and keep the storekit-driven process (printing, the dashboard, POS integration) running alongside them. ## What You Can Build Design your own ticket layout for a Star cloud printer: allergen banners, big order codes, station sections. Big orders, deliveries, allergy notes and till failures to the right person, with rules you edit yourself. A TV screen that moves orders across New, Preparing, Ready and Done as storekit does. What sold out, when and why, with a Slack digest every morning. A ledger that fills itself in on every payout, with a reconciled tick-box and CSV export. The prompt skeleton every recipe uses, and the context block to paste so the AI gets storekit right first time. The [webhook events reference](/docs/developers/webhooks/webhook-events) lists every event storekit sends, and each one is a tool waiting to be built: | When this happens | Event | Ideas | | --------------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A new order is placed | `order.created` | [Custom kitchen ticket](/docs/guides/build/recipes/custom-kitchen-ticket), [live order board](/docs/guides/build/recipes/live-order-board), [a text for orders over £100](/docs/guides/build/recipes/order-alerts) | | An order fails to reach your till | `order.pos.dispatch.failed` | [Text the manager on shift](/docs/guides/build/recipes/order-alerts) | | A guest leaves a rating | `order.rating.updated` | Low ratings straight to the GM | | A dish runs out | `item.out_of_stock` | [Running list of what sold out and a morning digest](/docs/guides/build/recipes/out-of-stock-log) | | The store closes or opens | `store.closed`, `store.opened` | Team channel post, "did someone forget to reopen?" check | | A printer drops offline | `printer.status.offline` | Text whoever is on shift | | A payout is sent | `payments.payout.created` | [Row in the reconciliation sheet](/docs/guides/build/recipes/payout-reconciliation) | | A payment link is paid | `payment_link.paid` | Mark the invoice paid, send a thank-you | ## What You Cannot Build (Yet) * **Tools that change storekit.** Webhooks are one-way, from storekit to you. Updating menus, prices or availability from your own app needs the storekit API, which is in early access and granted case by case — [request access](/docs/developers/introduction#requesting-api-access). * **Changes to storekit's own tickets, emails and screens.** There is no template editor in the dashboard for kitchen tickets or customer emails. The [custom kitchen ticket recipe](/docs/guides/build/recipes/custom-kitchen-ticket) works around this with a second printer that your app drives; storekit's own printing is untouched. ## Related No app needed: send any event straight to a Slack channel from the webhooks portal. Connect Claude or ChatGPT to your account and ask about sales, orders and menus (beta). Every event storekit sends, with example payloads. For the developer you hand this to when a tool outgrows an app builder. ## Related topics - [Integrations Overview](/docs/guides/integrations/overview.md) - [API & Webhooks](/docs/guides/integrations/api-webhooks.md) - [Developer Introduction](/docs/developers/introduction.md) - [Free Modifiers](/docs/guides/menu/free-modifiers.md) - [Writing a Prompt That Works](/docs/guides/build/prompting-guide.md)