| When | Workshop & client | Chef | Guests | Order status | Assigned to | Order by | Schedule delivery |
|---|
Everyone at an event is usually ordered from the same store, by the same person, on the same day. Set it once and apply it to every guest.
A spreadsheet from the client, or anything with one guest per row. Drop a CSV below, or copy the cells straight out of Excel and paste them in. Columns are matched by their headings — first name, last name, email, phone, address, apt, city, state, zip, country — and a single Name column is split in two. Nothing is added until you have seen what it read. A guest already on this event is found by their email, and the file fills in or corrects their details — so a corrected sheet can simply be uploaded again. An empty cell never clears anything.
Or paste the rows, headings included:
A sheet with one row per parcel: who it is for, and the tracking number. Drop an Excel file or a CSV below, or paste the rows. Columns are matched by their headings — name (or first and last), email, and tracking number. Full UPS links work as well as bare numbers. Nothing is written, and nobody is told anything, until you have seen what it matched.
Or paste the rows, headings included:
For somebody the address link never reached — phoned in, or an event booked before the link existed. It goes on the same guest list the form writes to, so there is still only one of it.
Kept for 90 days. A guest is only ever contacted on the channels they ticked when they sent their address — see Rules / Options for the wording every message starts from, and Guest updates at the top of this event for whether it sends them without anybody pressing anything.
Whether an event tells its guests by itself is set on the event, above its guest list — on unless somebody unticks it, one client at a time. Everything else is a person pressing Tell them on a row, or Tell them all on the event, and reading the message first.
Either way, a guest is only ever contacted on the channels they ticked when they sent their address, never more than five times for one event, and never after replying STOP. An organizer can turn it off for their whole event.
Reword these if you like. Rockoly: and Reply STOP to end. are added for you and cannot be edited out — a message with no sender's name and no way to stop is one a carrier is entitled to block, and it would be blocked for every guest at once.
These are the kits the desk orders from — ingredients, products and prices. The recipe a chef is briefed with, and the copy an organizer passes on to their guests, are PDFs kept on Recipes.
Drop an .xlsx here, or .
One sheet per kit, read exactly as the master workbook is: the row carrying an
Ingredients header is found wherever it sits, and the columns are read off it.
Up to about 3.5 MB — the whole master workbook goes through
scripts/import-ofd-recipes.mjs instead, because only that can pull out the class handouts.
Drop a PDF here, or .
One PDF per session, up to 12 MB — export it from Canva or Slides as a PDF first. The title and length are read off the file's name (Chef Notes - Spanish Paella (60').pdf) and can be corrected before it is added.