Installers need a supplier who can support the exact system they quote, deliver the agreed configuration and keep replacements compatible. Evaluate a camera, recorder, firmware version and accessory list together. A low equipment price can be outweighed by a return visit caused by an undocumented substitution or a recording function that was never tested.
Confirm availability and delivery for the actual order
For QuarkView orders, shipping guidance says US fulfillment is available for selected products and the quote confirms the current origin, method, cost and timing. Confirm the exact SKU, quantity and destination before promising an installation date. Warehouse availability for one configuration does not establish stock for a mixed order or the next batch.
Ask for current availability, dispatch timing, estimated transit, split-package details, import responsibilities and what happens if an agreed item is unavailable. Keep dispatch and arrival as separate milestones. If a sample is being approved before a batch, reconfirm the batch configuration and lead time after sample acceptance rather than treating the sample quote as an ongoing stock reservation.
Record model, firmware and accessory consistency
Keep a bill of materials with the camera model and lens, recorder model, hardware and firmware versions, drive option, power equipment, mounts, adapters, package contents and required software/licences. Ask how the supplier identifies a revision and notifies you before a substitution. “Same megapixels” does not establish the same housing fit, event support or compatible firmware.
For a project requiring compliance documents, request the applicable documents for the exact model, variant and destination. Check that the identifiers match the quote and sample; a family brochure or a document for another model is not the project's evidence.
When ONVIF conformance is claimed, use the official conformance guidance and product database to check the product and listed firmware/software version. The ONVIF FAQ also distinguishes profile functions from brand-specific functions. Do not treat a basic video connection as proof that proprietary events, analytics search or every optional feature works with the client's recorder.
Accept a sample as a system, then approve the batch
Test the proposed camera, recorder, drive, power path and software together. Provide the real viewing tasks and target distances before the sample is selected. Ask for suitable setup instructions, supported recording modes and any known integration conditions. Record what was tested and what remains an exception; a sample video from another scene is not the acceptance result for your site.
| Task | Acceptance action | Record with the result |
|---|---|---|
| Required visual detail | Replay moving subjects at the intended near/far positions in normal day and night lighting | Lens/framing, lighting, recording settings and any obscured task |
| Recording and storage | Record all intended channels, retrieve a known interval and check the selected drive is supported | Models, drive, schedule, bitrate assumptions and timestamps |
| Events and remote access | Trigger each required event and test the approved user from the required network | Camera/recorder/app versions, event recipient and permission scope |
| Export and recovery | Open a saved export in the receiving player; perform an agreed interruption/restoration test | Export format, any gap, restart result and unresolved limitations |
Illustrative acceptance decision: a sample camera displays video in the NVR, but its required person event does not appear in the recorder search. Live-video compatibility passes; event-search acceptance remains open. Ask the supplier to demonstrate a supported version/configuration or propose a tested alternative before approving the batch. This is an example, not a reported customer incident.
Compare the delivered batch's labels, versions, connectors and contents with the approved sample record. Agree beforehand how changes and non-matching deliveries are handled. Define any batch inspection or sampling arrangement in the order; a single working sample does not prove every shipped unit has passed a stated test.
Agree the support scope, escalation and spare plan
Ask which hours and time zone apply, which contact channel to use, what product/setup issues are covered, how an urgent recording failure is escalated, and any agreed response target. Separate initial response, diagnosis and repair or replacement timing. If an out-of-hours service is required, specify it in the agreement and confirm its availability before selling that service to a client.
Prepare a fault report with order reference, exact models and versions, affected channels, power/network arrangement, recording settings, timestamps and checks already attempted. Keep passwords private and preserve important video before a reset, format or update. QuarkView’s support guidance asks buyers to distinguish local video, remote access and recording problems and supply model-specific context.
QuarkView’s warranty guidance describes support for eligible products and a diagnosis-led return process. Check the applicable terms for the order: coverage start, exclusions, return approval and destination, freight responsibility, repair/replacement timing and any charges. Contact support before returning equipment. A warranty period is not a promise of immediate replacement, an advance unit or reimbursement for an installer's site labour.
For critical repeat installations, agree which replacement camera, recorder, power adapter and mounting parts can be supplied, their compatibility and replenishment timing. Decide who holds any project spare and who pays for it. A stocked spare may shorten a site interruption, but stock and swap procedures must be agreed; do not assume loan units or cross-shipping are included.
Keep repeat orders and updates under change control
Ask how long the proposed model and compatible accessories are expected to remain available and how end-of-sale or firmware changes will be communicated. Specify the approved replacement process if the original model changes. Keep configuration backups and use a representative system for an agreed update check before applying a new version across client sites; verify recording, events, access and export afterwards.
Assign installation and maintenance responsibilities separately from supplier support. The client handover should identify device versions, network and account ownership, recording-health checks, incident retrieval, and the person who can visit if remote recovery fails. Do not leave the client dependent on an installer's personal administrator account.
Put commercial, OEM and service terms into the quote
| Area | Order should specify |
|---|---|
| Configuration and substitutes | Exact models/versions, lens/drive/accessories, acceptance record and who must approve a change |
| Price and delivery | Sample and batch quantities/prices, quote validity, stock/dispatch/transit, destination charges and split shipments |
| Support and returns | Hours/time zone, scope, escalation, eligible terms, return approval, freight and proposed repair/replacement process |
| Continuity | Replacement compatibility, spare ownership, repeat-order availability and change notices |
| OEM/private label, if requested | Approved artwork and packaging, sample approval, MOQ, branding scope, documents and firmware/update responsibility |
QuarkView’s support FAQ allows installer, reseller and OEM/private-label enquiries with sample needs, quantities, repeat-order plans and destination. Request the specific terms you need through the quote form; an enquiry is not acceptance of a service level or customisation scope.
Use the sample-testing checklist and system-design checklist to prepare the evidence you want reviewed before purchase.