Halo RFQ helps industrial teams capture the information they have and keep the next decision in human hands.
Start with the information in front of you. Then confirm the identifier, add the request details and keep the context for a person to review.
Halo RFQStart with what you know.
Illustrative mobile screen · Fictional data
01 / EnterAlready know the identifier? Enter it directly on your phone. Add quantity and request notes, including anything the reviewer needs to check.
No QR tag required. A known identifier is enough to start a request.
Halo RFQTake a snapshot or choose an image.
Illustrative mobile screen · Fictional data
02 / ScanUse the phone camera to take a QR snapshot, or choose a saved QR image. Review the decoded content, then explicitly apply the supported part identifier.
Review, then apply. A QR code is an entry aid, not a confirmed catalog match. Continuous scanning is not claimed.
Halo RFQTake a photo or choose a label image.
Illustrative mobile screen · Fictional data
03 / ReadTake a photo of an English equipment label, or choose a label image. Local OCR returns an editable suggestion for the part number.
Check the suggestion. Correct the result and choose to apply it. A photo does not establish part suitability.
Standalone source and recorded phone acceptance support QR snapshot/image decoding and English label OCR suggestions, with explicit application. The Salesforce-native app has separate Quick RFQ, Scan-to-RFQ and Read Label entry screens; feature parity and end-to-end acceptance require validation for your scope.
This website uses a sample identifier and fictional details. It does not activate your camera, decode a QR code or run OCR. Every path still needs human confirmation; no automatic replacement selection is implied.
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.
Illustrative mobile layouts with fictional data. These are recreated screen mockups, not screenshots of a deployed mobile app.
Halo RFQCheck what you know. Record what needs review.
Start with the identifier, quantity and the question from the field.
Halo RFQCarry the distributor context with the request.
No distributor is contacted or assigned.
Preserve the existing relationship for the reviewer to confirm.
Halo RFQThe same details. A human decision next.
Check the part, distributor ownership and missing information.
Bring the same context into the next conversation.
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.
The request should carry its context beyond the phone. Halo RFQ’s email designs give the requester, distributor and representative a message shaped around their role in the handoff.
Halo RFQA branded message keeps the reference and captured details together.
Concept: a brief branded alert directing the recipient to the request for review.
Illustrative concept only. SMS sending is not implemented or demonstrated.Requester, distributor and rep email versions have documented demo-inbox receipt. That evidence does not establish production delivery or acceptance across external organizations.
Account verification, password reset, RFQ confirmation, team notification and status-update previews exist. Live authentication and delivery acceptance remain pending.
A future option requiring provider selection, consent, sender registration, opt-out controls and delivery acceptance. No SMS is sent by this site or demo.
For a pilot, agree on brand treatment, sender identity, recipients, message content and channel scope. Customer-specific branding and live delivery need implementation and acceptance review. Discuss implementation →