How do I use Hologram Test Mode to QA devices in the factory and keep SIMs inactive until deployment?

Quick Answer: Use Hologram Test Mode to bring devices online in the factory with free test data, run your QA workflow, then return SIMs to Hibernate so they stay inactive (and bill-free) until they transmit real production data in the field. You manage all of this in the Hologram Dashboard or via API, so you can automate activation timing across thousands of devices.

Most teams pay for connectivity months before a device ever reaches a customer. SIMs get activated at the factory, sit in boxes or on shelves, and quietly rack up charges while generating zero value. Test Mode changes that: you can QA every device on live networks, confirm your firmware, APNs, and telemetry, and still keep SIMs inactive until actual deployment.

With a bit of process discipline and some light automation, you can treat connectivity like any other software lifecycle: test, stage, and only bill when you actually ship.

Why This Matters

If you’re manufacturing connected hardware at scale—EV chargers, farm sensors, medical gateways, retail kiosks—factory QA is non-negotiable. But traditional cellular workflows force an ugly tradeoff:

• Test devices in a lab with “special” SIMs that don’t match production, then hope real-world activation behaves the same.
• Or activate production SIMs early, burn budget on idle inventory, and lose track of which SIM is where.

Hologram Test Mode eliminates that tradeoff. You can:

• Use the same Hologram SIM in the factory and in the field.
• Run full end‑to‑end QA with real mobile cores and carriers.
• Keep SIMs effectively “asleep” until the device starts sending real data in the wild.

That means lower cost of goods sold (COGS), less SKU complexity, and fewer “it worked on the bench but fails in the field” escalations.

Key Benefits:

• Zero data charges before deployment: Test Mode provides free test data and Hibernate keeps SIMs inactive until devices are actually transmitting in production.
• Real-world QA at the factory: Validate connectivity, device configuration, and cloud workflows using the same SIMs and networks your customers will use.
• Operational simplicity at scale: Use the Hologram Dashboard and APIs as a single pane of glass to track SIM state, automate lifecycle changes, and avoid manual spreadsheets.

Core Concepts & Key Points

Concept	Definition	Why it's important
Test Mode	A Hologram SIM state that provides free, limited test data so you can bring devices online for QA without incurring ongoing data charges.	Lets you validate connectivity, firmware, and end-to-end workflows in the factory without paying for full production plans.
Hibernate Mode (Inactive SIMs)	A low-cost or no-usage state where SIMs remain provisioned but not actively transmitting billable data.	Keeps inventory “on ice” between manufacturing and deployment so you aren’t paying for idle SIMs sitting in boxes or warehouses.
Lifecycle Automation via Dashboard & API	Managing SIM states (Test Mode → Hibernate → Active) programmatically or in bulk through the Hologram Dashboard and REST APIs.	Prevents human error, ensures consistent activation timing across fleets, and lets you scale QA and deployment without adding headcount.

How It Works (Step-by-Step)

Here’s the high-level flow I recommend for using Hologram Test Mode to QA devices in the factory while keeping SIMs inactive until deployment.

1. Plan your SIM lifecycle and data thresholds

   Before you touch hardware, decide:

   • When SIMs should move from Test Mode to Hibernate.
   • What you consider “enough” QA (e.g., 1–2 MB of test data per device).
   • How you’ll trigger production activation:
     • Automatically when the device passes a data threshold (e.g., first time it sends X MB in the field).
     • Or explicitly via your backend (e.g., when a device is shipped/scanned at the destination).

   Many teams, like Vital Health Links, rely on a simple pattern: factory QA in Test Mode, then devices are packaged and shipped in Hibernate and only activate when they transmit from the clinic or deployment site.

2. Insert Hologram SIMs at manufacturing and enable Test Mode

   At the factory:

   • Insert Hologram SIMs (or solder eUICC-based Hyper SIMs) directly on the line.
   • Use the Hologram Dashboard to:
     • Import SIMs (if not already visible).
     • Group/tag them as a manufacturing batch (e.g., factory-qa, build-2026-04, region-us).
     • Confirm they’re in Test Mode so they can use free test data for QA.

   If you’re integrated with the Hologram API, you can have your manufacturing system automatically:

   • Register the SIM’s ICCID and device serial/IMEI.
   • Set Test Mode for each new SIM.
   • Add tags to keep factory batches organized.

3. Run your factory QA using Test Mode data

   With SIMs in Test Mode, power on each device and run your QA script:

   • Bring up the cellular connection using your configured APN.
   • Perform a connectivity handshake with your cloud or backend.
   • Send a small test payload (e.g., device ID, firmware version, sensor snapshot).
   • Validate telemetry round trip (device → network → cloud → back to device if needed).
   • Optionally, force a reboot and reconnect to catch flaky modem behavior before it reaches the field.

   Test Mode’s free data is designed for exactly this: enough real‑world usage to confirm that your device works on Hologram’s multi-carrier network, without turning on long-term billing.

   Customers like Amper and Arable use this pattern: devices are activated for testing, but data charges don’t kick in until their customers actually start using them.

