Customers

1. 1

   Parse filters and pagination

   Customer list requests use server-side filters and page queries before UI renders rows.

   Relevant Product code

   • src/features/customers/server/list/filters.ts
   • src/features/customers/server/list/page-query.ts
2. 2

   Project list rows

   Projection helpers keep list rows compact and prevent detail-only fields from being loaded for every customer.

   Relevant Product code

   • src/features/customers/server/list/sensitive-data.ts
3. 3

   Resolve provider detail

   Detail pages use provider customer ids to load customer, billing, and related records.

   Relevant Product code

   • src/features/customers/shared/provider-customer-id.ts
   • src/features/customers/server/detail/customer.ts
4. 4

   Group billing context

   Billing grouping helpers organize subscriptions, invoices, charges, refunds, and disputes for detail UI.

   Relevant Product code

   • src/features/customers/server/billing/grouping.ts

Use this example as a starting point, then adapt it to your product's rules and configuration.

Customer directory reads are permission-gated, bounded in PostgreSQL, and masked according to the active profile's data permissions.

const profile = await getCachedActiveProfile();
if (!profile || !(await canAccessAsync(profile.role, "customerOperations"))) {
  throw new Error("Unauthorized");
}

const [supabase, provider, enabledModels] = await Promise.all([
  getServiceSupabase(),
  getBillingProvider(),
  getEnabledBillingModels(),
]);
const offset = (filters.page - 1) * filters.limit;

const { data, error } = await supabase.rpc("get_customer_directory_page", {
  p_provider: provider,
  p_enabled_models: enabledModels,
  p_query: safeQuery ?? undefined,
  p_population: filters.population,
  p_status: effectiveStatus,
  p_limit: filters.limit,
  p_offset: offset,
});
if (error) throw error;