Frequently Asked Questions

A manufacturer. EASCO states it designs and builds hardware at its own Shenzhen facility, not sourced from third-party suppliers and rebranded.

Confirm contingency and backup timelines directly with EASCO for any deadline-critical project.

Request these directly as part of your procurement due diligence.

Ask EASCO for the specific registration reference if you need it for a procurement file.

EASCO describes remote diagnosis and spare parts shipping, but no formal return or dispute policy is published. Confirm terms in writing before ordering.

Confirm the exact figure for your model directly with EASCO.

No, it's a generic industry term, also used by other manufacturers. EASCO's real models are named (Yunyi, Starship 4, etc.). Confirm which model a quote actually refers to.

Confirm mask-condition performance directly if your site requires them.

EASCO documents individual methods and some combined credentials, but not chained dual-biometric verification; confirm directly if this is a project requirement.

Pricing depends on hardware configuration, quantities, shipping destination, and customization, so EASCO typically requests basic project information before preparing a quotation

Confirm quote currency and exchange-rate handling before finalizing a large order.

Given milestone-based OEM payments, confirm what happens to paid funds if a project is cancelled mid-production.

For standard orders, EASCO raises financing needs directly during quotation.

Confirm Incoterms (EXW, FOB, DDP, etc.) explicitly before ordering.

EASCO describes remote WhatsApp/video diagnosis, but no guaranteed SLA is published; confirm one directly for 24/7 sites.

Confirm directly if data residency or self-hosting is a compliance requirement.

At this level of detail. Request full API documentation before committing to an integration architecture.

Confirm scalability limits directly for multi-site or high-device-count deployments.

EASCO's Facial Recognition Terminal pages list English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Turkish, Italian, French, Hebrew, Russian, Dutch, and Arabic, plus custom languages not confirmed as consistent across every product line or the management software.

EASCO states OEM is available "above minimum volume" without giving a number; ask directly for the current threshold.

Get this in a written agreement before commissioning custom firmware work.

EASCO documents customization within single product lines, not cross-category combinations. Ask directly if this fits your project.

Request one from EASCO before sharing sensitive files.

EASCO states a contract ensures spec adherence at the prototype stage, but no remediation process is described; confirm recourse before approving payment milestones.

EASCO doesn't price by product category publicly. Request a comparative quote directly if this is a real decision point.

Each format is documented individually; confirm cross-format platform compatibility directly.

Motor cycle ratings are documented; wear-part lifespan for sensors and readers isn't; ask directly for maintenance planning.

Ask directly if standardizing modules across a mixed deployment.

EASCO positions stainless for corrosion resistance; specifically confirm a comparative service-life figure directly if longevity is the deciding factor.