Industrial RFQ capture for the handoff from field teams to inside sales. Bring the part, the request and the distributor relationship into the same review conversation.
Type a part number · Scan a QR · Read a label photo ↓
2-minute synthetic walkthrough · No sign-in or real data needed
Open full screenshot ↗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.
A facilities professional can start with the identifier in front of them, record what is needed and leave suitability decisions for human review.
Explore the field-to-review demo ↗For the product interface, view the actual app screenshots.
A number on a label starts the conversation. Who supplied it, what the field user needs and what remains uncertain give your team something useful to review.
Start with a part identifier. Confirm editable details and describe the request without having to make an engineering decision.
Try the capture flow →Keep Distributor / Sold By context visible alongside the inquiry. Make the existing channel part of the review conversation.
See the context →Bring the identifier, quantity and request details together. Let a person confirm suitability, ownership and the next step.
Understand the capabilities →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.
Begin with a known part. Capture assistance supports data entry; people confirm the details.
Check the identifier, quantity and notes. Uncertainty belongs in the request.
Show the distributor relationship and review the complete request.
See a demo receipt and an illustrative internal review view. Nothing is sent.
The demo illustrates the handoff. Standalone and Salesforce-native work have different capabilities and acceptance requirements.
Evaluate known-part capture, editable QR/OCR suggestions, saved requests and receipts in a separate local workspace.
Distributor-context handoff and reviewer actions shown in this website are illustrative, not standalone functionality.
See standalone evidence →Evaluate request lines, distributor context and internal review components, with subscriber configuration and license fit to confirm.
Current end-to-end acceptance, catalog behavior and operational readiness require validation.
Explore implementation questions →Human review stays central. No automated replacement selection, engineering, pricing or ordering. Production readiness and live email delivery are not established; optional connectors remain proposed.
Full capability status →A synthetic walkthrough today. A scoped pilot conversation next.