Use public-safe sourcing examples, applications, swatch requests, RFQs, quotes, dashboards, and protected exports.
Help Center
Find the right intake path for buyer applications, mill verification, swatch requests, RFQs, and quote review during the AURELEAN MVP.
I am a buyer. Where do I start?
Use the buyer application for founding access, browse the catalogue, save fabrics, then create an RFQ when you are ready to compare mills.
- Include company, role, fabric categories, target regions, and sourcing timeline.
- Use the swatch box path when you need physical material review before RFQ comparison.
I am a mill. How do I join?
Submit the mill partner application. AURELEAN reviews specialties, certifications, swatch support, and RFQ readiness before verification.
- List certificate names and active material categories, not confidential client contracts.
- Use the verification page to understand the staged MVP review criteria.
What happens after I submit?
AURELEAN routes intake into the current review queue, scores completeness, and uses the submitted sourcing context to decide the next buyer, mill, swatch, or RFQ step.
Are quotes and orders production binding?
In MVP demo mode, quote and order records may be synthetic workflow examples. Treat them as product validation unless a separate commercial agreement exists.
What should I avoid submitting?
Do not submit confidential purchase orders, private price books, personal payment details, regulated documents, or buyer/supplier contracts until authenticated production storage is active.
Client Intake Readiness
AURELEAN can support controlled demos and qualification intake today. Before confidential procurement use, the platform still needs verified deployment, authenticated workspaces, durable persistence, and reviewer access controls.
Collect buyer and mill context, certificate names, renewal context, and sourcing intent without private contracts.
Do not submit purchase orders, regulated documents, private price books, or supplier contracts until production storage exists.
Select deployment, add auth/RBAC, move off JSON persistence, add object storage, and rerun browser QA.
Client-intake readiness depends on verified deployment, production persistence, authenticated workspaces, and reviewer access controls. The current MVP pages collect qualification context and route serious inquiries without claiming final transaction infrastructure.