Recipes

One recipe for each job. Each says what it does and who it is for, gives the steps with their commands, and says what is refused.

• A manager's AI assistant on our MCP server
• A till key that asks an AI model
• Approvals by workflow, with a nightly export
• Approvals across stores
• Feed a data warehouse from the shop
• Set a shop up with no code
• Building a connected app
• A button on a Desk record (a Desk action)
• Set up fifty stores from one file
• Reading iVendNext's events reliably
• The hosted sandbox site
• Making the integration user for a connected app
• Shipping your own data in a manifest
• Prove your app moves no money: the money kit
• Your own screen inside the shop's frame (a partner page)
• A till key: one pure core, answered from your own server
• A standalone portal with "Sign in with iVendNext"
• A receipt laid out for your market
• The customer's release gate
• "Sign in with iVendNext"
• Keep a customer's own system in step with iVendNext
• Receiving iVendNext webhooks safely