KISSA COFFEE HOUSE / 喫茶こもれび
KISSA
COFFEE HOUSE.
A hospitality case study that connects brand identity, menu context and a synthetic operating dataset to the EVA workflow — clean the mess, ask the business question, build the decision view.

A quiet cup, a gentle moment.The brand story, identity, menu, coffee beans, merchandise and visual materials below come from the supplied Kissa website and brand guideline assets.
WHAT IS DEMO-BASED?Every sales figure, customer pattern, stock warning, forecast and recommendation is generated as a synthetic EVA sample. It does not claim to describe the real business.
01 / Brand context
BEFORE WE TOUCH THE DATAA QUIET CUP.
A GENTLE MOMENT.
The supplied Kissa Komorebi brand is built around gentle pauses in everyday life: warm light, simple objects, good coffee and enough space to slow down.
“Komorebi” describes sunlight filtering gently through leaves. The identity translates that feeling into a hand-drawn branch and bird, a restrained palette and soft, tactile applications across cups, packaging, menus, coffee bags and merchandise.
.png)
.png)
.png)
Warm service, approachable flavours and a space that asks nothing from you.
Beans, brewing, packaging and details are considered slowly and intentionally.
Not a special occasion — a better little moment inside an ordinary day.
THE BUSINESS
UNIVERSE.
The data model should understand the business it represents. For Kissa, that means the menu, beans, merchandise and the experience around them — not only a generic “sales” column.
Drip Coffee · Americano · Café Latte · Cappuccino · Vanilla Latte.
Cheesecake · seasonal baked goods · simple food for a gentle pause.
Ethiopia Light Roast · Costa Rica Medium Roast · House Blend Dark Roast.
Tote bag · ceramic mug · travel mug · coaster set.



02 / The modeled business problem
THE DATA EXISTS.
THE DECISION SYSTEM DOESN'T.
POS exports, mobile orders, stock counts, loyalty fields and manual sheets arrive with different labels, formats and assumptions.
A generic dashboard can push volume without asking whether the service experience still feels calm, simple and on-brand.
Coffee, food, beans and goods behave differently. One total-sales number hides the margin, frequency and operational role of each category.
The goal is not more charts. It is a short list of what changed, why it matters and what to do next.
RAW → READY →
RECOMMEND.
The public Kissa sample deliberately begins messy. EVA DATA repairs the reporting layer, EVA AI lets the user choose the question, and EVA LABS turns the result into a structured management view.
Mixed dates, JPY strings, aliases, missing cells and duplicate IDs.
Products, channels, dates, numeric types and source metadata become consistent.
Insights · management dashboard · forecast · marketing opportunities.
KPIs, data health, product mix, customer patterns, forecast and notes.
Optional human review for marketing, pricing, operations or growth decisions.
03 / Same sample, one dashboard language
WHITE / BLACK / THIN TYPOGRAPHYTHE CASE STUDY
IS THE WORKSPACE.
The homepage, client case and EVA Workspace now use the same Kissa sample logic. This keeps the sales story consistent: see the raw data, see the cleanup, then see the business answer.
Protect calm service during the peak window.
The modeled signal says capacity and ingredient coverage should be fixed before traffic is increased.

Business recommendations are interpreted against the customer experience the brand is trying to create.
- 01Peak service.
Protect throughput without making the experience feel rushed.
- 02Seasonal pairing.
Test a simple coffee + bake bundle.
- 03Take-home growth.
Use beans and goods after-purchase, not as counter clutter.
- 01Protect peak capacity before demand generation.
The synthetic sample suggests the immediate constraint is service/stock reliability rather than awareness.
- 02Keep promotions simple.
A single coffee + seasonal bake test fits the brand better than a complex discount matrix.
- 03Grow basket outside the rush.
Beans and goods can lift value without adding operational complexity at peak.
A forecast is an assumption surface, not a promise.
Change average ticket, orders/day and COGS inside EVA Workspace to see how the curve moves.
DESIGNED AS
ONE SYSTEM.
The visual identity gives EVA more context than a spreadsheet alone. The case study therefore treats branding, product structure and operational data as parts of one business system.




Have raw data.
Need the decision layer?
Start with EVA DataLab for a small CSV, explore the Kissa sample in EVA Workspace, or ask EVALUATION to build a production data and decision system around your business.