Exploring as:merchantDemo control — switches the live catalog behind this store.
Service status
Auto-Refill plan lookup is connected. Signed-in shoppers can confirm a provider plan on their BigCommerce cart.
One-time purchase
Live through the BigCommerce sandbox cart and hosted checkout.
Plan and cart intent
Provider-backed plan lookup and authenticated cart-intent confirmation are ready.
Recurring schedule
Created only by the provider after its signed order webhook verifies the completed order and payment state.
Portal
Provider-backed portal session and customer ownership check required.
Payment
Provider-owned. Aisles does not collect or authorize payment credentials here.
Merchant capability manifest
See every intended Kibble capability in one place.
The source snapshot captured 2026-06-29 reports these seven capabilities as live. Aisles exposes catalog evidence or a fixed service boundary without creating a cart, account, order, payment, or subscription.
Snapshot: live · 2026-06-29storefront
Subscribe & save
Choose a recurring cadence and receive the merchant-configured subscription price.
Canonical registry: listed — The 2026-06-28 canonical registry lists subscribe-and-save as a PDP demo capability.
Separate the payer from the recipient and let the recipient manage the subscription.
Canonical registry: absent — The 2026-06-28 canonical registry says gift is absent because no gift_tokens table exists; the 2026-06-29 demo-state reports one live portal scenario.
Action types describe what may change. Each surface proof names its stable route, exact zone instances, prerequisites, and expected rendered evidence. Readiness is separate from both AI-zone and provider-call counts.
Action typeselect_products
rules · home
Select approved products
Selects only from the merchant candidate set; catalog membership stays fixed.
home proof
Route and trigger
/?observe=true#kibble-signal-lab Apply a synthetic shopper scenario · user-triggered
/product/puppy-starter-kit?observe=true Run bounded AI · user-triggered
Named zones
pdp.related
Candidates
Exactly three or four unique current products. Native related products are preferred; category siblings are labeled category_sibling with no merchant-related claim.
Before
Merchant order and merchant-authored related heading. Observe: 0 AI zones · 0 AI calls
Changed
The same PDP candidate IDs appear in a model-selected order.
Kept
The original order remains as a valid model-selected result.
Expected result
1–2 AI zones · 1–2 AI calls The related rail counts; optional PDP marketing counts only when visible.
Fewer than three candidates, an unapproved route, invalid output, or a failed gate keeps the approved PDP rail and renders zero AI zones.
Why this route is stable: The local showcase preflights 4 unique category_sibling candidates from fixture 833824a875f1fbe83a5d1d9164f521aa38e64e3902d22623a6af1b8cad84fe49; a drifting live catalog still fails closed.
An invalid visibility/variant pairing, crossed binding, failed gate, or failed sibling execution keeps the merchant PLP and publishes no model zones; a valid hidden selection is an AI-kept result with two rendered zones.
Why this route is stable: The pinned Dog Food PLP includes one named optional marketing slot hidden by default.
An invalid visibility/variant pairing, crossed binding, failed gate, or failed sibling execution keeps the merchant PDP and publishes no model zones; a valid hidden selection is an AI-kept result with one rendered zone.
Why this route is stable: The pinned proof product 3064 preflights four honest category siblings; pdp.below-description is hidden by default.