The Honeywell Dolphin CT60 is a rugged Android handheld scanner built for nonstop warehouse, manufacturing, and field‑logistics work. If you’ve just unboxed one or you’re trying to squeeze more efficiency from a fleet already in service, this user guide walks you through setup, scanning, configuration, and everyday tips. We’ll cover details most teams gloss over - like scan tuning, Android Enterprise enrollment, app deployment choices, WMS/ERP connectivity patterns, security, and maintenance - so your CT60s stay responsive, accurate, and easy to support.
Table of Contents
- Meet the Honeywell Dolphin CT60
- Unboxing and Physical Setup
- Power, Battery, and Accessories
- Network and Enterprise Enrollment
- Barcode Scanning on the CT60
- Configuring Android and Honeywell Tools
- App Deployment and WMS/ERP Connectivity
- Best Practices for Scanning Workflow Design
- Troubleshooting and Maintenance
- Security, Compliance, and MDM
- Top 10 Mobile Apps for CT60 Warehousing
- Tips, Shortcuts, and Power User Moves
- Conclusion
- FAQs
Meet the Honeywell Dolphin CT60
The Honeywell Dolphin CT60 is a purpose‑built, rugged Android mobile computer with an integrated enterprise‑grade imager. Think of it as a modern forklift for your data: compact, strong, and made to carry heavy scanning workloads. It balances performance with durability and is designed to run all day in challenging environments.
Out of the box, the CT60 supports popular barcode symbologies, enterprise Wi‑Fi roaming, Bluetooth peripherals, and Android Enterprise features for secure management. Whether your team uses telnet emulation, a browser‑based WMS, or native apps, the CT60 accommodates the stack with scan intents and configuration utilities that reduce friction for workers and IT.
Where the CT60 shines is in the little operational optimizations: fast aim/trigger responsiveness, readable daylight screens, and long‑life batteries you can swap without losing your place mid‑task. When configured well, you get sub‑second scans and instant form fills, which add up to real throughput gains across a shift.
Unboxing and Physical Setup
Start with a visual inspection. Confirm the device, battery, charging base or USB‑C cable, and any pistol grip, hand strap, or protective boot are present. Check serial numbers against your asset register; labeling devices on day one prevents mix‑ups when you scale your fleet.
Seat the battery securely and charge the device fully before first use. Many teams are tempted to skip this step, but a full initial charge helps calibrate the device’s battery reporting. While charging, set up your asset tag, barcode label, and a simple name scheme (for example, CT60‑RCV‑01 for receiving, CT60‑PICK‑02 for picking) to make help‑desk calls faster and clearer later.
Fit any accessories carefully. If you’re adding a pistol grip, follow the manufacturer’s instructions to avoid stressing the frame or misaligning the trigger. For screen protection, a high‑quality tempered glass protector is a cheap insurance policy in drop‑prone work. Test the holster or cradle location on a cart or forklift to confirm it’s reachable and safe during motion.
Power, Battery, and Accessories
Battery practice sets the tone for your shift. Encourage users to place devices on charge at breaks instead of waiting until they hit low‑battery warnings. If your operations run multiple shifts, consider a rotation bin for fully charged batteries - label them so people return drained ones for recharging rather than pocketing spares.
Use genuine or certified batteries; mismatched third‑party packs can show erratic percentages or fail prematurely. Where hot‑swap is supported, configure your apps to retain state during swaps so users don’t lose the current pick list or receive screen.
Accessories multiply productivity when chosen well. Pistol grips reduce wrist fatigue for high‑volume scanning. Ring scanners paired over Bluetooth free the hands for carton handling. Forklift mounts with power keep devices at eye level and charged. Balance ergonomics with safety; test accessories with a small pilot group and collect feedback before scaling.
Network and Enterprise Enrollment
Reliable Wi‑Fi is the backbone of a happy CT60 fleet. Survey coverage around racking, docks, and staging areas, and tune roaming thresholds so devices switch access points before users notice lag. Use WPA2‑Enterprise or WPA3 where available; pre‑shared keys are manageable in small sites but become brittle in growth.
For Android Enterprise, decide between work‑profile mode and fully managed devices. Most warehouses prefer fully managed (dedicated device) enrollment to lock the device to a launcher, auto‑install work apps, and enforce security baselines. Document your DPC (Device Policy Controller) QR code or zero‑touch flow so staging new units is repeatable.
If your fleet needs cellular, provision LTE SIMs with an APN that supports your security requirements. Keep an eye on background data consumption - some apps sync aggressively. MDM policies that limit large uploads to Wi‑Fi help avoid surprise bills while still providing fallback connectivity for drivers and field teams.
Barcode Scanning on the CT60
Start with symbologies. Enable only the types you actually scan - Code 128, Code 39, Interleaved 2 of 5, EAN/UPC, or Data Matrix/QR, depending on your labels. Disabling unused types reduces false positives and accelerates decode speed. If you scan dense 2D codes, test the default focus range and illumination settings with real labels from your floor.
Next, decide how scans populate your apps. Many workflows use keyboard‑wedge mode, where a scan acts like typed input followed by an optional suffix (often Enter or Tab). Others integrate via scan intents or SDKs, which are more precise and faster for native apps. Whichever you choose, keep it consistent across apps so users don’t have to relearn behaviors from screen to screen.
Tune feedback. Audible beeps and haptic vibration confirm success in noisy environments; colored aimers and reticles help target small labels on curved surfaces. Create a short testing script for onboarding: scan a short UPC, a long Code 128, a torn label, a 2D code at a shallow angle, and a far target from a ladder or forklift. Catching decode edge cases early saves you hours in troubleshooting later.
Configuring Android and Honeywell Tools
Within Android settings, lock down distractions and error sources. Disable auto‑rotate if it causes accidental context changes on forklifts. Raise screen timeout just enough to avoid constant reauthentication, but balance it against battery life and security. Configure language, date/time, and keyboard to match your ERP/WMS format expectations.
Leverage Honeywell utilities for fine‑grained control. Honeywell’s configuration tools let you define scanner profiles, remap triggers, and manage keystroke behaviors per app if needed. Export and version‑control these profiles so your help desk can redeploy a known good configuration after a reset or update.
Browser‑based WMS users benefit from a locked‑down enterprise browser or launcher. Pin tabs, hide address bars, and block non‑work destinations. For form‑based apps, set your suffix to Tab or Enter based on the field flow. Small details like this create a sense of “the system reads my mind,” which speeds up work and reduces accidental errors.
App Deployment and WMS/ERP Connectivity
You have three main options for app delivery: telnet emulation clients for legacy green‑screen systems, enterprise browsers for web apps, and native Android apps talking to your WMS/ERP API. Each path can be excellent if your network and scanning layer are tuned.
For native apps, handle connectivity gracefully. Warehouses have dead zones; plan for offline steps, local queues, and clear on‑device validation so errors are blocked before they hit the ERP. Protect your core systems by batching or buffering traffic rather than spamming the ERP with thousands of tiny calls per minute during a wave pick.
Many teams bridge the gap between rugged devices and complex ERPs with a mobile warehousing layer. A good example is Cleverence Inventory, a mobile data collection and workflow platform that replaces paper/desktop steps with guided Android workflows. It is designed as an ERP‑friendly layer - think “software glue” - with an offline‑first engine (local queue and embedded device database), sub‑second device response, and certified connectors for major ERPs like SAP ECC/S/4HANA, Oracle E‑Business/Fusion, and Microsoft Dynamics 365, plus NetSuite, Odoo, QuickBooks, Zoho, and Xero via connectors/APIs. It posts to the ERP safely (idempotent, auditable) and includes out‑of‑the‑box flows like receiving, put‑away, wave/zone picking, packing, shipping, cycle counts, transfers, and on‑device label printing (ZPL/CPCL). Security controls include HTTPS/TLS, JWT auth, encrypted device DB, role‑based access, and MDM friendliness. Teams often pilot in 2–4 weeks on one process, see 30–40% time savings on counts, and surface 1–2% phantom stock fast - using their existing rugged devices without custom ERP code.
Best Practices for Scanning Workflow Design
Start with the fewest possible touches. Every time a user shifts grip, hunts a small button, or hesitates between fields, your throughput drops. Design screens and field order to match the physical journey (dock to staging to rack) and the way hands actually move (scan → confirm → move). If your WMS allows it, prefill likely fields based on location, user role, or prior scan context.
Standardize label content and placement. If receivers have to angle a carton to find the label, you’re burning seconds per case. Agree with suppliers on barcode type, size, and placement. Where you control labeling, print larger, high‑contrast codes and add human‑readable text for fallback. When multiple barcodes are near each other, use masking or targeted symbology enablement so the scanner reads the right one.
Measure outcomes, not opinions. Track items per minute, scan error rate, and rework counts per team and per device. Use those numbers to test small changes (suffix Enter vs Tab, crosshair brightness, button mapping). Communicate wins: “this tweak saved 15 seconds per pallet” makes the next change easier to accept.
Troubleshooting and Maintenance
Most scanning issues trace back to three roots: labels, network, or configuration drift. Start with labels - are they smudged, wrinkled, low contrast, or printed at too low DPI? A quick reprint test separates label problems from device problems fast.
Next, test network health. If users report lag at certain aisles, walk the path with a device and a simple latency monitor. Look for noisy handoffs between access points or channel congestion. MDM logs and Wi‑Fi controllers can help pinpoint problem cells; sometimes a small antenna realignment works wonders.
Finally, confirm configuration. Has a suffix changed? Was a symbology disabled? Did an OS update reset a privacy toggle that blocks scanning? Keep a gold image - a known good set of OS build, app versions, and scanner profiles - so you can compare and restore quickly. Wipe and redeploy is not a defeat; it’s often faster than hunting a hidden toggle.
Security, Compliance, and MDM
Security policies should be practical, not punitive. Use strong device PINs or managed sign‑ins that don’t force users to break flow constantly. Encrypt data at rest and in transit, and restrict copy/paste from work to personal profiles if you use work‑profile mode.
Choose an MDM/EMM that supports Android Enterprise fully - zero‑touch enrollment, app configs, kiosk mode, and certificate distribution. Tag devices by site, role, or workflow so you can push targeted updates without disrupting other teams. Audit logs are your friend when investigating who changed what, when.
When apps bridge to ERPs, enforce HTTPS/TLS and token‑based authentication (for example, JWT). Implement least‑privilege roles in both the mobile layer and the ERP. If you use a middleware layer like Cleverence Inventory, leverage its role‑based access controls, encryption, and audit trails to meet IT governance needs without slowing workers down.
Top 10 Mobile Apps for CT60 Warehousing
The CT60’s strength is its flexibility: it runs a wide spectrum of warehouse apps, from modern native clients to ruggedized browsers and TE emulators. Here’s a neutral, use‑case‑driven shortlist that often comes up in deployments. Always test with your labels, network, and ERP before committing.
We order this by common warehouse scenarios - green‑screen modernization, browser WMS, guided native flows - rather than by vendor marketing. Consider time‑to‑pilot, offline behavior, ERP integration depth, and TCO in your evaluation.
Don’t treat this as a popularity contest; the right tool is the one that fits your process and IT constraints today, with room to grow.
- Honeywell Enterprise Browser or launcher for locked‑down web access to WMS screens.
- SOTI MobiControl tools (kiosk/remote support) to stabilize and support the fleet at scale.
- Cleverence Inventory for guided Android workflows with offline‑first engine and ERP‑friendly posting.
- Ivanti Velocity (Wavelink) to modernize telnet/VT sessions with touch/scan optimization.
- StayLinked SmartTE/Evolve for resilient TE and modern UI overlays with strong session handling.
- Scandit SDK or app for advanced camera‑based scanning and augmented assistance where appropriate.
- BlueFletch Enterprise Launcher for secure, shared‑device sign‑in and kiosk experiences.
- Microsoft Power Apps‑based forms for simple, custom data capture tied to SharePoint/Dataverse.
- SAP mobile clients (Fiori/ITSmobile variants) aligned to SAP EWM/WM processes.
- Oracle mobile apps for MSCA/WMS Cloud where Oracle is the operational system of record.
If your priority is quick wins without ERP risk, a mobile warehousing layer like Cleverence can bridge rugged devices and ERP neatly - sub‑second UX on the device, with buffering so the ERP isn’t overwhelmed by chatty mobile traffic. If your priority is TE modernization, Velocity or StayLinked may be a faster first step. For browser‑based WMS, lock things down with an enterprise browser and scan‑aware form tuning.
Whichever route you choose, run a 2–4 week pilot on one process (cycle counts or receiving) and measure items/min, error rate, and sync reliability. Expand only after you’ve banked the first set of gains.
Tips, Shortcuts, and Power User Moves
Map the side buttons to high‑frequency actions. For example, set the lower side key to toggle flashlight for dark rack labels, or to switch between pick and verify modes in your app. Keep mappings uniform across sites to reduce confusion for floaters.
Use suffix Tab strategically. When forms are consistent, a scan followed by Tab can jump to the next field without extra taps. If a field sometimes needs manual edits, consider Enter instead so users can confirm before moving on. Small changes in suffix behavior can yield big speedups in repetitive work.
Document the “three quick checks” for floor leads: a) verify Wi‑Fi indicator strength and roaming, b) test a known‑good label at near and far range, c) check the scanner profile name/version. These checks solve a surprising percentage of “it’s broken” tickets without calling IT.
Conclusion
Getting the most from the Honeywell Dolphin CT60 isn’t about a single killer setting; it’s a series of small, thoughtful choices. Tighten your scan profiles to the labels you actually use. Enroll devices with Android Enterprise so updates and support are predictable. Choose apps and middleware that respect both worker speed and ERP stability. Then measure, tweak, and repeat.
When you combine a sturdy device with good labels, solid Wi‑Fi, and guided workflows, you get fewer recount loops, faster dock‑to‑stock times, and calmer help desks. Build your rollout around a focused pilot, capture the before/after metrics, and use those wins to scale with confidence.
The CT60 is capable hardware. With the right configuration and a realistic plan for connectivity, security, and change management, it becomes a quiet productivity engine that keeps product moving and the ERP clean.
FAQs
-Which barcode symbologies should I enable first on the CT60?
Start with what your labels actually carry: Code 128, Code 39, EAN/UPC, and Data Matrix/QR if you use 2D. Disable the rest at first. Add only when a real use case appears. This speeds up decoding and reduces accidental reads of the wrong nearby code.
-Should I use keyboard‑wedge or scan intents with my apps?
Keyboard‑wedge is simple and works with almost any form, but it’s less precise. Intents or an SDK provide faster, more reliable integration for native apps and can carry metadata (symbology, timestamp). Use wedge for quick wins; standardize on intents for long‑term stability.
-How do I handle dead zones where Wi‑Fi drops?
Design offline‑tolerant mobile flows. Use a local queue and embedded database on the device, sync automatically when connectivity returns, and prioritize critical transactions. Middleware designed for this pattern reduces user frustration and protects your ERP from partial posts.
-What’s the fastest way to stage a batch of CT60s?
Use zero‑touch or QR‑code enrollment to bind devices to your MDM/EMM, then push a versioned app bundle and scanner profile. Keep a gold image (OS build, app versions, configs) and a short smoke test script. This makes wipe‑and‑reprovision a safe, quick fix when needed.
-Do I need special labels to improve scan speed?
Not special, just consistent and legible. Use adequate size and contrast, avoid placing multiple barcodes too close, and pick symbologies aligned to your data length. For rough environments, durable stock and proper adhesive matter more than exotic print tech.