Ask a buyer what a solar camera costs and they will quote you the FOB price. Ask them what it costs to run and most will pause. That pause is where deals are lost — because the operating cost of a 4G camera is a SIM data plan paid every month for years, and for a distributor selling a hundred units, it is the number their customers will complain about first. This guide is the arithmetic behind that monthly bill, and how to specify a camera fleet so the bill stays small.
1. Why data cost decides the deal more than hardware price
Over a three-year horizon, the hardware price is paid once and the data plan is paid 36 times. A camera that costs $4 more at wholesale but uses a third of the data can be the cheaper product by a wide margin. This is also the single most common source of post-sale friction: buyers forgive a slightly higher unit price, but they do not forgive a monthly data bill that was never mentioned. Give your customers the monthly figure in writing before they order, and you remove the main reason they stop answering your messages eighteen months later.
2. How much data does one 4G camera actually use?
Consumption is not fixed by the camera — it is set by the operating mode. The three modes below are the ones we see in the field, with typical monthly ranges per camera:
| Operating mode | Monthly data per camera | What drives it |
|---|---|---|
| PIR-triggered event upload (recommended default) | ≈ 0.2 – 0.6 GB | Number of real events per day; clip length; app push notifications are tiny |
| Scheduled snapshot / short recording | ≈ 0.5 – 1.5 GB | Interval of scheduled captures; how many are retained in the cloud |
| Always-on streaming + cloud backup | ≈ 3 – 8 GB and up | Continuous bitrate, plus every clip re-uploaded for backup |
The enormous spread explains why two customers with "the same camera" report completely different bills. A site with real events three times a day sits comfortably in a small data bundle; a site left on continuous live view from a phone will burn through it in a week. PIR wake-up design is therefore not a battery feature — it is a connectivity-cost feature. The camera sleeps, the PIR wakes it, a short clip is uploaded, and the radio returns to sleep.
3. The four settings that move the bill
- Resolution and bitrate. Full-resolution clips on every event cost more than sub-stream clips. Many apps let you upload a lower-resolution event clip and keep the full-resolution file on the local TF card — the best of both worlds: cheap data, court-grade local evidence.
- Clip length. A 10-second event clip uses roughly a third of a 30-second one. Tune clip length to the scene: gates need less, open yards need more.
- Detection sensitivity and zones. Every false trigger is paid for in data. Tight detection zones plus human-shape filtering reduce both nuisance alerts and monthly cost — which is why we treat careless PIR aiming as a cost problem, not just an annoyance (see the aiming section in our installation guide).
- Cloud backup. Local TF-card recording is free and unlimited. Optional cloud storage is a subscription on top of data — useful for customers who fear device theft, but it should be an explicit choice, never a surprise.
4. Choosing a carrier — and which SIM type
There is no universal best SIM, only the best SIM for a given market. Before shipping, confirm three things for every destination:
- Does the carrier cover the actual site, not the city? Rural and peri-urban coverage is where deployments fail. Ask the customer for a signal reading at the mounting point, or better, send a sample and let them test with their own SIM.
- Are the bands matched? A modem must support the carrier's LTE bands in writing. Bands vary by country and by operator within the same country, and a mismatch shows up as a camera that "works" but drops offline at night. Every unit we export is band-configured per destination market.
- What is the plan's policy on device SIMs? Some consumer plans forbid permanent data devices or throttle after a fixed volume; some carriers offer dedicated IoT/M2M or CCTV SIM products with stable terms. This is local commercial territory and it changes constantly — always confirm current terms with the customer's local carrier or their SIM supplier, and do not rely on a general statement from any manufacturer.
For multi-country distributors, two structures compete: local SIMs bought in each market (usually cheapest per GB, but the customer manages many carriers) and regional or global IoT SIMs (one management portal, single invoice, higher per-GB cost but much lower admin overhead). For fleet operators — parking chains, telecom tower companies, logistics yards — the managed IoT route frequently wins on total cost because of the admin savings alone.
Fleet sites are also where consolidated hardware pays off: a single multi-lens unit such as the MSL31 street-light camera covers an entire car park on one SIM and one data plan, instead of four separate cameras with four separate lines to fund.
5. Estimating a site's monthly bill before you quote it
A worked example a buyer can repeat with their own numbers: a site with 8 cameras, each triggering about 6 real events per day, each event uploading a 15-second clip. That is roughly 20–45 MB per camera per month in total — call it 0.2–0.35 GB — so 8 cameras sit comfortably inside a 3 GB monthly pool, with headroom for app push notifications. The same site switched to continuous live viewing would need many times that. This is why the specification conversation should always include the operating mode, not just the model number.
6. The five SIM traps to warn your customers about
- Leftover or shared SIMs. A SIM still registered to someone else, or reused across devices, fails registration — and the camera looks broken when it is not.
- Inactive/data-paused periods. Some prepaid plans suspend or deactivate the line for inactivity or non-renewal. A camera that has been sitting in a box for three months may need reactivation before it will connect.
- NAT and port restrictions. Most consumer 4G plans put devices behind a carrier NAT with no inbound access. Cloud-relay app designs handle this transparently; systems that expect the customer to open ports will not work on these plans. Our units use the outbound-relay design so no port forwarding is ever required.
- Roaming behaviour. A foreign SIM left on automatic network selection may register on the wrong operator and burn roaming data. Lock the network in the app where the option exists.
- Registration requirements. Several markets now require SIM registration against a national ID or business licence. Confirm local rules before promising an installation date, since registration lead time is usually the schedule risk, not shipping.
7. What we configure before shipment
Because data economics start at the factory, every export order includes: LTE bands locked for the destination market and, where the customer provides details, the target carrier; a default upload profile that favours event-triggered clips over continuous streaming; local TF-card recording enabled so the customer is never dependent on paid cloud storage for evidence; and app defaults pre-set so a non-technical end user can add the camera without a support call. If your market needs a specific APN or plan type, tell us at order stage and we will document it in the packing list.
Frequently asked questions
How much data does a solar 4G camera use per month?
In the default PIR-triggered event-upload mode, typically 0.2–0.6 GB per camera per month. Scheduled snapshot recording runs 0.5–1.5 GB. Continuous live streaming with cloud backup can exceed 3–8 GB. The operating mode matters far more than the model.
Can I use the customer's existing local SIM card?
In most markets yes — the unit accepts a standard SIM and we band-configure it for the destination country. Confirm that the local plan permits permanent data devices and that coverage reaches the actual site, not just the nearest city. For multi-country fleets a managed IoT SIM is often simpler.
Do the cameras need port forwarding or a fixed IP?
No. The cameras connect outbound to the cloud relay, so they work behind carrier NAT on ordinary consumer 4G plans. No static IP address and no router configuration are required.
Does local recording cost data?
No. Recording to the on-board TF card is local and free. Data is consumed only when video or notifications travel over the mobile network, such as app push alerts and remote playback.
The bottom line
The monthly data bill is part of your product, whether you quote it or not. Specify PIR-triggered event upload with local TF recording as the default, match LTE bands to the destination carrier, and be explicit with customers about the difference between event clips and continuous streaming. Do that and a solar camera fleet stays cheap to run for years — which is exactly the reputation that makes your next container order repeat business.