Decide what the checkout must know
In food, the checkout carries more weight than in any other category we work in. It has to establish where the customer is, whether you can serve that postcode, which window they will be present for, whether the basket needs chilled handling, and in alcohol whether they are old enough to buy.
Each of those is a constraint from the operation, surfaced to the customer at the moment of decision. Getting it wrong does not produce a bad conversion rate — it produces refunds and wasted product.
Bundles are a data problem
A subscription box or mixed case is not one product. It is a container whose allergens, nutrition and shelf life are a function of what is inside it this cycle.
Modelling it that way means those values stay correct when contents rotate. Modelling it as a single product with manually maintained attributes means they are correct until the first rotation and wrong thereafter — which, in this category, is the kind of wrong that matters.
Where this sits
The storefront is eCommerce development, the allergen and nutrition structure is product data, and connecting delivery windows to real carrier and warehouse capability is integration work.