The label operations backend for online food brands

Fast label iteration between product drops

Change the recipe, watch the label update. Move nutrition math out of Excel and into a tool that enforces § 101.9 rounding.

Product-page-ready label assets

Export a PDF, PNG, or SVG for your product listing page. High-DPI vector for retail cartons; PNG for Amazon A+ content.

Managing labels across many SKUs

Every recipe saves to the cloud. Tag by product line, filter by launch status, duplicate a base recipe for a new SKU.

Shipping across a state line changes which rules you are under

A lot of DTC food brands start in a home kitchen under a state cottage food law, selling locally, entirely legitimately. Then the store goes live and the first order ships to another state.

At that moment you are in interstate commerce. Cottage food statutes are state law and generally do not reach beyond the state line, so the framework you were operating under stops applying and the full federal packaged-food requirements take over: Nutrition Facts under § 101.9 unless an exemption covers you, ingredient statement under § 101.4, net quantity under § 101.7, name and place of business under § 101.5, and allergen declaration.

Nothing warns you when this happens. The checkout does not know, and neither does the customer. It is worth deciding deliberately whether you are a local cottage food business or a national packaged-food business, because the labeling obligations are genuinely different and only one of them survives a shipping label.

Your product page is advertising, not labeling - and a different agency reads it

The FDA governs what is on the package. The FTC governs how you advertise it: your product detail page, your email flows, your paid social, and what your affiliates and influencers say on your behalf.

This catches DTC brands specifically, because for you the listing is the storefront and it gets written by marketing rather than by whoever handled the label. A claim that would never have made it onto the pack - "clinically proven," "burns fat," "boosts immunity" - routinely lands in the product description or an influencer script, where a different regulator with a different standard is reading it.

The practical rule: hold your marketing copy to the same claim discipline as your label. If it could not go on the package, it should not go in the ad.

Allergens carry more risk without a retailer in the chain

Selling through a grocery buyer means someone else's QA process reviews your label before it reaches a shelf. Selling direct removes that layer entirely - your allergen declaration goes from your spreadsheet to a customer's kitchen with nothing in between.

Undeclared allergens are consistently among the leading causes of food recalls in the US, and the usual mechanism is mundane: a supplier changes a formulation, or a shared production line introduces cross-contact, and the ingredient statement never gets updated because updating it is manual.

Generating the "Contains:" line from the recipe rather than maintaining it by hand removes the failure mode. Change an ingredient and the allergen declaration changes with it - including sesame, which the FASTER Act added as the ninth major allergen and which appears in more products than most brands assume.

Marketplace listing requirements

Amazon, Walmart Marketplace, Thrive, and most grocery-delivery platforms require a legible image of the Nutrition Facts panel and ingredient statement on the product detail page, and listings get suppressed when the image is missing or unreadable. Their image specifications are their own, separate from anything the FDA requires.

Export high-DPI PNG for marketplace imagery and A+ content, and vector PDF, SVG, EPS or AI for the physical carton - same panel, from the same recipe, in whatever the channel asks for.