CCTV Lead Times: From Inventory to Deliverable Systems

For a CCTV project, the useful stock figure is the number of complete, approved systems you can receive by the required date. A manufacturer's inventory balance supplies business context. A supplier's camera count supplies one part of a delivery plan. Neither, on its own, establishes when the installation can proceed.

Consider a hypothetical order for ten identical systems, each requiring ten cameras, one NVR and one switch. Even with all 100 cameras ready, only eight complete systems are possible if just eight approved NVRs are available. That arithmetic is the central purchasing question in this guide: which required item limits the number of usable systems?

We connect that question to manufacturer disclosures reviewed on 13 November 2026, then develop a practical allocation and delivery checklist. Financial amounts are reported accounting values; the project quantities are explicitly hypothetical. No current Hector Weyl inventory, dispatch promise or customer installation is represented.

1. What the 2026 reports tell a CCTV buyer

The consolidated balance sheets in Hikvision's and Dahua's 2026 third-quarter reports both show higher inventory values at 30 September than at 31 December 2025. The comparison is between balance-sheet dates, rather than two equivalent nine-month sales periods.

Hikvision links increased procurement and inventory expenditure to its operating cash-flow change on PDF page 4. Dahua attributes inventory growth mainly to increased stockbuilding on PDF page 3. The quarterly statements are unaudited. Read the Hikvision filing and Dahua filing.

Our procurement interpretation is limited: these balances justify asking what has been stocked and where it sits in the supply process. They do not identify the finished units available to your seller. There is no basis here for converting either amount into camera quantities, predicting a particular lead time or concluding that every product faces the same supply conditions.

Our earlier CCTV price-increase guide examines quotation changes. This article addresses a separate decision: whether the approved equipment basket can arrive together.

2. Read the inventory composition before inferring availability

Dahua's 2026 half-year report provides a more detailed example. Its inventory note, PDF pages 133–134, separates the following closing book values. These are 30 June 2026 amounts, not a breakdown of September's balance.

Using the unrounded book values, finished goods represent approximately 32.92% of this total, an author calculation. Book values reflect the relevant impairment provisions; they are not selling prices. See the half-year report, inventory note 9.

The practical implication follows from the categories: material waiting for production cannot be treated as a completed camera ready for dispatch. Even a finished-goods total does not provide the model, lens, quantity or allocation information needed for an individual order. Do not apply the June percentage to September, to another manufacturer or to a distributor's stock list.

3. Follow the evidence from stock to allocation

Ask for availability against one exact equipment schedule. Each row should identify the model and suffix, required quantity, stock holder, physical location, confirmation time and quantity the seller can allocate to the order. Keep an unconfirmed production estimate visibly separate from confirmed finished stock.

Ownership matters. A seller's own stock and partner-held stock are different supply sources. Two quotations may also refer to the same physical lot. Before adding quantities, establish that the units are distinct and that the seller has a confirmed route to supplying them. Otherwise, a spreadsheet can double-count the equipment the project depends on.

For example, an offer for 60 own-stock units plus 40 confirmed partner-held units describes 100 distinct units only if those two lots are separate. A second offer for the same partner's 40 units does not raise the physical total to 140. This is a hypothetical reconciliation example. Keep the lot or reservation reference beside the quantity, and leave ownership or access uncertainties open rather than filling them with an optimistic number.

A reservation should have a clear quantity and expiry or release condition. “Available today” leaves the buyer exposed if those units can be sold elsewhere before the order is accepted. Ask what action secures the allocation, who confirms it and what happens if the agreed dispatch date changes.

This is a proposed purchasing process, not a statement about any particular supplier's warehouse controls. The point is to preserve the evidence behind the availability claim, including the date on which it was checked.

4. Count complete systems at the bottleneck

Return to the hypothetical ten-system order. Assume every approved system requires ten cameras, one NVR and one suitable switch. All drives, mounts, cables, power arrangements and other requirements are assumed ready and approved. The example demonstrates quantities only; it does not validate a real network or device combination.

Complete systems = the smallest whole-system count supported by any required item. Here, min(100 ÷ 10, 8 ÷ 1, 10 ÷ 1) = 8. The order is two complete systems short, despite all cameras being available. Actual readiness still depends on inspection, configuration and the remaining site requirements.

The bottleneck can move. If ten NVRs become available but only 92 of the required camera configuration are accepted, cameras support floor(92 ÷ 10) = 9 systems. Eight remaining cameras do not make the tenth identical system complete. Record which item limits each release rather than reporting only a total percentage of equipment received.

This calculation is useful for identical, indivisible systems with dedicated equipment. Projects using shared recorders, central storage or uneven camera counts need a site-specific allocation model. Do not force them into the same ten-camera template.

Location and timing can also constrain a release. Equipment held at different locations may be part of the same total yet unavailable for the same installation window. Assign the confirmed units to the intended phase and destination before counting them in a kit. A later shipment can support a later phase, but it cannot retrospectively satisfy the earlier phase's receiving requirement.

5. Verify the configuration behind the quantity

A unit only contributes to the approved kit when its configuration matches the requirement. Confirm the full model and suffix, selected lens, required firmware and included accessories. A similarly named camera with a different field of view may cover a different task, even when its headline resolution matches.

