How to Handle Meal Customisation for Meal Prep Clients on Shopify

Meal customisation is one of the most requested features by meal prep customers — and one of the hardest to implement well on Shopify. Here's how to build a customisation system that works for both customers and your production team.

What Customers Want from Customisation

Meal prep customers typically want to customise along three dimensions: which meals they receive (from your weekly menu selection); how many portions of each; and dietary preferences (no red meat, extra protein, lower carb). Some customers also want to exclude specific ingredients, which creates allergen management complexity. Your customisation system should support the first two dimensions as standard and handle dietary preferences as structured options rather than free text.

Shopify's Native Limitations

Shopify's standard product variant system is not designed for meal plan customisation. You cannot natively build a system where a customer selects 10 meals from a menu of 20, specifies quantities for each, and checks out as a single order. Custom solutions — either via Shopify apps or bespoke development — are required.

SaltAI's Subscription Customisation

SaltAI's Subscriptions app includes per-delivery meal selection for subscription customers. Subscribers receive a selection email before each delivery cutoff with their current week's meals and the option to swap items from the active menu. Selections are synced to your production plan automatically, eliminating the manual work of reconciling customer selections with production orders.

Managing the Allergen Intersection

Meal customisation and allergen management interact in important ways. If a customer is selecting meals, they need to know the allergen profile of each meal to make safe choices. Your customisation interface should display allergen information for every meal option — not just on the product page but in the selection interface itself.

Setting Up Your Menu Structure for Customisation

Before you can build a working customisation flow, your menu architecture needs to support it. Each meal on your Shopify store should exist as its own product with clearly defined tags indicating its dietary profile — high protein, dairy free, gluten free, low carb, and so on. These tags become the filtering mechanism inside your selection interface. Without consistent tagging at the product level, any customisation system you layer on top will produce messy results that frustrate customers and create errors in your production plan.

Portion sizing is another dimension that needs structure before it can be presented to customers cleanly. If you offer both single-portion and double-portion options, these should be configured as variants rather than separate products, so they stay attached to the correct meal and its allergen data. Customers who want extra portions of a specific meal should be able to select that within the meal card itself, not by hunting through a separate product listing. Keeping portions tied to their parent meal reduces confusion at checkout and makes production summaries far more accurate.

The cadence at which your menu refreshes also affects how you structure products in Shopify. If you run a weekly rotating menu, you need a reliable method for activating and deactivating meals each week without breaking active subscriptions or customer selections. One practical approach is to maintain meals as permanent products and use availability toggles or collection membership to control what appears in the selection interface for any given week. Planning this structure before you configure your customisation app will save you significant rework later.

Building Structured Dietary Preferences Instead of Free Text

Free-text fields for dietary preferences are a support liability. When a customer types "no onions, prefer chicken, not too spicy" into a notes box, you have created an obligation that is almost impossible to fulfil consistently at scale. Production teams cannot reliably parse free-text instructions across dozens of orders, and there is no way to systematically flag when a meal on the menu conflicts with what a customer has written. Structured options — checkboxes, dropdown filters, predefined preference tags — are the only practical approach for any meal prep business preparing more than a handful of orders per week.

The right way to build structured preferences is to map your real menu against the preferences you are prepared to guarantee. If your kitchen can reliably produce a dairy-free version of every meal, offer dairy-free as a preference. If gluten-free requires cross-contamination precautions that you cannot consistently manage, do not offer it as a simple preference — handle it through your allergen declaration process instead. The distinction between a preference and an allergen requirement matters legally and operationally. Your customisation interface should make that distinction visible to customers, not blur it.

Once your preference options are defined, connect them to your menu filtering so that a customer who selects "no red meat" only sees meals that meet that criterion in their selection interface. This is where consistent product tagging pays off directly. If every qualifying meal is tagged correctly, the filter works automatically. If your tagging is inconsistent, customers will either see meals they cannot eat or miss meals they would have chosen. Auditing your product tags every time you publish a new menu is a small operational habit that prevents a significant volume of customer complaints.

Communicating Cutoff Deadlines Clearly

Cutoff deadlines are the operational heartbeat of any meal prep subscription, and poor communication around them is the single most common source of customer frustration. If a customer misses the selection window, they either receive a default box they did not choose or their order is skipped — neither outcome is satisfying without prior warning. Your cutoff communication strategy needs to be proactive, multi-touch, and timed to how your customers actually behave, not just when it is convenient for your production schedule.

Email is the primary channel for cutoff reminders, but timing matters more than most merchants realise. A single email sent 48 hours before cutoff works well for highly engaged customers who check their inbox daily, but it misses the segment who only act on reminders when they arrive the morning of the deadline. A two-email sequence — an initial selection prompt when the weekly menu goes live, followed by a final reminder 24 hours before cutoff — captures a materially higher proportion of active selections and reduces the volume of default boxes you need to pack. SaltAI's Subscriptions app automates this sequence without requiring manual sends each week.

SMS reminders are worth adding once your subscription base reaches a size where missed selections are costing you real operational overhead. Open rates on SMS are significantly higher than email for time-sensitive prompts, and a short message linking directly to the selection portal can recover customers who missed both email reminders. Be transparent in your signup flow that SMS reminders are part of the subscription experience, and give customers the option to opt out if they prefer email only. Clear communication about how the selection process works — including what happens if they miss the cutoff — should appear in your onboarding sequence the moment a subscription is activated.

Translating Selections into a Production Plan

The final piece of the customisation puzzle is the most operationally critical: turning individual customer selections into a production plan your kitchen can actually execute. If you are manually downloading order exports and building a spreadsheet each week, you are creating a process that does not scale and introduces transcription errors that lead to wrong meals being packed. The goal is a system where customer selections flow directly into a production summary without manual intervention between the two.

A production summary for a meal prep kitchen needs to answer three questions clearly: how many portions of each meal are required in total, which customers are receiving which meals, and what the packing configuration is for each order. The total portions number drives your ingredient purchasing and cooking volume. The per-customer breakdown drives packing. These are two different views of the same data, and your system should generate both automatically from the selections it has collected. Exporting a single flat file and manually splitting it into two formats each week is an avoidable source of errors.

Integration between your selection system and your packing workflow also reduces the risk of meals being swapped between orders during packing — a mistake that has serious consequences when allergens are involved. Printed packing slips or a packing screen that displays each order's exact contents, generated directly from confirmed selections, gives your team a reliable reference at the point of packing rather than relying on memory or handwritten notes. Building this integration properly at the start of your subscription operation is far less costly than retrofitting it after you have experienced the errors that a manual process produces.

Launch meal plan subscriptions with per-delivery customisation on Shopify with SaltAI.

Try SaltAI Subscriptions free at saltai.app — no credit card required.