Magento for Bakery + Pastry

Different jobs, three different tools.

• Goldbelly is a marketplace, not a platform. You list your bakery on goldbelly.com, they handle fulfillment + marketing + customer service, they take ~25-35% commission. Magnolia Bakery, Levain Bakery, Tatte and ~1,200 other bakeries use it as a ship-nationwide channel — not as their own site. Goldbelly owns the customer.
• Toast Online Ordering is bolted onto Toast POS. Best for single-location bakeries doing walk-in + light online pickup + maybe DoorDash hand-off. No real B2B layer, no custom-cake configurator, no subscriptions, no national frozen ship. Ceiling hits around $1-2M online GMV.
• Magento + Hyvä is your own platform. You own customers, own the configurator, own subscriptions, run B2B wholesale + DTC on one stack, and list on Goldbelly as one of your channels (not the only channel).

The right answer for most $1M+ bakeries: Magento as the order-of-record + Goldbelly as a national-ship channel + Toast at the counter. Each does what it’s good at.

Both. They’re commodity APIs at this point, and the right pattern is multi-carrier failover.

DoorDash Drive — widest US coverage, best for suburban + secondary metros. Per-delivery cost $7-12 depending on distance + tier. Insulated cooler-bag option for refrigerated. API returns a quote + ETA in <800ms.

Uber Direct — stronger in NYC, SF, LA, Chicago + EU/UK metros. Per-delivery $8-14. Better real-time tracking UX (Uber-style map). Allows scheduled deliveries (book Tuesday 2pm window for a Tuesday 10am order).

Magento integration is two webhooks: get quote on cart, create delivery on order placement. ShipperHQ orchestrates the carrier choice based on ZIP + product cold-chain tag + day-of-week. If DoorDash returns “no driver available,” failover to Uber Direct; if both fail, fall back to a same-day flat-rate courier or block the 90-minute window. Customer never sees the carrier choice happen.

For multi-location bakeries (e.g. 3 Tatte cafes in Boston), Magento Multi-Source Inventory routes the order to the closest store by customer ZIP, then triggers DoorDash pickup from that store.

Standard pattern: FedEx Express overnight (Priority Overnight or Standard Overnight) with the box packed in 2-3 lb of dry ice inside 1.5-inch EPS foam in a corrugated outer. Holds frozen for 36-48 hours.

Critical bits:

• ZIP transit cutoff — FedEx Express delivers next-business-day to ~95% of US ZIPs, but 2-day to remote areas (parts of AK, HI, MT, ND). ShipperHQ rule blocks any ZIP > 1-day transit so a chocolate ganache cake doesn’t arrive defrosted on day-2. Magento attribute cold_chain_class per SKU triggers the rule.
• Friday cutoff — FedEx doesn’t deliver Sunday on Express. Orders placed Friday 2pm onwards ship Monday. Cart messaging must tell the customer this before they pay, not after.
• Dry-ice IATA labeling — dry ice is regulated as ORM-D / UN1845. FedEx label must show the dry-ice weight + Class 9 marking. Magento checkout passes this metadata to the shipping label print queue.
• Packaging cost — $8-15 per box (foam + dry ice + outer). Bake it into the product price or surface as a flat ship surcharge; never as a surprise at checkout.

Levain Bakery and Magnolia Bakery both run this pattern (with Goldbelly handling the logistics for some volume). Damage / spoilage rate on a well-tuned setup runs <0.5% — the gating factor is dry-ice weight and EPS foam thickness, not the carrier.

Three pieces wired together:

• Wholesale catalog visibility — cafes register a company account, get approved, see a wholesale-only category with trade pricing (typically 40-55% off retail). On Adobe Commerce that’s the native B2B Companies module; on Open Source it’s Aheadworks B2B Suite or Amasty Company Accounts + customer-group price rules + hidden categories.
• Standing-order schedule — the cafe sets “24 croissants every Tuesday + Friday at 7am pickup” once. Magento + a subscription / recurring-order extension (Aheadworks Subscriptions, Bold Subscriptions) generates the order, sends the cafe an editable order email Monday + Thursday, and routes to your fulfillment queue. Cafes love this — they don’t want to re-order 6 times a week.
• Net-30 invoicing — Apruve, Resolve, or TreviPay underwrite the credit. They pay you on day-1, customer pays them on day-30. You eat a 2-3% fee but offload AR + collections + bad debt. For wholesale-led bakeries this is non-negotiable — cafes will not pay card-on-pickup for $800/week orders.

