| When | Workshop & client | Chef | Guests | Delivered | Order by |
|---|
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.
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.
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.
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.