A Portal for Partners, Rituals, and After-Sales

Client Portal / Kettl Tea / Crash Baggage

A client portal should not feel like a locked drawer behind a website. It should feel like the private part of the relationship: the place where the brand continues after purchase, partnership, service, education, and support.

Kettl Tea and Crash Baggage are useful together because they sit at opposite ends of tone. Kettl is quiet, precise, educational, and ritual-based. Crash Baggage is loud, playful, and built around a refusal of perfect surfaces. One sells tea through origin, craft, freshness, and preparation. The other sells luggage through attitude, damage, travel, and visual identity. The portal had to respect both worlds. It could not be a generic account area.

For Kettl, the portal needed to behave like a professional tea room, a wholesale desk, and a knowledge library. For Crash Baggage, it needed to behave like a product registration system, a repair flow, a travel archive, and a brand community layer.

The shared principle was post-purchase continuity.

The Problem

Most e-commerce systems treat the purchase as the end of the journey. For these brands, the purchase is closer to the beginning.

A Kettl customer may need to learn how to brew a specific tea, understand harvest notes, reorder at the right time, download information for a café menu, or train staff on preparation. A wholesale customer may need batch information, product photography, invoice history, education material, stock updates, and reorder suggestions.

A Crash Baggage customer may need to register a suitcase, request support, replace a part, submit a repair photo, access warranty information, or share the marks collected through travel. A retail partner may need campaign assets, product information, display guidance, and updated collection material.

The problem was not lack of information. The problem was that the information belonged to different relationships. Consumer, wholesale partner, retailer, internal operator, and support team all need different versions of the same brand system.

What We Diagnosed

We divided the portal into three user layers.

The first layer was Direct Customer. This user needs clarity: order history, product registration, usage guidance, care instructions, support status, and relevant recommendations.

The second layer was Professional Partner. This user needs operational material: wholesale ordering, batch information, staff training, product images, menus, line sheets, retail assets, and reorder timing.

The third layer was Internal Operator. This user needs control: customer records, partner permissions, support requests, asset updates, batch management, inventory signals, and service reporting.

Once these layers were separated, the portal became less about login and more about role-based experience.

What We Built

For Kettl, we designed a Tea Partner Portal.

The center of the system was the batch library. Each tea could carry origin, producer, harvest period, processing method, storage guidance, tasting notes, brewing parameters, and recommended use cases. This made the product more legible for both direct customers and professional partners. The portal also included brew guides, wholesale ordering, education material, staff training notes, product photography, menu descriptions, and reorder prompts. A café partner could log in, review the current tea lineup, download accurate descriptions, place a reorder, and train a new staff member without asking the Kettl team to resend the same files. The interface needed to feel calm. The work was operational, but the atmosphere had to stay close to the ritual of tea.

For Crash Baggage, we designed a Travel Care Portal.

The system began with product registration: model, color, purchase date, channel, warranty status, and owner record. From there, the customer could submit a support request, upload photos, check service status, purchase replacement parts, or access care information. The more brand-specific layer was the travel marks archive. Instead of treating dents and scratches only as damage, the portal could allow users to submit travel images, suitcase marks, stickers, airport tags, and stories. Support and community were held in the same space, but with different permissions and review flows. For retail partners, the portal provided campaign assets, product sheets, display references, collection updates, and wholesale support.

Automation Layer

The automation was designed to reduce repeated service work.

For Kettl, wholesale orders updated inventory signals. Reorder timing could be estimated from previous purchase cycles. New teas could trigger a draft brew guide template. Partner downloads could inform the sales team which products were receiving attention. Low inventory could prompt internal review before a partner reached out.

For Crash Baggage, product registration created a warranty profile. Repair requests entered a service pipeline. Uploaded photos were routed to support or community review depending on the request type. Retail asset downloads created a partner activity signal. Repeated service issues were grouped into product feedback reports.

The goal was not to make the portal feel automated. The goal was to make the brand feel more responsive.

Visual Direction

The two portals needed different emotional temperatures.

Kettl should feel like a quiet archive of taste: warm white space, dark typography, subtle green or clay tones, precise batch cards, calm photography, and slow interaction. A professional customer should feel that the information is trustworthy and cared for.

Crash Baggage should feel more graphic and immediate: bold typography, dented textures, travel tags, sticker logic, strong product silhouettes, and clear service states. Even the repair flow can carry the brand’s humor, as long as the process remains simple.

In both cases, the portal had to be useful before it was expressive. A portal that looks good but cannot answer a support question, reorder request, or partner need is only a hidden landing page.

Result

The portal turned post-purchase interaction into a structured brand relationship. Kettl gained a system for education, wholesale support, batch clarity, and repeat ordering. Crash Baggage gained a system for registration, service, parts, retail partners, and user-generated travel memory. In both cases, the portal reduced repeated manual communication while making the relationship feel more considered.

The best client portal is not a back office. It is the part of the brand customers return to when the first transaction is already over.