Custom Storefront — Release Notes v1.1.0
| Release version | Custom Storefront 1.1.0 |
| Release date | 2026-06-10 |
| Applies to | Storefront API product detail · customer product pages |
| Availability | GA for tenants on the custom storefront channel |
New Features
- CS WhatsApp human chat. Pharmacists can open a human WhatsApp session from CS Command Center for a patient phone number. While active, the Evolution webhook pauses the marketing AI bot so staff messages reach the patient directly. Sessions auto-expire after 120 minutes of inactivity or when staff click End WhatsApp session.
- Pharmacist decision workspace. CS Command Center adds sidebar cards for recent decisions, urgency rules, and a dedicated pharmacist decision panel so intake review and order confirmation stay in one queue.
- Urgency rules drawer. Staff can tune how online orders surface priority (config-driven) without leaving the command center.
Improvements
- Product detail pages show Uses and Product overview again. Tabbed PIMS descriptions whose titles end with a colon (e.g.
Product Overview:,Uses:) now map correctly to the Storefront APIpdp.overviewfields consumed by the customer website. - Customer product page readability. Overview, Uses, and Warnings blocks render bold sub-headings with spacing; the Common side effects card spans full width at the bottom of the overview grid.
- Mobile layout on product pages. Header, buy box, and tab bar no longer clip on the right at ~390px viewport widths.
Bug Fixes
- Missing PDP sections on live products — customers saw only manufacturer/pack metadata because tab-title colons prevented section matching in
api/storefront/_lib/pdp.ts. (no migration) - Horizontal overflow on mobile product pages — grid children and the subscribe card could extend past the viewport; clipped with
min-w-0andoverflow-x: clip. (customer website —custom_store_front_ailaaj)
Known Issues
- Storefront support KB is new in this release — only a starter corpus ships; expand from real CS tickets.
- CS WhatsApp requires Evolution credentials — without
EVOLUTION_*env vars, human chat send fails gracefully but messages do not deliver. - Product tabs still scroll horizontally on very narrow screens — by design; all tabs remain reachable via swipe.
Notes for operators
- Apply migration
20260622150300_storefront_cs_whatsapp_handoffbefore enabling CS WhatsApp human chat. - Deploy both repos for the full experience:
ailaaj-connect-hub(API + CS UI) andcustom_store_front_ailaaj(customer PDP layout). - Registered storefront patients (
customers.customer_channel = api) never receive the marketing WhatsApp AI bot — human CS chat is the intended path.
Further reading
- Custom Storefront Integration Guide — API map + CS loop (updated §9–§12)
- Storefront API README — routes and env vars