source: .forge/discovery/research/tea-export-domain-notes.md Β· generated β€” edit the markdown, not this file

Tea Export / Private-Label Domain Notes

Date: 2026-06-17
Context: Domain orientation for Empire Teas CRM + AI discovery.

Business workflow to keep in mind

Lead / buyer inquiry
β†’ qualification
β†’ product brief
β†’ sample development
β†’ sample dispatch
β†’ sample feedback
β†’ quotation
β†’ negotiation
β†’ confirmed order
β†’ ERP handoff
β†’ production / packing / QC
β†’ export documentation
β†’ shipment
β†’ payment / reorder / account growth

Why this domain is CRM-heavy

Tea exporters and private-label manufacturers manage long-running customer relationships, repeated product development cycles, and many follow-ups before an order becomes real.

CRM needs to track more than β€œdeal amount”:

  • Country/market.
  • Buyer type.
  • Product interest.
  • Packaging format.
  • Certification requirements.
  • Sample status.
  • Quote status.
  • Customer-specific preferences.
  • Reorder cycles.
  • Complaints and claims.
  • Trade fair interactions.

Private-label complexity

Private-label customers may require:

  • Custom blend.
  • Custom packaging.
  • Local language labels.
  • Halal/Kosher/Organic/Fairtrade/FDA/other certification evidence.
  • Samples and approvals before ordering.
  • Multiple quote revisions.
  • Country-specific import/export documents.

This creates many handoffs between sales, tea tasters/R&D, packaging, QA, export documentation, and eventually ERP/order processing.

Best-fit AI areas

AI should support repetitive knowledge/document/communication work:

  • Extract inquiry requirements from email.
  • Draft customer replies.
  • Generate internal product briefs.
  • Summarize account history.
  • Find similar previous deals/quotes.
  • Draft follow-up emails.
  • Read shipping instructions and create document checklist.
  • Search certifications/SOPs/product docs.

AI should not autonomously decide:

  • Final pricing.
  • Compliance approval.
  • Export clearance.
  • Quality release.
  • Financial posting.

CRM-to-ERP boundary

CRM should own:

  • Leads.
  • Customer/account relationships.
  • Opportunities.
  • Samples.
  • Quote follow-up.
  • Communications.
  • Pre-order workflow.

ERP should own:

  • Confirmed sales orders.
  • Inventory.
  • Procurement.
  • Production.
  • Warehouse.
  • Finance.
  • Invoicing.
  • Core transaction records.

Potential shared/integrated data:

  • Customer master.
  • Product/SKU references.
  • Order status.
  • Shipment status.
  • Invoice/payment status.
  • Document links.

Discovery watch-outs

  • Do not let CRM become a mini-ERP.
  • Do not design AI without clean CRM stages and fields.
  • Sample/quote workflows may currently live in Excel/WhatsApp/email.
  • Sales teams may resist extra CRM data entry unless automation reduces work.
  • ERP migration may create timing/integration uncertainty.

Generated from .forge/discovery/research/tea-export-domain-notes.md by .claude/lib/render-docs-html.js. Markdown is canonical.