Skip to content

Food and beverage · Local pickup

Local-Pickup Schema for Food and Beverage on Shopify

Coffee roasters, bakeries, brewers, distillers, and tasting-room brands routinely run hybrid retail — DTC online plus pickup at a physical location. AI engines parsing queries like 'best coffee near me for pickup' need a structured signal that the brand offers local pickup. The install ships OfferShippingDetails1 with in-store pickup, Place schema2 for the pickup locations, metafield population per SKU and per location, and a Knowledge Base FAQ pipeline answering pickup-specific buyer questions.

Published

Why local pickup matters for F&B AI citation

Local-pickup intent is one of the largest AI shopping query categories for food and beverage. 'Coffee near me', 'best bakery in [city] for pickup', 'distillery near [city] tasting room' — these queries cluster around buyer intent that DTC-only structured data cannot answer. AI engines that can't extract a pickup signal from a brand's Catalog data treat the brand as DTC-only and skip it for pickup queries, even when the brand actually offers pickup.

The Shopify AI optimization doc4 recommends complete and up-to-date policies for AI agent access, and the pickup policy is one of the surfaces that signals hybrid-retail capability. The schema-and-metafield layer extends the policy signal with structured pickup metadata that AI engines parse directly — location, hours, lead time, payment method, ID requirements. Brands with the structured signal get cited for pickup queries; brands without it get cited only for DTC shipping queries regardless of the actual retail footprint.

The schema layer — OfferShippingDetails and Place

Two schema.org types carry the pickup signal. OfferShippingDetails (under Offer) declares the shipping options for a product including in-store pickup as a delivery method. Place (or its LocalBusiness subtype) declares the physical pickup location with address, geo coordinates, opening hours, and contact information. Together they let AI engines extract 'this product is available for pickup at this location at these times'.

The install adds OfferShippingDetails1 on every product that offers pickup, with shippingDestination pointing at the pickup Place and shippingRate at $0 (or whatever the pickup convenience fee is). The Place schema2 uses LocalBusiness subtype where the location is a retail entity (CafeOrCoffeeShop, Bakery, Brewery, Distillery), with the appropriate openingHoursSpecification, address, geo coordinates, and contact. Both schemas are emitted from the theme.liquid layer or via dedicated Shopify apps.

Metafield population per SKU and per location

Two metafield sets carry the pickup data the schema serializes. Per-SKU: pickup_available (boolean — not all SKUs may be available for pickup, especially limited-batch or perishable items), pickup_lead_time, pickup_locations (array of location IDs). Per-location (using Shopify Metaobjects): location address, hours by day, payment methods accepted, ID requirements (for alcohol pickup), and contact information.

The Metaobject pattern is the install standard for the per-location data because it normalizes the location detail across the catalog — every SKU references the same location Metaobject rather than duplicating the address on each PDP. The Shopify Catalog feed3 picks up the structured data through Product schema additionalProperty and the OfferShippingDetails block. AI engines reading the feed see the pickup signal at both the product level and the offer level, which is the consistent extraction pattern.

Shopify's native Local Pickup feature

Shopify ships Local Pickup as a native checkout option that can be enabled per location and per product. When configured, Shopify emits the relevant pickup signal at checkout and exposes pickup as a delivery method in the order confirmation. The install verifies Local Pickup is enabled where applicable, augments the native signal with the schema-and-metafield layer documented above, and reconciles any conflicts between the native and custom data.

Local Pickup native handles checkout mechanics (the buyer selecting pickup vs ship, the order being routed to the pickup location, the confirmation email with pickup instructions). It does not by default emit Place schema or richly-structured OfferShippingDetails — those still come from theme code or a schema app. The install treats native Local Pickup as the table-stakes checkout layer and the custom schema-and-metafield as the AI-extraction layer.

Knowledge Base FAQ pattern for pickup queries

The Knowledge Base FAQ pipeline carries the prose-answer layer for pickup queries. Six pickup-specific FAQs cover most buyer questions. 'Do you offer local pickup?' (boolean answer with location reference). 'Where is your pickup location?' (address with map link). 'What are your pickup hours?' (hours by day, with holiday exception note). 'Do I need ID for pickup?' (especially for alcohol pickup — yes, and which IDs are accepted). 'How long does pickup take to be ready?' (lead time from order). 'Can I pay at pickup or do I have to pay online?' (payment policy).

The Knowledge Base managing-FAQs doc5 specifies 1-2 sentence answers per FAQ, stored as metaobjects under Content > Metaobjects. The six-FAQ pickup set is the F&B install default; brands with category-specific pickup logic (alcohol ID requirements, cold-chain handling, batch-availability calendars) add category-specific FAQs on top. The AI agents Shopify routes through Knowledge Base have access to these answers when buyers ask the engine pickup questions, which is the moment the brand earns or loses the pickup-intent citation.

Keep reading