Buyer FAQ

Questions about content, RFQs, and platform-owned customer data

WordPress helps publish procurement content. Supabase and the platform CRM continue to own inquiry capture, lead assignment, supplier access, and buyer data protection.

Is WordPress storing buyer inquiries?

No. WordPress only manages published content. RFQ submissions, CRM records, lead assignments, and supplier access remain in the platform-owned Supabase system.

Can a supplier see all leads from content traffic?

No. Supplier sales users only see qualified leads assigned inside the CRM. Content traffic and unassigned buyer records stay platform-owned.

Why use WordPress if the front end is Next.js?

WordPress gives operators an easy publishing backend, while Next.js keeps the public site fast, structured, and consistent with the industrial sourcing brand.

Can procurement guides link directly to RFQ?

Yes. Every content template routes buyers back to the platform RFQ form so SEO traffic can become structured, trackable buying intent.

Next step

Submit a structured RFQ through the platform

Product requirements and buyer contact details go into the platform CRM, not WordPress.

Go to RFQ