Sell Wholesale Baking Supplies by the Bag, the Allergen and the Lot

Three things set this trade apart. The same ingredient sells by the bag, the case and the pallet. Many ingredients contain a major food allergen that federal law tells the label how to declare. And the bag on the dock has a lot number and a best-by date that the buyer will ask about.

The unit changes with the buyer. A home-based bakery business orders a bag of flour and a case of baking cups. A wholesale bakery orders the same flour by the pallet. A cafe chain orders on a standing schedule for several locations. Each of those buyers expects its own price, its own minimum and its own way to reorder. A storefront built around one unit per product makes the small buyer pay pallet logic or the large buyer place forty line items.

The catalog is wider than the ingredients. A bakery supply house sells flour, sugar, chocolate and leavening, and also decorating supplies, cake boards and boxes, baking cups, parchment, pans and smallwares. Ingredients carry allergen and lot data. Pans and packaging carry sizes and case counts. One product template cannot hold both, and a buyer filtering for nut-free sprinkles should not have to scroll past sheet pans.

Trade pricing is the norm, not the exception. Bakeries, caterers and restaurants buy on account. The price a bakery sees for a case of chocolate can be its contract price, not the list price, and it may be paying on net terms. Shopify's own wording fits this exactly: "B2B catalogs determine the products and pricing your B2B customers can access."

The list is set by law. The FDA says "The major food allergens are milk, eggs, fish, Crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame." The Food Allergen Labeling and Consumer Protection Act of 2004 named the first eight. The FASTER Act then declared "sesame as the 9th major food allergen recognized by the United States," and "The change was effective on January 1, 2023." Baking runs through that list. FDA's own label examples read like a bakery's ingredient shelf: "lecithin (soy)," "flour (wheat)," and "whey (milk)."

The label has two ways to say it. According to the FDA's food allergies page, "The allergen's food source must be declared at least once on the food label in one of two ways." One is in parentheses after the ingredient, with examples such as "flour (wheat)" and "whey (milk)." The other is a "contains" statement next to the ingredient list, for example "Contains wheat, milk, and soy." The law also requires "the type of tree nut (for example, almonds, pecans, walnuts)" to be declared. So "tree nuts" is not enough on its own. The label says which nut.

"May contain" is a different thing. The FDA describes advisory statements such as "produced in a facility that also uses [allergen]" and says "Such statements are not required by law." It adds that they "must be truthful and not misleading." A bakery buyer reading a product page needs to tell the declared allergen from the advisory line. A catalog that pastes the whole label into one text field cannot show the difference.

The bakery is a labeler too. FDA says "FALCPA's labeling requirements extend to retail and food-service establishments that package, label, and offer products for human consumption." A bakery that packages and labels what it bakes builds its own allergen statement from what its suppliers declared. The supplier's allergen data is an input to the buyer's label, which is why it belongs on the product page and not only on the bag.

Every bag has a lot. The lot number and best-by date are printed by the manufacturer, and the buyer receiving a pallet wants to know which lot and which date arrived. When a supplier needs to reach the customers who received a lot, that answer has to come from the order history, not from someone's memory of the dock.

Some bakery items sit on the FDA's Food Traceability List. FDA's Food Traceability Rule sets recordkeeping requirements "for persons who manufacture, process, pack, or hold foods included on the Food Traceability List (FTL)." The Food Traceability List includes shell eggs, nut butters and fresh soft cheeses, with cream cheese and mascarpone among FDA's examples. For nut butters it covers "all forms of nut butters, including shelf stable, refrigerated, frozen, and previously frozen products." For eggs, the list notes that "Pasteurized eggs can be fully exempt" under the rule's exemptions. The list also says the requirements reach "foods that contain listed foods as ingredients, provided that the listed food that is used as an ingredient remains in the same form (e.g., fresh) in which it appears on the list." On timing, FDA proposed extending the compliance date to July 20, 2028, and says a 2026 appropriations act "directed FDA not to enforce the Food Traceability Rule prior to that same date." Whether the rule applies to a given business or food is a question FDA's own Getting Started pages are written to answer. The storefront's part is to keep lot data attached to the order so the records exist.

Units as selling options, rules at checkout. Bag, case and pallet are set up as separate selling units for each ingredient, built during implementation from your item master. Shopify B2B quantity rules then hold each buyer to the right order size. "Minimum quantity rules let you define the fewest number of an item that can be purchased at one time," and Shopify's own example for increments reads "if your products are boxed in multiples of 10, then you can set your increment rule to 10." Quantity rules "are re-validated in checkout," so a case of 12 cannot be ordered as 7.

Price breaks for the bigger order. "Volume pricing lets you offer additional price breaks to customers when they purchase larger quantities," with "up to 10 price breaks per product which are applied to each variant." The price break quantity must be "a multiple of the increment that you set in your quantity rules." A wholesale bakery sees its pallet price. A home-based bakery business sees its bag price. Both come from catalogs assigned to "companies and company locations," in Shopify's words.

Filters that match how bakeries shop. Ingredients filter by type, brand, pack size and allergen. Pans, boards and packaging filter by size and case count. Separate product templates for ingredients and for bakeware and packaging are built during implementation.

