@mohasinac/appkit 4.23.0 → 4.25.0

package/dist/_internal/shared/checkout/order-math.js

@@ -1,8 +1,8 @@
 import { roundRupees } from "../../../utils/number.formatter";
 /**
- * The single source of truth for "what do we charge for this line".
+ * The single source of truth for "what do we charge for ONE COPY of this line".
  *
- * Three cases, in priority order:
+ * Four cases, in priority order:
  *
  *  1. **A locked price** — an accepted offer or a won auction. `lockedPrice` is
  *     the negotiated/won amount and it OVERRIDES the current listing price, which
@@ -10,18 +10,33 @@ import { roundRupees } from "../../../utils/number.formatter";
  *     copies of this function looked at `lockedPrice`, so an accepted offer was
  *     billed at the seller's listed price while the cart UI displayed the agreed
  *     one (`item.lockedPrice ?? item.price`) — the buyer saw ₹X and paid ₹Y.
- *  2. **A bundle line** (SB-UNI-5 2026-05-13) — `item.price` is the bundle price
- *     locked at add-time.
- *  3. **Everything else** — the live Firestore price, so a stale cart-cached
+ *  2. **A multi-member line** — the sum of its members' own snapshotted prices,
+ *     weighted by each member's per-copy quantity. A `"group"` line pins
+ *     `item.quantity` to 1, so this is both the unit price and the line total;
+ *     see the invariant on `CartLineMember`.
+ *  3. **A legacy bundle line** (SB-UNI-5 2026-05-13) — written before
+ *     `groupMembers` existed. `item.price` is the bundle price locked at
+ *     add-time.
+ *  4. **Everything else** — the live Firestore price, so a stale cart-cached
  *     price is never charged on a COD/UPI order.
  *
  * `product` may be null for a locked line whose listing has since been archived;
  * the locked price is still owed, so that case must not dereference `product`.
+ *
+ * 🛑 Do not hand-roll this rule at a call site. It has been re-derived by hand
+ * six times, and the two copies that lived in the consumer repo
+ * (`src/app/api/payment/create-order/route.ts`) each reproduced the bundle
+ * branch while silently omitting case 1 — so Razorpay captured the LIST price
+ * for an accepted offer while the cart displayed the negotiated one. Call
+ * `lineTotalFor` and let this function stay the only definition.
  */
 export function unitPriceFor(item, product) {
     if (typeof item.lockedPrice === "number" && item.lockedPrice > 0) {
         return item.lockedPrice;
     }
+    if (item.groupMembers?.length) {
+        return roundRupees(item.groupMembers.reduce((sum, m) => sum + m.unitPrice * m.quantity, 0));
+    }
     if (item.bundleCategorySlug && item.bundleProductIds?.length) {
         return item.price;
     }
@@ -31,6 +46,14 @@ export function unitPriceFor(item, product) {
     // crash whenever a cart line outlives its listing.
     return product?.price ?? item.price;
 }
+/**
+ * What this line contributes to a subtotal: one copy's price × the number of
+ * copies. THE call site should use this rather than multiplying `unitPriceFor`
+ * itself — that multiplication is where the six hand-rolled copies diverged.
+ */
+export function lineTotalFor(item, product) {
+    return unitPriceFor(item, product) * item.quantity;
+}
 /**
  * P-6 — pre-order groups charge each product's own `preOrderDepositPercent`
  * (falling back to the generic COD deposit % when a product doesn't have one
@@ -41,7 +64,7 @@ export function unitPriceFor(item, product) {
  */
 export function computePreOrderDepositAmount(group, defaultDepositPercent) {
     const raw = group.reduce((sum, { item, product }) => {
-        const lineTotal = unitPriceFor(item, product) * item.quantity;
+        const lineTotal = lineTotalFor(item, product);
         const pct = product.preOrderDepositPercent ?? defaultDepositPercent;
         return sum + lineTotal * (pct / 100); // audit-money-units-ok: percentage divisor, not paise
     }, 0);

package/dist/_internal/shared/checkout/rules/_limits.d.ts

@@ -1,6 +1,16 @@
 /** Checkout window / capacity constants — single source of truth. */
-/** Maximum distinct line items in one cart (hard cap, already enforced at addToCart). */
-export declare const CART_MAX_ITEMS = 50;
+/**
+ * Maximum distinct line items in one cart (hard cap, enforced at every
+ * add-to-cart entry point).
+ *
+ * Re-exported, not re-declared. This value existed as three independent `= 50`
+ * literals — here, in `constants/limits.ts`, and in
+ * `_internal/shared/features/cart/config.ts` — with nothing tying them
+ * together, so raising the cap in one place would have left two silently
+ * disagreeing. `constants/limits.ts` is a dependency-free leaf module, so this
+ * costs no import chain.
+ */
+export { CART_MAX_ITEMS } from "../../../../constants/limits";
 /**
  * Maximum number of order documents that can be created in one checkout
  * transaction.  If the cart produces more groups than this the checkout is

package/dist/_internal/shared/checkout/rules/_limits.js

@@ -1,6 +1,16 @@
 /** Checkout window / capacity constants — single source of truth. */
-/** Maximum distinct line items in one cart (hard cap, already enforced at addToCart). */
-export const CART_MAX_ITEMS = 50;
+/**
+ * Maximum distinct line items in one cart (hard cap, enforced at every
+ * add-to-cart entry point).
+ *
+ * Re-exported, not re-declared. This value existed as three independent `= 50`
+ * literals — here, in `constants/limits.ts`, and in
+ * `_internal/shared/features/cart/config.ts` — with nothing tying them
+ * together, so raising the cap in one place would have left two silently
+ * disagreeing. `constants/limits.ts` is a dependency-free leaf module, so this
+ * costs no import chain.
+ */
+export { CART_MAX_ITEMS } from "../../../../constants/limits";
 /**
  * Maximum number of order documents that can be created in one checkout
  * transaction.  If the cart produces more groups than this the checkout is

package/dist/_internal/shared/checkout/rules/_registry.js

@@ -8,6 +8,7 @@
  *
  * No grep of the consumer codebase needed.
  */
+import { isMultiMemberLine } from "../line-members";
 import { standardRule } from "./standard.rule";
 import { auctionRule } from "./auction.rule";
 import { preOrderRule } from "./preorder.rule";
@@ -77,8 +78,13 @@ export function getSplitKey(item) {
 export function runSyncPreflight(pairs, paymentMethod) {
     const byType = new Map();
     for (const pair of pairs) {
-        if (pair.item.bundleProductIds?.length)
-            continue; // bundles skip — direct checkout
+        // Multi-member lines (bundle or grouped selection) skip the per-listing-type
+        // preflight: their `listingType` describes the wrapper, not the members, so
+        // a per-type rule would be applied to the wrong thing. Tested via the shared
+        // predicate rather than `bundleProductIds?.length`, which answers "is this a
+        // legacy bundle" and would say no for a `groupMembers`-backed line.
+        if (isMultiMemberLine(pair.item))
+            continue;
         const lt = (pair.item.listingType ?? "standard");
         const bucket = byType.get(lt) ?? [];
         bucket.push(pair);

package/dist/_internal/shared/features/cart/config.d.ts

@@ -1,3 +1,4 @@
-export declare const CART_MAX_ITEMS = 50;
+/** Re-exported from the single declaration — see `constants/limits.ts`. */
+export { CART_MAX_ITEMS } from "../../../../constants/limits";
 export declare const CART_SESSION_TTL_DAYS = 30;
 export declare const CART_GUEST_STORAGE_KEY = "appkit:cart";

package/dist/_internal/shared/features/cart/config.js

@@ -1,3 +1,4 @@
-export const CART_MAX_ITEMS = 50;
+/** Re-exported from the single declaration — see `constants/limits.ts`. */
+export { CART_MAX_ITEMS } from "../../../../constants/limits";
 export const CART_SESSION_TTL_DAYS = 30;
 export const CART_GUEST_STORAGE_KEY = "appkit:cart";

package/dist/_internal/shared/features/cart/schema.d.ts

@@ -22,9 +22,9 @@ export declare const addToCartSchema: z.ZodObject<{
     productId: string;
     productTitle: string;
     productImage: string;
+    isOffer?: boolean | undefined;
     offerId?: string | undefined;
     lockedPrice?: number | undefined;
-    isOffer?: boolean | undefined;
 }, {
     storeId: string;
     price: number;
@@ -35,9 +35,9 @@ export declare const addToCartSchema: z.ZodObject<{
     storeName?: string | undefined;
     quantity?: number | undefined;
     productImage?: string | undefined;
+    isOffer?: boolean | undefined;
     offerId?: string | undefined;
     lockedPrice?: number | undefined;
-    isOffer?: boolean | undefined;
 }>;
 export declare const updateCartItemSchema: z.ZodObject<{
     productId: z.ZodString;
@@ -80,9 +80,9 @@ export declare const mergeGuestCartSchema: z.ZodObject<{
         productId: string;
         productTitle: string;
         productImage: string;
+        isOffer?: boolean | undefined;
         offerId?: string | undefined;
         lockedPrice?: number | undefined;
-        isOffer?: boolean | undefined;
     }, {
         storeId: string;
         price: number;
@@ -93,9 +93,9 @@ export declare const mergeGuestCartSchema: z.ZodObject<{
         storeName?: string | undefined;
         quantity?: number | undefined;
         productImage?: string | undefined;
+        isOffer?: boolean | undefined;
         offerId?: string | undefined;
         lockedPrice?: number | undefined;
-        isOffer?: boolean | undefined;
     }>, "many">;
 }, "strip", z.ZodTypeAny, {
     guestItems: {
@@ -108,9 +108,9 @@ export declare const mergeGuestCartSchema: z.ZodObject<{
         productId: string;
         productTitle: string;
         productImage: string;
+        isOffer?: boolean | undefined;
         offerId?: string | undefined;
         lockedPrice?: number | undefined;
-        isOffer?: boolean | undefined;
     }[];
 }, {
     guestItems: {
@@ -123,9 +123,9 @@ export declare const mergeGuestCartSchema: z.ZodObject<{
         storeName?: string | undefined;
         quantity?: number | undefined;
         productImage?: string | undefined;
+        isOffer?: boolean | undefined;
         offerId?: string | undefined;
         lockedPrice?: number | undefined;
-        isOffer?: boolean | undefined;
     }[];
 }>;
 /**

package/dist/_internal/shared/features/notifications/action-url.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Where does a notification LAND?
+ *
+ * ## The problem this solves
+ *
+ * `actionUrl` was set by **5 of 40** `sendNotification()` call sites, so the
+ * other 35 arrived in the bell as text with nothing to click. Every writer
+ * that did set one hand-wrote the path, which is the same drift the ROUTES
+ * map exists to prevent.
+ *
+ * Worse, the destination is **role-dependent**: an offer notification sent to
+ * the buyer belongs at `/user/offers`, the same event sent to the seller at
+ * `/store/offers`, and an admin escalation at `/admin/offers`. A per-writer
+ * literal cannot express that, so writers that guessed a single path sent
+ * half their recipients somewhere they have no permission to be.
+ *
+ * ## Honest fallbacks, not invented pages
+ *
+ * `bid`, `offer` and `review` still have **no per-record page in any role** —
+ * W8 fixed those dead-end listings with a detail MODAL, not a route. So this
+ * resolver points them at the list the record lives in. That is a real,
+ * permitted, useful destination; fabricating `/user/bids/{id}` would produce
+ * a 404 and `audit-nav-page-wiring` would (correctly) fail on the ROUTES key.
+ *
+ * When those pages are built, change the entry here and all 40 call sites
+ * follow. That is the whole point of the indirection.
+ */
+import type { NotificationRelatedType } from "../../../../features/admin/schemas/firestore";
+/**
+ * Which portal the recipient reads this in.
+ *
+ * Deliberately NOT the `role` string off the session: a seller is also a
+ * buyer, and which portal a notification belongs to is a property of the
+ * EVENT, not of the person. The order-shipped notification goes to the buyer
+ * in `/user`, and the same shipment's payout notification goes to the same
+ * human in `/store`.
+ */
+export type NotificationAudience = "buyer" | "seller" | "admin";
+/**
+ * Resolve the page a notification should open.
+ *
+ * Returns `undefined` when there is genuinely nowhere to go — a `promotion`
+ * or a `welcome` has no record behind it — so the caller renders a plain,
+ * non-clickable row rather than a link to the dashboard the user is already
+ * looking at.
+ */
+export declare function resolveNotificationActionUrl(relatedType: NotificationRelatedType | undefined, relatedId: string | undefined, audience: NotificationAudience): string | undefined;

package/dist/_internal/shared/features/notifications/action-url.js

@@ -0,0 +1,111 @@
+/**
+ * Where does a notification LAND?
+ *
+ * ## The problem this solves
+ *
+ * `actionUrl` was set by **5 of 40** `sendNotification()` call sites, so the
+ * other 35 arrived in the bell as text with nothing to click. Every writer
+ * that did set one hand-wrote the path, which is the same drift the ROUTES
+ * map exists to prevent.
+ *
+ * Worse, the destination is **role-dependent**: an offer notification sent to
+ * the buyer belongs at `/user/offers`, the same event sent to the seller at
+ * `/store/offers`, and an admin escalation at `/admin/offers`. A per-writer
+ * literal cannot express that, so writers that guessed a single path sent
+ * half their recipients somewhere they have no permission to be.
+ *
+ * ## Honest fallbacks, not invented pages
+ *
+ * `bid`, `offer` and `review` still have **no per-record page in any role** —
+ * W8 fixed those dead-end listings with a detail MODAL, not a route. So this
+ * resolver points them at the list the record lives in. That is a real,
+ * permitted, useful destination; fabricating `/user/bids/{id}` would produce
+ * a 404 and `audit-nav-page-wiring` would (correctly) fail on the ROUTES key.
+ *
+ * When those pages are built, change the entry here and all 40 call sites
+ * follow. That is the whole point of the indirection.
+ */
+import { ROUTES } from "../../../../next/routing/route-map";
+/**
+ * Resolve the page a notification should open.
+ *
+ * Returns `undefined` when there is genuinely nowhere to go — a `promotion`
+ * or a `welcome` has no record behind it — so the caller renders a plain,
+ * non-clickable row rather than a link to the dashboard the user is already
+ * looking at.
+ */
+export function resolveNotificationActionUrl(relatedType, relatedId, audience) {
+    if (!relatedType || !relatedId)
+        return undefined;
+    switch (relatedType) {
+        case "order":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.ORDER_DETAIL(relatedId))
+                : audience === "seller"
+                    ? String(ROUTES.STORE.ORDER_DETAIL(relatedId))
+                    : String(ROUTES.USER.ORDER_DETAIL(relatedId));
+        case "product":
+            // The public listing page — the one destination that is the same for
+            // everyone, because a product page is public.
+            return String(ROUTES.PUBLIC.PRODUCT_DETAIL(relatedId));
+        // ── List-level, because no per-record page exists in ANY role ─────────
+        // W8 gave these listings a detail modal rather than a route. Linking the
+        // list is honest; a fabricated `/…/{id}` would 404.
+        case "bid":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.BIDS)
+                : audience === "seller"
+                    ? String(ROUTES.STORE.BIDS)
+                    : String(ROUTES.USER.BIDS);
+        case "offer":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.OFFERS)
+                : audience === "seller"
+                    ? String(ROUTES.STORE.OFFERS)
+                    : String(ROUTES.USER.OFFERS);
+        case "review":
+            // The public review page exists; the admin/seller sides are modals.
+            return String(ROUTES.PUBLIC.REVIEW_DETAIL(relatedId));
+        case "blog":
+            return String(ROUTES.BLOG.ARTICLE(relatedId));
+        case "user":
+            // Only an admin has a per-user page. A user notified ABOUT themselves
+            // (a ban, a role change) belongs on their own account hub, not on a
+            // page they cannot open.
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.USER_DETAIL(relatedId))
+                : String(ROUTES.USER.PROFILE);
+        case "support_ticket":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.SUPPORT_TICKET_BY_ID(relatedId))
+                : String(ROUTES.USER.SUPPORT_TICKET(relatedId));
+        case "scammer":
+            // Admin-only surface — the public scam registry is browsed, not
+            // notified about.
+            return audience === "admin" ? String(ROUTES.ADMIN.SCAMMER_BY_ID(relatedId)) : undefined;
+        case "catalogueItem":
+            // The owner edits it; an admin reviews it from the approvals queue,
+            // which is a list because approval is a queue-shaped job.
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.CATALOGUE_APPROVALS)
+                : String(ROUTES.USER.CATALOGUE_EDIT(relatedId));
+        case "payout":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.PAYOUT_DETAIL(relatedId))
+                : String(ROUTES.STORE.PAYOUT_DETAIL(relatedId));
+        case "store":
+            return audience === "admin"
+                ? String(ROUTES.ADMIN.STORE_DETAIL(relatedId))
+                : String(ROUTES.STORE.DASHBOARD);
+        default: {
+            /*
+             * Exhaustiveness. A new `relatedType` cannot compile without an answer
+             * to "where does this land", which is precisely the check that was
+             * missing when `catalogueItem` was smuggled in behind an `as never`.
+             */
+            const _exhaustive = relatedType;
+            void _exhaustive;
+            return undefined;
+        }
+    }
+}

package/dist/client.d.ts

@@ -262,6 +262,8 @@ export type { WishlistCapEventDetail } from "./features/wishlist/hooks/useWishli
 export { getGuestWishlistItems, addToGuestWishlist, removeFromGuestWishlist, isInGuestWishlist, clearGuestWishlist, getGuestWishlistCount, getGuestWishlistByType, } from "./features/wishlist/utils/guest-wishlist";
 export { InteractiveProductCard } from "./features/products/index";
 export type { InteractiveProductCardProps } from "./features/products/index";
+export { GroupMemberPicker } from "./features/products/components/GroupMemberPicker";
+export type { GroupMemberPickerProps, GroupPickerMember, } from "./features/products/components/GroupMemberPicker";
 export { MarketplaceBundleCard } from "./features/products/components/MarketplaceBundleCard";
 export type { MarketplaceBundleCardProps, MarketplaceBundleCardData, MarketplaceBundleCardLabels, } from "./features/products/components/MarketplaceBundleCard";
 export { CompareOverlay } from "./features/products/components/CompareOverlay";

package/dist/client.js

@@ -282,6 +282,7 @@ export { SyncManagerMount } from "./core/components/SyncManagerMount";
 export { useWishlistCount, useWishlistCountWithLimit, WISHLIST_CAP_EVENT } from "./features/wishlist/hooks/useWishlistCount";
 export { getGuestWishlistItems, addToGuestWishlist, removeFromGuestWishlist, isInGuestWishlist, clearGuestWishlist, getGuestWishlistCount, getGuestWishlistByType, } from "./features/wishlist/utils/guest-wishlist";
 export { InteractiveProductCard } from "./features/products/index";
+export { GroupMemberPicker } from "./features/products/components/GroupMemberPicker";
 export { MarketplaceBundleCard } from "./features/products/components/MarketplaceBundleCard";
 export { CompareOverlay } from "./features/products/components/CompareOverlay";
 export { COMPARE_MAX_ITEMS } from "./features/products/constants/action-defs";

package/dist/constants/api-endpoints.d.ts

@@ -239,6 +239,15 @@ export declare const CART_ENDPOINTS: {
     /** Per-store paid add-on selections — the source of truth for what's charged. */
     readonly ADDONS: "/api/cart/addons";
     readonly COUPON: "/api/cart/coupon";
+    /**
+     * Add a buyer-assembled group selection as ONE line. Separate from `GET`'s
+     * POST on purpose: that is the hot path behind every product card's
+     * Add-to-cart, and widening its `{productId, quantity}` schema into a
+     * discriminated union would put this feature's blast radius on it.
+     */
+    readonly GROUP: "/api/cart/group";
+    /** Replace a grouped line's member quantities (whole array, not a delta). */
+    readonly GROUP_MEMBERS: (itemId: string) => string;
 };
 export declare const CATEGORY_ENDPOINTS: {
     readonly LIST: "/api/categories";
@@ -695,6 +704,15 @@ export declare const API_ENDPOINTS: {
         /** Per-store paid add-on selections — the source of truth for what's charged. */
         readonly ADDONS: "/api/cart/addons";
         readonly COUPON: "/api/cart/coupon";
+        /**
+         * Add a buyer-assembled group selection as ONE line. Separate from `GET`'s
+         * POST on purpose: that is the hot path behind every product card's
+         * Add-to-cart, and widening its `{productId, quantity}` schema into a
+         * discriminated union would put this feature's blast radius on it.
+         */
+        readonly GROUP: "/api/cart/group";
+        /** Replace a grouped line's member quantities (whole array, not a delta). */
+        readonly GROUP_MEMBERS: (itemId: string) => string;
     };
     readonly CATEGORIES: {
         readonly LIST: "/api/categories";
@@ -1153,6 +1171,15 @@ export declare const API_ROUTES: {
         /** Per-store paid add-on selections — the source of truth for what's charged. */
         readonly ADDONS: "/api/cart/addons";
         readonly COUPON: "/api/cart/coupon";
+        /**
+         * Add a buyer-assembled group selection as ONE line. Separate from `GET`'s
+         * POST on purpose: that is the hot path behind every product card's
+         * Add-to-cart, and widening its `{productId, quantity}` schema into a
+         * discriminated union would put this feature's blast radius on it.
+         */
+        readonly GROUP: "/api/cart/group";
+        /** Replace a grouped line's member quantities (whole array, not a delta). */
+        readonly GROUP_MEMBERS: (itemId: string) => string;
     };
     readonly CATEGORIES: {
         readonly LIST: "/api/categories";

package/dist/constants/api-endpoints.js

@@ -279,6 +279,15 @@ export const CART_ENDPOINTS = {
     /** Per-store paid add-on selections — the source of truth for what's charged. */
     ADDONS: "/api/cart/addons",
     COUPON: "/api/cart/coupon",
+    /**
+     * Add a buyer-assembled group selection as ONE line. Separate from `GET`'s
+     * POST on purpose: that is the hot path behind every product card's
+     * Add-to-cart, and widening its `{productId, quantity}` schema into a
+     * discriminated union would put this feature's blast radius on it.
+     */
+    GROUP: "/api/cart/group",
+    /** Replace a grouped line's member quantities (whole array, not a delta). */
+    GROUP_MEMBERS: (itemId) => `/api/cart/${encodeURIComponent(itemId)}/members`,
 };
 // ---------------------------------------------------------------------------
 // Categories

package/dist/constants/notification-types.d.ts

@@ -1,18 +1,46 @@
 /**
- * Notification Type Registry — W1-33
+ * Notification Type Registry — DERIVED, not restated.
  *
- * Canonical list of notification type IDs. Shared across:
- *  - AdminNotificationsView filter chips
- *  - NotificationPreferencesPanel (per-type toggles)
- *  - sendNotification() dispatch (type-based channel routing)
+ * ## What this file used to be, and why it mattered
  *
- * Add new types here. Don't redefine the list inline in components.
+ * A hand-written 9-value list that called itself "canonical" while
+ * `NotificationDocument.type` held 27. Two of its nine —`review_posted` and
+ * `payout_processed` — were not real values at all, so those chips matched
+ * zero rows forever. Its two consumers were not cosmetic:
+ *
+ *  · `AdminNotificationsView`'s filter chips, so an admin could not filter
+ *    **18 of the 27 real types** and was offered two that never appear.
+ *  · `AdminSiteSettingsView`'s per-channel allow-list, so an admin literally
+ *    **could not allow-list `offer_received` or `payment_review`** for email
+ *    or WhatsApp — the toggle did not exist.
+ *
+ * Everything here now derives from `NOTIFICATION_TYPE_VALUES`, so a new
+ * notification type is one edit and cannot be missing from either surface.
+ *
+ * ## Why the import points where it does
+ *
+ * `features/admin/schemas/firestore.ts` imports nothing from `constants/`,
+ * so this direction is acyclic. That is NOT true of `field-names.ts`, which
+ * is a deliberate leaf that `features/products/types` imports — which is why
+ * that file keeps its duplicated values and relies on an audit instead.
+ */
+import { NOTIFICATION_TYPE_VALUES } from "../features/admin/schemas/firestore";
+import type { NotificationType } from "../features/admin/schemas/firestore";
+export { NOTIFICATION_TYPE_VALUES };
+export type { NotificationType };
+/** Alias kept for the two existing importers. */
+export declare const NOTIFICATION_TYPES: readonly ["order_placed", "order_confirmed", "order_shipped", "order_delivered", "order_cancelled", "bid_placed", "bid_outbid", "bid_won", "bid_lost", "auction_ended", "review_approved", "review_replied", "product_available", "promotion", "system", "welcome", "account_action", "offer_received", "offer_responded", "offer_expired", "offer_counter_accepted", "refund_initiated", "prize_won", "prize_reveal_expired", "emi_installment_due_soon", "emi_installment_overdue", "payment_review", "catalogue_images_stale"];
+/**
+ * `order_shipped` → `Order shipped`.
+ *
+ * Derived rather than hand-labelled: a hand-written label map is the same
+ * drift risk one layer down, and every one of these values is already a
+ * readable snake_case phrase.
  */
-export declare const NOTIFICATION_TYPES: readonly ["order_placed", "order_shipped", "order_delivered", "order_cancelled", "bid_placed", "bid_outbid", "bid_won", "review_posted", "payout_processed"];
-export type NotificationType = (typeof NOTIFICATION_TYPES)[number];
+export declare function notificationTypeLabel(type: NotificationType | string): string;
 /**
- * Shape used by filter-chip rows (id + display label).
- * Prepended with an "All" option for the typical filter-chip pattern.
+ * Shape used by filter-chip rows (id + display label), with the usual "All"
+ * option prepended.
  */
 export declare const NOTIFICATION_TYPE_TABS: ReadonlyArray<{
     id: string;

package/dist/constants/notification-types.js

@@ -1,37 +1,48 @@
 /**
- * Notification Type Registry — W1-33
+ * Notification Type Registry — DERIVED, not restated.
  *
- * Canonical list of notification type IDs. Shared across:
- *  - AdminNotificationsView filter chips
- *  - NotificationPreferencesPanel (per-type toggles)
- *  - sendNotification() dispatch (type-based channel routing)
+ * ## What this file used to be, and why it mattered
  *
- * Add new types here. Don't redefine the list inline in components.
+ * A hand-written 9-value list that called itself "canonical" while
+ * `NotificationDocument.type` held 27. Two of its nine —`review_posted` and
+ * `payout_processed` — were not real values at all, so those chips matched
+ * zero rows forever. Its two consumers were not cosmetic:
+ *
+ *  · `AdminNotificationsView`'s filter chips, so an admin could not filter
+ *    **18 of the 27 real types** and was offered two that never appear.
+ *  · `AdminSiteSettingsView`'s per-channel allow-list, so an admin literally
+ *    **could not allow-list `offer_received` or `payment_review`** for email
+ *    or WhatsApp — the toggle did not exist.
+ *
+ * Everything here now derives from `NOTIFICATION_TYPE_VALUES`, so a new
+ * notification type is one edit and cannot be missing from either surface.
+ *
+ * ## Why the import points where it does
+ *
+ * `features/admin/schemas/firestore.ts` imports nothing from `constants/`,
+ * so this direction is acyclic. That is NOT true of `field-names.ts`, which
+ * is a deliberate leaf that `features/products/types` imports — which is why
+ * that file keeps its duplicated values and relies on an audit instead.
  */
-export const NOTIFICATION_TYPES = [
-    "order_placed",
-    "order_shipped",
-    "order_delivered",
-    "order_cancelled",
-    "bid_placed",
-    "bid_outbid",
-    "bid_won",
-    "review_posted",
-    "payout_processed",
-];
+import { NOTIFICATION_TYPE_VALUES } from "../features/admin/schemas/firestore";
+export { NOTIFICATION_TYPE_VALUES };
+/** Alias kept for the two existing importers. */
+export const NOTIFICATION_TYPES = NOTIFICATION_TYPE_VALUES;
+/**
+ * `order_shipped` → `Order shipped`.
+ *
+ * Derived rather than hand-labelled: a hand-written label map is the same
+ * drift risk one layer down, and every one of these values is already a
+ * readable snake_case phrase.
+ */
+export function notificationTypeLabel(type) {
+    return String(type).replace(/_/g, " ").replace(/^./, (c) => c.toUpperCase());
+}
 /**
- * Shape used by filter-chip rows (id + display label).
- * Prepended with an "All" option for the typical filter-chip pattern.
+ * Shape used by filter-chip rows (id + display label), with the usual "All"
+ * option prepended.
  */
 export const NOTIFICATION_TYPE_TABS = [
     { id: "All", label: "All" },
-    { id: "order_placed", label: "Order placed" },
-    { id: "order_shipped", label: "Order shipped" },
-    { id: "order_delivered", label: "Order delivered" },
-    { id: "order_cancelled", label: "Order cancelled" },
-    { id: "bid_placed", label: "Bid placed" },
-    { id: "bid_outbid", label: "Bid outbid" },
-    { id: "bid_won", label: "Bid won" },
-    { id: "review_posted", label: "Review posted" },
-    { id: "payout_processed", label: "Payout processed" },
+    ...NOTIFICATION_TYPE_VALUES.map((id) => ({ id, label: notificationTypeLabel(id) })),
 ];

package/dist/features/account/types/index.d.ts

@@ -37,16 +37,7 @@ export interface UserOrder {
     createdAt?: string;
     updatedAt?: string;
 }
-export type NotificationType = "order" | "offer" | "promo" | "system" | "message";
-export interface UserNotification {
-    id: string;
-    title: string;
-    message: string;
-    type: NotificationType;
-    isRead: boolean;
-    createdAt: string;
-    href?: string;
-}
+export type { NotificationType } from "../../admin/schemas/firestore";
 export type OfferStatus = "pending" | "countered" | "accepted" | "paid" | "declined" | "expired" | "withdrawn";
 export interface UserOffer {
     id: string;

package/dist/features/admin/actions/notification-actions.d.ts

@@ -1,4 +1,5 @@
 import type { NotificationDocument, NotificationCreateInput } from "../schemas";
+import { type NotificationAudience } from "../../../_internal/shared/features/notifications/action-url";
 export declare function markNotificationRead(id: string): Promise<void>;
 export declare function markAllNotificationsRead(userId: string): Promise<number>;
 export declare function deleteNotification(id: string): Promise<void>;
@@ -16,6 +17,17 @@ export interface SendNotificationInput extends NotificationCreateInput {
     emailHtml?: string;
     /** Buyer paid the ₹10 WhatsApp order-updates addon — enables WhatsApp channel for this notification even when the user has no standing WhatsApp subscription. */
     orderWhatsappAddonPaid?: boolean;
+    /**
+     * Which portal the recipient reads this in — decides where `actionUrl`
+     * points when the caller does not supply one.
+     *
+     * Defaults from the notification TYPE, not from the recipient's role: a
+     * seller is also a buyer, and `order_shipped` belongs in `/user` while the
+     * payout for that same order belongs in `/store`. Pass it explicitly only
+     * when one type genuinely reaches two audiences — `offer_received` goes to
+     * the seller, `offer_responded` back to the buyer.
+     */
+    audience?: NotificationAudience;
 }
 export interface SendNotificationResult {
     notification: NotificationDocument;