Skip to content

Recipes

Reference3 minPractitioner

A recipe builds one whole process, start to finish. Each one lists the modules and fields, the relations, the forms and views, the workflows, the record page buttons and the permissions, then suggests what to change for your own business. Each recipe also links to the page on beezr.io that tells the same story from the customer’s side.

Recipes assume you have done the Quickstart. They tell you what to build and why. For the clicks, they link to the how-to pages.

Which recipe should I start with?

Section titled “Which recipe should I start with?”
Procurement with a supplier portalVendors, RFx events, bids, contracts, purchase orders and invoices raised after delivery is accepted.An approvals hubPayment requests routed by amount, chased every morning, signed and posted to finance. Collections follow-upA missed payment opens a case by API, promises are watched, agencies see only their cases.Production orders from an online storeA Shopify order arrives by webhook, becomes production jobs, and deducts materials from stock. Loan applications and repayment schedulesAn approved application becomes a contract, and a Custom function solves the repayment schedule.

How are recipes different from tutorials?

Section titled “How are recipes different from tutorials?”

A tutorial holds your hand through one small build. A recipe assumes you know the pieces and shows how they fit together for a process that exists in real companies. Expect a recipe to take from half a day to a day, and to leave you with a working application you can adapt.

To check your setup as you build, the Troubleshooting pages cover the common causes.

What's next

Procurement with a supplier portalBuild procurement from vendor to invoice: RFx events, bids, contracts, purchase orders and delivery acceptance that gates invoices.An approvals hubBuild an approvals hub: payment requests routed by amount, chased daily, signed on screen and posted to a finance system.

Last checked