A food ordering product type gives WooCommerce a reusable model for menu items while keeping customer meal choices separate from dish information. Editors maintain ingredients, preparation, serving details, and availability consistently; customers choose only the options required for their order.
This guide builds a Prepared Meal model with Custom Product Type for WooCommerce.
Define the menu-item model
A Prepared Meal is a WooCommerce product with stable ingredients, preparation, serving information, meal properties, and availability details, plus optional choices supplied by the customer.
This definition keeps the dish record separate from one customer’s spice preference or preparation note.
Separate menu data from customer choices
| Value | Structure |
|---|---|
| Ingredients and preparation | Food Details fields |
| Serving size | Product field or commercial version as appropriate |
| Cuisine or menu section | Taxonomy or category |
| Customer spice choice | Customer option |
| Customer note | Customer text |
| Preferred date | Booking-oriented input when required |
Choose fields that improve ordering
Every public field should answer a practical customer question:
| Customer question | Field |
|---|---|
| What is included? | Ingredients |
| How large is the meal? | Serving Information |
| How is it prepared? | Preparation Method |
| How long does preparation take? | Preparation Time |
| Does it match a dietary property? | Controlled meal field |
Step 1: Create Menu Item and Menu Items
- Go to WooCommerce > Product Types > Add New.
- Create Menu Item and Menu Items labels.
- Select an available product-page layout, or keep the default WooCommerce layout.
- Enable Custom Taxonomy for a dedicated menu hierarchy when useful.
- Choose Display In Shop and add a concise badge such as Prepared Meal.
Step 2: Build the Food Details tab
Enable Back-end Fields and Admin Fields, then set Admin Fields Tab Label to Food Details.
| Field | Type | Example |
|---|---|---|
| Preparation Time | Number | 25 |
| Serving Information | Text | Serves one |
| Meal Type | Select | Main course |
| Vegetarian | Checkbox | Yes |
| Preparation Method | Radio | Freshly prepared |
| Ingredients | Textarea | Rice, vegetables, herbs |
Step 3: Display decision-making information
Enable Show In Front for ingredients, serving information, preparation time, and meal properties. Position essential facts before Add to Cart or in the Single Product Summary.
Build an effective menu page
- Use an accurate, well-lit product image.
- Describe the meal and its main appeal.
- Show ingredients, serving information, and preparation facts.
- Present the price and purchase action.
- Offer only the customer choices available for that dish.
Keep the product description appetizing and benefit-led. Use Food Details for facts customers need to scan across several menu items.
Step 4: Add customer meal options
- Spice level through a dropdown or radio choice.
- Optional extras through checkboxes.
- Preparation note through customer text.
- Delivery or collection date when the workflow requires it.
Stable dish facts remain in Food Details. Order-specific preferences belong to the buyer-input layer.
Use versions only for real menu offers
Small and large meals can be purchasable versions when they have different prices or commercial data. Spice level can remain a customer option when it personalizes one meal without creating a separately managed product version.
Ingredients should remain product facts. A customer request to remove or add an ingredient belongs to the order input.
Keep the order form short
Do not ask customers to confirm information already stated in Food Details. Collect only choices the kitchen can fulfill and notes the team will use. Controlled dropdowns and checkboxes are preferable when the options are fixed.
Step 5: Test the first menu item
- Add an appetizing title, description, price, and accurate image.
- Select Menu Item as the product type.
- Complete Food Details.
- Add only necessary customer options.
- Preview the page and purchase controls on mobile and desktop.
A strong menu model reduces repeated formatting and gives customers comparable information across dishes.
Final food product QA
- The image and description accurately represent the meal.
- Ingredients and serving information are complete.
- Meal options match what the kitchen offers.
- Variations represent real commercial versions only.
- Customer notes are not used for stable product facts.
- The mobile ordering path is easy to complete.
Maintain consistency across the menu
Use the same serving, preparation, and meal-property labels across every menu item. Review customer notes to identify choices that should become controlled options, and remove options the kitchen no longer fulfills.
When availability or preparation changes, update the authoritative Food Details value rather than editing several repeated paragraphs. This keeps the menu easier to maintain and reduces conflicting information during busy ordering periods.
Train every menu editor on the approved vocabulary.
Review customer feedback and refine unclear meal labels before expanding the menu further.
Use Custom Product Type vs Product Add-Ons to separate menu facts from meal customization.
Use the product type vs add-ons guide to separate menu facts from customer choices, then apply the custom field workflow to build the store-managed data layer.
Frequently asked questions
Should ingredients be customer options?
No. Ingredients describe the menu item. A customer removal or extra request is order-specific input.
Should meal sizes be variations?
Use a purchasable-version structure when sizes have real commercial differences such as price or SKU.
Can menu items have their own taxonomy?
Yes. Custom Taxonomy can provide a dedicated hierarchical menu structure.
