Whole Foods Demos, Merchandising, and Vendor Programs

A Whole Foods demo needs two approvals to be useful: permission to run the event and a credible plan to keep sellable product available. Confirm the current program rules with your supplier contact, then put the store, distributor and demo provider on one inventory plan before booking labor.

The checklist below is a brand-side planning tool, not a statement of a chain-wide booking deadline, required provider or minimum velocity. Whole Foods says not all supplier standards and policies are public. Confirm the current instructions for your market and account rather than carrying over another region’s process.

Name the owners before booking

One founder should not have to guess who owns every handoff. Write a named person against each responsibility, including a backup and a way to reach them during the event.

Ask who may approve additional inventory. A demo rep should not promise extra cases, discounts or a changed date without the relevant account and store approval. Coordinate in-store demo costs with the same person who owns the inventory exposure.

Before the event confirm real availability

Check the exact sellable SKU, pack, store and receiving route. “At the distributor” is not enough if stock sits at the wrong DC, the store cannot order it, or the order has not been placed. Keep the order reference and delivery expectation together.

Use this before-event checklist:

• Confirm the store, event window and current approval in writing.
• Ask the current supplier/program contact how booking, staffing, food handling, insurance and cancellations work for this account.
• Confirm the store-designated ordering contact and the distributor/DC contact.
• Record sellable units on shelf and in backstock, plus the time and source of that count.
• Separate product used for samples from product available for shoppers to buy.
• Confirm any incoming order’s quantity, receipt date and exception owner. Treat an unconfirmed shipment as uncertain supply.
• Agree the stock target, regular-sales reserve and replenishment trigger with the store.
• Obtain approval for extra stock, freight, display materials and total spend.
• Set a final confirmation checkpoint early enough to change the event under the applicable cancellation terms.

Do not publish a universal “book this many weeks ahead” rule. Lead time depends on account approval, provider capacity, store orders, receiving schedules and product availability. Ask for each deadline and work backwards from the slowest confirmed dependency.

A stock issue belongs in the UNFI and Whole Foods out-of-stock workflow, with the evidence needed to distinguish ordering, DC supply and shelf execution. A booked demo does not repair any of those on its own.

Work through the inventory arithmetic

Here is a fictional example for Juniper Pantry [Demo planning]. These numbers illustrate the calculation; they are not a Whole Foods target, forecast or stocking instruction.

The store reports 60 sellable units. A confirmed receipt of 48 units arrives before the event, giving 108. The brand and store allow 12 units for samples and reserve 24 for regular shoppers through the next confirmed receipt. That leaves a planning capacity of 72 incremental unit sales: 108 − 12 − 24.

If the event scenario assumes 80 incremental sales, the plan is eight units short. The account owner can ask about approved replenishment, reduce the event scope or change the date. The team should not quietly consume the regular-sales reserve to make a forecast look feasible.

If the 48-unit receipt is not confirmed, available planning capacity falls to 24 units: 60 − 12 − 24. Record both scenarios. Inventory promised by email is not the same evidence as a received and orderable case.

During the demo watch the shelf

Give the event lead a short operating card with the store contact, item identifier, approved sample stock, inventory threshold and escalation route. The card should answer what to do when sales exceed the plan as well as when they disappoint.

Check sellable stock at the start and at agreed intervals. Record shelf stock and confirmed backstock separately. Track units used for sampling, shopper sales if available, time out of stock and any price or display exception. Take photos only under the store’s permissions and avoid collecting shopper or employee personal information unnecessarily.

When inventory reaches the agreed trigger, tell the store-designated contact and brand account owner. Confirm whether replenishment can actually arrive. Adjust sampling or stop under the approved event plan if continued activity would leave shoppers with no product to buy. Do not promise shoppers a restock date that operations has not confirmed.

Link the observations to your store-audit checklist. An empty facing, a missing shelf tag and a distributor shortage are different exceptions and need different owners.

After the demo close the replenishment loop

An event report is incomplete if it ends with samples handed out. Complete a same-event handoff and set a follow-up based on the store’s next ordering and receiving cycle.

• Reconcile opening stock, receipts, sample usage, recorded sales and closing sellable stock. Explain any difference instead of forcing the count to balance.
• Confirm the closing shelf condition and any remaining display or pricing issue.
• Record who placed the replenishment request, its reference and expected receipt.
• Assign an owner to verify the receipt and shelf restoration. Keep the issue open until the agreed evidence arrives.
• Compare performance with a relevant store baseline and note promotions, stockouts and other differences.
• Decide whether to repeat, change or stop the event based on contribution and execution, not samples alone.

The demo ROI guide supplies a framework for evaluating economics. Observed lift during a promotion does not prove that the demo caused every additional sale.

Price the event from a current quote

Ask for labor, session duration, minimums, sample product, equipment, training, travel, cancellation charges and any separate store or program costs. Confirm who pays each item. A provider’s quote and the account’s current terms are stronger budgeting inputs than a generic per-demo range.

For a worked example, assume $260 labor, $36 sample product and $24 supplies, for $320 of direct event cost. If each incremental sold unit contributes $2 after its variable costs, direct break-even is 160 incremental units: $320 ÷ $2. This hypothetical excludes longer-term repeat purchases and any additional fixed costs. Do not substitute retail shelf price for brand contribution.

Coordinate any Whole Foods price promotion with that model. A discount can change contribution per unit and inventory demand at the same time. Use written authorization and actual funding terms rather than assuming all promotions are treated alike.

Keep vendor programs separate from demo approval

Whole Foods’ supplier information page is the starting point for the Supplier Portal and its published LEAP information. Confirm the current application period and eligibility there; an older application calendar is not a current deadline. Accelerator participation is not an event booking confirmation.

The Local Producer Loan Program describes financing for small-scale local or emerging producers. Check current qualifications and financing terms directly. A financing opportunity is not a substitute for funded event economics or store authorization.

UK suppliers have a separate published demo guidelines page. Its existence is useful evidence that market-specific instructions matter. Do not apply those instructions to a US or Canadian account without confirmation.

The final go or change decision

Run the event when approval, trained staff, sellable inventory, regular-sales reserve and replenishment ownership are confirmed. If a dependency remains unresolved, record who must resolve it and when the booking can still be changed. That is a usable operating decision, even when the right decision is to move the event.