Inside PiiComm’s Staging Operation: How Thousands of Devices get Deployed Across Canada

A national retailer needs 2,400 Zebra TC52 devices staged, kitted with store-specific configurations, and deployed to 300 locations before the holiday peak with zero disruption to checkout operations.

That is not a hypothetical. It is the kind of engagement PiiComm executes routinely from its purpose-built Canadian staging facilities.

For a VP of IT or procurement leader evaluating deployment partners, the difference between a provider that has refined its processes over 15+ years and one that is still building them shows up in moments like these. PiiComm has deployed more than 500,000 devices across thousands of locations for organisations including Air Canada, Giant Tiger, and Alstom. That number represents operational maturity—processes stress-tested across enough deployments to surface and resolve edge cases that a smaller provider has not yet encountered.

This post details how PiiComm’s device staging and deployment operation works at enterprise scale: the physical process, the configuration discipline, the multi-province logistics, and the vertical-specific expertise that turns a purchase order into a fleet of working devices.

What a PiiComm staging engagement actually looks like

Most enterprises have never seen the inside of a staging facility. They send a purchase order, and weeks later, devices show up. What happens in between determines whether those devices work on day one or generate a wave of help desk tickets.

When PiiComm receives a shipment of 1,000 Zebra TC73 handhelds from the manufacturer, the first step is not configuration—it is inspection. Every unit is checked for DOA (dead on arrival) defects before any software touches it. In 15+ years of staging operations, PiiComm has caught DOA rates that would have reached end users and caused immediate downtime had devices shipped directly from the OEM to the field.

Catching a DOA device at the staging facility costs minutes. Catching it at a remote warehouse or hospital floor costs days.

Device receipt, inspection, and DOA testing

A pallet arrives from Zebra or Honeywell. Before a single device enters the configuration queue, technicians open each box and run power-on diagnostics. Battery health, screen responsiveness, button functionality, cellular radio activation, Wi-Fi connectivity—every component that could fail in the field gets tested in the facility.

The economics here matter. A device that passes power-on testing but fails to connect to the client’s network is functionally DOA. PiiComm’s technicians test connectivity against the client’s network profile, not just against a generic test signal. This catches the device that would have prompted a help desk call from a truck stop in northern Ontario or a nursing station in rural Quebec.

Defective units are flagged, documented, and returned to the OEM for replacement—before the deployment timeline is affected.

Gold Image configuration and zero-touch enrollment

The Gold Image is the master software configuration that defines what every device in the fleet will look like: operating system version, security settings, MDM profile, business applications, network credentials, and user interface customisations.

PiiComm builds the Gold Image in collaboration with the client’s IT team, tests it against production environments, and then applies it identically to every device in the deployment. The result is that device #2,000 is configured exactly the same as device #1.

Zero-touch enrollment takes this further. Devices are enrolled in SOTI or 42Gears before they leave the staging facility, so the moment a device powers on at the end-user site, it is already under MDM management. PiiComm’s staging process ensures automated provisioning via zero-touch enrollment, removing the need for manual setup by IT teams or end users.

For a VP of IT managing a distributed workforce, this means field teams and store managers never touch a configuration screen. The device arrives ready to work.

Precision kitting—more than putting devices in boxes

A common failure mode in large deployments is the “almost ready” device. The scanner arrives configured, but without its holster. Or with the wrong SIM card. Or without the quick-start guide that the warehouse associate needs to get started.

PiiComm’s kitting process treats accessories as part of the device, not as afterthoughts. Each kit is assembled to a site-specific bill of materials: the device, rugged case, screen protector, stylus, SIM card (pre-activated on the correct Canadian carrier), vehicle charger if required, printed user documentation, and any site-specific materials.

The box a technician opens in Moncton contains everything needed to start working immediately. No calls to IT asking where the charger is. No delays waiting for a missing SIM card to arrive separately.

Asset tagging and chain-of-custody documentation

