Halo RFQ helps industrial teams capture the information they have and keep the next decision in human hands.
Part identifier. Quantity. Request notes. Distributor / Sold By context in the Salesforce-native workflow. Each contributes to a clearer handoff.
This is the deployed Salesforce-native Quick RFQ form, captured October 16, 2026 with fictional values entered on screen. The form was not submitted.
Explore the Demo ↗
Open full screenshot ↗
Distributor / Sold By context gives a reviewer a starting point for checking the existing relationship before commercial follow-up. The demo illustrates this handoff; no distributor is contacted.
Try the distributor-context step ↗For the product interface, view the actual app screenshots.
Captured directly from the deployed development app on October 16, 2026. Larger previews focus on the app itself. Open any screenshot for the complete original, including Salesforce navigation.
Open full screenshot ↗
Open full screenshot ↗
Open full screenshot ↗These images show the Salesforce-native admin experience. They do not establish standalone feature parity, OCR accuracy, production readiness or live email delivery. The interactive walkthrough remains a separately labeled synthetic illustration.
“Verified” below means bounded implementation evidence, not production certification. Website interactions are labeled “Demonstrated.”
Known-part capture, quantity and notes; requester-scoped saved requests, search and receipts. Local QR image/camera decoding and OCR suggestions require explicit user application; phone acceptance is recorded.
Standalone has no live Salesforce connection. Distributor-context handoff and reviewer actions shown in this website are illustrative, not implemented standalone features.
Separate Quick RFQ, request-line, distributor-context and internal review components exist, including assignment/status controls and permission boundaries.
Subscriber configuration, license fit, catalog behavior and current end-to-end pilot acceptance require validation. A prior controlled matching issue means successful matching must not be assumed.
Editable synthetic capture → distributor context → request review → demo receipt → internal review recreation.
Browser memory only. No request record, email, routing, camera access, authentication or backend execution.
Standalone HTML/plain-text previews and owner-run local authentication and delivery test tools exist.
ST-67 live authentication and delivery acceptance remain pending. A preview is not proof of delivery.
Optional ERP, PIM, PLM, Sales Cloud, Service Cloud, Field Service and Manufacturing Cloud adapters are future scope.
No connector is represented as active here. Managed packaging and AppExchange listing/approval are not established.
Evaluate the standalone workflow separately from a customer-owned Salesforce implementation. Agree on user roles, data ownership and operating responsibilities before introducing real information.
Local OCR in standalone should not be confused with autonomous part selection or the historical Salesforce photo-assisted concept.
Plan the implementation conversation →A synthetic walkthrough today. A scoped pilot conversation next.
