Good questions.
Clear boundaries.
What Halo RFQ demonstrates, what current evidence supports and what still needs to be agreed.
Who is Halo RFQ for?
Industrial manufacturers, manufacturers’ representatives, distributors and service teams that need a clearer capture-to-review handoff. Workflow fit and deployment requirements should be evaluated in a scoped pilot.
Is this just a QR-code generator?
No. The focus is capturing RFQ information and preserving context for human review. QR is one possible entry aid. A known part number can start the process without a new tag deployment.
Does Halo RFQ choose a replacement or provide a quote?
No. A part identifier or capture suggestion is not a suitability decision. Engineering, selection, pricing, quoting, ordering and approval stay with qualified people and the relevant business process.
Does it require Salesforce?
The standalone implementation is separate from Salesforce-native work. This website combines ideas in a synthetic walkthrough; it does not establish feature parity or connect the implementations. Confirm the right scope, licensing and responsibilities during evaluation.
Can I scan a label or use OCR?
Current standalone source includes local QR image/camera decoding and English label OCR suggestions that require explicit application. Recorded phone acceptance exists. This website uses a fictional label and requests no camera access. Broader accuracy or autonomous part selection is not claimed.
Will a request automatically email my distributor?
No such promise is made. Standalone email previews and local test tools exist, but ST-67 live authentication and delivery acceptance remain pending. Salesforce notification source is separate and does not establish current delivery acceptance. Nothing is sent by this website.
Which integrations are available?
Salesforce-native work is a distinct implementation. Optional ERP, PIM, PLM and other Salesforce cloud adapters are proposed future scope. No live connector operates in this website.
Is it production-ready or AppExchange-approved?
Production readiness is not established. A managed-package release and AppExchange listing or approval are not established. Security, operational, licensing and end-to-end acceptance must be reviewed for the intended deployment.
What does it cost and how long does implementation take?
No prices, fixed rollout times or license commitments are published. Discuss user roles, workflow scope, software and third-party licensing, configuration, training and support to define a proposal.
What happens to information entered in this demo?
It stays in the current page’s memory. No backend request, CRM write, email, analytics or persistent storage is used. Enter fictional information only. Reset or refresh to discard changes.
How can we discuss a pilot?
Use Discuss a Pilot to view the conversation topics and open an email draft to halobusinesssystems@gmail.com. Your email app handles the draft; you decide whether to send. This site has no contact form and collects no leads.
See the context.
Explore the conversation.
A synthetic walkthrough today. A scoped pilot conversation next.