Every device staged by PiiComm receives a tamper-evident asset tag before it leaves the facility. The tag’s serial number is logged and synchronised to the client’s central asset database—or to PiiComm’s AIM portal if the client is using PiiComm’s lifecycle management services.

This is not administrative overhead. It is the foundation for everything that follows.

The asset record created during staging tracks the device through its entire operational life: which site it was deployed to, when it was serviced, what repairs it has received, and ultimately, how it was decommissioned. For organisations facing compliance audits—PIPEDA requirements, PHIPA in Ontario healthcare, Quebec Law 25—this documented chain of custody proves that devices were handled correctly from the moment they arrived at PiiComm’s facility.

Configuration consistency across hundreds of sites

Configuration drift is the silent killer of large-scale deployments. When 15 different IT staff at 15 different sites manually configure devices, the result is 15 slightly different configurations—each one a potential source of application errors, security gaps, and help desk tickets.

One scenario PiiComm encounters regularly: an organisation deploys 500 devices in-house across five sites, then discovers three months later that 80 devices at one location are running a different MDM policy because a local technician used an outdated configuration script. The remediation cost—sending a technician or pushing a remote fix to 80 devices, re-testing, and re-documenting—far exceeds the cost of centralised staging.

The question every procurement manager should ask when evaluating deployment options: will device #2,400 be configured exactly the same as device #1?

PiiComm’s comparison of in-house vs. managed staging shows that in-house error rates are variable due to manual entry mistakes, while automated Gold Image provisioning targets a zero-error configuration rate. For a procurement manager writing an RFP, this is a measurable quality metric to evaluate against.

Why centralised staging eliminates configuration drift

One facility. One Gold Image. One QA process.

Every device passes through the same configuration workstation, receives the same software load, and undergoes the same verification testing. There is no opportunity for a well-meaning technician at Site 7 to “improve” the configuration or apply a patch that was not part of the approved image.

When a configuration change is required—a new application version, an updated security policy—PiiComm updates the Gold Image once. Every device staged after that change receives the new configuration automatically.

MDM enrollment at the staging facility, not in the field

SOTI or 42Gears enrollment happens before the device ships—not after it arrives at a store, warehouse, or hospital.

This distinction matters operationally. A device enrolled at the staging facility is under management from the moment it powers on at the end-user site. Security policies are active. Application restrictions are enforced. Remote wipe capability exists from minute one.

A device shipped without MDM enrollment requires local IT intervention to complete setup—intervention that may not happen correctly, may not happen promptly, and may not happen at all at remote sites without dedicated IT staff.

Multi-province, multi-site deployment logistics

Canada is 7,000 kilometres wide. A deployment that works in the GTA does not automatically work in northern Alberta or rural Quebec.

The logistics of getting the right devices to the right sites, on the right day, with the right configurations, is where most deployment plans break down. PiiComm has managed rollouts where devices needed to arrive at a distribution centre in Moncton, a retail store in Winnipeg, and a field office in Fort McMurray within the same deployment window. Each site has different receiving procedures, different contact personnel, and different time zones.

The staging facility coordinates all of this. The client’s IT team is not managing 300 separate shipments.

Secure warehousing and Gold Stock inventory

Not every device ships immediately after staging. PiiComm maintains purpose-built Canadian warehousing for “Gold Stock”—pre-staged devices held in secure inventory, ready for immediate deployment.

Gold Stock serves three operational needs. First, it supports rapid response to new site openings: a retailer adding 12 stores in Q3 can draw from pre-staged inventory rather than waiting for a new manufacturing run. Second, it absorbs seasonal surges: a T&L company ramping up for holiday shipping can scale its fleet without lead-time anxiety. Third, it provides emergency replacement inventory: when a device fails at a critical site, a replacement ships the same day from Gold Stock rather than entering a weeks-long staging queue.

The warehousing is not an afterthought bolted onto a staging process. It is integrated infrastructure that makes deployment timelines predictable.

