Related Posts
Jump To Key Section
Rolling out phones and tablets to a workforce feels like a purchasing task. But it is an operational project with a purchasing step in the middle. The companies that understand these things actually decide the right thing about the operational questions first, then let those answers drive the device order. They follow this exact order. But the one who doesn’t get it pays a great price for the wrong configuration and spends the next quarter fixing it.
The blog explores nine decisions that you should think about before you place an order in bulk.
Write one sentence per role: what the device does, where it is kept, and what happens if it fails. A tablet mounted at a nursing station has different needs than one that rides in a delivery van. That sentence determines screen size, ruggedness, cellular versus Wi-Fi, and how much cosmetic wear you can manage. Get this on paper before anyone talks about models.
New devices make sense when the model must be current for many years or when an executive-facing role demands it. For most operational deployments, certified pre-owned devices deliver the same role at a substantially lower cost, and the money saved usually funds spares.
If you go pre-owned, do not accept “good condition.” Ask for the supplier’s written grading. A well-run distributor defines grades such as A+ (like new), A (light use, minor marks), B (moderate wear visible at arm’s length), and C (heavier cosmetic wear), and states that every grade is totally functional. Match the grade to the role: A for customer-facing staff, B for anything that lives in a situation.
Nothing derails a rollout quicker than a pallet of phones that will not activate on your carrier. Confirm whether devices are factory unlocked or carrier-specific, and whether they have been evaluated on the bands your carrier uses. If your team spans regions with many carriers, unlocked is the safer default. Ask the supplier to confirm clean IMEIs on every unit in writing.
This is the step most usually left until the boxes arrive. Every device should enroll into your management platform automatically on first boot. For Android, that is Zero-Touch Enrollment and, on Samsung hardware, Knox Mobile Enrollment. For Apple devices, it means Apple Business Manager. Your supplier requires to be able to note device identifiers with these programs before shipment, which is a capability, not a given. Distributors such as TG Wireless, which operate as certified Android Zero-Touch and Samsung Knox partners, can handle this at the point of sale so devices land on desks already connected to your MDM.
Ask directly: “Can you register these devices to our zero-touch or Knox account before they ship?” If the answer is not clear, expect to enroll several hundred devices by hand.
Decide what “ready to hand out” means for your team. Does each device require a case, a screen protector, a charger, a SIM, and an asset tag? Should the box be marked by department or site? Kitting is cheap when the supplier does it once at the warehouse and costly when your IT staff does it at a desk. Put the exact kit contents in the purchase order.
A warranty is only as good as the process after it. Ask three questions: How long is the warranty? How do I return a faulty unit, and who pays shipping? How immediately is a replacement dispatched? A twelve-month warranty with a self-service RMA form and a stated sub-one-percent return rate shows you the supplier tests devices before they ship. A thirty-day warranty tells you they do not.
Devices break, get lost, and leave with departing employees. Your fleet will require replacements for years, so ask how the supplier handles a model that goes out of stock. The right answer is that no distributor can guarantee a specific model indefinitely. What a good one can do is commit to equivalent-spec substitutions that run the same apps and management profiles, and quote availability at the time of each order instead of promising it for the life of the deployment.
Every pre-owned device should arrive data-wiped and free of activation locks. Add a check to your receiving process: power on a sample, confirm there is no previous owner’s account, and confirm the IMEI matches the packing list. Suppliers with R2 or ISO certifications have documented processes for this; ask to view them.
Order a pilot lot first, even if it is only ten devices. Enroll them, kit them, hand them to actual users for two weeks, and fix what breaks. Then place the complete order with a delivery schedule that matches your onboarding capacity. For tablets in particular, where mounts, cases, and network settings usually need adjustment, suppliers that specialize in wholesale tablets for corporate deployments will usually support a pilot before a large order.
Explain the job: pick the grade, confirm the carrier, settle enrollment and kitting, get the warranty and continuity terms in writing, confirm security on receipt, and pilot before you scale. Do those nine things and the bulk order becomes the easy part.
Ans: The two types of deployment methods are rolling deployment and blue-green deployment.
Ans: The four phases of deployment are pre-deployment, deployment, post-deployment, and reintegration.
Ans: The tools for deployment are Jenkins, GitHub Actions, and GitLab CI/CD.