Multi-location pickup matters for cafe chains: one company account, 6 delivery addresses, the standing order auto-rotates pickup location by day. Magento ships this natively in B2B Companies; bolt-on extensions need a custom field on the order.

Magento custom options + a small extension layer. Flow:

1. Size: 6″ (serves 8-10) → 8″ (serves 16-20) → 10″ (serves 30-40) → sheet (serves 60+). Drives base price.
2. Flavor: vanilla / chocolate / red velvet / lemon / carrot. No price impact usually.
3. Filling: buttercream / cream-cheese / ganache / fruit. Some add $5-15.
4. Decoration: text (free), theme (preset $20-40), photo upload (premium $40-80). Photo uploads to pub/media/customcake/ via Magento file upload + attaches to the order line item visible to the decorator.
5. Delivery date: lead-time-aware date picker blocks anything under 7 days out (or 14 days for tiered wedding cakes). Decorator capacity calendar blocks any date already at 8 cakes booked. No overbooked weddings.

Dynamic SKU concatenates the choices for the kitchen ticket (e.g. CAKE-8-VAN-BC-PHOTO-2026W23). Dynamic price recalculates on each option change client-side via Hyvä + Alpine.js.

Wedding-cake variant adds a partial-payment flow: 50% deposit on order, 50% balance due 7 days before pickup (auto-charged to vault token). Magento doesn’t do this natively — needs a partial-payment extension (PayCron, MageWorx) or a custom payment module. Either way it’s the difference between “customer cancels with 48h notice and you eat the cake” vs. “you’re paid before you start.”

The legal frame is FDA + FALCPA (Food Allergen Labeling and Consumer Protection Act), updated by the FASTER Act 2021 which added sesame as the 9th major allergen effective January 2023. The current Big-9: milk, eggs, fish, shellfish (crustacean), tree nuts, peanuts, wheat, soybeans, sesame.

Magento implementation: three flags per SKU per allergen:

• entire-bakery-free-of-X — the bakery has no X anywhere on premises (e.g. Erin McKenna’s, a 100% nut-free vegan bakery). The strongest claim. Mislabeling here is an FDA recall.
• shared-equipment — product made on equipment that also processes X. The middle claim, mandatory FDA disclosure where applicable.
• may-contain — trace amounts possible due to facility processing. The softest claim.

PDP renders allergen badges; category pages support filterable allergen facets (/nut-free, /gluten-free, /vegan, /dairy-free). Checkout warning fires if the customer has flagged an allergy in their account and the cart contains a shared-equipment or may-contain SKU. Every catalog edit triggers a compliance audit log entry — who changed which flag when. Auditable trail if an incident happens.

Compliance is not optional for bakeries shipping nationwide — one wrong “nut-free” flag on a cookie that goes to a peanut-allergic 8-year-old is a multi-million-dollar FDA + civil-suit problem. Build the flags correctly on day one.

Three surfaces, three different requirements:

• Product Detail Page (PDP) — the ingredient panel must list the Big-9 allergens called out by name (e.g. “Contains: wheat, milk, eggs”). If processed on shared equipment, add “May contain: tree nuts, peanuts.” This is FDA-mandated for any packaged food sold across state lines — which is every shipped order.
• Cart + checkout — if the customer is signed in and has flagged an allergy in their account, fire a banner-level warning on cart load (not just a footnote). “You’ve flagged a peanut allergy. The items in your cart are made on shared equipment with peanuts. Continue?” Force an explicit acknowledgement checkbox before order placement.
• Shipping label + outer packaging — FDA requires the allergen statement on the consumer-facing label, not just the e-commerce page. Magento order export must include the allergen field so the label printer can print it on the carton.