Allergens as data, not a paragraph. Each ingredient carries the nine major food allergens as separate fields, the tree nut type where it applies, the "contains" statement and any advisory statement, kept apart. Those fields are built during implementation and filled from the manufacturer's label data. A buyer can filter for products whose declared allergens exclude peanuts and tree nuts, and the advisory line still shows on the page.

The label stays the source. Uncap does not test products or assess allergens. The storefront shows what the manufacturer declared, from your item data, so the product page and the bag say the same thing.

Lot and date on the order line. Lot numbers and best-by dates come from your ERP or warehouse system at fulfillment and are written back to the order, built during implementation. The buyer sees which lot shipped in its order history. Your team can answer which customers received a given lot from the same record. The lot, catch weight and expiry patterns shared with the parent food distribution build are covered on the food distribution page linked below.

Date rules per account. An account that will not accept product inside a set number of days of its best-by date gets that rule applied at ordering, built during implementation from your ERP data.

Reorders in Uncap Portal. In Uncap Portal, each buyer sees their assortment and pricing, with reorder lists and order history a click away, so the weekly flour and sugar order is one click from being next week's. Accounts are real multi-user accounts with roles and permissions, with budgets, approvals and limits per user. NET terms, invoices and payments sit in the portal. In Shopify, "Payment terms define how long a company has to pay for an order," with net terms from net 7 to net 90.

Volume and contract quotes in Uncap Quotes. For the pallet order, the new cafe group or the seasonal contract, Uncap Quotes applies negotiated prices, tiers and volume breaks automatically, sends exceptions to the right approver and generates clean, shareable quote documents. Quotes carry validity windows and a full revision history, and approved quotes turn straight into Shopify orders.

One record for price, stock and lot. Uncap Connect is the real-time data layer between Shopify and your ERP: inventory, orders, customers and pricing move the moment they change, not in an overnight batch. It starts at $8,000 for onboarding and then a flat $390 per month. Field-level rules decide which system wins, every time, and failed sync events are isolated, surfaced in a live console and replayable, so nothing is silently dropped. Connect has native support for Shopify B2B companies, locations, catalogs, price lists and payment terms. Syncing allergen fields and lot data from your item master is configured during implementation. Integration can also run as a managed iPaaS integration.

• Bag, case and pallet units. Separate selling units per ingredient, built during implementation, with Shopify quantity rules for minimums and increments.
• Volume pricing. Up to 10 price breaks per product in Shopify B2B, on catalogs assigned to each company and location.
• Allergen fields. The nine major food allergens, tree nut type, the "contains" statement and advisory statements as separate fields, built during implementation from your label data.
• Allergen filters. Buyers narrow to products whose declared allergens exclude what their kitchen avoids.
• Lot and best-by on the order. Written back from your ERP or warehouse system at fulfillment, built during implementation.
• Date rules per account. Minimum days to best-by applied at ordering, built during implementation.
• Trade accounts and reorders. Uncap Portal with each buyer's assortment and pricing, reorder lists, order history and NET terms.
• Volume quotes. Uncap Quotes with approvals, validity windows, revision history and one-click conversion to an order.
• ERP sync, Connect or managed iPaaS. Inventory, orders, customers and pricing kept current between Shopify and the ERP.

The line between product and build, in writing. Quoting and approvals ship in Uncap Quotes, trade accounts and reorders in Uncap Portal, and ERP sync in Uncap Connect. Bag to pallet units, allergen fields and filters, lot and best-by on the order and date rules per account are built during implementation from your data. The scope says which is which.

Credentials you can check. Uncap is a Shopify Platinum Partner.

Scoped before it is built. The Uncap Blueprint is a $7,500 fixed-price, 4-week Shopify migration plan. It covers solution architecture, a data migration taxonomy, an ERP integration audit, UX and flow prototyping and a replatforming risk register, and the fee is credited 1:1 toward implementation. For a baking supply seller, that architecture work can cover the unit model, the allergen and lot fields and the ERP integration. You walk with everything you need to brief any agency or your in-house team.

This page sits under food distribution ecommerce, which covers catch weight, lot and expiry, cold chain and contract pricing for food manufacturers and distributors. This page goes down to baking: ingredients sold by the bag and the pallet, allergen statements, and the bakeware and packaging sold beside them. For containers and storage sold to kitchens, see food storage and containers. For distributors whose product is the supplies around the food, see restaurant and hotel supply. For the drinks side of a cafe's order, see beverage distribution, which covers route delivery, container deposits and licensed accounts. For the ordering and traceability terms, see the glossary entries for lot number and case pack, the guide to order minimums, case packs and MOQs on Shopify, and what food distributors should evaluate before building an online channel. For the ERP side, see the SAP Business One, Sage X3 and NetSuite integrations or the full list of ERP integrations.

Bring two things. The first is one ingredient's item record with its bag, case and pallet units and its allergen statement. The second is the last lot question a customer asked your team. Together they show how much of your catalog is already data and how much still lives on the bag.

Talk to Our Experts about your baking supply catalog, or start with a Blueprint if what you need first is the unit model, the allergen fields and the ERP integration written down and costed.