An equipment label already has a QR code. Instead of asking someone to type the asset code from the label, you want the checkout form to scan it, let the borrower confirm the value, and save that code with the request. You also need the form to remain usable when camera access is unavailable.
With Walla connected to ChatGPT or Claude, you can request a QR scanner as a Custom Field and add it to an equipment checkout form. This walkthrough provides the build request, camera and manual-entry tests, and a check of the saved response. The equipment IDs and test records are fictional.
This example captures one equipment code per request. It does not check live inventory, reserve the equipment, verify borrower eligibility, or approve a loan. Those are separate operational or integration steps.
1. Define the code before building the scanner
For this exercise, each QR label contains plain text such as EQ-0001. It does not contain a website link. Print the same code as readable text beside the QR symbol so a borrower can type it if scanning fails.
Part | Example rule |
|---|---|
Code format | EQ- followed by exactly four digits, such as EQ-0001. |
Normalization | Trim surrounding whitespace and convert letters to uppercase for both input methods. |
Scanning | Read one code, stop scanning, and show the result for confirmation. |
Manual entry | Keep a visible alternative that does not require camera permission. |
Saved answer | assetCode as a string and entryMethod as scan or manual. |
Scope of validation | Check the code format only. A matching code is not proof that the asset exists or is available. |
Keep the code as text so EQ-0001 retains its leading zeros. If your existing labels contain URLs or a different format, define that parsing rule separately before adapting the prompt.
Connect Walla to your assistant and choose the intended workspace. Use the English Walla connection guide. Custom Fields follow a build, preview, approval, and placement workflow. Read the Custom Fields guide
2. Paste this QR scanner request into ChatGPT or Claude
Replace [workspace name or ID]. These are requirements for the generated field; verify the resulting implementation on the actual phones and form links your borrowers will use.
Use Walla to build a reusable Custom Field named “Equipment QR Scanner” in [workspace name or ID]. Check for a suitable existing field first. Ask me if the workspace or revision target is ambiguous.
Create a Start scan button, a Stop scan action, a visible Enter code manually alternative, an equipment-code input, and a Use code confirmation action. Start the camera only after the user chooses Start scan. Request camera video only, not microphone access. Prefer the rear camera when available, and handle unavailable devices without blocking manual entry.
Read QR text in the form EQ- followed by exactly four digits, for example EQ-0001. Trim surrounding whitespace and uppercase the letters. Preserve the code as a string, including leading zeros. Reject other text and URLs; never automatically open a scanned URL or navigate away.
After one successful decode, stop the camera and present the candidate code. Save a valid answer only after Use code confirms the normalized value. If the candidate is edited, the user switches to manual entry, or a rescan starts, invalidate the previously confirmed answer until the new value is confirmed. Manual edits must use entryMethod manual.
Use Walla’s supported Custom Field value and validation contract. The requested saved answer is an object with assetCode as a string and entryMethod equal to scan or manual. A required field must reject an empty, malformed, or unconfirmed candidate. Show the actual output schema you implement.
If camera permission is denied, ignored, unavailable, or restricted by the browser or hosting environment, show an understandable message and keep Enter code manually usable. Do not repeatedly force the permission prompt. Stop active camera tracks on Stop scan, successful decode, switching to manual entry, or leaving the scanning interface. A camera request that resolves after scanning was cancelled must not restart the stream or replace a manually entered code.
Decode in the field without uploading camera frames for this example. Do not store photos, video, raw unrelated QR contents, or extra device metadata. Do not connect to an equipment database, reserve stock, or mark a loan as approved.
Make all controls usable on a narrow phone screen and with a keyboard. Check whether the available decoder and runtime can support scanning; do not assume a browser-native decoder exists on every device. If scanning cannot work in the target environment, explain the limitation and keep the manual alternative.
Build the review preview, explain the camera lifecycle, manual fallback, validation, and saved-value format, and identify any unmet requirement. Wait for my approval before registering the build. Do not attach it to a production form or publish any form.
Confirm that you received a Walla build and review preview, rather than only a description of a scanner. Test scanning with a physical label or a code displayed on a second device.
3. Test camera access and the manual alternative
Browser camera access requires user permission and a secure context such as HTTPS. Embedded pages can also be restricted by the host’s camera permissions policy. These browser conditions are separate from whether a QR decoder works. Read MDN’s camera-access guidance
Test the direct respondent link and, if you plan to embed the form, the actual embedded page too. A working preview does not establish that the deployed or embedded form can access the camera.
Situation | Expected behavior |
|---|---|
Camera access allowed | Scanning begins after Start scan, decodes the label, and stops before confirmation. |
Permission denied | Show the manual-entry option without preventing the borrower from continuing. |
Permission prompt left unanswered | The borrower can cancel scanning and use manual entry. |
Permission later granted after cancellation | Any late stream is closed; the current manual value remains unchanged. |
No camera, blocked access, or unsupported decoding | Explain the limitation and allow manual input. |
Wrong QR content, including a URL | Reject the candidate; do not navigate or report a valid equipment code. |
Switch to manual entry or stop scanning | Release the camera; confirm the final code through the selected path. |
If permission was blocked, the borrower may need to review the browser’s site permissions before retrying. The form cannot override that decision. Manual entry should remain available regardless.
Copy this revision request if the fallback fails
Revise Equipment QR Scanner. On [device, browser, and direct or embedded page], [describe the camera or fallback problem]. Keep the agreed saved answer shape unless a change is necessary and explained.
Test permission denial, an unanswered prompt, switching to manual entry, cancelling a pending camera request, and a late permission grant after cancellation. The manual path must not require camera access, and late camera activity must not overwrite the current code. Return a revised preview and state any remaining platform restriction. Wait for approval; do not publish a form.
4. Create a draft equipment checkout request form
After reviewing the field, approve the build and ask the assistant to create the test form. The borrowed equipment is still subject to your team’s separate confirmation.
I approve the reviewed Equipment QR Scanner build. Register that version and create a new draft form named “Equipment Checkout Request Test” in [workspace name or ID].
Add these questions: Test case ID, short text, required for this test; Borrower name, short text, required; Work email, email, required; Requested return date, date, required; Intended use, long text, optional; Equipment code, a required placement of the scanner version we just approved.
Use this introduction: “Submit an equipment checkout request. Scan the QR label or enter the printed code manually. Sending this form does not confirm equipment availability or loan approval.” Use a thank-you message saying the request was received and needs review.
Read back the form ID, scanner question ID, registered version, required settings, and actual saved-value schema. Reuse the approved field rather than building a duplicate. Keep the form unpublished. Explain any placement step that cannot be completed with the available tools.
For editor placement, open Custom Fields when adding a question and select the registered scanner. Check the form contains a required equipment-code question and that the manual confirmation path works.
Publish only “Equipment Checkout Request Test” with form ID [test form ID] and return its respondent link for fictional test submissions. Do not publish or modify another form.
5. Run these test submissions
Use invented borrower details and a suitable future return date. These cases define expected results; they are not a report of tests already performed on a generated field.
Test ID | Action | Expected result |
|---|---|---|
QR-001 | Allow the camera, scan EQ-0001, and confirm Use code. | A submitted response with assetCode EQ-0001 and entryMethod scan. |
QR-002 | Deny camera permission, type eq-0002 with surrounding spaces, and confirm. | A submitted response with normalized assetCode EQ-0002 and entryMethod manual. |
QR-003 | Scan EQ-0001, then switch to manual entry, replace it with EQ-0003, and confirm. | Only EQ-0003 is saved, with entryMethod manual. |
QR-004 | Enter EQ-12 or scan unrelated text, then attempt to submit. | No valid submission accepted for the malformed equipment answer. |
QR-005 | Read a valid code but do not confirm Use code. | The required unconfirmed answer prevents valid submission. |
QR-006 | Manually confirm EQ-9999. | The format passes, but existence and availability remain unverified. |
QR-006 demonstrates the boundary of this example. A correctly formatted string may still identify an unknown or unavailable asset. A successful scan or submission should not produce an “equipment available” or “loan approved” message.
Also test rescanning after an earlier confirmation, retrying after an invalid candidate, leaving the scanner question, and returning before submission. Confirm that camera use and the currently confirmed code remain consistent.
6. Check the equipment code stored with each response
Open the test form’s Response Sheet, find the valid test records, and inspect their response details. Use CSV or XLSX export if you need to inspect the collected representation outside Walla. Read the English Response Sheet guide
Stored value | QR-001 | QR-002 | QR-003 |
|---|---|---|---|
assetCode | EQ-0001 | EQ-0002 | EQ-0003 |
entryMethod | scan | manual | manual |
What this checks | Camera path saved the confirmed string. | Manual fallback saved the normalized code. | An earlier scanned value was replaced. |
The property names above are the requested design. Check the actual registered output schema before interpreting an answer. The code should remain a string, and only the final confirmed value should be present.
Copy this response-verification request
In form [test form ID], inspect the submitted equipment-code answers for QR-001, QR-002, and QR-003 using the scanner field’s actual output schema. Use stored responses, not the camera preview, a candidate input, or default properties.
Expect QR-001 to contain assetCode EQ-0001 and entryMethod scan; QR-002 to contain EQ-0002 and manual; and QR-003 to contain only EQ-0003 and manual. Check that the code is a string and that QR-003 does not retain the earlier scanned EQ-0001 as its submitted code.
Check whether a completed response was accepted for the malformed QR-004 test or the unconfirmed QR-005 test. For QR-006, report the captured code without claiming that it exists in inventory or is available.
Report response identifiers, observed values, and mismatches. Do not edit or delete responses. If a value or type is not exposed by the available tools, leave it unverified and explain what I should inspect in the response details or export.
When inspecting an export, match the equipment answer to the same response’s test ID, borrower details, and requested return date. Structured answers may appear as serialized values, so inspect the actual file rather than assuming every property gets a separate spreadsheet column.
A scanner that displays the right code but saves a stale or empty answer has not passed the storage check. Correct the implementation or placement and repeat both scan and manual tests before using it for real requests.
7. Hand the request to the equipment manager
Keep a separate operational record of the review. For example, track the response ID, captured asset code, requested return date, assigned reviewer, inventory verification, decision, and actual handover date.
Step | What must be checked |
|---|---|
Capture | The final confirmed equipment code is stored with the request. |
Identify | An authorized reviewer or connected system matches the code to an actual asset. |
Review | Availability, borrower eligibility, dates, and any approval requirements are checked. |
Handover | The team records the decision and actual equipment handover through its chosen process. |
If you later add inventory lookup or reservation, test those behaviors as a separate integration, including two people requesting the same asset. A QR reader alone does not enforce exclusive reservations.
Start with one code format, a visible manual alternative, and a few fictional submissions. Use the English Custom Fields guide and Walla connection guide to build and revise the capture experience through conversation.
Open Walla to build an equipment checkout form




