source: .forge/discovery/meeting-notes/2026-08-03-requirements-clarification.md · generated — edit the markdown, not this file

Empire Teas CRM — Requirements Clarification Meeting Notes

Date: 3 August 2026 Meeting: Discussion — Requirements clarification Attendees: Thilina Abeyrathna (Altrium), Rukshan Salgado (Altrium), Dinil Gamage (Altrium); Kavindu Anthony (Empire Teas, kavindu@empire.lk), Praveen (Empire Teas) Source: Google Meet transcript + Gemini-generated notes (some recordings unavailable). Cleaned and reproduced here as the discovery record.

Why this file exists: this meeting answered the “Closing Pre-Kickoff Questions” (sent 28 July 2026). The confirmed answers were folded into the PRD as Rev 6 and into the project proposal (v0.3). See project-prd-history.md ### Rev 6 and the resolved OQ rows (OQ-10, OQ-11, OQ-38, OQ-40, OQ-42, OQ-45, OQ-47). The one item left open is OQ-9 (product-held certifications) — see the action items below.


Summary

Pricing structure, approval hierarchy, roles/access, and a few operational workflows were clarified. The most consequential outcomes: bulk pricing is keyed to client-specific buying standards (each with a unique running number), there is no formal volume tiering, quote approval runs on a gross-profit-margin floor with Managing Director sign-off for below-margin deals, the Tea Room is a separate team needing its own access, and the tea-auction system exposes a public API.

Action items

  • Kavindu Anthony — contact Kavi Amali to clarify how product certifications are stored and managed (the product side of the certification mapping).
  • Praveen — obtain and provide the relevant Quality Control (QC) documentation.

Details

Product grades and client standards

Praveen explained that clients may use multiple grades or “buying standards” within a single scenario, and that competition percentages can help determine the standard price. A single client (e.g. a Turkish client) might purchase multiple standards, such as BOP1 and POSOS. Weekly prices are offered to clients for these various standards; bulk buyers typically purchase according to their preferences and current market prices across four to five different standards. Each standard is assigned a unique, client-specific running number, so the same identifier is never used for different clients. [~00:00–00:01]

Volume-based pricing

Asked whether there is a formal tiered structure for volume-based pricing, Praveen clarified that the company has no formal tier structure. Price drops are generally associated with value addition rather than order volume; ordering more material can give a small price composition, but bulk bag orders (whether a 20-foot or 40-foot container) see very nominal fluctuations of only one or two cents. [~00:01–00:02]

Certification management

On how product certifications are tracked, Praveen said the process is straightforward and suggested Kavi Amali as the right person to consult. Kavindu committed to connecting with the relevant department to clarify how certifications are stored. (Product-side certification data is still outstanding — see action items.) [~00:03]

Payment terms

Standard payment terms discussed: Letters of Credit (LC), Open Account, Documents Against Acceptance (DA), and Cash Against Documents (CAD). Praveen confirmed they also work with advance payments at varying percentages, and that the three main categories — LC, DA, and CAD — cover the primary structures. Terms are defined per customer by the finance department, and the specific terms are visible within the [ERP] system. [~00:03–00:05]

Sample development rounds

On the average number of sample rounds to close a typical private-label deal: if matching a client’s existing sample, typically one or two attempts; developing a new standard to suit a specific market can take six or seven rounds. Deals are almost always locked before reaching ten rounds. [~00:05–00:06]

Market-based pricing

Pricing is completely different depending on the destination market. Prices for Europe are high, while prices for Palestine / Eastern markets are very nominal — pricing fluctuates based on the specific market. [~00:06–00:07]

Pricing approval process

Representatives are given a required gross-profit percentage that must be maintained. The system holds costing information, and staff can offer prices within the established margins without special approval. Any new contract that does not achieve the required gross-profit percentage must receive special approval from the Managing Director before it can be processed. [~00:07–00:08]

Tea Room team access

The “T-room” (Tea Room) team is a separate entity from the R&D / tea-taster role and requires its own access to the system. [~00:09]

Auction system integration

On the tea-auction system: it is integrated with the current ERP, and a public API is available for the team to retrieve the necessary data. [~00:09–00:10]

Executive access roles

A separate executive read-only access role is required (system oversight without the ability to modify data). More broadly, they need distinct levels of access for different users, including read-only, edit, AI, and execute permissions. [~00:10]

Generated from .forge/discovery/meeting-notes/2026-08-03-requirements-clarification.md by .claude/lib/render-docs-html.js. Markdown is canonical.