You quote each event per guest, and Magpie takes the deposit at signing. You plan the prep from your recipes.

A proposal has a cover, the menu, pictures of past events, a timeline and your terms. Each line has a quantity, a unit such as guest, a price and a tax rate. Saved sections and your price list keep the dishes and prices you quote again. Each recipient gets their own link. They need no Magpie account to read it, ask questions, choose and sign.

Yes. A line priced per guest can let the client change the quantity. You set the fewest guests, the most and the steps you allow. Their page works out the totals again each time they change it. The totals they accept are the ones their invoices use.

Yes. A pricing section can offer 2 to 4 menus as packages, and you can mark one Recommended. Each has a name, a description and its own lines. Extras such as a bar or a late-night snack go in their own pricing section. Before accepting, the client chooses a package and can add or remove extras.

The first payment in the proposal's schedule can be a deposit due on acceptance. You set it as a percentage or an amount. When the client signs, its invoice will be issued. They pay it by card, into your Stripe account. Magpie adds no fee, and Stripe's processing fee is taken from the payment.

A payment can be due on a date, or a number of days after acceptance. It can be a percentage or an amount. Its invoice will be issued and emailed then, with reminders until it is paid. The final payment takes whatever is left when you bill it. The invoices then add up exactly to the accepted total.

Yes, with an invoice of its own. An accepted proposal keeps the choices and totals that were signed. You invoice the extra guests from the client's contact, at the same price per guest. It will be emailed with a Pay online button. The contact lists it with the proposal's invoices.

Yes. A client can ask about the whole proposal or one section, or request changes. Your reply will be emailed to them. When you revise it, the next version is sent with your note on what changed. Earlier versions stay readable.

Yes. Each recipient either signs and accepts, or reads only. The event planner can read the proposal and ask questions without signing. Every signer signs, in any order, before the proposal is accepted. A proposal goes to up to 20 recipients.

Yes. You can require approval for every proposal before it is sent. It can also apply only above a one-time total or a discount you set. The approvers can approve it or ask for changes. Any change after approval will ask for approval again.

They come through an enquiry Form with the questions you choose. It can ask for the date, the number of guests and dietary needs. Anyone with the link can answer without signing up first. Magpie will email you each response, and a summary counts the answers to each choice. You can download every answer as one CSV file.

Yes. A tasting can be a service on your booking page, with its length, location and chefs. The client chooses a free time on the page. They get a confirmation email with a link to reschedule or cancel. The booking will add an event to the chef's calendar.

Each recipe lists its ingredients, in their units or packs, and any recipes inside it. It has the method, how much it makes, how long it keeps, storage and allergens. Changes stay a draft until you or a manager put the new version in use. You and your managers see what each recipe costs, from its ingredients' average cost. Employees and shift leads do not see costs.

Yes. You plan each recipe's batch for the event's day: how much, and who makes it. Magpie lists what the open batches need against stock not set aside for other batches. Starting a batch sets its ingredients aside. Recording what was made takes what was used out of stock, scaled to the amount made.

Yes. Each fridge or cold room, freezer, hot holding, cooking and cooling can have a temperature point. Each point has the target range and critical limits you set. A reading out of range will open an incident with what to do next. You can download the readings as a CSV file, each with who recorded it.

A load-out checklist can be a routine that runs only when someone starts it. It can have ticks, temperatures at your points and a photo. Someone starts it from Today before each event. A failed check can ask for a note and report an incident. The completed checklist keeps every answer.

Each supplier lists the items it sells, in its packs and at its prices. Magpie turns what is running low into an order for each supplier. You email it from Magpie, or mark it as sent. Receiving the delivery will add it to stock at the price charged. Anything short is kept under Differences.

Yes. You bill the company's contact with line items and a tax rate for each line. With the Customer tag, its payment terms and billing address fill in the draft. Sending will email the PDF with a Pay online button, with reminders until it is paid. You can record a bank transfer by hand, in full or in part.

Yes. You make an invoice with the month's lunches, then make it recurring. Magpie will issue and email an invoice with the same lines every month. Each has its Pay online link. You can change the lines, pause the schedule or end it.

You list the week's meals in your online shop, with options such as portion size. A long text field can ask for dietary notes, and each order shows the answer. The menu can go live automatically at the time you choose. Buyers choose pickup or one of your local delivery days. They pay into your Stripe account, with no Magpie fee.

Yes. People you invite to the team see their published shifts under My shifts. When you publish, they get one notification listing what changed. They can swap a shift with a coworker. Anyone else who works an event can be given shifts with only a name.