Type the part number.
Already 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 RFQ / Halo Business SystemsProtect distributor relationships.
Protect distributor relationships.
Capture RFQs faster.
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 ↗Three ways to start / from your phoneType it. Scan a QR.
Type it. Scan a QR.
Read a label photo.
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.
Capture a QR code.
Use 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.
Read a label photo.
Take 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.
What is verified?
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.
What can I try here?
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.
At the equipment. With the context.
Capture the request where the work happens.
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.
One request. Three perspectives.The part is only part
The part is only part
of the story.
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.
Capture what you know.
Start with a part identifier. Confirm editable details and describe the request without having to make an engineering decision.
Try the capture flow →Preserve the relationship.
Keep Distributor / Sold By context visible alongside the inquiry. Make the existing channel part of the review conversation.
See the context →Review before acting.
Bring the identifier, quantity and request details together. Let a person confirm suitability, ownership and the next step.
Understand the capabilities →A closer look / mobile workflow
The handoff, in your hand.
Illustrative mobile layouts with fictional data. These are recreated screen mockups, not screenshots of a deployed mobile app.
Halo RFQSTEP 02 · SYNTHETIC DEMO
Confirm the details.
Check what you know. Record what needs review.
Part identifierDEMO-VLV-204
Quantity2
UnitEach
Request detailsConfirm availability and suitability for the existing assembly.
Fictional details · No catalog match01
Capture the request
Start with the identifier, quantity and the question from the field.
Halo RFQSTEP 03 · SYNTHETIC DEMO
Keep the relationship.
Carry the distributor context with the request.
Distributor / Sold ByExample Industrial Supply
Relationship contextExisting distributor relationship
Context for a person to confirm.
Synthetic scenario · Nothing sentNo distributor is contacted or assigned.
02
Keep distributor context
Preserve the existing relationship for the reviewer to confirm.
Halo RFQSTEP 05 · SYNTHETIC DEMO
Review the handoff.
The same details. A human decision next.
Needs human review
- Part identifier
- DEMO-VLV-204
- Quantity
- 2 · Each
- Distributor / Sold By
- Example Industrial Supply
Confirm before follow-up.
Illustrative review · No record createdCheck the part, distributor ownership and missing information.
03
Put review in human hands
Bring the same context into the next conversation.
Capture → Context → ReviewA better handoff starts
Walk through a synthetic RFQ ↗01 02 03 04
A better handoff starts
with a clearer request.
Walk through a synthetic RFQ ↗Identify
Begin with a known part. Capture assistance supports data entry; people confirm the details.
Confirm
Check the identifier, quantity and notes. Uncertainty belongs in the request.
Keep context
Show the distributor relationship and review the complete request.
Review
See a demo receipt and an illustrative internal review view. Nothing is sent.
Choose the workflow, then the scopeOne capture-to-review story.
One capture-to-review story.
Two implementation tracks.
The demo illustrates the handoff. Standalone and Salesforce-native work have different capabilities and acceptance requirements.
Standalone capture
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 →Salesforce-native workflow
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 →Put the handoff to the testSee the context.
See the context.
Explore the conversation.
A synthetic walkthrough today. A scoped pilot conversation next.