For retailers.
AI playbooks that fit how a retail floor actually runs.

The stockout-to-stocktake prompt runs before the morning walk-through — flag the SKU on the floor, check the back-room, drop the reorder if the PO cadence is overdue, and set explicit expectations for the customer who is going to walk in expecting the SKU ("here is what we have on the floor today, here is when the next shipment lands"). It is written for a 90-second floor walk, not a 10-minute inventory dump, and the trade vocabulary stays specific so the floor lead does not have to translate generic SaaS advice into independent-retailer, boutique, or small-chain terms.

The register-hesitation prompt walks through the same three steps used at the front of the line: restate what the loyalty ID actually does in plain language, lay out every option the store actually offers (including the punch-card path), and lock the next nudge before the customer gets to the door. The objection-handling language covers loyalty signup stalls, gift-card-vs-loyalty-id confusion, and the generic "I will think about it" — without sounding like a high-pressure pitch. The point is not to close harder; it is to make sure a hesitant "let me think about it" does not quietly become a buyer the CRM never sees again.

The lapsed-buyer reactivation prompt posts three short touch-points over six weeks — a first nudge within week one of the 90-day mark, a second touch at week three, and a friendly outreach at week six offering a soft commit to an in-store event or a reorder window. It runs against the CRM segment so a reactivation actually lands before the buyer drifts to a competitor, not just stays in the email list. Worked through on a small-floor rollout, it returned fifteen to twenty percent of the 90-day-lapsed cohort to an in-store visit inside the next reset cycle, and the same cadence maps onto punch-card holders who never migrated to the loyalty ID.

The end-of-day-to-selling prompt reads the same register summary the manager reconciled at close and rewrites it in the structure a buyer actually uses for the next PO — sell-through per SKU per day, void/return pattern, gift-card vs. loyalty-id balance, window timing on each category — in the specific phrasing the buying cycle looks for on the next-vendor review. The wording matches across the morning walk, the mid-day reset, and the close so the floor reads like one continuous merchandising story rather than three loose register dumps, and so the next PO does not bounce on a missing data point the buyer never had to track before.

Three primary stalls, each with an associate-tone response rather than a digital-marketer-tone response: loyalty signup hesitation ("here is what we send you and what we do not — three short touch-points, no newsletter spam"), gift-card-vs-loyalty-id confusion ("here is how both work in this store, and here is the simplest path for the way you shop"), and the generic "I will think about it" ("here is what changes if we wait, and here is the shortest path to keep your punch-card credit"). The point is to answer the actual stall, not to circle back to the close — written for the associate on the register, not the script reader.

The store-team rollout checklist ships as a 30/60/90 adoption plan — week one runs on two champions (one floor lead, one register lead), day thirty adds the second wave, day sixty adds the buyer and PO cadence, day ninety lands the multi-window seasonal pattern. The plan stays trade-specific: prompts are pre-mapped to the morning walk-through, the register handover, the end-of-day reconciliation, and the buyer's next-vendor review so each rollout wave lands a workflow the team actually runs rather than a generic SaaS checklist. Designed for a single-store independent retailer, a small boutique group, and a small retail chain coordinating across stores without losing the trade vocabulary.