Coordinated delivery windows and tracked shipping

A device staged perfectly but delivered at the wrong time creates operational disruption.

PiiComm coordinates delivery scheduling across multiple sites—real-time tracking, documentation at every stage, and communication with site-level contacts to ensure devices are received and activated without disrupting operations. For a retail deployment, this means devices arrive during the four-hour morning receiving window, not during the afternoon sales rush. For a healthcare deployment, it means devices arrive when the unit coordinator is present to receive them, not during a shift change.

Every shipment is tracked. Every delivery is documented. The client sees exactly where their devices are at every moment between the staging facility and the end-user site.

Turnaround SLAs that match operational deadlines

A deployment SLA is only as good as the infrastructure behind it. Any provider can promise a turnaround time; the question is whether they have the facility capacity, the trained staff, and the supply chain relationships to deliver it when a client needs 3,000 devices staged in 10 business days.

Deployment speed directly affects time-to-value for a technology investment. PiiComm’s dedicated production lines enable deployment of thousands of devices in days, not months. For a CFO calculating the cost of delayed deployment—idle devices sitting in boxes, extended parallel-run costs while old and new systems overlap, deferred productivity gains—the difference between “days” and “months” is a measurable financial impact.

Seasonal retailers know this pain intimately. If devices are not in stores by October, the holiday peak is compromised. PiiComm builds deployment schedules backward from the client’s operational deadline—not forward from the purchase order date. The staging facility’s capacity is allocated against the go-live date, not the order date.

Scaling from hundreds to thousands without facility constraints

PiiComm’s staging facility is purpose-built for elastic scale. The client does not need to worry about whether the provider has enough bench space or staff for a large rollout.

This is a direct contrast to in-house staging, where a 3,000-device rollout means commandeering a conference room for six weeks, pulling IT staff from other projects, and hoping the building’s electrical capacity can handle 200 devices charging simultaneously.

PiiComm’s facility handles the volume. The client’s IT team stays focused on strategic work.

How PiiComm handles scope changes mid-deployment

Real deployments rarely follow the original plan exactly. A client adds 200 devices to a rollout. A configuration requirement changes after staging has started. Shipments need to be redirected to different sites because a store opening was delayed.

These scope changes are not exceptions—they are the operational reality of enterprise deployments.

PiiComm’s staging operation is built to absorb changes without restarting the process. When a client changes a configuration requirement after 800 of 2,000 devices have already been staged, the facility can update the Gold Image for the remaining 1,200 devices and—if required—recall and reconfigure the already-staged units. The alternative, in an in-house staging operation, is often to ship the misconfigured devices anyway and “fix it in the field,” creating the exact configuration drift and remediation costs that centralised staging was supposed to prevent.

Flexibility is not a marketing promise. It is an operational capability that shows up when a deployment hits reality.

The process discipline and logistics infrastructure described above apply across every deployment PiiComm manages. But staging 500 Zebra scanners for a warehouse is not the same as staging 500 clinical tablets for a hospital network—the devices may be similar, but the configurations, compliance requirements, accessory kits, and deployment logistics differ materially by industry.

Vertical proof—how staging and deployment works across five Canadian industries

Transportation and logistics—deploying rugged devices across a national fleet

A long-haul driver picks up a sealed kit at the Mississauga terminal. Inside: a Zebra TC78 handheld, vehicle-mount cradle pre-configured to their specific truck model, vehicle charger, and a one-page quick-start guide. They mount the device, power it on, and are operational before leaving the yard.

No IT intervention. No configuration screens. No calls to a help desk from a truck stop in northern Ontario.

T&L deployments require devices that work in extreme Canadian temperatures—minus 20°C and below in winter, plus 40°C in summer trailer interiors. PiiComm stages Zebra and Honeywell rugged handhelds with vehicle-mount cradles matched to specific fleet models, cellular connectivity pre-activated on the correct carrier, and applications configured for the driver’s route and role.