Check the recorder and switch against the complete load. Camera-input count does not establish the required analytics capacity or retention period. PoE port count alone does not establish the power budget. Keep those technical checks attached to the approved equipment schedule so that a proposed substitution cannot bypass them.

For related planning methods, see our lens and target-width guide, PoE power-budget guide and 30-day storage calculation. Their assumptions also need to match the proposed configuration.

At receipt, reconcile model labels and quantities with the allocation confirmation. Record discrepancies before counting those units as accepted stock. A packaging count can establish that boxes arrived; the project's technical acceptance criteria establish whether their contents satisfy the order.

6. Separate availability, dispatch and site readiness

A dated stock confirmation describes a position at a particular time. A dispatch date describes a later action. Arrival, inspection, configuration and installation follow their own sequence. Put those milestones in the purchasing plan instead of allowing one ambiguous “delivery” date to stand for all of them.

Ask which date is confirmed and which is estimated. Record dependencies such as acceptance of the purchase order, approved configuration, payment conditions where applicable and any outstanding accessories. A production completion estimate still needs a path through dispatch and receipt before it becomes a usable project date.

Work back from the required site milestone. Allow time for your actual receiving and acceptance process, and identify who owns any unresolved step. No universal transit or commissioning allowance is established here. Use the route, destination, equipment and project process that apply to the order.

If a date changes, assess the complete-system impact. A delay to one low-quantity but essential item may prevent more work than a delay to several spare cameras. That is why the equipment dependency list belongs beside the transport schedule.

7. Decide deliberately between phased release and substitution

In the hypothetical example, releasing eight complete sets might support a useful first phase. Sending 100 cameras alone might leave the installer unable to finish any of the ten specified systems. The better choice depends on the approved site sequence, access arrangements and responsibilities for equipment already received.

Document what the first phase can complete and what remains open. Include the missing quantities, confirmation owner and next review date. Partial delivery should remain visible in the order record until the balance has been accepted; it should not silently become a completed project milestone.

A substitute can be another option, but availability does not establish equivalence. Recheck the required viewing task, interfaces, recording, events, analytics and power/storage needs as applicable. Keep the original requirement, proposed difference, evidence and approval decision together. Obtain the relevant project approval before treating a changed configuration as interchangeable.

8. Give each procurement exception a next action

Use a brief with three linked parts: the approved equipment schedule, order-specific availability evidence and the release/acceptance plan. Update the same records as evidence changes, rather than creating several disconnected stock totals.

Keep the final decision explicit: release the supported phase, hold for missing evidence or approve a documented revision. Recheck time-sensitive allocation before acting on an expired confirmation. This turns a general conversation about manufacturer stock into an order decision the project team can review.

A useful request reads: “Please confirm the attached full models and options, distinct available quantities, stock holder and allocation conditions. State the earliest confirmed dispatch milestone and outstanding dependencies. Identify any line that prevents the proposed complete-system release.” Attach the site or phase allocation and name the person responsible for reviewing exceptions. This gives both sides a common record to update.

For a Hector Weyl proposal, send the full equipment schedule, quantities and required milestones. Hector Weyl MOQ is 100 units. Ask for current configuration and supply confirmation; this article does not offer prices, inventory or a guaranteed lead time.

9. Frequently asked questions

Does higher manufacturer inventory mean shorter CCTV lead times?

The financial balance alone cannot establish that. Verify the required model, quantity, allocation and dated delivery plan with the seller.

Is finished-goods value a count of available cameras?

No. It is an accounting value for a category. It does not supply the unit mix or allocation required for an individual project.

Can I add quantities from two supplier quotations?

First confirm that they refer to distinct units. Two offers may depend on the same partner-held lot.

What does an “in stock” statement need?

Request the full configuration, quantity, stock holder, confirmation time and reservation conditions, followed by the relevant dispatch confirmation.

Should cameras be delivered before the NVRs?

Assess what the approved installation phase can complete. A camera-only shipment does not establish complete-system readiness.

Can I use Dahua's June category mix for September?

No. The detailed example belongs to the June reporting date. September's total does not provide that same category breakdown in the cited table.

Is the ten-system example a Hector Weyl stock offer?

No. Every quantity is hypothetical. Confirm actual equipment, availability and project acceptance separately.

10. Sources, dates and calculation scope

Hikvision: 2026 Q3 report, disclosure URL dated 17 October 2026; PDF pages 4 and 7. Dahua: 2026 Q3 report, disclosure URL dated 24 October 2026; PDF pages 3 and 5. Consolidated amounts are rounded; quarterly statements are unaudited.

Inventory composition: Dahua 2026 semi-annual report, disclosure URL dated 22 August 2026; inventory note 9, PDF pages 133–134. Book values at 30 June are used consistently. The 32.92% finished-goods share is calculated from unrounded figures.

Scope: sources rechecked on 13 November 2026. These are business disclosures, not live SKU stock lists. Procurement conclusions and workflows are our analysis; the kit example is hypothetical, with all other requirements assumed satisfied. No field test or current delivery performance is claimed.