This canonical guide helps buyers who need avatr 11 huawei, avatr 11 harmony, avatr 11 electric suv, avatr 11 features, avatr 11 interior, avatr 11 extended warranty, avatr 11 ground clearance, avatr 11 dimensions length width height, China market context, and realistic 0-60 / 0-100 planning in one place. Start with the tool, then validate results with dated sources, version boundaries, and execution-risk checks.
Quick dimensions and ground-clearance answer (reviewed May 25, 2026)
Current official AVATR 11 size anchor: 4895 x 1970 x 1601 mm, wheelbase 2975 mm. Earlier launch material used 4880 x 1970 x 1601 mm, so treat the 15 mm length delta as a version boundary.
Ground-clearance intent note: AVATR SG owner manual table lists minimum ground clearance 155 mm (with no-load 18°/21° approach/departure angles in the currently downloadable Jul 24, 2025 manual), while reviewed global AVATR pages do not explicitly publish a ground-clearance field.
Sources: current AVATR configuration page and AVATR launch announcement, and AVATR SG owner manual.
Harmony intent note: go to #avatr-11-harmony to keep Harmony Edition wording tied to dated release context, current trim boundaries, and executable next steps.
Huawei intent note: go to #avatr-11-huawei to separate collaboration naming from legal roles such as importer-of-record, warranty principal, and software-delivery ownership.
Extended-warranty intent note: go to #avatr-11-extended-warranty to see what is known, what is unknown, and the minimum contract checks before deposit.
Features intent note: go to #avatr-11-features to separate public feature anchors from market-specific delivery boundaries before you sign.
Interior intent note: go to #avatr-11-interior to check public AVATR 11 cabin color labels, material boundaries, ambient lighting separation, and quote-ready verification steps on this same canonical URL.
Boundary model: AVATR public sources disclose body width (1970 mm) but do not publish verified mirror-to-mirror width. Keep mirror allowance explicit and rerun with measured values.
If your query is avatr 11 interior or avatr 11 interior colors, this canonical page answers it without a duplicate route. Pick a public color label to see buyer-fit guidance, material and lighting boundaries, quote risks, and the minimum verification action before deposit.
Best fit: Fleet, executive, and low-maintenance presentation.
Boundary: Best treated as the neutral default. The public label does not prove live allocation, exact material split, or destination-market availability.
Next action: Ask seller for dated configuration screenshot, trim code, VIN/build-order match, and daylight cabin photos.
Source scope: public AVATR 11 configuration labels reviewed Jun 2, 2026. This selector is a procurement-screening tool, not a live stock promise.
Canonical answer
Use one URL: /learn/avatr-11
The alias keywords "avatr 11 interior" and "avatr 11 interior colors" are merged into this canonical page. Do not create a competing route.
Public color options found
NAPPA grey | NAPPA red | Misty purple / Cotton white
The reviewed AVATR 11 configuration page exposes three interior color labels. Treat them as public configuration options, not guaranteed VIN-level stock or market allocation.
Ambience vs upholstery split
256-color ambient lighting is not the same as upholstery color
Regional product pages reference ambient-lighting capability, while the configuration color labels identify cabin material/color choices. Keep those two signals separate in quotes.
Cabin package scope
5-seat baseline, 4-seat Royal Edition, optional VIP package
The official configuration table distinguishes standard seating layouts from the 4-seat Royal Edition and a 4-seat VIP package that adds independent rear seats, rear 50W charging, HALO screen, privacy glass, dynamic ambient lighting, UV sterilization, and microfiber suede.
Evidence boundary
Color label confirmed; live availability pending
Public sources do not provide a trim-by-trim export-market allocation matrix, so the contract packet must freeze date, trim, VIN/build-order, and cabin photos.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and canonical intent | Aliases "avatr 11 interior" and "avatr 11 interior colors" map to /learn/avatr-11 | No dedicated standalone /learn/avatr-11-interior or /learn/avatr-11-interior-colors route is provided | Use /learn/avatr-11#avatr-11-interior for direct alias handling on one canonical URL. |
| Cabin scope | This section covers interior color labels, material naming, ambient lighting, and photo/QC evidence for seat, door, dash, roof, and rear-cabin checks. | Public sources do not provide a complete trim-by-trim export-market cabin package matrix. | Ask the seller to freeze cabin color, material, lighting package, trim, order date, and VIN/build-order reference in the quote packet. |
| Interior color labels | Reviewed AVATR configuration page lists NAPPA grey, NAPPA red, and Misty purple / Cotton white. | Public page does not prove live stock, trim pairing, destination-market availability, or VIN-level allocation. | Request dated configuration screenshot, trim code, VIN/build-order mapping, and cabin photos before deposit. |
| Ambient lighting | Regional AVATR 11 pages reference 256-color ambient lighting as a cabin feature. | Ambient-lighting color range does not disclose upholstery color, material condition, or export-market package availability. | Quote ambient lighting separately from seat/door-panel color and verify delivered feature package. |
| Material and naming scope | The official configuration page uses NAPPA labels, lists steering wheel NAPPA leather with bacteriostat material, and separates roof material between premium fabrics and microfiber suede depending on trim/package. | Public page does not publish a full surface-by-surface material map for seat, door, dash, roof, and market-specific package differences. | Require a written interior-material annex and photo set for seats, door panels, dashboard, roof liner, and rear cabin before deposit. |
| Seat comfort and rear-cabin package | The current official configuration table lists front electric adjustment, lumbar support, leg support, heating, ventilation, massage, easy entry/exit, driver memory, rear heating/ventilation/massage, ISOFIX, and a 4-seat VIP package on selected/package paths. | Public sources do not prove the exact delivered seat-function mix for every VIN, export channel, or retrofitted/demo vehicle. | Make the quote packet list front and rear seat functions separately, then verify with cabin video showing controls, screens, and rear-seat hardware. |
| Audio, screens, and cockpit electronics | The official configuration table lists Meridian audio, 2016W amplifier, 7.1.4 speaker setup, driver headrest speaker, HarmonyOS, 15.6-inch central screen, 10.25-inch touchscreen, HALO interactive screen, DMS camera, Face ID, gesture control, OTA, and multi-screen connection. | Public sources do not guarantee app/service availability, language pack, map coverage, OTA eligibility, or privacy/driver-monitoring rules in every destination market. | Require delivered-cockpit photos/video, software version, language/region settings, app availability, and OTA/support responsibility in the signed annex. |
| Order-date configuration drift | Official note 10 says vehicles ordered on May 16, 2026 or later receive the fixed open center console cup holder as standard, while earlier orders continue with the original configuration. | Public sources do not provide a VIN-by-VIN history for center-console hardware, demo-stock build dates, or market-specific substitutions. | Record order date, production date, VIN/build order, and console photos before treating interior photos from another listing as representative. |
| Used/demo vehicle condition | Light and high-contrast cabins create different inspection and resale risks. | No public official matrix gives stain/wear thresholds by interior color. | Add interior close-up photo set, cleaning-condition clause, and pre-shipment QC checklist to the deal file. |
| Decision question | Current answer | Evidence status | Procurement action |
|---|---|---|---|
| What does the broader "avatr 11 interior" query need? | It needs cabin color, material, ambient-lighting, photo evidence, and VIN-level configuration proof on one page. | Intent merge review for add-kw-avatr-11-interior-page, Jun 2, 2026. | Use this canonical interior section as the buyer checklist before treating any interior claim as contract-ready. |
| Which colors can be named from public evidence? | NAPPA grey, NAPPA red, and Misty purple / Cotton white are public configuration labels. | Official AVATR configuration page reviewed Jun 2, 2026. | Use those names for shortlist screening and quote requests, with screenshot date attached. |
| Can a broker promise any of the three colors from the page alone? | No. The public page is not live inventory and does not prove VIN/build-order allocation. | No reliable public trim-by-market allocation or stock dataset was identified in this review. | Ask for VIN or build-order mapping, seller stock proof, and dated cabin photos before payment. |
| Which interior facts are more than color labels? | Seat layout, seat functions, roof material, cockpit screens, audio system, wireless charging, air purification, fragrance, DMS/Face ID, and the May 16, 2026 cup-holder change all affect delivered-cabin value. | AVATR official configuration table extracted Jun 2, 2026; some items are trim/package/order-date scoped. | Turn the interior quote into a checklist with rows for color, material, seating layout, seat functions, cockpit electronics, audio, charging ports, and order-date hardware. |
| Does 256-color ambient lighting expand the upholstery palette? | No. It is a lighting feature and should be quoted separately from material/upholstery color. | AVATR regional product page ambience wording reviewed Jun 2, 2026. | Keep two quote lines: interior color/material and ambient-lighting feature availability. |
| What is the strongest counterexample to a generic interior claim? | The Royal Edition is listed as 4 seats while the mainstream Max/Ultra rows are 5 seats, and the optional 4-seat VIP package changes rear seating, charging, privacy glass, HALO screen, ambient lighting, UV sterilization, and suede scope. | AVATR official configuration page reviewed Jun 2, 2026. | Never accept “AVATR 11 interior” as one fixed package; require trim, seating layout, VIP package status, and rear-cabin photos. |
| What is the main color-condition tradeoff for used or demo stock? | Light two-tone cabins need stricter stain and wear inspection; red cabins need stronger resale-audience validation. | Procurement risk inference from visible color/material contrast; no official AVATR wear-threshold matrix is public. | Use a pre-shipment interior QC checklist, daylight photo set, and cleaning/remediation clause. |
Boundary model: published claim must be 2.5-12.0 s. Output is a planning spread, not a lab-certified acceleration test. 0-60 values are shown as derived estimates only.
Published baseline (canonical)
6.0 s (0-100 km/h)
Official AVATR 11 single-motor launch figure (Mar 24, 2023). Use this as baseline when intent is "avatr 11 0-100".
Current-catalog counterexample (Apr 2026 snapshot)
6.9 / 6.5 / 3.9 s listed across REEV/EV/AWD; EV + REEV shown together
This confirms that one AVATR 11 page can contain multiple powertrain contexts. Keep trim and date tags explicit before quoting 0-100 numbers.
Decision threshold for shortlist stage
If projected high > 7.0 s, verify with live test evidence
When the scenario band drifts too far above the claim, request VIN-level test data before deposit.
| Decision context | Use / not use | Why |
|---|---|---|
| Spec-sheet filtering during shortlist | Use | Good for fast first-pass screening between similar-size EV options. |
| Final contract and shipping commitment | Do not use alone | A published claim or simulated band is not a substitute for VIN-level delivered-spec confirmation. |
| Cross-market legal/compliance decisions | Do not use | 0-100 performance does not resolve import legality, tariff burden, connector fit, or after-sales execution risk. |
Updated May 9, 2026. This section answers "avatr 11 0-60" on the canonical URL without creating a separate route. Values are explicitly labeled as official or derived.
Official-data boundary (reviewed May 9, 2026)
Official AVATR pages publish 0-100 km/h, not 0-60 mph
Treat any AVATR 11 0-60 answer as a derived planning metric unless official 0-60 test documentation is released.
Unit conversion anchor
60 mph = 96.56064 km/h (exact conversion basis)
NIST revised conversion factors and eCFR unit conventions use 1 mile = 1609.344 m, which anchors reproducible mph-km/h conversion.
Method-risk counterexample
0-60 values can include rollout methodology in some OEM pages
Tesla Model Y official page includes "with rollout subtracted" notation, showing that 0-60 values across sources may not share one test protocol.
| Source context | Official 0-100 value | Derived 0-60 value | Method | Boundary note |
|---|---|---|---|---|
| 2023 AVATR 11 single-motor launch baseline | 6.0 s (official) | 5.8 s (derived) | 6.0 × 0.9656064 using 60 mph = 96.56064 km/h and constant-acceleration assumption | Planning-only conversion. Not an official AVATR 0-60 certification value. |
| Current AVATR 11 Max REEV Edition (config page) | 6.9 s (official listing) | 6.7 s (derived) | 6.9 × 0.9656064 | Official page note says values are reference data and affected by weather/road/SOC/load/tire. |
| Current AVATR 11 Max EV Edition (config page) | 6.5 s (official listing) | 6.3 s (derived) | 6.5 × 0.9656064 | Cannot be back-filled into 2023 single-motor baseline without trim/date reset. |
| Current AVATR 11 Ultra EV AWD (config page) | 3.9 s (official listing) | 3.8 s (derived) | 3.9 × 0.9656064 | Different powertrain context; use only as a trim-specific counterexample. |
Boundary model: Budget 25k-200k USD, annual use 3k-60k km, timeline 1-18 months. Outside this range, use manual advisory instead.
Policy reminder: choose your target market before running the tool. US route models 100% Section 301 additional duty plus regulator-path compliance gates (with 2023 model-year age exemptions only in 2044/2048); EU route models a 20.7%-35.3% anti-subsidy duty stress band plus a separate Feb 2026 undertaking-exemption verification branch.
If your query is avatr 11 electric suv, this page is the canonical answer: run the tool layer first, then validate trim/date/policy boundaries in the report layer before deposit.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 electric suv" is merged into this canonical page. Do not create a competing route.
Intent + page scope
Electric SUV answer + executable tools
This page combines dimensions fit checking, acceleration boundaries, and import-risk gates so electric SUV intent is answered with action, not only text.
Evidence split
2023 launch baseline + current listing snapshot
Keep dated launch claims and current EV/REEV listing facts separated when quoting or comparing trims.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and canonical intent | Alias "avatr 11 electric suv" maps to /learn/avatr-11 | No dedicated standalone /learn/avatr-11-electric-suv route is provided | Use /learn/avatr-11#avatr-11-electric-suv for direct alias intent handling on one canonical URL. |
| Electric SUV product framing | This page uses AVATR 11 electric SUV baseline with dimensions, acceleration, and policy-risk context | No single public source provides complete country-by-country homologation and service readiness in one list | Use this page for baseline screening, then confirm destination-country compliance/service scope in writing. |
| Trim and powertrain boundary | Current official listing mixes EV + REEV and multiple 0-100 values across trims | VIN-level deliverable trim and software/connector package by destination market | Lock trim/date/country in the quote packet before treating any headline spec as executable. |
| Execution next step | Tool layer returns fit status, landed-cost band, and policy gate status with explicit next action | Actual contract terms (logistics, warranty, adaptation, registration path) | Run the tool first, then move to a written sourcing checklist before deposit. |
| Date | Official update | Boundary | Minimum action |
|---|---|---|---|
| Aug 24, 2023 | Harmony Edition launch article publishes four variants and dated pricing window context. | Launch-page claims are historical anchors and should not be treated as universal current-delivery terms. | When quoting now, keep this as baseline evidence and add current config + policy checks. |
| Sep 24, 2023 | Official AVATR announcement states Harmony cockpit OTA upgrade opened to all AVATR 11 users. | All-user OTA wording does not prove identical feature availability across every destination market. | Require VIN + software-branch + destination-market scope in signed delivery docs. |
| Nov 6, 2023 | Official AVATR.OS 2.0.2 article says OTA was pushed to all users and reiterates delivered-vehicle precedence. | Website and OTA notes can diverge from final delivered configuration without contract-level mapping. | Lock order date, delivery configuration snapshot, and warranty/version annex before payment milestones. |
If your query is avatr 11 harmony, this page is the canonical answer: keep Harmony Edition claims date-scoped, validate current trim/warranty boundaries, and run tool checks before deposit.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 harmony" is merged into this canonical page. Do not create a competing route.
Harmony evidence anchor
Launch + OTA timeline (Aug-Nov 2023)
Official updates show Harmony Edition launch, then all-user Harmony cockpit OTA (Sep 24, 2023), then AVATR.OS 2.0.2 all-user OTA (Nov 6, 2023).
Decision-safe action
Keep harmony claims tied to release date and trim scope
Before deposit, lock one dated baseline and confirm current trim, warranty clauses, and market execution conditions in writing.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and canonical intent | Alias "avatr 11 harmony" maps to /learn/avatr-11 | No dedicated standalone /learn/avatr-11-harmony route is provided | Use /learn/avatr-11#avatr-11-harmony for direct alias intent handling on one canonical URL. |
| Known Harmony release facts | Official updates show Harmony Edition launch (Aug 24, 2023), all-user Harmony cockpit OTA (Sep 24, 2023), and AVATR.OS 2.0.2 all-user OTA (Nov 6, 2023) | VIN-level deliverable mix, market-level homologation readiness, and local service execution by channel | Use Harmony timeline as dated baseline, then validate live quote packet by trim/date/country before payment. |
| Warranty claim boundary | Campaign wording and terms-page wording can differ by date, owner status, and geography | No unified public matrix confirms transferability and cross-border applicability for every channel | Treat lifetime-style wording as pending evidence until policy version mapping is provided in signed contract annexes. |
| Execution next step | This page combines tool output, source table, and risk matrix for one-page decision support | Final landed-cost and compliance path still depend on destination market and transaction timing | Run tool layer first, then move to written sourcing checklist and policy gate confirmation. |
If your query is avatr 11 huawei, this page is the canonical answer: keep Huawei collaboration wording tied to dated product evidence, then validate legal and service roles in writing before deposit.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 huawei" is merged into this canonical page. Do not create a competing route.
Collaboration boundary
Huawei branding is not a legal-role shortcut
Huawei collaboration and ADS wording are product/context signals. They do not automatically define importer-of-record, warranty principal, or customs responsibility in every market.
Entity-role signal (dated)
HK AVATR about page states Changan 40.99%, CATL 14.1%, Huawei strategic partner
This is a role signal, not an auto-allocation of seller/importer/warranty accountability in each destination market. Keep contract entities explicit.
Decision-safe action
Lock role matrix in writing before deposit
Before payment, bind seller legal entity, importer channel, warranty claimant route, and software-branch scope to signed contract annexes.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and intent | Alias "avatr 11 huawei" maps to canonical /learn/avatr-11 | No dedicated standalone /learn/avatr-11-huawei route is provided | Use /learn/avatr-11 and jump to #avatr-11-huawei for direct alias handling on one canonical URL. |
| Known collaboration signal | Official AVATR pages and releases include Huawei collaboration and ADS naming in AVATR 11 context | No single public matrix maps Changan/Huawei/AVATR branding to importer-of-record and warranty-principal roles by destination market | Request a signed role matrix: seller legal entity, importer entity, customs declarant, and warranty service entity. |
| Feature and software execution scope | Official AVATR notes state some functions are OTA-dependent and delivered-vehicle configuration prevails over website content | VIN-level software branch, region-level feature enablement, and service-response SLA by channel | Before deposit, lock VIN-level feature declaration, software version path, and support ownership in contract language. |
| Execution next step | This canonical page already provides fit, acceleration, dimensions, policy, and risk tools in one flow | Final role accountability across sourcing, customs, registration, and after-sales in your destination market | Run the tool layer, then move to written quote validation with role-boundary evidence. |
| Evidence signal | Verified fact | Boundary / limitation | Minimum executable action |
|---|---|---|---|
| Official ownership + partner role signal (AVATR HK about page) | Page states Changan holds 40.99%, CATL 14.1%, and Huawei acts as strategic partner mainly providing intelligent components. | This does not identify the transaction counterparty, importer-of-record, or warranty principal for your destination market. | Map legal entities in writing: seller, exporter, importer-of-record, warranty service entity. |
| Founding collaboration statement (AVATR official Nov 15, 2021 news) | Official AVATR news states the AVATR 11 project is jointly developed by Changan Automobile, Huawei, and CATL. | Joint development wording is product/technology context, not customs-entry or after-sales liability allocation. | Require a signed annex that ties each liability layer to a legal entity and jurisdiction. |
| Regulator responsibility baseline (MIIT 2021 intelligent-vehicle access opinion) | MIIT requires production enterprises to take quality/safety responsibility and to inform users about driver responsibility and use conditions for assisted-driving functions. | This is an access/supervision baseline and does not replace destination-country import/registration requirements. | Keep smart-driving claims bounded by written user-responsibility clauses and destination compliance checks. |
| Importer legal-responsibility anchor (19 CFR 141.1, US) | The regulation states the importer of record is liable for any duties and taxes due. | A brand or technology label cannot substitute for importer-of-record designation in customs documents. | For US routes, require customs paperwork to name the exact importer-of-record before payment. |
| Market-specific warranty/service counterexample (AVATR HK + AVATR SG pages) | AVATR HK pages describe local terms and warranty certificate context; AVATR SG pages define local operator terms and service scope, with roadside-assistance language explicitly bounded to Singapore. | Local market terms can differ by operator and region; they are not globally portable by default. | Treat cross-border transfer and service availability as pending evidence until seller/importer provides signed region mapping. |
Sources: AVATR official news, AVATR HK/SG official pages and warranty document, MIIT 2021 intelligent-vehicle access guidance, and 19 CFR 141.1 importer-of-record rule. If destination-role mapping is not contract-signed, treat liability allocation as pending evidence.
If your query is avatr 11 features, this page is the canonical answer: use the tool layer for immediate screening, then validate feature delivery by trim, software version, and market scope before deposit.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 features" is merged into this canonical page. Do not create a competing route.
Feature decision boundary
Treat feature lists as trim + market + software scoped
Public listing and launch sources provide useful anchors, but delivered feature unlock can differ by region, map policy, and software version.
Decision-safe action
Require written feature declaration before payment
Lock delivered ADAS/cockpit/charging capability by VIN, trim, and destination-market scope in contract addenda.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and intent | Alias "avatr 11 features" maps to canonical /learn/avatr-11 | No dedicated standalone /learn/avatr-11-features route is provided | Use /learn/avatr-11#avatr-11-features for direct alias handling on one canonical URL. |
| Feature anchors from official pages | Official AVATR pages provide trim-level product and feature messaging that can be used as baseline screening evidence | A single public source does not guarantee identical delivered feature sets across all import markets | Use this page for screening, then request dealer/importer feature declaration by VIN and destination market. |
| ADAS and map-dependent capability | Feature availability can vary by regulation, map scope, software version, and local policy constraints | No public per-market AVATR 11 matrix confirms all delivered ADAS feature states | Treat advanced feature claims as pending evidence until contract and delivery docs confirm market-legal enablement. |
| Execution next step | This page combines tool output, risk matrix, and source table for feature-related decision framing | Post-sale update cadence and service response quality by channel | Before deposit, require a written software/support update path and service-SLA responsibility in your purchase package. |
| Evidence signal | Verified fact | Boundary / limitation | Minimum executable action |
|---|---|---|---|
| Official AVATR configuration snapshot (accessed May 18, 2026) | Top cards show HUAWEI ADS 4 while AVATR 11 trim rows show ADS 3 lidar version; row details list lidar x3, millimeter-wave radar x3, high-definition cameras x11, and ultrasonic radar x12. | One page can contain mixed naming layers. A marketing-series label is not proof that every market receives the same delivered feature scope. | Freeze screenshot date + trim code in your quote packet and require VIN-level delivered ADAS scope in signed annexes. |
| AVATR official notes 4/5/6/7 (accessed May 18, 2026) | AVATR notes some intelligent-driving functions need future OTA activation, NCA city routes are not available for all roads/cities, the system cannot replace driver control, and ADS advanced package is sold separately. | Feature visibility in catalog does not equal immediate delivery, full-city availability, or zero-additional-cost activation. | Before deposit, lock OTA activation window, package pricing, supported-city scope, and driver-responsibility wording in contract text. |
| AVATR official note 10 + page disclaimer (May 16 / May 18, 2026) | AVATR states that for orders on/after May 16, 2026 the front-row cup holder changed to standard configuration, and that delivered vehicle configuration prevails over website assets. | Configuration drift can happen inside one model year, including items not highlighted in top-level feature marketing. | Lock order date, BOM snapshot, and “delivered vehicle prevails” acknowledgement before payment milestones. |
| NHTSA automation-level baseline (accessed May 18, 2026) | NHTSA states Level 2 still requires the human driver to supervise and stay engaged, and consumer-market availability is currently concentrated below Levels 3-5. | ADAS naming should not be interpreted as self-driving transfer of legal responsibility. | Use destination-market legal guidance to define driver duty and incident liability before promising “hands-off” behavior. |
| EU mandatory safety rollout + type-approval process (Jul 2024 / Jul 2026) | European Commission states GSR systems apply to all new vehicles sold in the EU from Jul 7, 2024; Implementing Regulation (EU) 2024/1721 supplies technical-information templates and applies from Jul 7, 2026. | Passing catalog-level feature claims is not equivalent to proving destination-market type-approval documentation for the exact configuration. | For EU routes, request CoC/type-approval evidence package tied to the delivered configuration before shipment. |
Source scope: AVATR official configuration notes/disclaimer, NHTSA automation and reporting guidance, and EU safety/type-approval pages. These rows are execution controls, not legal advice.
Need a contract-ready AVATR 11 features checklist?
Before deposit, request VIN-level feature delivery scope, software-activation timing, and destination-market compliance evidence in writing.
If your query is avatr 11 extended warranty, this canonical page is the decision path: keep warranty statements tied to source date, ownership status, and region before you treat them as executable deal terms.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 extended warranty" is merged into this canonical page. No competing route is published.
What is actually known
Public sources show campaign wording plus a separate terms-page rule set, not one universal promise
The Aug 24, 2023 launch page and the current terms page both mention lifetime-style rights but with different trigger wording. Treat scope as version-bound evidence and verify by VIN.
Decision-safe next step
Require written warranty scope confirmation before deposit
Bind VIN, purchase date, owner status, and service region to signed terms before payment milestones.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and intent | Alias "avatr 11 extended warranty" maps to canonical /learn/avatr-11 | No dedicated standalone /learn/avatr-11-extended-warranty route is provided | Use /learn/avatr-11#avatr-11-extended-warranty for direct alias handling on the canonical URL. |
| Time-bounded campaign statement | Aug 24, 2023 launch article states first-owner lifetime three-electric coverage when order deadline was Dec 31, 2023 | Automatic applicability to current deals, second owners, or cross-border transactions | Do not quote campaign wording without written current applicability confirmation by VIN and owner type. |
| Campaign vs terms-page version match | Launch-page wording (Dec 31, 2023 order window) and current terms-page wording (pre-Dec 31, 2022 deposit condition, mainland scope, ownership-change termination) are both publicly visible | Which wording controls your deal path if contract annexes and seller channel documents point to different policy versions | Treat as pending evidence until seller/importer provides signed clause mapping that cites the exact rights notice/protocol version for your VIN. |
| Baseline policy terms | Official terms page shows 5y/120,000 km vehicle and 8y/160,000 km three-electric baseline warranty, plus 2y charging-pile equipment scope | How each channel/market modifies service execution and claim responsibility | Identify responsible after-sales entity and attach claim process terms to the signed purchase package. |
| Statutory baseline vs paid add-on contract | China SAMR auto three-guarantee rules define minimum after-sales obligations, while paid extended service contracts are optional add-ons sold separately | No reliable public AVATR cross-border service-contract template with deductible/exclusion matrix was identified | Request full contract pack before deposit: three-guarantee certificate, covered-system list, exclusions, deductible rules, and claim-response timeline by market. |
| Execution risk | Warranty language can be ownership- and channel-conditioned in policy text | Unified public matrix for second-owner and cross-border transferability | Treat transferability as pending evidence and collect signed seller/importer confirmation before payment. |
Evidence gap to keep visible (reviewed May 18, 2026)
No reliable public AVATR dataset was found for cross-border warranty-claim frequency, approval/denial ratio, or payout speed by importer channel. Treat projected claim economics as pending evidence unless your contract provides auditable historical claim records.
Stage1b enhanced pass adds trim-level mass and battery spread, warranty-scope boundaries, and cross-jurisdiction legal-layer checks. All core claims are source-dated for re-check.
| Trim | Energy / drive | Curb weight (kg) | Battery (kWh) | CLTC EV range (km) | CLTC overall range (km) | 0-100 km/h (s) | Charging window |
|---|---|---|---|---|---|---|---|
| Max REEV Edition | REEV / RWD | 2240 | 39.05 | 225 | 1065 | 6.9 | 30-80% in 15 min; 0-80% not listed for REEV row |
| Max EV Edition | EV / RWD | 2310 | 116.79 | 815 | N/A (EV row) | 6.5 | 0-80% in 35 min; 30-80% in 25 min |
| Ultra EV Edition AWD | EV / AWD | 2410 | 116.79 | 760 | N/A (EV row) | 3.9 | 0-80% in 35 min; 30-80% in 25 min |
| Black Knight | EV / AWD | 2410 | 116.79 | 760 | N/A (EV row) | 3.9 | 0-80% in 35 min; 30-80% in 25 min |
| Royal Edition | EV / AWD | 2410 | 116.79 | 760 | N/A (EV row) | 3.9 | 0-80% in 35 min; 30-80% in 25 min |
| Source context | Known | Boundary | Minimum action |
|---|---|---|---|
| AVATR 11 Harmony Edition launch article (Aug 24, 2023) | Limited-time first-owner offer included lifetime warranty for motor, battery, and electronic control system when order was placed by Dec 31, 2023 | Time-bounded promotion from launch context; do not treat as universal always-on policy. | For any transaction now, request written warranty validity by VIN, purchase date, and region. |
| AVATR warranty policy page (official terms page) | Vehicle warranty: 5 years or 120,000 km; three-electric system warranty: 8 years or 160,000 km; home charging pile equipment and installation: 2 years | Policy page wording is general and channel-specific. Cross-market service scope is not fully enumerated on one public page. | Bind warranty terms to contract language and identify responsible service entity before payment. |
| AVATR terms page lifetime-rule clauses (type=10181039) | Current terms-page text includes mainland-China scope language, pre-Dec 31, 2022 deposit-condition wording, and ownership-change termination clauses for lifetime rights | This wording can conflict with campaign-era summaries if contract annexes are not version-labeled. | Mark version match as pending until contract annex explicitly references the controlling policy version for your VIN and owner path. |
| China SAMR auto three-guarantee regulation (Order No.43) | Regulation effective Jan 1, 2022 sets minimum three-guarantee validity (>=2 years or 50,000 km) and minimum warranty period (>=3 years or 60,000 km), with new-energy serious-safety clauses and repair-delay compensation duties | These are regulatory minimum obligations and do not automatically resolve cross-border claim execution or non-mainland service routing. | Require a complete three-guarantee certificate and service-response commitments in writing before deposit milestones. |
| US and EU consumer-law layer (FTC/CFPB, US §2308, EU portal) | US guidance distinguishes separately sold service contracts from included manufacturer warranties; EU legal guarantee baseline remains seller-centered and usually at least 2 years (with some second-hand adjustments) | These frameworks are jurisdiction-specific and cannot be imported as automatic AVATR cross-border warranty coverage. | When destination market changes, re-check local legal baseline and align your contract counterpart and claim path before payment. |
| Transferability and cross-border execution | Policy text includes ownership-condition language, indicating warranty scope can change with ownership status. | No unified public matrix confirms second-owner and cross-border transferability for each AVATR 11 route. | Treat transferability as a pending evidence item and collect signed confirmation from seller/importer. |
If your query is avatr 11 china, this canonical page provides one answer path: use dated China domestic price anchors, then separate domestic baseline from export execution assumptions.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 china" is merged into this canonical page. Do not create a competing route.
China pricing anchors
Launch anchor RMB 319,900-349,900 | current listing RMB 289,900-429,900
Use dated scope labels: 2023 launch baseline for historical intent, current configuration snapshot for execution checks.
China policy timing
2024-2025 full exemption cap RMB 30k; 2026-2027 half-levy cap RMB 15k
For domestic China planning, transaction month can materially change effective tax outcomes.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and intent | Alias "avatr 11 china" maps to canonical /learn/avatr-11 | No dedicated standalone "avatr 11 china" route is provided | Use /learn/avatr-11 and jump to #avatr-11-china for the China-specific quick answer. |
| China domestic price context | Official 2023 launch anchor (RMB 319,900-349,900) and current listing snapshot (RMB 289,900-429,900) are both available | Exact transaction discount, local dealership policy, and add-on package pricing | Lock one dated anchor first, then validate live quote components in writing before deposit. |
| China tax-window assumption | 2024-2025 and 2026-2027 purchase-tax windows use different cap structures | Potential future policy adjustments after the review date | Tag purchase month explicitly and rerun total-cost math if the timeline crosses policy windows. |
| Export reuse risk | China MSRP and domestic tax assumptions do not directly equal import landed cost | Destination-country homologation, duty, and service exposure | Switch to destination-specific tool pages after domestic baseline validation. |
If your query is avatr 11 2024, this page keeps one canonical answer: use 2023 launch data as baseline, then layer in current configuration and policy checks with explicit date scope.
Canonical page strategy
Single URL: /learn/avatr-11
The 2024 alias is merged into the canonical AVATR 11 page to prevent near-duplicate routing.
Model-year evidence split
2023 launch baseline + current snapshot
2023 official release values and current configuration values are both useful, but must be quoted with date and scope labels.
Decision-safe action
Use dated assumptions before payment
Before deposit, lock one release baseline, then validate current trim, connector, and policy gates in writing.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route decision | Canonical route remains /learn/avatr-11 | N/A | Do not create /learn/avatr-11-2024 or another competing URL. |
| Published launch baseline | Mar 2023 official single-motor launch: 0-100 km/h in 6.0 s | No official standalone AVATR 11 2024 launch bulletin in reviewed set | Quote 2023 baseline with date label, then add separate current-snapshot validation. |
| Current listing context | Current AVATR 11 configuration page lists EV + REEV with broader price/range spread | Trim-level export deliverability differs by destination | Use current listing as counterexample/reference, not direct replacement of 2023 baseline. |
| Execution risk | US/EU policy gates updated in 2024 can dominate landed-cost outcomes | Future tariff and homologation updates after review date | Re-check policy table and importer confirmation before final payment milestones. |
If your query is avatr 11 dimensions length width height, this canonical page keeps one answer path: use the current official AVATR page for live fit checks, and treat the earlier launch announcement as a version boundary rather than a competing route. Public pages show body width, but do not publish a verified mirror span, so a mirror-aware clearance check stays separate from the headline size anchor.
Canonical size answer
4895 x 1970 x 1601 mm
Current official AVATR page lists a 2975 mm wheelbase for the live fit anchor.
Launch boundary
4880 x 1970 x 1601 mm
Earlier launch material used a 15 mm shorter body length, so date/version labels matter.
Default planning width
2310 mm (1970 + 180 + 80 x 2)
This page's default mirror/safety assumptions leave only 30-40 mm against common 40'/20' dry-container door widths, so physical loading tolerances must be confirmed before shipment.
Ground-clearance source boundary
155 mm appears in AVATR SG owner manual
Global AVATR pages publish L/W/H and wheelbase but do not list a ground-clearance field. Keep market/source labels visible before quoting one global number.
Decision-safe action
Verify trim/date before shipping
Use the live official page for garage, carrier, and local compliance planning, then run a separate mirror-aware clearance check because public AVATR pages do not publish a verified mirror span.
| Dimension | Current official page | Earlier launch material | Why it matters |
|---|---|---|---|
| Length | 4895 mm | 4880 mm | Current official page is 15 mm longer; use the live snapshot for garage and transport planning. |
| Width | 1970 mm | 1970 mm | Width is unchanged across the reviewed sources. Public AVATR pages publish body width, but not a verified mirror-to-mirror span, so mirror-aware clearance still needs a separate check. |
| Height | 1601 mm | 1601 mm | Height is unchanged across the reviewed sources; verify roof and loading clearance against local facilities. |
| Wheelbase | 2975 mm | 2975 mm | Wheelbase stayed constant, so cabin proportion planning is stable across the reviewed sources. |
| Minimum ground clearance | Not listed on global AVATR /en/11 or /en/configuration pages | 155 mm in AVATR SG owner manual (V2, accessed May 25, 2026) | Treat this as market/manual-scoped evidence and confirm VIN-level suspension/wheel specification before relying on it for ramps, curbs, or ferry loading. |
| Measurement | Value | Why it matters |
|---|---|---|
| Published body width | 1970 mm | This is the public AVATR body-width figure on the reviewed product/configuration pages. |
| Mirror-to-mirror width | Not published | No verified public AVATR source reviewed on May 9, 2026 discloses a mirror-span measurement. |
| Ground clearance publication boundary | Not listed on public AVATR global pages reviewed on May 25, 2026 | Global AVATR pages show L/W/H and wheelbase; they do not expose a dedicated ground-clearance field in the reviewed snapshot. |
| Ground clearance in market owner manual | AVATR SG owner manual table: minimum ground clearance 155 mm; no-load approach/departure 18°/21° | Useful operational clue, but market/manual context and trim/load state can differ. Keep VIN-level confirmation as final authority. |
| Owner-manual measurement context (secondary) | Singapore owner manual labels 1970 mm as width excluding side mirrors | Useful boundary clue, but this is a market manual artifact. Keep VIN-level/local-spec confirmation as the final authority. |
| OEM parameter-change disclaimer | Delivered-vehicle configuration prevails over posters/media | AVATR /en/11 states page visuals and specs may not fully represent delivered vehicles and technical parameters can change. |
| US National Network width cap (CMV rule) | 102 inches (2.6 m) | 23 CFR 658.15 sets this as a legal-width reference for relevant network operations; it is not a garage-fit rule. |
| US transport-width counterexample | Rear-view mirrors excluded for CMV width determinations | 23 CFR 658.16 is a legal-width measurement regime, not a passenger-SUV clearance rule. |
| EU transport-width reference | 2.55 m authorized-vehicle width | Useful as a shipping or road-transport envelope check, but not a substitute for garage fit. |
| Envelope reference | Limit / door width | Body-only margin (1970 mm) | Body + mirror margin (2150 mm) | Operational margin (2310 mm) | Boundary note |
|---|---|---|---|---|---|
| US National Network legal-width reference (23 CFR 658.15) | 2600 mm | +630 mm | +450 mm | +290 mm | Regulatory envelope reference. Not a garage, ramp-angle, or loading-bay maneuverability guarantee. |
| EU authorized-vehicle width reference | 2550 mm | +580 mm | +400 mm | +240 mm | Useful legal-traffic envelope benchmark; local permit and route constraints can still be tighter. |
| 20' dry container door width (Maersk equipment sheet) | 2350 mm | +380 mm | +200 mm | +40 mm | Maersk notes dimensions vary by container series. Confirm actual assigned unit, frame tolerance, and loading angle. |
| 40' standard / 40' high dry container door width (Maersk equipment sheet) | 2340 mm | +370 mm | +190 mm | +30 mm | At default assumptions, remaining door margin is thin. Any extra tolerance stack can flip pass to no-fit. |
Default operational width = 1970 + 180 + (80 x 2) = 2310 mm. If your mirror allowance or safety margin is higher, rerun the tool first and treat this table as a conservative baseline, not a loading approval.
Source note: current official AVATR page snapshot plus the launch announcement, US eCFR width clauses, and Maersk dry-equipment specifications. Transport-envelope rows are operational references, not vehicle-registration or legal advice. For garage, carrier, or local compliance planning, verify the exact trim/date and delivered configuration before committing.
If your query is avatr 11 ground clearance, this canonical page keeps one answer path: use source-scoped geometry data first, then validate market and VIN boundaries before relying on a single clearance number for ramps, curbs, or loading.
Canonical answer
Use one URL: /learn/avatr-11
The alias keyword "avatr 11 ground clearance" is merged into this canonical page. No competing route is published.
Published numeric anchor
155 mm minimum ground clearance
The currently downloadable AVATR SG owner manual (V2, file date Jul 24, 2025) lists minimum ground clearance 155 mm, with no-load approach/departure 18°/21° on the same geometry table.
Global-page boundary
No explicit ground-clearance field on AVATR global pages
The reviewed AVATR /en/11 and /en/configuration snapshots publish L/W/H + wheelbase, but do not expose a dedicated ground-clearance line.
Decision-safe action
Treat 155 mm as source-scoped, then verify VIN-level spec
Before ramp/curb/loading commitments, confirm wheel/tire size, suspension state, and delivered-vehicle spec sheet in writing.
| Dimension | Known | Unknown / boundary | Minimum action |
|---|---|---|---|
| Route and intent | Alias "avatr 11 ground clearance" maps to canonical /learn/avatr-11 | No dedicated standalone /learn/avatr-11-ground-clearance route | Use /learn/avatr-11#avatr-11-ground-clearance for direct alias handling on one canonical URL. |
| Published value and source scope | AVATR SG owner manual geometry table publishes minimum ground clearance as 155 mm | Global AVATR /en/11 and /en/configuration pages do not list a ground-clearance field in the reviewed snapshot | Keep source labels explicit and avoid projecting one market manual value to all trims and markets without confirmation. |
| Operational interpretation | Ground clearance is typically evaluated together with approach/departure angles and load state | No unified public OEM table was found for trim-by-trim exported ride-height variance by destination market | For ramps, curbs, and ferry loading, request VIN-level geometry and use a measured-site clearance check before payment. |
| Metric | Value | Source context | Boundary note |
|---|---|---|---|
| Minimum ground clearance | 155 mm | AVATR SG owner manual geometry table (V2, accessed May 25, 2026) | Manual-market scope only; verify delivered VIN spec and load condition before execution. |
| Approach angle | 18° (no load) | AVATR SG owner manual geometry table (same table as ground clearance) | Road/curb contact risk still depends on wheelbase, tire, and ramp profile. |
| Departure angle | 21° (no load) | AVATR SG owner manual geometry table (same table as ground clearance) | Use as planning anchor; final pass/fail needs site measurement and VIN-level confirmation. |
| Longitudinal passing angle | 13° / 12° (no load, two SG model codes) | AVATR SG owner manual geometry table (same page as ground clearance) | Useful crest-reference clue, but model-code and load-state differences require VIN-level confirmation before commitment. |
| Scenario | Known fact | Decision implication | Limit / counterexample |
|---|---|---|---|
| Manual geometry baseline (SG owner manual V2) | Minimum ground clearance 155 mm, no-load approach/departure 18°/21°, and no-load longitudinal passing angle 13°/12°. | No-load values are first-pass filters only; passenger/cargo load and tire/suspension setup can reduce effective clearance margin. | Market-manual scope only. Do not treat as a universal global AVATR figure. |
| Derived thresholds from published geometry | Derived from 155 mm clearance + 2975 mm wheelbase: breakover angle approx 11.9°; no-load approach/departure grade references approx 32.5% / 38.4%. | Useful when your ramp or crest profile is measured and you need a fast go/no-go triage before site inspection. | Derived rigid-body model only. It does not include suspension compression, tire deformation, or dynamic pitch. |
| US public-road hump reference (FHWA) | FHWA ePrimer describes a typical speed hump as 3-4 in (76-102 mm) high and 12 ft (3658 mm) long, with crossing speed often around 15-20 mph. | Versus 155 mm static clearance, nominal vertical delta is 53-79 mm before load transfer and transition-shape effects. | Traffic-calming guidance is roadway-context dependent and is not a private-ramp passability certification. |
| UK statutory road-hump envelope | UK Highways (Road Humps) Regulations 1999 set 25-100 mm height and >=900 mm minimum hump length. | The legal max hump height (100 mm) leaves 55 mm static margin against a 155 mm baseline before dynamic losses. | Jurisdiction-specific legal envelope only; local geometry and installation profiles can vary materially. |
| Public trim-level ride-height dataset | Global AVATR pages and reviewed SG model page publish L/W/H and wheelbase but do not publish a dedicated trim-by-trim ground-clearance matrix. | Use VIN-level document checks before any ramp, curb, ferry, or basement commitment. | Insufficient public data (待确认 / 暂无可靠公开数据) for export-market trim-by-trim dynamic ride-height variance. |
Sources: AVATR SG owner manual, FHWA Traffic Calming ePrimer, and UK Highways (Road Humps) Regulations 1999. Derived thresholds are computed from published geometry anchors on this page and are not a substitute for measured site checks.
Minimum executable path for ground-clearance decisions
Use this page for first-pass screening. Before any physical passability commitment, request VIN-level suspension/wheel/tire specs and measure your real ramp or curb geometry on-site.
| Gap | Previous weakness | Stage1b evidence increment | Decision impact |
|---|---|---|---|
| Ground-clearance angle values were stale against the currently downloadable manual | The page still showed 19°/23° while the currently downloadable AVATR SG owner manual (file date Jul 24, 2025) shows no-load approach/departure 18°/21° for listed SG model codes. | Updated all ground-clearance references to 155 mm with no-load 18°/21°, added no-load longitudinal passing angle 13°/12°, and surfaced file-date scope in the quick-answer and source table. | Removes stale-angle drift and lowers the risk of overestimating ramp/curb tolerance in pre-shipment checks. |
| Ground-clearance execution layer lacked external obstacle references | The report gave one clearance number, but did not anchor it against public-road hump geometry from regulator-grade sources. | Added FHWA traffic-calming geometry references (typical hump 3-4 in high, 12 ft long) and UK statutory road-hump envelope (25-100 mm height, >=900 mm length), then converted implications into static-margin checks. | Users can now compare a quoted 155 mm against real public-road obstacle envelopes instead of relying on abstract caution text. |
| No-load geometry was not translated into executable thresholds | The page listed ground-clearance metrics but did not provide a reproducible threshold model for breakover and ramp-grade triage. | Added derived geometry thresholds from published values: breakover approx 11.9° (from 155 mm + 2975 mm) and no-load approach/departure grade references approx 32.5% / 38.4%, with explicit model limits. | Gives users a practical first-pass go/no-go method before site measurement and VIN-level confirmation. |
| Dimensions section lacked quantitative transport-envelope checks | The page explained body width vs mirror uncertainty, but did not quantify clearance against widely used loading and legal-width envelopes. | Added source-backed envelope table with US 102-inch (2.6 m) legal-width reference, EU 2.55 m reference, and Maersk 20'/40' dry-container door widths (2350/2340 mm), plus body-only vs assumed-width margins. | Users can now see when a nominal pass becomes fragile under realistic mirror and safety assumptions before booking transport. |
| Delivered-spec variability was not explicit in dimensions risk framing | Users could still over-trust published brochure values without seeing the OEM disclaimer hierarchy. | Added AVATR official /en/11 disclaimer context (delivered vehicle prevails; technical parameters can change) and a secondary owner-manual boundary note (width shown as excluding side mirrors). | Improves contract-stage behavior: users are guided to verify VIN-level and delivered-spec measurements, not only marketing snapshots. |
| Alias intent "avatr 11 china" was not explicit on-page | The canonical URL already covered AVATR 11 and related aliases, but "avatr 11 china" was not directly labeled in hero/anchors/FAQ, which could reduce intent-match clarity. | Added a dedicated China intent summary section (#avatr-11-china), alias anchor links, FAQ coverage, and explicit canonical wording to keep one URL while clarifying domestic-vs-export boundaries. | Users searching "avatr 11 china" can now get a direct answer path on the canonical page without route splitting or mixed-assumption confusion. |
| Alias intent "avatr 11 ground clearance" was not explicit on-page | Ground-clearance intent was partially implied inside dimensions text, but lacked a dedicated alias anchor and source-scoped quick answer. | Added a dedicated ground-clearance summary section (#avatr-11-ground-clearance), source-scope table, FAQ coverage, and explicit canonical wording while keeping one URL. | Users searching "avatr 11 ground clearance" now get a direct answer path with source boundaries, instead of mixing market-manual values with global-page assumptions. |
| Alias intent "avatr 11 interior" was merged but not explicitly answered | The change required alias_merge into /learn/avatr-11, but the canonical page needed a direct interior anchor covering cabin color, material, ambient lighting, and VIN/photo verification boundaries. | Added #avatr-11-interior, preserved #avatr-11-interior-colors as a compatible sub-anchor, and expanded the selector/table/FAQ copy to cover broader interior intent beyond color labels. | Users searching "avatr 11 interior" now get an immediate answer and quote-ready cabin evidence checklist on the canonical page without creating a duplicate route. |
| Interior section still over-weighted color labels | The section answered color/material/lighting but did not expose seat layout, rear-cabin package, audio, cockpit screens, DMS/Face ID, or order-date hardware drift from official configuration evidence. | Added source-backed interior package rows: 5-seat vs 4-seat Royal Edition, 4-seat VIP package contents, front/rear seat-function checks, Meridian 2016W 7.1.4 audio, HarmonyOS cockpit electronics, DMS/Face ID, and May 16, 2026 cup-holder configuration change. | Users can now convert an interior inquiry into a contract-ready checklist instead of treating “interior” as only color selection. |
| Alias intent "avatr 11 0-60" lacked explicit method boundary | The page answered 0-100 but did not provide a reproducible 0-60 conversion method, missing conditions and protocol mismatch risk. | Added a dedicated 0-60 section with exact unit-conversion anchor (60 mph = 96.56064 km/h), derived scenario table, and explicit "planning-only" boundary. | Users can answer 0-60 intent on the canonical URL without mistaking derived values for official certification data. |
| Current AVATR 11 catalog facts were partially stale | The page still used older mixed-catalog anchors (for example 815 km and no explicit multi-trim 0-100 listing) in key boundaries. | Refreshed with current official AVATR configuration snapshot facts: EV + REEV listing, price range RMB 289,900-429,900, CLTC overall up to 1065 km, and listed 0-100 values across trims (6.9 / 6.5 / 3.9 s). | Users can see a concrete counterexample and avoid mixing 2026 mixed-catalog values into 2023 baseline decisions. |
| US age-based compliance boundaries were under-specified | US section mentioned RI/compliance burden but did not show calendar-year boundaries for 25-year/21-year exemptions. | Added NHTSA HS-7 and EPA age-based boundary facts: 2023 model-year reaches EPA 21-year exemption in 2044 and FMVSS 25-year path in 2048. | Users can distinguish near-term RI/compliance path from long-horizon age exemptions before placing deposits. |
| Charging section lacked regional structure and timeline depth | The report highlighted global charger totals but did not include China fast-charger growth or AFIR 2027 pool upgrade milestones. | Added IEA 2025 regional structure data (China 5.2 million public points in 2024, Europe >1 million with >150k fast and >70k ultra-fast) and AFIR 2027 TEN-T pool requirement context. | Improves route-level feasibility judgement for public-charging-dependent import plans. |
| Time-sensitive source freshness was lagging | Data source table and FX anchor language pointed to prior access timestamps and did not reflect the latest April 2026 review pass. | Refreshed source timestamps and updated the static FX planning reference to the May 11, 2026 H.10 weekly release (latest value used: 6.8005 on May 8). | Reduces hidden drift in cost projections and keeps time-sensitive assumptions auditable. |
| Trim-level execution data lacked mass/battery granularity | The page had price/range/performance anchors, but users still lacked one table showing curb-weight and battery-capacity spread across REEV/EV trims. | Added official configuration snapshot table (accessed May 14, 2026) with trim-level curb weight (2240-2410 kg), battery capacity (39.05 vs 116.79 kWh), range, acceleration, and charging windows. | Users can now distinguish cargo/loading and charging implications by trim instead of assuming one generic AVATR 11 profile. |
| Warranty scope was easy to over-generalize | Earlier text did not separate time-limited launch offers from baseline policy terms, increasing risk of warranty over-promising in cross-border deals. | Added source-backed warranty boundary table: Aug 24, 2023 first-owner lifetime three-electric campaign (through Dec 31, 2023) versus policy-page baseline terms (5y/120k vehicle + 8y/160k three-electric + 2y charging pile). | Decision flow now forces date/channel/written-contract checks before using warranty claims in payment decisions. |
| Warranty section still leaned on OEM-only narrative | The page had AVATR source coverage, but lacked independent consumer-protection and statutory baseline framing to separate OEM promises from legal minimums. | Added China SAMR three-guarantee baseline (effective Jan 1, 2022), US service-contract vs warranty legal framing (FTC/CFPB + §2308), and EU legal-guarantee baseline context to the warranty decision layer. | Users can now separate OEM campaign claims, statutory minimum obligations, and optional paid service contracts before deposit. |
| Version conflict handling for lifetime wording was under-specified | Public AVATR sources show different lifetime-trigger wording across launch-page and terms-page contexts, but the page did not explicitly flag this as an unresolved evidence conflict. | Added explicit campaign-vs-terms version-match boundary and a mandatory contract-clause mapping action (VIN + owner type + policy version) before payment. | Reduces false certainty and prevents users from treating unmatched policy versions as executable warranty promises. |
| China domestic policy timing for "avatr 11 2024" was not explicit | The page emphasized US/EU policy gates but did not state China purchase-tax window shifts and cap changes between 2024-2025 and 2026-2027. | Added official purchase-tax schedule anchors: 2024-2025 full exemption with RMB 30,000 per-car cap, then 2026-2027 half-levy with RMB 15,000 cap. | Users comparing model-year budgets can now separate policy-window effects from MSRP moves before signing. |
| REEV tax-eligibility technical gate after 2025 was missing | Current AVATR 11 listing includes REEV, but the report did not clarify that 2026-2027 tax-eligibility adds new technical thresholds. | Added 2025 No.24 policy anchor for 2026-2027: PHEV/REEV conditional equivalent all-electric range >=100 km and fuel/electricity threshold checks, with directory-removal consequence. | Prevents users from assuming all REEV trims retain identical tax treatment after Jan 1, 2026. |
| US NEVI route assumptions lacked service-level requirements | US charging section only highlighted CCS Type 1 connector requirement and missed minimum port count/power/uptime constraints. | Expanded NEVI evidence with 23 CFR 680 minimums: >=4 network-connected ports, 150 kW simultaneous capability per corridor port, and >97% annual uptime. | Improves route-execution screening quality for public-charging-dependent import scenarios. |
| Overseas expansion signal was underused in channel-risk framing | Channel section focused on 2023 domestic milestones and lacked newer official overseas-operation facts and limits. | Added official overseas-page evidence: overseas business rollout started in 2024, region contact matrix, and AVATR 11/07 Nepal/Sri Lanka 190 kW note as a market-specific counterexample. | Users can separate brand globalization momentum from market-specific homologation/service certainty with fewer hidden assumptions. |
| EU duty section lacked undertaking-exemption branch after Feb 2026 | Policy table treated EU anti-subsidy duties as mostly static percentages and did not expose the post-review undertaking exemption path. | Added Regulation (EU) 2026/330 + Decision (EU) 2026/328 evidence: Article 2a/2b exemption mechanics, undertaking-document conditions, and current accepted model scope (CUPRA Tavascan). | Prevents false binary decisions ("always taxed" vs "always exempt") and forces exporter/model-level verification before EU landed-cost commitment. |
| 2026-2027 REEV tax gate was not quantified enough for execution | The page mentioned >=100 km equivalent range but did not include curb-weight split thresholds for fuel and electricity ratios or the directory cutover timeline. | Added 2025 No.24 numeric thresholds (<70%/<75% fuel ratio and <140%/<145% electricity ratio), plus Jan 1, 2026 directory enforcement and non-compliant model removal context. | Users can now separate "REEV label" from "tax-eligible REEV configuration" before signing, reducing compliance drift risk. |
| Current AVATR configuration execution signals were underused | The report used price/range/acceleration anchors but did not surface charging-window split and ADS wording divergence from the same official page. | Added current official page facts for 0-80 vs 30-80 charging windows by powertrain and explicit ADS wording boundary (ADS 4 top cards vs ADS 3 table row). | Improves trim-level execution checks and reduces risk of over-interpreting one marketing label as delivered feature equivalence. |
| Features intent lacked regulator-grade execution boundaries | The page warned that feature delivery can vary, but did not anchor that warning with concrete automation-level responsibility and destination-market compliance signals. | Added a features regulatory-delivery matrix with dated evidence from AVATR official notes (OTA activation, NCA city scope, separate ADS package, May 16, 2026 configuration change), NHTSA Level-2 responsibility boundary + 2025 SGO update context, and EU Jul 7, 2024 mandatory safety rollout plus 2024/1721 technical-information template boundary. | Users now have a contract-ready checklist for feature claims instead of generic caution text, reducing over-promise risk before deposit. |
| Harmony intent evidence was still launch-centric | Harmony section focused on Aug 24, 2023 launch context and did not expose the subsequent all-user OTA timeline, which can change interpretation of “Harmony” intent. | Added a dated Harmony timeline using official AVATR updates: Sep 24, 2023 all-user Harmony cockpit OTA and Nov 6, 2023 AVATR.OS 2.0.2 all-user OTA with delivered-vehicle precedence boundary. | Users can now separate launch-era messaging from post-launch software rollout reality before signing. |
| Charging structure freshness lagged behind 2025/2026 updates | Charging section still centered on 2024-point snapshots and lacked latest 2025 global and early-2026 China infrastructure markers. | Refreshed charging evidence with IEA 2026 (global public points >7 million by end-2025; China >4.7 million public points) and China State Council portal Feb 2026 snapshot (21.01 million total facilities). | Improves route-readiness decisions for public-charging-heavy scenarios by reducing stale-capacity assumptions. |
| Harmony ecosystem regional-availability risk lacked explicit uncertainty flag | Page discussed feature variability but did not isolate the missing public matrix for Harmony app/service availability by market. | Added a dedicated pending-evidence row for Harmony ecosystem app/service availability and an executable minimum verification path. | Prevents overconfidence that “all-user OTA” means identical regional service availability in export workflows. |
| Huawei-intent section lacked dated entity-role evidence | The section warned that Huawei naming is not a legal shortcut, but it did not show a source-backed ownership/partner role signal in the same block. | Added official AVATR HK ownership + partner-role evidence (Changan 40.99%, CATL 14.1%, Huawei strategic partner) and linked it to a contract-entity action path. | Users can now separate collaboration branding from executable contract accountability before deposit. |
| Importer-of-record responsibility was not explicit in Huawei decision path | Huawei-intent guidance listed role checks but did not anchor customs-responsibility allocation with a legal-text citation. | Added 19 CFR 141.1 liability anchor (importer of record is liable for duties and taxes) to the Huawei accountability matrix. | Reduces the risk of assuming a technology brand can replace customs-entity responsibility in import workflows. |
| Cross-market service/warranty counterexamples were underused in Huawei section | The section did not show concrete evidence that AVATR service and warranty language can be operator- and market-specific. | Added AVATR HK and AVATR SG terms/warranty/service counterexamples (including SG roadside-assistance regional scope) and a mandatory signed region-mapping action. | Improves risk control for users who might otherwise project one market warranty/service claim to another market. |
Direct answer for "avatr 11 harmony"
Use the same canonical /learn/avatr-11 URL and jump to #avatr-11-harmony
No dedicated /learn/avatr-11-harmony route is created. Harmony intent is answered on one page with launch-date context, boundary notes, and next actions.
Harmony is a timeline, not one frozen spec card
Official chain: Aug 24, 2023 launch -> Sep 24, 2023 all-user Harmony cockpit OTA -> Nov 6, 2023 AVATR.OS 2.0.2 all-user OTA
For decision safety, bind Harmony claims to dated releases plus delivered-vehicle disclaimers, then confirm VIN + market scope in writing.
Direct answer for "avatr 11 huawei"
Use the same canonical /learn/avatr-11 URL and jump to #avatr-11-huawei
No dedicated /learn/avatr-11-huawei route is created. Huawei collaboration intent is resolved on one page with role boundaries and next actions.
Huawei collaboration is a technology signal, not a legal-role default
Official AVATR regional page shows Changan 40.99%, CATL 14.1%, and Huawei strategic-partner positioning (accessed May 26, 2026)
Treat this as evidence of collaboration context. Contract entity roles (seller/importer/warranty principal) still need signed market-specific allocation.
Direct answer for "avatr 11 electric suv"
Use the canonical /learn/avatr-11 URL with one tool-first flow and one evidence stack
No dedicated /learn/avatr-11-electric-suv route is created. Use the #avatr-11-electric-suv anchor for the alias-specific summary, boundary table, and next-action path.
Direct answer for "avatr 11 interior"
Use the same canonical /learn/avatr-11 URL and jump to #avatr-11-interior
No dedicated /learn/avatr-11-interior route is created. Interior intent is answered with cabin color selection, material boundaries, ambient-lighting separation, known/unknown notes, and next-action checks on the canonical page.
Direct answer for "avatr 11 extended warranty"
Use the same canonical /learn/avatr-11 URL and jump to #avatr-11-extended-warranty
No dedicated /learn/avatr-11-extended-warranty route is created. Warranty claims stay decision-safe only when date, owner status, and region are validated in writing.
Direct answer for "avatr 11 2024"
No separate "avatr 11 2024" route is created; this canonical URL merges 2023 launch baseline + current configuration snapshot
Use one decision page: /learn/avatr-11. Treat model-year references as dated evidence slices (launch baseline vs latest listing), not interchangeable values.
Direct answer for "avatr 11 china"
Use the same canonical page (/learn/avatr-11): China intent is answered with dated launch + current listing anchors on one URL
No separate /learn/avatr-11-china route is created. China-specific summary, boundaries, and next actions are grouped under the dedicated anchor section.
Direct answer for "avatr 11 dimensions length width height"
Current official AVATR page: 4895 x 1970 x 1601 mm with a 2975 mm wheelbase
Earlier launch material used 4880 x 1970 x 1601 mm, so the 15 mm length delta should be treated as a version boundary, not a contradiction.
Direct answer for "avatr 11 ground clearance"
Published minimum ground clearance found in AVATR SG owner manual: 155 mm
The currently downloadable AVATR SG owner manual (file date Jul 24, 2025) lists 155 mm with no-load approach/departure 18°/21°. Global AVATR pages do not publish a ground-clearance field, so treat this as market/manual-scoped evidence and verify VIN-level specs before physical-clearance decisions.
Dimensions fit boundary
Body width is published; mirror span is not
Public AVATR pages show 1970 mm width and do not publish a verified mirror-to-mirror figure, so garage and shipping clearance need a separate mirror-aware check.
Default shipping-door margin is narrow after assumptions
With 180 mm mirror allowance + 80 mm side margins, planned width becomes 2310 mm
Compared with Maersk dry-container door widths (2350 mm for 20' and 2340 mm for 40'/40' high), only 40-30 mm remains before angle/ramp/frame tolerances.
Direct answer for "avatr 11 0-60"
No official AVATR 11 0-60 mph figure is published in the official AVATR release/configuration sources reviewed on May 9, 2026
Use 0-60 as a planning conversion only: 60 mph = 96.56064 km/h, and any derived value from 0-100 assumes constant acceleration unless VIN-level test evidence is provided.
Direct answer for "avatr 11 0-100"
Official 2023 single-motor AVATR 11 launch claim: 0-100 km/h in 6.0 s
This value comes from AVATR official March 2023 release data and is the canonical baseline on this page for 0-100 intent.
US legal-age exemptions do not unlock a 2023 unit yet
2023 model-year timing: FMVSS 25-year path earliest 2048; EPA 21-year emissions exemption earliest 2044
NHTSA HS-7 and EPA import guidance separate age-based exemptions from standard RI/compliance pathways. For near-term execution, duty budget alone is not enough.
2023 quoting must lock one official release baseline
Mar 2023: RMB 319,900-349,900 | Aug 2023: RMB 300,000-390,000
AVATR published both a Mar 2023 single-motor release and an Aug 2023 Harmony Edition release. Use one dated baseline per quote and keep the release disclaimer context.
Current catalog is a counterexample, not a direct 2023 substitute
Current AVATR 11 page shows EV + REEV, up to 1065 km CLTC overall range, and listed 0-100 values of 6.9 / 6.5 / 3.9 s across trims
These values are useful execution references but should not be mixed directly into 2023 single-motor baseline quotes without reset of assumptions.
Trim execution spread is wider than one headline suggests
Official May 2026 snapshot shows 2240-2410 kg curb weight and 39.05/116.79 kWh battery split across REEV/EV trims
Procurement risk rises if you quote only one generic "AVATR 11" line. Lock trim-level mass, battery, range, and charging-window values in writing before shipment.
Warranty statements are not one-size-fits-all
Aug 24, 2023 launch article had a first-owner lifetime three-electric offer through Dec 31, 2023, while AVATR policy page also lists 5y/120k vehicle + 8y/160k three-electric baseline terms
Treat warranty as channel/date-bound. Cross-border transferability and second-owner applicability should be confirmed contractually, not assumed from marketing text.
Policy shock still dominates import risk
US: 100% duty + compliance gate | EU: 7.8%-35.3% extra duty + 10% base duty
For US/EU buyers, post-2024 policy layers are often more decision-critical than trim-level MSRP differences, and they can block execution even when headline budget looks sufficient.
EU duty path now has a conditional exception branch
From Feb 10, 2026, Regulation (EU) 2026/330 adds Article 2a/2b undertaking exemptions for qualifying imports
Decision (EU) 2026/328 currently accepts a model-specific undertaking for Volkswagen (Anhui) + SEAT (CUPRA Tavascan). AVATR 11 undertaking applicability remains unconfirmed and must be checked before quoting.
China purchase-tax timing now has hard date cliffs
2024-2025: full purchase-tax exemption capped at RMB 30k per NEV passenger car; 2026-2027: 50% reduction capped at RMB 15k
If your quote crosses policy windows, total cost can move materially. Do not reuse a 2024 tax assumption in a 2026 transaction model.
2026-2027 REEV tax relief is now threshold-driven
PHEV/REEV must meet >=100 km equivalent all-electric range plus fuel/electricity ratio limits by curb-weight band
MIIT/MOF/SAT 2025 No.24 sets fuel-consumption ratio limits (<70% for <2510 kg; <75% for >=2510 kg) and electricity-consumption ratio limits (<140% / <145%). Tax treatment now depends on technical compliance, not only badge type.
NEVI route quality is a service-level gate, not just a plug type
NEVI corridor stations must support at least 4 network-connected DCFC ports, 150 kW per port, and >97% annual uptime
Connector fit alone is insufficient for public-charging-heavy plans; add route service-level checks before deposit.
Charging access should be checked by structure, not only point count
IEA 2026: global public points exceeded 7 million by end-2025; China reached over 4.7 million public points (>65% global share) and 21.01 million total facilities by end-Feb 2026
Queue and route risk follow power mix, uptime, and corridor quality rather than point totals alone.
Connector compatibility remains a first-order execution gate
EU AFIR requires Combo 2 on public DC and raises TEN-T pool minimum to 600 kW by Dec 31, 2027; US NEVI minimum standards require CCS Type 1 on funded DC ports
If your delivered connector/adapter path is unverified, route assumptions can fail even when charger density is high.
Domestic traction helps confidence but does not prove export readiness
AVATR reported 12,000 delivered by Aug 30, 2023 and targeted >350 channel contacts by end-2023
Official delivery/channel milestones reduce early product uncertainty, but they are not equivalent to country-level homologation, service coverage, or connector compatibility proof.
Do not mix 2023 intent baseline with current EV/REEV catalog values
Current AVATR 11 listing includes EV + REEV and wider price/range spread
Current configuration pages can show post-2023 powertrains and expanded range bands. Treat them as execution references, not as 2023 canonical pricing evidence.
| Profile | Fit | Why |
|---|---|---|
| Premium-tech buyer with home charging | High | Best alignment with long-range use and software-centric cabin expectations. |
| Public-charging-only urban owner | Medium | Can work, but charging queue uncertainty and route dependency reduce certainty. |
| Low-buffer importer (<10% cash reserve) | Low | High exposure to variable import fees and shipping timing. |
| Fast replacement cycle (<=12 months ownership) | Low | Cross-market resale and warranty transferability are hard to optimize in short cycles. |
| Assumption | Value | Note |
|---|---|---|
| Base vehicle anchor (2023 intent) | Mar 2023: RMB 319,900-349,900; Aug 2023: RMB 300,000-390,000 | Both are official AVATR releases. Keep release date + trim scope explicit when quoting. |
| China purchase-tax schedule (passenger NEV) | 2024-2025: full purchase-tax exemption (cap RMB 30,000/vehicle); 2026-2027: 50% levy (tax reduction cap RMB 15,000/vehicle) | Policy window materially changes domestic total-cost math. Keep purchase-date assumptions explicit in every quote. |
| 2026-2027 REEV eligibility gate (tax relief) | PHEV/REEV: equivalent all-electric range >=100 km; fuel-consumption ratio <70% (<2510 kg) or <75% (>=2510 kg); electricity-consumption ratio <140% (<2510 kg) or <145% (>=2510 kg) | From Jan 1, 2026, directory-listed models must meet these thresholds. Non-compliant entries can be removed from the tax-reduction directory. |
| EU undertaking exception path (countervailing duty) | Since Feb 10, 2026, Article 2a/2b allows duty exemption only for accepted undertaking entities with compliant undertaking declaration + invoice chain | Current accepted case is Volkswagen (Anhui) + SEAT for CUPRA Tavascan. Do not assume AVATR 11 is covered without exporter/model-level proof. |
| Trim-level execution snapshot (official AVATR page) | Curb weight 2240-2410 kg; battery capacity 39.05/116.79 kWh; charging windows vary by powertrain (REEV 30-80 in 15 min; EV 0-80 in 35 min) | Accessed May 14, 2026. Use trim-level values in logistics and charging planning instead of one blended model assumption. |
| FX reference for stress test | 1 USD = 6.8005 CNY | Federal Reserve H.10 weekly release date May 11, 2026 (May 8, 2026 column value used). This tool uses a static planning reference; recheck live FX before transaction. |
| Warranty-claim boundary handling | Launch campaign vs policy baseline must be separated (time-limited first-owner lifetime offer vs standard term page) | Use dated source context and contract text. Do not project one market or campaign claim to all ownership paths. |
| 0-60 conversion method boundary | 60 mph = 96.56064 km/h; ratio vs 100 km/h = 0.9656064 | Conversion basis is reproducible (NIST + eCFR unit conventions), but derived 0-60 values assume constant acceleration and are not official AVATR certification metrics. |
| Import + compliance uplift | 44%-58% | Model sensitivity band only. No reliable unified global public dataset supports one universal uplift percentage. |
| US compliance eligibility gate | For under-25-year nonconforming vehicles: RI path + 150% bond + 120-day conformity workflow | NHTSA import FAQ indicates permanent import is constrained if FMVSS certification is absent. EPA import forms and declarations are also required. |
| US NEVI corridor service-level baseline | NEVI corridor stations: >=4 network-connected DCFC ports, >=150 kW simultaneous capability per corridor port, and >97% annual uptime | This does not guarantee your route experience, but it sets the minimum service-quality floor for funded corridor assets. |
| US age-based exemption boundary (2023 model-year) | EPA 21-year path earliest 2044; FMVSS 25-year path earliest 2048 | NHTSA HS-7 and EPA import guidance define age-based exemptions that do not solve near-term import execution for a 2023 vehicle. |
| Cycle-to-reality boundary | No universal CLTC-to-real conversion factor | EPA adjusted-range context (including common 0.7 label workflow) is method-specific and cannot be transplanted as a universal CLTC conversion law. |
| Decision threshold used by this tool | >=15% budget headroom above modeled landed-high | Internal risk-control rule for this page, not an industry-regulator standard. |
| Metric | Value | Evidence level | Updated / Effective | Source |
|---|---|---|---|---|
| 2023 AVATR 11 single-motor launch | RMB 319,900-349,900; CLTC 600/705 km; 230 kW max power; 0-100 km/h in 6 s | Official OEM release | Published Mar 24, 2023 | AVATR official news |
| 2023 Harmony Edition MSRP + ADS 2.0 messaging | RMB 300,000-390,000; four variants; up to 730 km CLTC; 750V fast charging architecture | Official OEM release | Published Aug 24, 2023 | AVATR official news |
| Harmony cockpit all-user OTA rollout scope | Official Sep 24, 2023 announcement states Harmony cockpit OTA upgrade opened to all AVATR 11 users, including existing users and newly delivered Harmony Edition users. | Official OEM release | Published Sep 24, 2023; accessed May 26, 2026 | AVATR official news (Harmony cockpit OTA) |
| AVATR.OS 2.0.2 all-user OTA + delivered-vehicle boundary | Official Nov 6, 2023 article says AVATR.OS 2.0.2 was pushed to all users and reiterates that some functions are realized via OTA while final delivered configuration prevails. | Official OEM release + disclaimer context | Published Nov 6, 2023; accessed May 26, 2026 | AVATR official news (AVATR.OS 2.0.2) |
| AVATR ownership + partner-role signal (Hong Kong official page) | AVATR HK About page states Changan holds 40.99%, CATL holds 14.1%, and Huawei is a strategic partner mainly providing intelligent components. | Official AVATR regional site | Page accessed May 26, 2026 | AVATR Hong Kong about page |
| AVATR 11 interior color options | Reviewed configuration page lists NAPPA grey, NAPPA red, and Misty purple / Cotton white as public interior color labels. | Official OEM configuration page; option availability still trim/market/VIN scoped | Reviewed Jun 2, 2026 | AVATR official configuration page |
| AVATR 11 interior material naming boundary | The same official configuration page includes a note that the Suede roof on the Cotton white interior option is faux suede leather; public sources do not provide a full surface-by-surface material map. | Official OEM configuration footnote plus explicit public-data limitation | Reviewed Jun 2, 2026 | AVATR official configuration page |
| AVATR 11 ambient-lighting boundary | Regional AVATR 11 pages reference 256-color ambient lighting; this is a cabin feature signal, not a substitute for upholstery color confirmation. | Official AVATR regional product page | Reviewed Jun 2, 2026 | AVATR Singapore model page |
| AVATR 11 seating layout and 4-seat VIP package boundary | Current official configuration table lists 5-seat mainstream rows, 4-seat Royal Edition, and a 4-seat VIP package with independent rear seats, rear seatback electric adjustment, rear 50W wireless charging, HALO interactive screen, rear privacy glass, dynamic flowing ambient lighting, UV sterilization in cabin, and microfiber suede. | Official OEM configuration page; package availability remains trim/order/VIN scoped | Extracted Jun 2, 2026 | AVATR official configuration page |
| AVATR 11 cockpit electronics and comfort-feature scope | Official configuration table lists Meridian audio with 2016W amplifier and 7.1.4 speaker setup, HarmonyOS, 15.6-inch central screen, 10.25-inch touchscreen, HALO interactive screen, DMS camera, Face ID, gesture control, OTA, front/rear seat heating/ventilation/massage rows, dual-zone AC, heat pump AC, AQS purification, PM2.5 filter, and intelligent fragrance system. | Official OEM configuration page; actual delivered mix must be confirmed by trim, market, software version, and VIN | Extracted Jun 2, 2026 | AVATR official configuration page |
| AVATR 11 interior order-date hardware drift | Official note 10 says orders on May 16, 2026 or later receive a fixed open center console cup holder as standard, while vehicles ordered before May 16, 2026 continue with the original configuration. | Official OEM configuration note | Note effective May 16, 2026; extracted Jun 2, 2026 | AVATR official configuration page notes |
| AVATR joint-development statement (Nov 15, 2021) | Official AVATR news states AVATR 11 is jointly developed by Changan Automobile, Huawei, and CATL. | Official OEM release | Published Nov 15, 2021; accessed May 26, 2026 | AVATR official news (Nov 15, 2021) |
| Hong Kong local operator and governing-law boundary | AVATR HK terms identify Evolve New Energy Motors Company Limited as platform operator and state governing-law/jurisdiction terms under Hong Kong law. | Official AVATR regional legal page | Page accessed May 26, 2026 | AVATR Hong Kong terms and conditions |
| Hong Kong warranty-certificate market scope signal | AVATR HK warranty certificate PDF identifies local authorized distributor context and includes market-scoped policy wording (e.g., prior written approval requirement before outside-HK use). | Official AVATR regional warranty document | PDF link accessed May 26, 2026 | AVATR Hong Kong warranty certificate PDF |
| Singapore local operator legal-entity signal | AVATR SG terms identify Premium DPL Premium Automobiles Pte. Ltd. as site/service operator. | Official AVATR regional pages | Pages accessed May 26, 2026 | AVATR Singapore terms page |
| Singapore roadside-assistance regional scope signal | AVATR SG services page states 24-hour roadside assistance language scoped to Singapore. | Official AVATR regional page | Page accessed May 26, 2026 | AVATR Singapore services page |
| China assisted-driving responsibility baseline (MIIT) | MIIT 2021 access guidance requires production enterprises to assume quality/safety responsibility and to inform users about driver responsibility and operating conditions for assisted-driving functions. | Primary regulator policy guidance | Published Jul 30, 2021; accessed May 26, 2026 | MIIT intelligent connected vehicle access opinion (2021) |
| US importer-of-record duty liability anchor | 19 CFR 141.1 states the importer of record is liable for any duties and taxes due on the merchandise. | Primary regulatory text | CFR page accessed May 26, 2026 | 19 CFR 141.1 (Who may make entry) |
| AVATR channel expansion milestone (2023) | Official conference note: >240 channel contacts in 90 cities, with >350 planned by end-2023 | Official OEM release | Published Jul 21, 2023 | AVATR official news |
| AVATR delivery and transaction-price signal (2023) | Official financing announcement reports 12,000 delivered units and average transaction value around RMB 360,000 | Official OEM release | Published Aug 30, 2023 | AVATR official news |
| China NEV purchase-tax window (2024-2027) | 2024-2025: exemption with max RMB 30,000 per NEV passenger car; 2026-2027: half levy with max RMB 15,000 tax reduction per car | Primary policy announcement | Published Jun 19, 2023; accessed May 9, 2026 | MOF + SAT + MIIT Announcement 2023 No.10 |
| 2026-2027 REEV technical eligibility for tax reduction | For PHEV/REEV passenger cars: conditional equivalent all-electric range >=100 km and fuel/electricity threshold checks under 2025 No.24; noncompliant models can be removed from the tax-reduction directory | Primary policy announcement | Published Oct 9, 2025; accessed May 9, 2026 | MIIT + MOF + SAT Announcement 2025 No.24 |
| 2026-2027 REEV ratio thresholds (detailed) | Fuel-consumption ratio in charge-sustaining test: <70% (<2510 kg) or <75% (>=2510 kg) vs GB 19578-2024 limit; electricity-consumption ratio in charge-depleting test: <140% (<2510 kg) or <145% (>=2510 kg) vs GB 36980.1-2025 limit | Primary policy announcement | Published Oct 9, 2025; accessed May 9, 2026 | MIIT + MOF + SAT Announcement 2025 No.24 |
| 2026 directory cutover and removal rule (tax reduction) | From Jan 1, 2026, listed models must meet the new requirements; non-compliant models are removed from the reduction directory. For models targeting 2026 Issue 1, application deadline was Dec 12, 2025. | Primary policy announcement | Published Oct 9, 2025; accessed May 9, 2026 | MIIT + MOF + SAT Announcement 2025 No.24 |
| Current AVATR 11 configuration page snapshot | Nationwide suggested retail price shown at RMB 289,900-429,900; EV + REEV entries listed together; CLTC overall range shown up to 1065 km | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| Current AVATR 11 trim-specific acceleration listing | Current configuration table lists 0-100 km/h by trim: 6.9 s (Max REEV), 6.5 s (Max EV), and 3.9 s (Ultra EV AWD and related variants) | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| Current AVATR 11 trim-level mass and battery split | Official configuration snapshot shows curb weight 2240-2410 kg and battery capacity split of 39.05 kWh (Max REEV) vs 116.79 kWh (EV trims) | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| Current AVATR 11 charging-window split by powertrain | 0-80% SOC super charging: 35 min (EV trims). 30-80% SOC super charging: 15 min (Max REEV), 25 min (EV trims). | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| Current AVATR 11 ADAS wording boundary on official page | Same official page currently shows ADS 4 in top-level model cards while configuration table rows list ADS 3 lidar version for AVATR 11 trims | Official OEM page snapshot | Accessed May 9, 2026 | AVATR official configuration page |
| AVATR official feature-delivery caveats (OTA and scope) | Official notes state some intelligent-driving functions require future OTA activation, NCA city routes are not available on all roads/cities, ADS advanced package is sold separately, and system capability does not replace driver control. | Official OEM page note | Accessed May 18, 2026 | AVATR official configuration page notes |
| AVATR order-date configuration drift example | Official note states orders on/after May 16, 2026 switched front-row cup holder to standard configuration; page disclaimer states delivered vehicle prevails and technical parameters can change. | Official OEM page note | Note effective May 16, 2026; accessed May 18, 2026 | AVATR official configuration page notes + disclaimer |
| US automation-level responsibility boundary | NHTSA states Level 2 still requires the human driver to supervise and remain engaged; Levels 3-5 are not broadly available for consumer purchase in current market context. | Official regulator guidance | Accessed May 18, 2026 | NHTSA levels of automation |
| US ADAS crash-reporting scope update | NHTSA notes the third amendment to Standing General Order took effect Jun 16, 2025 and expanded Level 2 reporting criteria while warning that database records are not a simple cross-brand safety ranking. | Official regulator guidance | Third amendment effective Jun 16, 2025; page accessed May 18, 2026 | NHTSA automated-vehicle safety action page |
| EU mandatory ADAS/safety baseline for all new vehicles | European Commission states General Safety Regulation systems apply to all new vehicles sold in EU from Jul 7, 2024 (e.g., intelligent speed assistance, drowsiness/distraction warning, event data recorder, lane-keeping and automated braking for cars/vans). | Primary EU regulator portal | GSR entry into force Jul 7, 2024; page accessed May 18, 2026 | European Commission vehicle safety page |
| EU type-approval technical information template boundary | Implementing Regulation (EU) 2024/1721 sets templates for technical information and test-result communication under Regulation (EU) 2019/2144; regulation applies from Jul 7, 2026. | Primary EU law text | Published Jun 21, 2024; applies Jul 7, 2026; accessed May 18, 2026 | EUR-Lex Regulation (EU) 2024/1721 |
| AVATR acceleration-data condition disclaimer | Official AVATR configuration footnote states performance data is reference-only and may be affected by weather, road condition, battery SOC, load, and tires | Official OEM page note | Accessed May 9, 2026 | AVATR official configuration page footnote |
| Current AVATR 11 dimensional anchor | Length/width/height 4895/1970/1601 mm; wheelbase 2975 mm | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| AVATR 11 mirror-span publication status | Not published on the public AVATR pages reviewed on May 9, 2026; only body width is shown | Official OEM page snapshot | Accessed May 14, 2026 | AVATR official configuration page |
| AVATR 11 ground-clearance publication boundary (global pages) | Reviewed AVATR global pages (/en/11 and /en/configuration) did not show an explicit ground-clearance field; they publish L/W/H and wheelbase anchors | Official OEM page snapshot | Accessed May 25, 2026 | AVATR official page + configuration page |
| AVATR 11 minimum ground clearance (market owner manual) | AVATR SG owner manual geometry table lists minimum ground clearance 155 mm, with no-load approach/departure 18°/21° and no-load longitudinal passing angle 13°/12° | Official market owner-manual document | Document file dated Jul 24, 2025; accessed May 25, 2026 | AVATR SG owner manual (PDF) |
| AVATR SG model-page publication boundary for ground clearance | Reviewed AVATR SG model page publishes L/W/H, wheelbase, and 0-100 data but does not expose a dedicated ground-clearance field | Official market product-page snapshot | Accessed May 25, 2026 | AVATR Singapore official model page |
| US public-road speed-hump geometry reference | FHWA ePrimer describes a typical speed hump as 3-4 inches high and 12 feet long; single hump crossing speeds commonly fall in the 15-20 mph range | Official US DOT guidance | Accessed May 25, 2026 | FHWA Traffic Calming ePrimer (Module 3, Part 2) |
| UK statutory road-hump envelope | Highways (Road Humps) Regulations 1999 set road-hump height at 25-100 mm and minimum hump length at 900 mm | Primary legislation text | In force Apr 28, 1999; accessed May 25, 2026 | UK Statutory Instrument 1999 No. 1025 |
| AVATR 11 trim-by-trim dynamic ride-height dataset | No reliable public dataset was identified for export-market trim-by-trim dynamic ride-height variance by wheel/tire/suspension setup | Explicit evidence gap | Reviewed May 25, 2026 | Insufficient reliable public dataset |
| Launch campaign warranty statement (time-bounded) | Aug 24, 2023 article states first owners could get lifetime warranty for motor/battery/electronic control when ordering by Dec 31, 2023 | Official OEM release | Published Aug 24, 2023; accessed May 14, 2026 | AVATR official news (Harmony Edition launch) |
| AVATR policy-page baseline warranty terms | Vehicle warranty 5 years/120,000 km; traction battery + drive motor + motor controller 8 years/160,000 km; smart home charging pile and installation 2 years | Official OEM policy page | Accessed May 18, 2026 | AVATR official terms page |
| AVATR terms-page lifetime-rule boundary details | Terms-page text includes mainland-China scope, pre-Dec 31, 2022 deposit-condition wording, and ownership-change termination clauses for lifetime rights; fallback baseline 5y/120k and 8y/160k remains listed when lifetime rights end | Official OEM policy page | Accessed May 18, 2026 | AVATR official terms page |
| China household auto three-guarantee baseline | Order No.43 (effective Jan 1, 2022): minimum three-guarantee validity >=2 years or 50,000 km, minimum warranty period >=3 years or 60,000 km, plus repair-delay replacement/transport-compensation obligations and new-energy safety-failure clauses | Primary regulator text (repost) | Effective Jan 1, 2022; accessed May 18, 2026 | Beijing AMR repost of SAMR Order No.43 (official text) |
| US service-contract vs warranty legal boundary | FTC/CFPB guidance distinguishes manufacturer warranty from optional service contracts; service contracts can have separate price, exclusions, and deductibles. 15 U.S.C. §2308 limits implied-warranty disclaimers when written warranty/service contract is provided in covered timing conditions | Official consumer guidance + federal statute | FTC/CFPB pages accessed May 18, 2026 | FTC + CFPB + US Code |
| CFPB definition boundary (manufacturer warranty vs service contract) | CFPB states manufacturer warranty is typically included in vehicle price, while extended vehicle warranty/service contract is usually optional and sold separately | Official consumer regulator guidance | CFPB page accessed May 18, 2026 | US CFPB Ask CFPB |
| Magnuson-Moss implied-warranty restriction anchor | 15 U.S.C. §2308 restricts disclaiming implied warranties when a written warranty is made or a service contract is entered at sale or within 90 days | Primary statute text | GovInfo PDF accessed May 18, 2026 | US Code (GovInfo) |
| EU legal-guarantee baseline for consumer sales | EU portal states legal guarantee generally covers new and second-hand goods for at least 2 years; for second-hand goods, a shorter period may be agreed but not less than 1 year | Official EU consumer portal | EU page last checked Apr 28, 2026; accessed May 18, 2026 | EU Your Europe portal |
| AVATR cross-border warranty-claim dataset availability | No reliable public per-market dataset was identified for AVATR 11 claim frequency, payout speed, or denied-claim ratios across importer channels | Explicit evidence gap | Reviewed May 18, 2026 | Insufficient reliable public dataset |
| AVATR official disclaimer on delivered-vehicle precedence | AVATR /en/11 states page videos/posters do not fully represent real-vehicle configuration and technical parameters may change; delivered vehicle from sales store prevails | Official OEM page disclaimer | Accessed May 9, 2026 | AVATR official AVATR 11 page disclaimer |
| Owner-manual dimensional wording (secondary market source) | Singapore AVATR 11 owner manual table shows width 1970 mm as "excluding the side mirrors" and lists length 4880 mm, wheelbase 2975 mm | Market manual (secondary evidence) | Document file dated Jul 24, 2025; accessed May 9, 2026 | AVATR Singapore owner manual PDF |
| US National Network width cap reference | 23 CFR 658.15 sets a width limitation of 102 inches (approx. 2.6 m) on the National Network (with specific statutory exceptions such as Hawaii 108-inch provision) | Official regulator guidance | Displaying title 23 up to date as of 5/01/2026; accessed May 9, 2026 | 23 CFR 658.15 |
| Maersk dry-container door-width reference (20' / 40') | Maersk dry equipment sheet lists door openings width at 2350 mm (20' standard) and 2340 mm (40' standard / 40' high), with explicit note that dimensions vary within container series | Carrier equipment specification | PDF accessed May 9, 2026 | Maersk dry equipment specifications PDF |
| US transport-width measurement counterexample | 23 CFR 658.16 excludes rear-view mirrors, turn-signal lamps, handholds, splash/spray suppression devices, and load-induced tire bulge from width determinations for commercial motor vehicles | Official regulator guidance | Displaying title 23 up to date as of 5/06/2026; accessed May 9, 2026 | 23 CFR 658.16 |
| EU transport-width reference | EUR-Lex implementing regulation text references a maximum vehicle width of 2.55 m for an authorized vehicle | Primary EU law text | Consolidated text accessed May 5, 2026 | EUR-Lex Implementing Regulation (EU) 2021/1328 |
| AVATR 11 launch dimensional anchor | Length/width/height 4880/1970/1601 mm; wheelbase 2975 mm | Official OEM launch context | Published Mar 14, 2022; accessed May 9, 2026 | AVATR official launch announcement |
| Mile-to-meter exact conversion anchor | NIST conversion table lists 1 mile (statute) = 1609.344 meters | Official standards body conversion table | NIST page updated Feb 3, 2026; accessed Apr 28, 2026 | NIST revised unit conversion factors |
| Regulatory unit-conversion convention for speed comparison | 40 CFR 1066.20 lists conversion conventions including 1 mile = 1609.344 m when aligning km/h and mph-based requirements | Primary regulation text | CFR edition posted Nov 28, 2023; accessed Apr 28, 2026 | US eCFR / GovInfo 40 CFR Part 1066 |
| 0-60 protocol comparability counterexample | Tesla Model Y official page lists 0-60 mph values and includes a "with rollout subtracted" note | Official OEM page note | Accessed Apr 28, 2026 | Tesla Model Y official page |
| Model Y China reference anchor | Up to 750 km (CLTC); 0-100 km/h in 4.3 s. Official page supports direct online ordering flow. | Official OEM page snapshot | Accessed Apr 27, 2026 | Tesla China model page |
| NIO ES6 benchmark pricing anchor | Starts RMB 338,000 (or RMB 268,000 with BaaS) | Official OEM release | Published May 16, 2025 | NIO official news release |
| US tariff policy gate for China-made EVs | Section 301 additional duty at 100% for listed EV HTS codes, effective Sep 27, 2024 | Primary regulation | Published Sep 18, 2024; effective Sep 27, 2024 | USTR Federal Register 89 FR 76581 |
| US import eligibility gate (NHTSA) | Under-25-year nonconforming vehicles cannot be permanently imported for road use unless entering approved compliance path; RI imports are bonded at 150% and must be brought into compliance within 120 days | Official regulator guidance | Accessed Apr 27, 2026 | NHTSA Importation and Certification FAQs |
| US FMVSS age-based exemption boundary (HS-7) | HS-7 Box 1 applies only when vehicle is 25 years old or older; a 2023 model-year reaches this boundary in 2048 | Official regulator declaration form | Accessed Apr 27, 2026 | NHTSA HS-7 Declaration form |
| US EPA import-form gate | EPA requires declaration forms for imported vehicles and engines, including Form 3520-1 for highway vehicles and ICI workflow where applicable | Official regulator forms guidance | Accessed Apr 27, 2026 | US EPA importing vehicles and engines forms |
| US EPA emissions age-based exemption boundary | EPA guidance states a vehicle at least 21 years old is generally exempt from emissions requirements if in original configuration; a 2023 model-year reaches this boundary in 2044 | Official regulator guidance | Page last updated Dec 9, 2025; accessed Apr 27, 2026 | US EPA importing vehicles guidance |
| US NEVI connector baseline for funded DC fast charging | Federal Register final rule states each charging port has to include at least one permanently attached CCS Type 1 connector and charge CCS-compliant vehicles | Primary regulation | Published Feb 28, 2023 | US Federal Register 2023-03500 |
| US NEVI minimum service-level baseline | 23 CFR 680.106/680.116 requires NEVI corridor stations to support >=4 network-connected DCFC ports, corridor-port power delivery up to 150 kW on request, and average annual uptime >97% | Primary regulation | eCFR title display up to Apr 24, 2026; accessed Apr 28, 2026 | US eCFR 23 CFR 680.106 and 680.116 |
| EU anti-subsidy duty gate (China-made BEVs) | Tesla 7.8%, BYD 17.0%, Geely 18.8%, SAIC 35.3%, others 20.7%-35.3%; on top of existing 10% import duty; valid 5 years | Primary regulation communication | Published Oct 29, 2024; effective Oct 30, 2024 | European Commission IP/24/5589 |
| EU undertaking exemption mechanism added after Feb 2026 review | Regulation (EU) 2026/330 amends 2024/2754 and adds Article 2a/2b: eligible imports can be exempt from countervailing duty only when undertaking-acceptance and customs-document conditions are met | Primary regulation | Published Feb 10, 2026; accessed May 9, 2026 | EUR-Lex Regulation (EU) 2026/330 |
| Accepted undertaking case details (current public decision) | Decision (EU) 2026/328 accepts undertaking for Volkswagen (Anhui) + SEAT, covering CUPRA Tavascan with TARIC additional code 89FZ | Primary decision text | Published Feb 10, 2026; accessed May 9, 2026 | EUR-Lex Decision (EU) 2026/328 |
| EU AFIR charging connector and pool requirement | From Apr 13, 2024, public DC recharging points must provide Combo 2 connectors; TEN-T light-duty pools require >=400 kW by Dec 31, 2025 and >=600 kW with at least two points >=150 kW by Dec 31, 2027 | Primary regulation | Consolidated text accessed Apr 27, 2026 | EUR-Lex Regulation (EU) 2023/1804 |
| Charging availability context (global + China) | IEA 2026 states global public charging points passed 7 million by end-2025; China had over 4.7 million public points and represented more than 65% of global stock | International agency report | Report year 2026 (end-2025 data points) | IEA Global EV Outlook 2026 |
| Charging structure context (Europe) | IEA 2026 notes Europe public charging points increased about 20% in 2025, with most growth in the Netherlands and Germany and fast-charger stock concentrated in Germany, France, and the UK | International agency report | Report year 2026 (2025 regional update) | IEA Global EV Outlook 2026 |
| China charging-facility latest official snapshot (end-Feb 2026) | State Council portal reports 21.01 million total charging facilities in China by end-Feb 2026, including 4.834 million public chargers and 16.176 million private chargers | Official government portal statistics | Published Mar 21, 2026; accessed May 26, 2026 | The State Council of the PRC (statistics release) |
| FX planning reference | USD/CNY noon buying rate listed as 6.8005 for May 8 in the May 11, 2026 H.10 weekly release | Official central bank release | Release date May 11, 2026 | Federal Reserve H.10 release |
| Range-method boundary for planning | EPA explains adjusted range methodology and notes common 0.7 label adjustment workflow | Official regulator methodology | EPA page reviewed Jul 18, 2025 | US EPA fuel economy and EV range testing |
| US import compliance baseline | NHTSA FMVSS certification labeling and EPA emissions compliance checks are required for imports | Official regulator guidance | NHTSA/EPA pages accessed Apr 18, 2026 | NHTSA + US EPA import guidance |
| ADAS feature availability boundary | Tesla states capability and availability can vary by market/region, vehicle and software version | Official OEM support policy | Accessed Apr 17, 2026 | Tesla Autopilot support |
| AVATR overseas rollout and market-specific note | Official overseas page states AVATR began overseas business rollout in 2024, lists regional overseas contacts, and includes a market-specific 190 kW AVATR 11/07 note for Nepal and Sri Lanka | Official OEM page statement | Accessed May 9, 2026 | AVATR official overseas page |
| Market | Effective date | Hard gate | Decision implication | Primary source |
|---|---|---|---|---|
| China domestic purchase-tax window (passenger NEV) | 2024-2027 by purchase date | 2024-2025: full purchase-tax exemption with RMB 30,000 cap per vehicle; 2026-2027: half levy with RMB 15,000 tax-reduction cap per vehicle | Domestic transaction timing can materially change total cost even when MSRP stays similar. | MOF + SAT + MIIT Announcement 2023 No.10 |
| China 2026-2027 REEV eligibility gate (tax reduction) | From Jan 1, 2026 | PHEV/REEV passenger cars need equivalent all-electric range >=100 km; fuel-consumption ratio <70% (<2510 kg) or <75% (>=2510 kg); electricity-consumption ratio <140% (<2510 kg) or <145% (>=2510 kg) | Do not assume all REEV trims keep equal tax treatment after Jan 1, 2026. Threshold failure can remove a model from the active tax-reduction directory. | MIIT + MOF + SAT Announcement 2025 No.24 |
| United States | Sep 27, 2024 | Section 301 additional duty for EV HS codes (including 8703.80.00) raised to 100% | Can dominate landed cost; this is only one gate in the US execution path. | USTR Federal Register 89 FR 76581 + NHTSA/EPA import guidance |
| United States (compliance path) | Always applies for modern vehicle imports | For nonconforming vehicles under 25 years old, permanent road-use import generally requires Registered Importer pathway and bond-backed conformity process | US legal road registration can fail even if tariff-inclusive budget is sufficient. | NHTSA Importation and Certification FAQs + US EPA import forms |
| United States (age-based FMVSS exemption boundary) | 25-year threshold by model year | HS-7 declaration Box 1 applies only when a vehicle is 25 years old or older | For a 2023 model-year AVATR 11, this boundary is reached in 2048, so it does not de-risk near-term import plans. | NHTSA HS-7 Declaration form |
| United States (age-based EPA emissions boundary) | 21-year threshold by model year | EPA states a vehicle at least 21 years old is generally exempt from emissions requirements if in original configuration | For a 2023 model-year AVATR 11, this boundary is reached in 2044, so normal EPA import declarations still apply in near-term execution. | US EPA importing vehicles guidance |
| European Union | Oct 30, 2024 | Definitive anti-subsidy duties on China-made BEVs: Tesla 7.8%, BYD 17.0%, Geely 18.8%, SAIC 35.3%, others 20.7%-35.3% | Policy-driven variance across brands can materially change procurement ranking; EC communication notes these are on top of the existing 10% import duty. | European Commission press release IP/24/5589 |
| European Union (undertaking exception path) | From Feb 10, 2026 | Amended Regulation (EU) 2024/2754 adds Article 2a/2b: eligible imports can be exempt from countervailing duty if they are manufactured, shipped, and invoiced by an undertaking-accepted company and customs documents match undertaking conditions | EU duty modeling now needs exporter/model-level undertaking verification. Current accepted case is model-specific (CUPRA Tavascan) and cannot be auto-applied to AVATR 11. | EUR-Lex Regulation (EU) 2026/330 + Decision (EU) 2026/328 |
| Other markets (generic import path) | Case-by-case | No unified global duty/homologation dataset covers all channels with one portable formula | Treat landed-cost uplift as scenario range, then verify with local broker + regulator before deposit. | Insufficient reliable unified public dataset |
| Route / market | Regulatory or data fact | What to verify before deposit | Counterexample / limit |
|---|---|---|---|
| European Union public DC corridor planning | AFIR requires Combo 2 (EN 62196-3) on publicly accessible DC recharging points. TEN-T light-duty pools move from >=400 kW by Dec 31, 2025 to >=600 kW by Dec 31, 2027, with at least two points >=150 kW by 2027. | Confirm the delivered AVATR 11 connector/adaptor path is contractually compatible with Combo 2 and warranty-supported. | A route can show high charger density but still fail if your connector path is not legally/technically usable. |
| United States NEVI-funded fast-charging route planning | 23 CFR 680 requires NEVI corridor stations to have at least four network-connected DCFC ports, each corridor-serving port able to deliver up to 150 kW on request, and each port to maintain average annual uptime greater than 97%; DC ports must include a permanently attached CCS Type 1 connector. | If relying on NEVI corridors, verify connector compatibility, adapter certification, route-level uptime disclosures, and site-level simultaneous power delivery behavior before procurement. | Budget can pass tariff math while daily route usability still fails when port availability/power-sharing reality is not validated. |
| Other markets / mixed-network planning | No unified global public dataset provides one reliable cross-country connector + compliance matrix for AVATR 11. | Build destination-specific connector inventory and legal-adapter checklist before shipping. | Using a global average charging assumption can hide local incompatibility and queue bottlenecks. |
| Date | Verified fact | How to use in decision | Boundary |
|---|---|---|---|
| Jul 21, 2023 | AVATR stated over 240 channel contacts across 90 cities and targeted over 350 by end-2023. | Supports domestic channel-maturity signal for 2023 context. | Does not prove overseas homologation or after-sales readiness in your target country. |
| Aug 30, 2023 | AVATR announced 12,000 delivered units and average transaction value around RMB 360,000. | Indicates non-trivial early delivery scale and premium positioning in domestic market. | Delivery scale is not equivalent to export compliance eligibility or local service-network depth. |
| Apr 18, 2026 | Current AVATR 11 official configuration page shows EV and REEV entries under one catalog. | Useful for current execution reference and trim-range checks. | Cannot be merged directly into 2023 baseline quote logic without resetting assumptions. |
| 2024 | AVATR official overseas page states overseas business rollout started in 2024 and shows a regional contact matrix (Europe/Middle East/APAC/Latin America/Africa). | Indicates active international channel-building momentum beyond 2023 domestic milestones. | Expansion messaging is not equivalent to destination-country homologation completion or after-sales service certainty. |
| Apr 28, 2026 | AVATR overseas page includes a market-specific note: AVATR 11/07 190 kW motor context for Nepal and Sri Lanka. | Confirms that delivered configuration can vary by market and should be contract-verified. | A market-specific power note cannot be generalized to all overseas AVATR 11 deliveries. |
| Concept | Valid when | Invalid when | Minimum action |
|---|---|---|---|
| 0-60 mph derived value vs official OEM performance disclosure | You treat 0-60 output as a planning conversion from an official 0-100 source and keep test-protocol caveats visible. | You present converted values as official AVATR-certified 0-60 mph performance, or compare them directly to sources using different protocols (for example rollout-subtracted figures). | Label converted 0-60 figures as derived estimates and require VIN-level test evidence for contract-stage decisions. |
| 2023 AVATR 11 baseline vs newer AVATR 11 pages | You are evaluating 2023-intent pricing/spec context for canonical keyword matching. | You directly mix newer AVATR 11 EV/REEV catalog specs (for example up to 1065 km CLTC overall range or 3.9 s AWD 0-100 listings) into 2023 single-motor quote logic. | Freeze one spec baseline per quote and document source date/trim before comparison. |
| CLTC numbers vs real-world planning | CLTC is used as within-cycle comparison anchor among China-listed trims. | CLTC is treated as guaranteed cross-market real-world range without duty-cycle adjustments. | Run at least one stress band and local-route check before purchase decision. |
| ADAS package name vs delivered capability | You treat ADS/Autopilot labels as product-family names only. | You assume identical feature unlock across all jurisdictions and map domains. | Require written feature-delivery scope by VIN/software/market in contract. |
| Smart-driving marketing label vs automation-responsibility level | You keep destination legal duties explicit and treat Level 2 systems as driver-supervised assistance. | You treat marketing labels as proof of self-driving responsibility transfer or hands-off legal operation by default. | Before payment, document driver-responsibility scope and local legal-operation boundary in buyer training and contract annexes. |
| Tariff feasibility vs legal import feasibility | You treat tariff, homologation, and registration as separate go/no-go layers. | You conclude “importable” only from MSRP plus duty math without checking regulator path requirements. | Complete regulator-path checklist before deposit (NHTSA + EPA in US route) and explicitly note that a 2023 model does not meet EPA 21-year (2044) or FMVSS 25-year (2048) age thresholds today. |
| Domestic channel traction vs destination-country execution certainty | You use delivery/channel milestones as confidence context for brand operational momentum. | You treat domestic delivery scale as proof of destination-country homologation, connector interoperability, or after-sales execution readiness. | Separate brand traction checks from market-specific compliance/service checks in your decision memo. |
| China purchase-tax benefit vs REEV trim eligibility after 2025 | You bind cost assumptions to purchase date and verify the exact model is in the active tax-reduction directory. | You apply 2024-2025 full-exemption logic to 2026-2027 purchases or assume all AVATR 11 REEV trims keep tax eligibility unchanged. | Check purchase date + latest tax-reduction directory membership immediately before signing and payment. |
| EU duty rate card vs undertaking-exemption pathway | You first apply the baseline duty table and then separately test whether the specific exporter/model is covered by an accepted undertaking with valid customs-document chain. | You apply one blanket duty or one blanket exemption to all China-made BEV imports without checking Decision-level undertaking scope. | Ask for exporter/model undertaking proof and matched customs documents before final EU landed-cost commitment. |
| Item | Status | Why | Minimum executable path |
|---|---|---|---|
| Official AVATR 11 mirror-to-mirror width value | Insufficient public data | Public AVATR global pages and reviewed official releases provide body width, but not a verified mirror-span measurement. | Treat mirror allowance as an explicit assumption and require VIN-level physical measurement before garage or transport commitment. |
| Official AVATR 11 0-60 mph certification value | Insufficient public data | Official AVATR release and configuration sources currently publish 0-100 km/h metrics, not an official 0-60 mph figure. | Do not publish a hard 0-60 claim as official; request OEM/distributor test documentation if 0-60 is contract-critical. |
| Unified global import + compliance uplift percentage | Insufficient public data | Public data is fragmented by jurisdiction, port route, insurance, tax class, and homologation path. | Build market-specific worksheet (duty, VAT/sales tax, logistics, compliance fees) before final quote. |
| AVATR 11 market-by-market ADAS feature unlock matrix | Insufficient public data | No single official public matrix covers all overseas legal/map/software states in one place. | Get importer + OEM written declaration for target country and software branch. |
| AVATR/Changan/Huawei role-allocation matrix by destination market | Insufficient public data | Public sources identify ownership/partner signals, but no unified official public matrix allocates seller/importer/warranty accountability for each market and channel. | Before deposit, require a signed role matrix with legal-entity names and jurisdiction scope for seller, importer-of-record, customs declarant, and warranty-service entity. |
| AVATR 11 Harmony ecosystem app/service availability matrix by region | Insufficient public data | Official updates confirm Harmony-related OTA rollout, but no unified official public matrix was identified for market-level app/service availability and ongoing support SLA. | Before deposit, require a signed region-specific feature matrix (apps, connected services, OTA cadence, fallback behavior) mapped to VIN and software branch. |
| AVATR 11 ADS advanced package regional pricing + activation SLA | Insufficient public data | Official notes indicate ADS advanced package is sold separately, but no unified public matrix was identified for destination-market package pricing, activation timing, and post-sale update SLA. | Require signed package quotation (price, activation timeline, update cadence, refund condition) tied to VIN and destination market before deposit. |
| Resale liquidity for non-China imported AVATR 11 | Insufficient public data | Secondary-market transactions are sparse and non-standardized in many target markets. | Model conservative residual value and require backup exit channel in sourcing contract. |
| Country-level AVATR 11 homologation + after-sales coverage map | Insufficient public data | No single official public page provides complete market-by-market homologation progress and after-sales readiness. | Request target-country importer confirmation with service-network and compliance scope in writing. |
| AVATR 11 VIN-level connector + adapter compatibility matrix (by destination market) | Insufficient public data | No single official public source publishes a complete cross-market connector and certified-adapter matrix for delivered VIN variants. | Require connector specification and adapter/warranty confirmation in signed procurement documents before shipment. |
| AVATR 11 cross-border warranty transferability matrix | Insufficient public data | Public sources show campaign offers and baseline terms, but do not provide one official matrix covering region transfer, second-owner status, and importer-channel edge cases. | Before payment, require seller/importer written confirmation of warranty scope by VIN, owner status, and service region. |
| Public VIN-level proof of AVATR 11 REEV tax-eligibility under 2026-2027 thresholds | Insufficient public data | Public sources provide policy thresholds but not one unified VIN-to-directory eligibility map for each active AVATR 11 REEV trim. | Before contract signing, verify the exact model code in the latest tax-reduction directory and archive the screenshot/date in deal records. |
| Public proof that AVATR 11 is covered by EU undertaking exemption path | Insufficient public data | Public EU documents confirm an accepted undertaking case for Volkswagen (Anhui) + SEAT and CUPRA Tavascan, but no public document in this review confirms AVATR 11 is included in an accepted undertaking scope. | Treat AVATR 11 as non-exempt by default until exporter/model-specific undertaking coverage is confirmed in writing with customs-document requirements. |
| Model / context | 0-100 anchor | Source context | Boundary note |
|---|---|---|---|
| AVATR 11 (2023 single-motor launch) | 0-100 km/h in 6.0 s | AVATR official release (Mar 24, 2023) | Launch claim from official release context; not a universal all-trim/all-condition value. |
| Tesla Model Y (China page snapshot) | 0-100 km/h in 4.3 s | Tesla China model page snapshot (accessed Apr 18, 2026) | Configuration, software, and market package can differ by order region and date. |
| Current AVATR 11 mixed EV/REEV catalog (Apr 2026 snapshot) | 0-100 listings include 6.9 s (REEV), 6.5 s (EV), and 3.9 s (AWD) | AVATR official configuration page snapshot | Use as trim-specific counterexample only. Do not treat this as a universal AVATR 11 0-100 value across model years and powertrains. |
| Model | Price anchor | Range anchor | ADAS positioning | Decision note |
|---|---|---|---|---|
| AVATR 11 (2023 baseline) | RMB 300k-390k | 600-730 km (CLTC) | ADS 2.0 launch messaging (Aug 2023 official release) | Use as canonical 2023 anchor. Do not mix with later model-year/powertrain pages without boundary checks. |
| AVATR 11 current configuration page (Apr 2026 snapshot) | RMB 289,900-429,900 | EV + REEV listed together; REEV CLTC overall range up to 1065 km; EV CLTC range shown at 815/760 km by listed trims | Same official page currently shows ADS 4 marketing headers and ADS 3 lidar-version table entries; no single export-delivery matrix is published | Counterexample: the table lists 0-100 values of 6.9 / 6.5 / 3.9 s plus 0-80 and 30-80 charging windows by powertrain, so trim/date scope must be frozen before quoting. |
| Tesla Model Y (Tesla China page snapshot) | N/A in static snapshot (re-check live configurator) | Up to 750 km (CLTC), 0-100 km/h in 4.3 s | Tesla support states capability/availability vary by market, model, and software | Service-network benchmark candidate, but final quote must be refreshed at order time. |
| NIO ES6 (May 2025 update) | Starts RMB 338k (or RMB 268k with BaaS) | N/A (range number not provided in cited launch release) | Upgrade claim stated; detailed matrix not fully enumerated in source | Useful for upfront-cash comparison due BaaS option; verify current packages before contract. |
High-impact + high-probability risks should be controlled before deposit. Treat these as go/no-go gates, not post-purchase fixes.
Medium-risk items can be accepted when contract language clearly allocates accountability (feature delivery, service, and cost overruns).
Low-confidence tool outputs should trigger manual advisory, not faster commitment.
| Risk | Impact | Probability | Mitigation |
|---|---|---|---|
| Container-door clearance overconfidence | High | Medium | Run door-width checks with mirror and safety assumptions, then confirm actual assigned container/unit tolerances before booking. |
| Policy and homologation drift | High | Medium | Lock a compliance checklist with your importer before deposit. |
| Underestimated landed cost | High | High | Maintain >=15% contingency over projected landed high estimate before committing. |
| US legal-import dead-end after purchase | High | Medium | For US route, verify NHTSA RI/EPA path eligibility before signing contract or shipping. |
| Age-exemption timeline misread (US route) | High | Medium | Treat EPA 21-year and FMVSS 25-year rules as future-date boundaries (2044/2048 for 2023 model-year), not immediate compliance shortcuts. |
| ADAS feature mismatch by market | Medium | Medium | Contractually list delivered ADAS package and update policy scope. |
| Driver-liability misunderstanding from smart-driving labels | High | Medium | Treat assisted-driving as driver-supervised unless local law explicitly states otherwise; include responsibility and usage-boundary wording in delivery training and purchase documents. |
| Charging friction for public-only users | Medium | High | Model weekly peak/off-peak charging windows before final purchase. |
| Destination connector/interoperability mismatch | High | Medium | Validate connector standard, adapter legality, and warranty coverage with network operators and importer before payment. |
| China purchase-tax assumption drift across policy windows | Medium | Medium | Lock purchase-date assumptions and re-run tax math when timeline crosses from 2025 to 2026. |
| NEVI corridor service-level mismatch vs route plan | Medium | Medium | Verify site-level port count, simultaneous power behavior, and uptime history for your primary route before commitment. |
| Assuming EU duty exemption applies automatically | High | Medium | Treat EU undertaking relief as exporter/model/document-chain specific. Require written proof that the shipped vehicle is within an accepted undertaking scope before payment. |
| Resale liquidity uncertainty | Medium | Medium | Plan hold period >=24 months or include buyback channel in sourcing deal. |
Assumptions: USD 70k budget, home charging, mixed use, medium import readiness, 4-month timeline.
Expected outcome: Usually lands in Strong fit with room for risk buffer and smoother execution path.
Pricing and Scope
Range and Usage
ADAS, Risk, and Process
Read avatr 11 harmony canonical quick answer
Use this anchor to answer harmony intent on the same canonical URL without route splitting.
Read avatr 11 huawei canonical quick answer
Use this anchor to resolve Huawei-collaboration intent on one canonical URL with role boundaries.
Read avatr 11 electric suv canonical quick answer
Use this anchor to answer electric SUV intent on the same canonical URL without route splitting.
Read avatr 11 features canonical quick answer
Use this anchor to resolve feature intent on the same canonical URL with trim/market/software boundaries.
Check avatr 11 interior on the canonical page
Use this anchor to answer interior and interior color intent with public options, selector feedback, material boundaries, and quote-check actions on one URL.
Read avatr 11 extended warranty canonical quick answer
Use this anchor to resolve extended-warranty intent on the same canonical URL with explicit boundary handling.
Read avatr 11 china canonical quick answer
Use this anchor for avatr 11 china intent so route and evidence remain on one canonical URL.
Read avatr 11 dimensions length width height canonical quick answer
Use this anchor for dimensions intent so live fit and launch-boundary data stay on one canonical URL.
Read avatr 11 ground clearance canonical quick answer
Use this anchor for ground-clearance intent so source-scoped value and execution boundaries stay on one canonical URL.
Read avatr 11 2024 canonical quick answer
Use this anchor for avatr 11 2024 intent so all evidence stays on one canonical URL.
Run AVATR 11 Australia import tool
Use this when your next step is Australia-specific tax, duty, and compliance path validation.
Run AVATR 11 Chile landed-cost tool
Use this when your next step is Chile-specific import cost and execution-risk modeling.
Run AVATR 11 Costa Rica landed-cost tool
Use this when your next step is Costa Rica-specific DAI/SC/Ley/IVA modeling and execution-risk checks.
Run AVATR 11 Egypt landed-cost tool
Use this when your next step is Egypt-specific ACI readiness and tariff-line risk modeling.
Run avatr 11 0-60 / 0-100 quick checker
Use the canonical AVATR 11 URL anchor for acceleration intent; do not split into a competing page.
Review avatr 11 0-60 conversion boundary
See method assumptions, applicability limits, and source-backed conversion basis in one section.
Talk to AVATR 11 sourcing team
Move from scenario screening to executable quote validation.
Request AVATR policy and pricing updates
Get current policy-gate and pricing anchor updates from the inquiry team.
Read EV market and comparison briefs
Review adjacent model context before final shortlist decisions.
Compare with 2023 U8 electric car price estimator
Use this page when AVATR vs U8 pricing volatility is part of your shortlist.
Canonical page for 2024 huawei avatr 12
Compare AVATR 11 fit decisions with AVATR 12 model-year price and import-risk boundaries.
Read AVATR 07 vs AVATR 12 decision report
Use this focused compare page when 07/12 is your active shortlist.
Review pre-shipment QC checklist
Validate inspection scope before you lock payment milestones.
Confirm service scope and support options
Use inquiry to confirm available support layers for execution.
Verify operator background and page purpose
Confirm page ownership and decision-support boundaries.
If your tool result is Strong or Conditional, move to quote validation with explicit feature, compliance, and service terms. If Weak, resolve charging and budget boundaries first.
Disclosure: This page is informational planning support, not legal/tax advice. Data points are sourced from public references listed above and can change after publication. Published: August 24, 2023. Last reviewed: Jun 2, 2026 (stage1c interior self-heal: aligned broader interior intent, selector guardrails, and source-backed cabin evidence boundaries). Review cadence: every 6 months, or within 48 hours after major tariff/compliance policy updates.