The driver who never visits a central office receives the same device configuration as the driver based at headquarters. That consistency matters when a dispatch system update needs to reach 800 devices simultaneously.

Retail—store-level configurations and seasonal surge readiness

A national retail chain facing a hard deadline needed to swap every point-of-sale device in 300 stores before the holiday rush. Doing it in-house would have meant months of kitting, shipping, and late-night store visits—plus the risk of registers going dark if anything slipped.

PiiComm completed the full fleet swap in under two weeks, well ahead of Black Friday, with no checkout lanes closed during the transition. Each POS unit was pre-configured with its store-specific profile, tagged to its exact location, and shipped in one coordinated wave. Technicians spent minutes plugging in ready-to-go hardware, not hours troubleshooting configuration issues.

Retail staging requires store-specific configurations—different POS profiles, different Wi-Fi networks, different peripheral setups per location. PiiComm’s Gold Image process supports these variants within a single deployment. Store 47 in Calgary receives devices configured for its network and printer setup; Store 183 in Halifax receives devices configured for its environment. Both are staged with identical quality assurance rigour.

Healthcare—clinical-ready devices with compliance built in

A device staged for a nursing unit is not the same as a device staged for a pharmacy. The Gold Image is tailored to the clinical workflow—medication scanning profiles for nursing, inventory management applications for pharmacy, different access controls based on role.

PiiComm configures healthcare devices with clinical application suites, encryption enabled by default, multi-factor authentication, and infection-control-compatible accessories: wipeable cases, sealed ports, antimicrobial screen protectors. The documentation a privacy officer needs—asset chain-of-custody, MDM enrollment confirmation, security configuration verification—exists before the device reaches a clinician’s hands.

For Ontario healthcare organisations, this means PHIPA compliance is built into the staging process. For organisations with Quebec operations, Quebec Law 25 requirements are addressed in the Gold Image. The device arrives compliant, not compliant-after-IT-finishes-configuring-it.

Manufacturing—plant-floor devices that survive harsh environments

Manufacturing deployments often require devices configured for specific production lines. Plant A’s devices run quality control applications on one network segment; Plant B’s devices run work-order tracking on another. Both need rugged accessories rated for dusty floors, temperature extremes, and constant vibration.

PiiComm’s staging includes heavy-duty cases, industrial-grade screen protectors, and configurations tailored to plant-specific systems. A device destined for the paint shop floor is not identical to one destined for the assembly line—but both pass through the same QA process, receive the same DOA testing, and ship with the same chain-of-custody documentation.

The Gold Image process supports multiple configuration variants within a single deployment. The client’s IT team defines the variants; PiiComm’s staging facility executes them at scale.

Field services—deploying to workers who never visit an office

A field service technician opens a box at their home in Kelowna. Inside: a Zebra TC53 configured with the field service application, pre-enrolled in SOTI, kitted with a vehicle charger and protective case. They power on the device and are working—no IT visit, no configuration call, no trip to a regional office.

PiiComm has managed field service deployments where devices ship directly to individual technicians’ home addresses across multiple provinces. Each device is configured for the technician’s role, connected to the correct MDM profile, and ready for immediate use.

Zero-touch enrollment is not a convenience in field services. It is a necessity. When your workforce is distributed across six provinces and may never set foot in a corporate facility, the device must arrive ready to work. PiiComm’s staging process makes that possible.

The infrastructure behind the SLA—PiiComm’s Canadian staging operation

Any managed mobility provider can describe a staging process on a website. The question a procurement manager should ask is: where is the facility? Who are the technicians? What happens at 2 a.m. on a Sunday when a deployment issue arises?

PiiComm manages 500,000+ devices across thousands of locations, with all core operational functions—staging, service desk, technicians, data infrastructure—executed in-country by PiiComm’s own Canadian team. For a reader evaluating data sovereignty and operational accountability, this eliminates the ambiguity of providers who claim “Canadian presence” but operate from US infrastructure.