4. Return devices to Hibernate until deployment

   After each device passes QA:

   • Send a command from your factory system (via Hologram API) or use the Dashboard to move SIMs from Test Mode to Hibernate.
   • Confirm the SIM state is updated in your manufacturing log (ICCID + device serial + SIM state).
   • Power down the device, package it, and ship it with the SIM already installed.

   In Hibernate:

   • Devices are effectively offline from a billing perspective.
   • SIMs remain mapped to your account and tagged, so you don’t lose track of inventory.
   • You incur zero data charges regardless of how long devices sit in storage or transit.

   Vital Health Links uses this exact lifecycle: devices leave the factory in Hibernate and can sit for months before deployment without adding cost.

5. Trigger production activation when devices are deployed

   When a device is installed in the field:

   • The device powers on and attempts to connect.
   • You can then:
     • Automatically activate when the device uses a defined amount of data (e.g., a one-time “deployment handshake”).
     • Or explicitly activate via your backend or the Hologram Dashboard when your ERP or installer app reports the device as deployed.

   Once activated:

   • The SIM moves to a standard billing plan (e.g., pay‑as‑you‑go or pooled data).
   • The Hologram Dashboard gives you real-time visibility into:
     • Which devices are connected.
     • Where they are (country/network).
     • How much data they’re using.
   • You can configure proactive alerts for anomalous usage (to catch misconfigurations early).

6. Monitor and refine your factory QA based on field data

   After you’ve deployed a few batches:

   • Use Dashboard reporting to see:
     • Activation timing by batch or model.
     • Early failure rates (devices that fail to connect in the field).
   • Feed that back into your factory QA:
     • If some devices pass bench tests but fail on certain carriers, add more carrier-testing steps.
     • If a specific firmware version shows more retries, tighten your QA thresholds before shipping.

   Over time, Test Mode becomes the backbone of a closed-loop improvement cycle for your hardware and connectivity stack.

Common Mistakes to Avoid

• Activating SIMs too early in the process:
  Avoid flipping SIMs directly to a fully active plan during manufacturing “just to be safe.” Use Test Mode for connectivity validation, then Hibernate to keep SIMs inactive until deployment. This is how teams avoid paying for months of idle SIMs.

• Losing track of SIM–device mappings:
  Don’t rely on manual labels or spreadsheets alone. Use tags in the Hologram Dashboard and/or store ICCID + device serial in your ERP or manufacturing system, and keep SIM state (Test/Hibernate/Active) in sync via API. This is critical when you have tens of thousands of devices across multiple factories.

Real-World Example

A remote patient monitoring provider (similar to Vital Health Links) ships cellular gateways to clinics across multiple regions. Their old connectivity workflow looked like this:

• SIMs were activated at the factory on a single-carrier contract.
• Gateways sat in a warehouse for 2–4 months.
• They paid for connectivity the whole time, even though the devices weren’t yet seeing patients.
• When they finally deployed, some locations had weak coverage, and debugging required shipping replacement SIMs and walking clinic staff through swaps.

After moving to Hologram:

• At manufacturing:
  SIMs are inserted and set to Test Mode. The QA station powers each gateway, uses free test data to:

  • Verify the modem connects.
  • Confirm traffic hits the clinical backend.
  • Run a quick OTA update check.

• After QA:
  The manufacturing system calls the Hologram API to move SIMs to Hibernate. Devices are boxed and can sit for months with zero data charges.

• At the clinic:
  When a nurse powers on the gateway for the first time:

  • The device sends a small “activation handshake” to the backend.
  • The backend calls Hologram’s API to switch the SIM to a production plan.
  • From that point, the Hologram Dashboard provides real-time visibility and proactive alerts on SIM health and usage.

Outcome:

• No more paying for idle inventory.
• No more SIM swaps.
• Devices maintain connectivity across 190+ countries and 550+ carriers, with the option to use eUICC Hyper SIMs and Outage Protection for clinical deployments that can’t tolerate downtime.

Pro Tip: If your manufacturer handles SIM insertion, have them integrate with the Hologram API so SIMs are automatically put into Test Mode on the line, then transitioned to Hibernate as part of the packaging step. That way you never have to manually track “which SIM is where,” and devices can automatically activate once they cross your defined data threshold in the field.

Summary

Using Hologram Test Mode, you can:

• Run full, real-world QA on the factory floor using free test data.
• Keep SIMs in Hibernate so they remain inactive (and bill-free) until devices are actually deployed.
• Control activation timing through the Hologram Dashboard or APIs, with a clean lifecycle from Testing → Hibernate → Active.

The result is predictable costs, fewer surprises at deployment, and a much cleaner operational model as your fleet grows to thousands or millions of devices.

Next Step

Get Started