---
title: "Spec table and per-variation warranty"
url: https://phatdev.net/en/docs/hungphat-laptop/bang-thong-so-bao-hanh
lang: en
updated: 2026-10-20
alternate:
  vi: https://phatdev.net/docs/hungphat-laptop/bang-thong-so-bao-hanh
markdown: https://phatdev.net/en/docs/hungphat-laptop/bang-thong-so-bao-hanh.md
---

# Spec table and per-variation warranty

Part of the doc set: [Hưng Phát Laptop (Theme)](https://phatdev.net/en/docs/hungphat-laptop.md)

> The product page shows a full technical specification table, and the warranty and genuine badge change with each version of the laptop.

On the product detail page (PDP), the theme shows a clean **Technical specifications table** and **dynamic warranty information** for each version of the laptop.

![The specifications area on a product page](https://phatdev.net/docs-img/hungphat-laptop/pdp-specs.png)

## Technical specifications table
The table lists: **CPU, RAM, Storage (SSD), Graphics card (VGA), Display, Camera, Audio, Wi-Fi, Bluetooth, Condition, Warranty**. Where the data comes from:
- **Single-configuration products:** taken from the product's short specifications field.
- **Multi-version products:** taken from the **description of each variation** - whichever version is selected, the table changes to match it.

## Warranty, the "Genuine" badge and SKU - they change with the version
For laptops with several options, when the customer **selects a version**:
- The **Warranty** pill changes to that version's own number of months (for example "Genuine warranty 12 months").
- The **"Chính Hãng"** (Genuine) badge only appears for genuine versions and hides itself for imported units.
- The **SKU** changes to that version's own SKU.

## What do you need to set up?
The table content is pulled automatically from product data - just **fill in the description/variation, the warranty months and the genuine flag** correctly when you create the product, and the theme handles the display.

> Alongside it there is a **per-product FAQ** (frequently asked questions, also following Google's schema) and **Q&A** (customers ask directly - see its own article).