Purpose-built facilities, not repurposed office space

PiiComm’s staging environment is designed for production-line throughput: dedicated workstations, controlled environments, secure storage, and the electrical and network infrastructure to stage thousands of devices simultaneously.

This is a direct contrast to the common competitor approach—and the common in-house approach—of staging devices on folding tables in a back office. When a deployment requires 3,000 devices staged in 10 business days, facility infrastructure determines whether that commitment is realistic or aspirational.

In-house technicians and bilingual service desk

PiiComm’s staging technicians are employees, not contractors. They are trained on Zebra, Honeywell, and Samsung hardware. They understand Gold Image configuration, MDM enrollment, and the QA testing protocols that catch failures before they reach the field.

The 24/7 bilingual (English/French) service desk is staffed in Canada—not routed to an offshore call centre during night hours. For Quebec healthcare organisations and federal government buyers, bilingual service capability is a procurement requirement, not a convenience. PiiComm meets that requirement natively.

Canadian data sovereignty from staging through decommissioning

The asset record created during staging follows the device through its entire operational life. When a device is eventually retired, PiiComm’s secure decommissioning process—certified to NIST 800-88 standards—erases data and documents the chain of custody from deployment through destruction.

Every step happens in Canada, under Canadian privacy law. PIPEDA applies federally. PHIPA applies in Ontario healthcare. Quebec Law 25 applies in Quebec. PiiComm’s Canadian-only operations, Canadian-hosted data infrastructure, and Canadian-staffed facilities mean data never crosses a border and is never subject to foreign data access laws.

What happens after deployment—lifecycle integration

The day devices arrive at your sites is not the finish line. It is the starting line.

The asset records, MDM enrollment, and configuration baselines established during staging become the foundation for everything that follows: ongoing management, break-fix support, spare pool replenishment, and eventual secure decommissioning.

From staging to the AIM portal—real-time fleet visibility from day one

Devices staged by PiiComm are automatically tracked in the AIM (Asset Intelligence Manager) portal from the moment they leave the staging facility. The client gets real-time visibility into device location, status, and health without building a tracking system from scratch.

The same asset record that was created during staging—serial number, configuration, deployment site—populates the AIM dashboard. When a device needs service, the history is already there.

Spare pool management and break-fix SLAs

Pre-staged replacement devices held in Gold Stock inventory are ready to ship when a device fails in the field. A warehouse associate in Thunder Bay does not wait two weeks for a replacement scanner. A same-day or next-day replacement ships from inventory that was already staged, configured, and tested.

This is where staging connects to PiiComm’s five managed mobility service pillars. The staging process creates the foundation; lifecycle management, MDMaaS, and secure decommissioning build on it.

For organisations evaluating staging partners, the question is not just “Can you deploy our devices?” It is “What happens after you deploy them?”

Getting started—what PiiComm needs to scope your deployment

A staging and deployment engagement starts with a scoping conversation, not a contract. PiiComm’s team needs to understand your fleet, your sites, your timeline, and your configuration requirements before proposing a deployment plan.

Information to have ready for a scoping conversation

• Device types and quantities (Zebra TC-series scanners, Honeywell handhelds, Samsung tablets, vehicle-mounted computers)
• Number of deployment sites and geographic distribution across provinces
• Target deployment timeline and any immovable deadlines (seasonal peaks, regulatory go-lives, store openings)
• MDM platform in use or planned (SOTI, 42Gears, Workspace ONE)
• Configuration requirements—applications, security policies, network credentials
• Accessory requirements—cases, screen protectors, styluses, vehicle chargers, SIM cards
• Compliance or regulatory considerations—PIPEDA, PHIPA, Quebec Law 25, industry-specific requirements

This information allows PiiComm to provide an accurate scope and timeline. It also signals to the PiiComm team that you are ready for a substantive conversation about execution, not a general capabilities overview.