State-level rules add wrinkles: California Prop 65 for any product with certain chemical exposures (mostly relevant for chocolate / cocoa cadmium + lead). NYC Department of Health requires calorie labels in some categories. UK + EU have their own 14-allergen list which is wider than Big-9 (adds celery, mustard, lupin, mollusks, sulphites) — if you ship UK/EU, multi-store-view Magento renders the localized allergen list per region.

Two completely different fulfillment patterns — never share the same packaging / carrier rules.

Frozen ship-nationwide — FedEx Express overnight, 2-3 lb dry ice, 1.5-inch EPS foam, 36-48 hour cold-hold. Used for: cakes, cookie dough, ice-cream-filled pastries, anything that must reach the customer below 32°F. Packaging cost $8-15/box. ZIP-transit cutoff blocks > 1-day delivery (no AK/HI/remote MT). FedEx ORM-D dry-ice labeling. Sunday no-delivery rule.

Refrigerated local — DoorDash Drive or Uber Direct with insulated cooler bag (carrier-provided), 90-minute door-to-door window. Used for: cream-filled pastries, mousses, fresh-cream cakes, anything 35-40°F. No dry ice. Packaging is a $1-2 insulated bag, not a $10 foam box. Distance limit ~15 miles. Customer SMS tracking via carrier API.

Magento attribute cold_chain_class on each SKU has 4 values: ambient (no cold), refrigerated-local-only (DoorDash + insulated bag, no ship), frozen-ship-only (FedEx dry-ice, no local), both (frozen for ship + refrigerated for local). ShipperHQ rules read this attribute on cart load and only offer the matching shipping methods. Cold-chain HACCP-compliant temperature log appended to every shipment (carrier API for local, internal log for FedEx).

Mixing the two patterns is the #1 bakery e-com failure mode. A cream-filled éclair shipped FedEx Express dry-ice arrives shattered + frozen-solid; a chocolate ganache cake out for 4-hour DoorDash delivery on a 95°F day arrives liquid. Tag every SKU correctly, then let the rules do the routing.

Subscriptions drive 35-50% of revenue for mature bakery DTC brands — the highest-LTV channel in food ecom. Two patterns:

• Cake-of-the-month club (Goldbelly + a few direct-to-consumer bakeries do this) — customer pays $50-120/month, receives a different signature cake each month, ships frozen via FedEx Express. Stripe Subscriptions (or Recharge / Bold Subscriptions on the Magento side) auto-charges monthly + creates the order. Curation is the marketing — September is pumpkin, December is gingerbread, February is chocolate-raspberry.
• Weekly pastry box (Tatte and Levain Bakery style locally, plus a few national bakeries) — 6 / 12 / 24 piece options, $30-90/week, delivered every Friday morning. Often local-only via DoorDash Drive standing slot rather than national-ship. Lower LTV than monthly cake but higher repeat rate (52 deliveries/yr vs 12).

Critical UX:

• Pause / skip / swap controls in the customer account — subscriber should be able to skip next month without canceling. Subscriptions with no pause feature churn 2-3x faster.
• Gift subscriptions — let a customer buy a 3-month or 6-month gift for someone else, pre-paid, no auto-renewal. Massive Q4 revenue driver.
• Cancellation analytics — track reason at cancel (cost / not eating it all / moving / quality issue). Use the data to adjust portion size or pricing.

Magento + Aheadworks Subscriptions or Bold Subscriptions is the typical stack. Stripe Billing as the underlying subscription engine (better dunning + retry logic than Magento native).

Yes — via Magento Multi-Source Inventory (MSI) + multi-store-view, native since 2.3.0. Architecture:

• Sources (kitchens / warehouses) per region: us_brooklyn, us_la_frozen_warehouse, uk_london, de_berlin_warehouse.
• Stocks (shopping experiences) per region: US stock aggregates US sources; UK stock = UK source only; EU stock aggregates DE + FR + NL sources.
• Store views per region for language, currency, allergen-disclosure list. US store view in USD with FALCPA Big-9 allergens; UK store view in GBP with FSA 14-allergen list; EU store view in EUR with EU 14-allergen list. Same SKU pool, region-specific compliance + pricing.

