Scanning is fast, but real operations are untidy. Labels become scratched, wet, folded, poorly printed, covered by stretch wrap, or positioned where a camera cannot read them. A documentation workflow needs a controlled fallback so the operator can continue without losing the connection between the item and its evidence.
Why codes fail in otherwise normal operations
A barcode may be valid in the business system and still be unreadable at the point of work. Common causes include:
- A torn, dirty, faded, or low-contrast label.
- Glare from plastic wrap, curved containers, or reflective packaging.
- A code printed too small or at insufficient resolution.
- Physical access that prevents the camera from getting a clear angle.
- An identifier shown on paperwork or a screen rather than encoded as a barcode.
Use manual entry without breaking traceability
CodaScan lets the operator type the identifier when scanning is not possible. The rest of the workflow remains the same: capture the relevant photos, add the configured metadata, and upload the evidence to the configured SharePoint destination.
The important operational rule is that the manually entered value must come from a reliable visible source, such as the human-readable number printed below the barcode, an order document, a product label, or the approved business system.
A simple fallback procedure
- 01
Try a clean scan first
Improve the angle, distance, lighting, or access without delaying the operation unnecessarily.
- 02
Locate the human-readable identifier
Use the number printed with the code or another source approved for that workflow.
- 03
Enter and visually verify the value
Compare the full entered code with the source before continuing.
- 04
Capture the evidence normally
Take the same required photos and metadata as a successfully scanned record.
- 05
Report recurring label problems
If the same product or printer repeatedly causes failures, correct the upstream labeling issue rather than normalizing manual entry.
Define acceptable identifiers before rollout
A manual-entry field is most useful when the team knows exactly what belongs in it. Decide whether the workflow expects an order number, SKU, batch, pallet identifier, shipment number, or another code. Document whether prefixes, leading zeros, spaces, and punctuation are significant.
This is also a good reason to test real labels during setup. Sample barcodes from production reveal formatting and print-quality issues that are easy to miss when a workflow is designed from spreadsheets alone.
Why this small feature matters
Manual code entry was added to CodaScan following a real customer request. It is a small interface capability with a large operational effect: the documentation process remains usable when the physical world does not match the ideal scanning scenario.
That is a useful test for product features in general. A good fallback preserves the structure of the workflow instead of sending operators to personal camera rolls, handwritten notes, or end-of-shift corrections.
Frequently asked questions
Should operators use manual entry all the time?
Scanning is usually faster and reduces typing, but manual entry is an appropriate fallback when the code cannot be read.
Can manually entered records still work offline?
Yes. Manual identifier entry is part of the same offline-capable capture workflow.
Does manual entry change the SharePoint destination?
No. The identifier is used by the configured workflow in the same way whether it was scanned or entered manually.