For a detailed technical overview to share with your procurement team or internal stakeholders, download PiiComm’s Staging & Deployment Guide.

Talk to a mobility expert

Contact PiiComm to discuss your deployment requirements. A scoping conversation typically covers fleet size, timeline, configuration complexity, and site distribution—enough to determine whether PiiComm is the right fit and to provide a preliminary deployment plan.

Frequently asked questions

How many devices can PiiComm stage and deploy simultaneously?

PiiComm’s staging facilities are built for elastic scale. Dedicated production lines handle deployments from hundreds to thousands of devices simultaneously. With 500,000+ devices deployed across thousands of locations, the facility infrastructure and staffing model are proven at enterprise scale—seasonal surges and national rollouts included.

What is PiiComm’s typical turnaround time for a large-scale device deployment?

Turnaround depends on fleet size, configuration complexity, and the number of destination sites. PiiComm builds deployment schedules backward from the client’s operational deadline—not forward from the order date. For most enterprise engagements, thousands of devices can be staged and shipped within days of receiving hardware.

Does PiiComm support multi-province deployments with site-specific configurations?

Yes. PiiComm routinely manages deployments across multiple provinces with site-specific Gold Image configurations, accessory kits, and delivery schedules. Each site receives devices configured for its specific network, application, and MDM requirements. Coordinated delivery windows and real-time shipment tracking ensure devices arrive when and where they are needed.

How does PiiComm ensure device configurations are consistent across hundreds of sites?

Every device is configured from a single Gold Image—a master software configuration that includes the client’s applications, MDM profile, security settings, and network credentials. Zero-touch enrollment automates provisioning. The result is that device #2,000 is configured identically to device #1, with no manual entry errors.

What compliance documentation does PiiComm provide with staged devices?

PiiComm provides documented chain-of-custody from device receipt through deployment, including asset tag records synchronised to the client’s database, MDM enrollment confirmation, QA test results, and shipping documentation. For healthcare and government organisations, this documentation supports PIPEDA, PHIPA, and Quebec Law 25 compliance audits.

Can PiiComm stage devices from multiple OEMs in a single deployment?

Yes. PiiComm is a Premier Zebra Technologies partner and holds partnerships with Honeywell and Samsung. Multi-OEM deployments are standard—a single engagement can include Zebra scanners, Honeywell handhelds, and Samsung tablets, each with its own Gold Image, accessory kit, and MDM configuration.

What happens if a device arrives defective at a PiiComm staging facility?

Every device undergoes DOA (dead on arrival) testing and rigorous QA—battery, connectivity, and application verification—before leaving PiiComm’s facility. Defective units are identified and replaced before shipping. This prevents the costly scenario of a broken device arriving at a remote warehouse or hospital floor.

Does PiiComm provide bilingual (English/French) deployment documentation and support?

Yes. PiiComm’s 24/7 service desk is bilingual (English/French) and staffed in Canada. Deployment documentation, user guides, and kitting materials can be produced in both official languages. For Quebec-based organisations and federal government buyers, bilingual service capability is a procurement requirement that PiiComm meets natively.

The staging decision

A device deployment is a moment when months of planning, procurement, and configuration decisions either come together or fall apart. The devices work on day one, or they generate a cascade of help desk tickets, missed deadlines, and remediation costs.

The question is not whether your organisation can stage devices. With enough time, enough staff, and enough conference room space, most IT teams can configure a few hundred units. The question is whether that is the best use of their expertise—and whether that approach scales when the deployment is 3,000 devices across 150 sites in six provinces, with a deadline that does not move.

PiiComm has spent 15+ years answering that question for Canadian enterprises. The staging facilities, the technicians, the Gold Image process, the logistics coordination, the bilingual service desk—all of it exists because organisations kept encountering the same failure modes and needed a partner who had already solved them.

Your IT team has strategic work to do. The devices should arrive ready.