Skip to main content
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.
  • An account with an AI app builder. The recipes are written for Replit, Lovable, Bolt and v0. 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

Custom Kitchen Ticket

Design your own ticket layout for a Star cloud printer: allergen banners, big order codes, station sections.

Order Alerts to Slack or Your Phone

Big orders, deliveries, allergy notes and till failures to the right person, with rules you edit yourself.

Live Order Board for the Pass

A TV screen that moves orders across New, Preparing, Ready and Done as storekit does.

Out-of-Stock Log and Morning Digest

What sold out, when and why, with a Slack digest every morning.

Payout Reconciliation Sheet

A ledger that fills itself in on every payout, with a reconciled tick-box and CSV export.

Write a Prompt That Works

The prompt skeleton every recipe uses, and the context block to paste so the AI gets storekit right first time.
The webhook events reference lists every event storekit sends, and each one is a tool waiting to be built:

​
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.
  • 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 works around this with a second printer that your app drives; storekit’s own printing is untouched.

Slack Notifications

No app needed: send any event straight to a Slack channel from the webhooks portal.

Ask an AI Agent

Connect Claude or ChatGPT to your account and ask about sales, orders and menus (beta).

Webhook Events

Every event storekit sends, with example payloads.

Developer Introduction

For the developer you hand this to when a tool outgrows an app builder.