Fast Nutrition — Meal Prep (WooCommerce Plugin)

A full meal-prep ordering system for the Fast Nutrition website, built on the latest WooCommerce + WordPress Blocks stack. It lets customers build meals (Protein + Carb + Greens, or two greens instead of a carb, or a pre-made set meal), attaches macros to every selection, handles quantity bundles and per-line-item add-ons, collects delivery / collection preferences via postcode-aware profiles, and gives kitchen staff a per-day prep dashboard and a printable prep sheet.

Requirements

Installation

The repository ships with vendor/ (composer dependencies) and assets/build/ (compiled blocks) already built, so no build step is required for production use.

1. Place the plugin in your WP install:

   wp-content/plugins/fastnutrition-mealprep/

2. Activate the plugin in WP Admin → Plugins. Activation creates three DB tables (fn_delivery_profiles, fn_blocked_dates, fn_prep_cache) and seeds the Ingredient Type and Allergen taxonomies.

That's it. If you're developing on the plugin and need to rebuild assets, see the Development section below.

Development (only if you're changing the code)

composer install                  # dev deps incl. PHPUnit + PHPCS
npm install                       # JS deps
npm run build                     # one-off build
npm run start                     # watch mode

Development scripts

npm run start        # watch mode for JS/CSS
npm run lint:js      # ESLint via @wordpress/scripts
composer test        # run PHPUnit
composer lint        # run PHPCS against WordPress + WooCommerce standards

Post-install checklist

Everything lives under the Meal Prep top-level menu in WP admin (the only per-product settings are the three meta boxes/tab on the Edit Product screen, which is the right place for them).

1. Meal Prep → Ingredients — create Proteins, Carbs, Greens, and Set Meals. Set meals are complete pre-made meals; they use the same Ingredient screen with Ingredient Type = Set Meal (see the sidebar taxonomy on the edit screen). A "Set Meals" shortcut submenu filters this list to just set meals. Each ingredient carries macros and an optional price modifier.
2. Meal Prep → Ingredient Types / Allergens — manage the taxonomy terms if you want to add e.g. a "Nut Free" diet tag.
3. Meal Prep → Delivery Profiles — create profiles (a group of postcodes + days of the week + time windows). Delivery profiles match by postcode; collection profiles apply to everyone. The dashboard widget flags postcode overlaps and WC shipping zones that aren't covered by any profile.
4. Meal Prep → Blocked Dates — one-off closures (Christmas, training days). Disables every slot on every profile for that date.
5. Meal Prep → Settings — toggle the multi-step checkout, convert a legacy shortcode checkout page to Blocks in one click, or auto-create a Macro Calculator page.
6. Meal Prep → Prep Dashboard / Prep Sheet — daily kitchen views.
7. Edit Product (any simple Woo product) — the extras live on the product itself because they're product-specific:
   • Meal Builder tab — enable the builder, choose tier (standard/bulk), allow double greens, allow set meal mode, restrict allowed ingredients.
   • Meal Add-ons meta box — per-line-item extras (e.g. +£1 boiled eggs).
   • Quantity Bundles meta box — e.g. 10 / £35, 15 / £50. Applies only to this product ID.

Where do I add Set Meals?

Meal Prep → Ingredients → Add Ingredient. In the right-hand sidebar, under Ingredient Type, tick Set Meal. Set the macros for the complete meal and (optionally) a price modifier. Then on each meal product that should offer set meals, tick Allow set meal mode in the Meal Builder tab and select which set meals are allowed.

Checkout — how it works now

You do not need to edit the checkout page or drop blocks into it. As long as the checkout page uses the standard WooCommerce Checkout block (the default for fresh stores since WC 8.x), the multi-step flow applies automatically.

• If your checkout page still uses the old [woocommerce_checkout] shortcode, go to Meal Prep → Settings and click Convert checkout page to Blocks. That replaces the shortcode with the block and keeps a WP revision of the old content.
• If you'd rather keep the single-page Woo checkout, turn off Enable multi-step checkout under Settings.
• The slot picker is auto-injected between the shipping address and payment blocks — no manual block placement required.

Third-party checkout plugins

The multi-step flow is a UI layer on top of the native WC Checkout block — we don't remove or replace anything. Any plugin that registers its UI against the Checkout block (upsells, cross-sells, extra fields, order bumps) will continue to render. Unknown blocks fall into Step 1 (Your details) by default. If a third-party plugin's UI needs to appear during Payment, add its CSS selector to the STEPS[2].matchers array in assets/src/blocks/multi-step-checkout/view.js and rebuild.

Do I need to create any pages?

No. The plugin uses the existing WooCommerce Cart and Checkout pages. If you want a dedicated Macro Calculator page, the Settings screen has a one-click button to create one; otherwise the [fn_macro_calculator] shortcode (or the Macro Calculator block) works on any page/post. Logged-in customers automatically get a Favourites tab added to their My Account page.

Feature overview

Meal builder (on product pages)

When a simple product has "Enable meal builder" ticked, the default Add-to-Cart button is replaced with the builder UI:

• Build mode: pick a Protein, Carb, Greens. Toggle "double greens" to swap the carb for a 2nd greens.
• Set meal mode (if enabled): pick a pre-made set meal.
• Per-line add-ons (e.g. boiled eggs +£1).
• Live macro total.
• Server-side validation rejects disallowed combinations.

Bundle pricing

Per-product quantity tiers (e.g. 10 for £35). Applies only to matching product IDs so desserts and other non-bundle products are untouched. The largest tier that fits is chosen; remaining qty is priced at base. Each cart line shows an effective per-meal price (e.g. 10 for £35 (~£3.50 each)).

Add-ons

Per-line-item. Each meal instance in the cart carries its own add-on selection and the price flows through to the order and emails.

Delivery / Collection profiles

A profile groups postcodes with the days and time windows you cover. Collection profiles ignore postcodes. The dashboard widget flags two conflict types:

• Postcodes that appear in more than one delivery profile (resolved by priority).
• WooCommerce shipping zones whose postcodes are not covered by any profile.

Blocked dates

Site-wide dates with an optional reason. Blocked dates disable every slot regardless of method or postcode.

Multi-step Blocks checkout

fastnutrition/multi-step-checkout wraps the native Woo Checkout block and presents 3 steps with nav buttons:

1. Your details (contact + shipping address)
2. Delivery or collection (postcode-aware slot picker)
3. Payment (payment methods + order summary)

The slot is persisted to the order via the Store API extensionCartUpdate — _fn_fulfilment is written on the order when it is placed.

Macros

Every ingredient carries {kcal, protein_g, carbs_g, fat_g, fibre_g}. At order time the snapshot is stored on each line item (so edits to ingredients later never change past orders) and the totals are printed at the bottom of the customer email.

Macro calculator

Block: fastnutrition/macro-calculator · shortcode: [fn_macro_calculator].

• Pulls ingredients from the REST API.
• "Add custom ingredient" creates a locally-stored (and optionally account-synced) entry.
• Optional daily-target progress bar.

Kitchen prep dashboard

WooCommerce → Meal Prep → Prep Dashboard.

• Filter by fulfilment date.
• By day view — aggregated ingredient totals ("15 portions of asparagus needed").
• By order view — table of orders with their individual selections.
• Rebuilt on order status change, backed by fn_prep_cache for fast dashboard loads.

Printable kitchen prep sheet

WooCommerce → Meal Prep → Prep Sheet. Three sections: Ingredient totals · Per-order pick list (with tick-off checkboxes) · Delivery run sheet grouped by profile and postcode. Print via the browser or download as a server-side PDF (Dompdf).

Customer favourites

Logged-in customers can save meal combos to their account and re-add them with a single click from My Account → Favourites.

REST endpoints (namespace fastnutrition/v1)

Store API extensions (namespace fastnutrition-mealprep):

• Cart endpoint: extensions.fastnutrition-mealprep.macros — running macro totals.
• Checkout endpoint: extensions.fastnutrition-mealprep.fulfilment — selected slot.
• Update callback: set_fulfilment — writes the slot to the WC session.

Directory layout

fastnutrition-mealprep/
  fastnutrition-mealprep.php      # bootstrap, HPOS + Blocks compatibility
  composer.json                   # PSR-4 autoload + Dompdf
  package.json                    # @wordpress/scripts build
  src/
    Plugin.php
    Install/Activator.php
    PostTypes/Ingredient.php
    Taxonomies/IngredientType.php
    Taxonomies/Allergen.php
    Products/{MealProduct,AddOnMeta,BundleMeta}.php
    Cart/{Selections,BundlePricer,AddOnPricer,OrderItemMeta}.php
    Macros/{Calculator,ShortcodeCalculator,CustomIngredientStore}.php
    Delivery/{Profile,ProfileResolver,BlockedDates,SlotAvailability}.php
    Checkout/{MultiStep,StoreApiExtensions}.php
    Admin/{MenuRegistry,PrepDashboard,PrepSheet,ProfileAdmin,BlockedDatesAdmin,BundleAdmin,ConflictsNotice}.php
    Account/Favourites.php
    Rest/RestController.php
    Support/AssetManager.php
  assets/src/blocks/
    meal-builder/
    macro-calculator/
    multi-step-checkout/
    slot-picker/
  assets/build/                   # produced by `npm run build`

Security notes

• Every admin action is capability-checked (manage_woocommerce) and nonce-verified.
• Customer-facing REST endpoints use is_user_logged_in() where writes are involved; public reads are limited to data that is already rendered on the shop.
• Order item selections are re-validated server-side on add-to-cart — no client-only trust.
• The ingredient CPT is registered as public => false so it never appears in sitemaps or search.

Known limitations / next steps

• The multi-step checkout navigation is implemented client-side by toggling classes. If your theme adds additional Woo blocks inside the checkout fields block, you can extend the STEPS array in assets/src/blocks/multi-step-checkout/view.js.
• Slot capacity is counted against paid/processing/on-hold orders. If you need to count abandoned checkouts too, extend SlotAvailability::count_booked().
• The Favourites "Save" button is exposed via REST; the product page UI currently adds a line in the builder via the block script (customize as needed).
• Translation: a languages/ directory is provided; generate a .pot with wp i18n make-pot . languages/fastnutrition-mealprep.pot.

License

GPL-2.0-or-later — same as WooCommerce and WordPress.