Selling food online is a logistics promise with a storefront attached

For anything chilled, frozen or freshly made, the delivery slot is not a shipping option — it is a condition of the sale. The date and window need to be chosen before checkout completes, capacity per slot has to be enforced so you cannot sell more deliveries than you can make, and cut-off times must be visible rather than discovered. Stores that treat this as an afterthought generate cancellations and refunds that no marketing spend can offset.

• Slot selection before payment, not after
• Capacity limits per slot, enforced automatically
• Cut-off times stated clearly on the product page
• Postcode or zone checks before the basket is built

Ingredient lists, allergen declarations, nutritional information and storage instructions have to be accurate, present and easy to find, because customers make health decisions from them. Structure this data as fields on the product rather than as free text buried in a description, so it displays consistently, can be filtered on, and can be updated without editing prose. Recipe or batch changes need a process that updates the product data at the same time as the label, not weeks later.

Available means something different when a product has a use-by date. Stock levels need to reflect what can actually be dispatched within its shelf life, and products with short lives may need to disappear from sale before they physically run out. Batch and date tracking are worth the effort in this category because the alternative — shipping something that arrives too close to expiry — produces refunds and reviews that follow you for months. Inventory sync covers the general mechanics; the perishable case simply raises the stakes.

Food and drink has some of the highest repeat rates in retail, and most of that revenue is decided by how easy it is to buy the same basket again. Order history that becomes a one-tap reorder, subscriptions for staples, and a saved-favourites list do more for annual revenue than most acquisition work. The subscription model fits this category unusually well, provided the self-service side — skip, pause, change date — genuinely works without contacting support.

Many food businesses sell within a delivery radius, ship nationally only for shelf-stable lines, or face restrictions on what can cross borders — alcohol in particular carries licensing and age-verification requirements that vary by jurisdiction. The storefront needs to know which products can go where before the customer builds a basket, and to say so plainly rather than failing at checkout. This is general information rather than legal advice: the specific rules for your products and destinations are a question for a specialist.

Products, pricing, stock, orders, customers, tax and payments remain in WooCommerce, along with your slot and route logic if it already runs there. The storefront layer changes: how quickly the catalogue loads on a phone in a kitchen, how the slot chooser presents capacity, how ingredient data is displayed, and how few taps a repeat order takes. Those are exactly the areas where a heavy theme costs a food store money.

If you sell shelf-stable products nationally with no slot logic, standard ecommerce advice applies and none of this complexity is needed. The work here earns its cost when delivery windows or perishability are central to your operation, when allergen data is being maintained by hand across a spreadsheet and a website, or when reorder friction is visibly capping the repeat revenue the category should be giving you.