Per-region payment + checkout: Stripe in US, Stripe + Klarna in UK, Stripe + Klarna + iDEAL in NL/DE. Per-region carrier: FedEx in US, DPD + Royal Mail in UK, DHL + GLS in EU. ShipperHQ rules per store view.

Compliance per region:

• US: FDA + FALCPA + FSMA. State-level wrinkles (CA Prop 65, NYC DOH calorie labels).
• UK: FSA Natasha’s Law — pre-packed-for-direct-sale items need full ingredient + 14-allergen label on the pack itself, not just online.
• EU: Regulation 1169/2011 covers food information to consumers. 14-allergen list. Distance-selling rules for cross-border DTC.

One Magento, three store views, three compliance lists, one operations team. Beats running three separate Shopifys + reconciling inventory + dual catalog edits.

Realistic ranges for a baby-DTC brand at $500k–$5M GMV:

• Audit: $499, ~20h @ $25/hr, 5 business days. Catalog mix, compliance posture, registry partnerships, subscription tooling review, recall-readiness check.
• Build: $4,999, ~200h @ $25/hr, 6 weeks. Stage-based catalog, ReCharge sub with graduation, Babylist + Amazon Baby + Target registry sync, bundles, Klaviyo milestone flows, recall workflow, compliance attribute set.
• Custom enterprise: quoted, multi-week engagement. Multi-brand, multi-region, full ERP integration.
• Hosting: $400–$1,500/mo on Cloudways / dedicated. Baby DTC needs over-provisioned for back-to-school + holiday traffic spikes. CDN (Cloudflare / Akamai) mandatory.
• Ongoing retainer: $1.5k–$5k/mo for stage-graduation flows + new-SKU compliance flagging + quarterly cert-expiry sweep.

My credentials: Adobe-Certified Magento + Hyvä developer (Adobe Commerce Architect + Front-End Developer + Cloud Developer). 7+ years of DTC builds across baby, fashion, beauty, and supplements. Shipped Magento for brands in the Bobbie / Honest / Hello Bello shape (premium DTC, sub-heavy, registry-driven). Same person on the keyboard from kickoff to launch — no offshore handoff. Hourly rate: $25/hr, fixed-fee on the audit + build packages above, flat retainer for ongoing.

Reach me on the form above or via the public Upwork profile linked in the footer.

Three common edge-case configurations, each with a different Magento shape:

• Storefront-only (no ship) — walk-in bakery doing local pickup + maybe DoorDash Drive same-day. Skip MSI complexity (one source, one stock). Skip FedEx Express + dry-ice. Skip national-ship product attribute. Keep custom-cake configurator + decorator calendar + allergen labeling. Often Toast Online Ordering is enough here; Magento only justifies itself if there’s a B2B wholesale layer or a custom cake configurator that Toast can’t do.
• Ship-only (no storefront) — pure DTC online bakery shipping nationwide frozen (e.g. dessert subscription brands). FedEx Express + dry-ice + ZIP-transit cutoffs are the entire fulfillment story. No DoorDash Drive. No local-pickup option. Often paired with a Goldbelly listing as a secondary channel. Subscription cadence matters more than B2B layer.
• B2B-only (wholesale to cafes, no DTC) — supplying croissants + pastries to 40 cafes daily. No public-facing catalog (everything is behind login). Adobe Commerce B2B Companies or Aheadworks B2B Suite + Apruve/Resolve Net-30 + standing-order schedules + multi-location pickup + production-planning report (how many croissants to bake tomorrow). No subscription. No custom-cake configurator. ShipperHQ rules are simpler (no national-frozen lane).

Mixed-mode bakeries (storefront + ship + B2B) get the full build. Single-mode bakeries get a leaner build — pay only for the lanes you need. The Audit step nails this down before scope is locked, so you’re not paying for features that don’t apply.