TRANSLATION GLOSSARY (ENGLISH → VIETNAMESE)
VietGara — Multi-Tenant SaaS Platform for Auto Garage Management & Maintenance
Version 1.0 — October 11, 2026
Status: agreed (Section 6). Terms marked UI are taken from the Vietnamese strings the products already ship (
vietgara-owner-web,vietgara-admin-weband the Flutter apps), so the documents and the screens use the same word. Terms marked Proposed are new and were accepted as listed; change one here, in a pull request, if a garage’s usage differs.
1. Purpose and how to use it
The documentation site publishes every page in English (the source of truth) and in Vietnamese. This glossary fixes the Vietnamese term for each recurring concept so that fifty-odd documents, translated in batches by different people, read as one text and match the product’s own screens.
- Translate from the English page; do not translate the Vietnamese UI back into English.
- When a term is in this glossary, use it exactly. When a term is missing, translate it, then add it here in the same pull request.
- A translated page carries
translated_from: <commit>in its frontmatter (see the README, “Writing and translating”).
2. Style rules
| Rule | Detail |
|---|---|
| Register | Neutral, formal technical Vietnamese. Impersonal statements (“Hệ thống gửi…”, “Chủ gara có thể…”). Address the reader as bạn only in procedures and user-facing text, as the UI does. |
| Do not translate | Product and brand names (VietGara, Kafka, Kong, Mailjet, Google Cloud Platform, Flutter…); code, API paths, HTTP methods, headers, JSON fields, SQL, event names (repair_order.closed), enum values, environment names; requirement and scenario IDs (FR-QUO-02, E2E-QUO-001); ADR numbers; file names. |
| Keep standard acronyms | API, REST, gRPC, SQL, OTP, JWT, MFA, SaaS, SSO, CI/CD, C4, ADR, FRD, NFRD, SAD, HLD, LLD, PDF, VND. Spell out once in Vietnamese only when a document already spells it out in English. |
| First use | A kept English technical term is written once as Vietnamese gloss (English term) when it is first used in a document, then plain: “bộ đệm ghi sự kiện (outbox)”. Glossary terms below that are marked keep are not glossed. |
| Headings and tables | Translate headings, table headers and captions. Keep section numbers (3.2.) unchanged so cross-references and FR-… links keep working. Anchors in links are generated from the English headings only on the English page; a Vietnamese link target uses the Vietnamese heading’s slug, so re-check in-page links after translating. |
| Mermaid diagrams | Translate node and edge labels; keep node IDs, subgraph IDs and syntax unchanged. Quote any label that contains parentheses. |
| Numbers and dates | In prose and tables use Vietnamese separators: “1,000” → “1.000”, “99.5%” → “99,5%”. Write “October 11, 2026” as “11 tháng 10, 2026”. Keep ISO dates (2026-10-11), code, JSON and SQL examples unchanged. |
| Quotation of UI text | When a document quotes an on-screen label, use the exact Vietnamese label from the UI. |
3. Terms
3.1. Business and people
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| garage | gara | UI | One branch; the tenant. |
| garage owner | chủ gara | UI | |
| owner (the account that holds the subscription) | chủ sở hữu | UI | Use when contrasting with staff of a garage. |
| staff, staff member | nhân viên | UI | |
| staff group | nhóm nhân viên | UI | |
| role | vai trò | UI | |
| permission | quyền | UI | |
| business module (permission area) | phân hệ | UI | The “module” of a Go modular monolith stays module (see 3.5). |
| manager | quản lý | Proposed | Default role. |
| accountant | kế toán | Proposed | Default role. |
| service advisor | cố vấn dịch vụ | Proposed | Default role; common term in the automotive trade. |
| technician | kỹ thuật viên | UI | |
| stock keeper (role) | thủ kho | Proposed | Default role “Inventory staff” → “nhân viên kho”. |
| customer | khách hàng | UI | |
| vehicle | xe | UI | |
| vehicle owner | chủ xe | UI | |
| license plate | biển số | UI | |
| VIN / chassis number | số khung | UI | |
| engine number | số máy | UI | |
| partner | đối tác | UI | Suppliers and insurers. |
| supplier | nhà cung cấp | UI | |
| insurer, insurance company | công ty bảo hiểm | UI | |
| user (Phase 3 terminology) | người dùng | UI | A person who signs in. |
| account (sign-in credentials) | tài khoản | UI | |
| platform admin | quản trị viên nền tảng | Proposed | UI nav says “Quản trị nền tảng”. |
| platform staff | nhân viên nền tảng | Proposed | |
| support access (read-only, owner-approved) | quyền truy cập hỗ trợ (chỉ đọc, do chủ gara duyệt) | Proposed | |
| invitation | lời mời | UI | |
| tenant, multi-tenant | tenant, multi-tenant | Proposed | Keep. Gloss once: “đa người thuê (multi-tenant)”. Each garage is a tenant. |
3.2. Quotes, repair orders and money
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| quote | báo giá | UI | |
| quote line, line item | hạng mục | UI | |
| labor | nhân công | UI | |
| part | phụ tùng | UI | |
| quantity | số lượng | UI | |
| unit price | đơn giá | UI | |
| line total | thành tiền | UI | |
| total | tổng cộng | UI | |
| draft / sent / approved / rejected / converted | nháp / đã gửi duyệt / đã duyệt / đã từ chối / đã chuyển lệnh sửa chữa | UI | Quote statuses. |
| approval mode | cách duyệt báo giá | UI | |
| approval link (public link) | liên kết duyệt báo giá | UI | |
| manual decision | ghi nhận thủ công | UI | |
| repair order | lệnh sửa chữa | UI | |
| Kanban board | bảng Kanban | UI | |
| open / in progress / waiting on parts / completed / closed | chưa bắt đầu / đang thực hiện / chờ phụ tùng / hoàn tất / đã đóng | UI | Repair-order statuses. |
| settlement | quyết toán | UI | |
| allocation (customer / insurer share) | phân bổ (phần khách hàng trả / phần bảo hiểm trả) | UI | |
| outstanding balance, receivable | công nợ phải thu | UI | UI shows “công nợ”. |
| payable | công nợ phải trả | Proposed | |
| receipt voucher (money in) | phiếu thu | Proposed | |
| payment voucher (money out) | phiếu chi | Proposed | Where the source says only “payment voucher”, choose by direction. |
| invoice | hóa đơn | Proposed | |
| e-invoice | hóa đơn điện tử | Proposed | |
| payment gateway | cổng thanh toán | Proposed | |
| claim (insurance) | hồ sơ bồi thường | Proposed | |
| tax code | mã số thuế | UI | |
| document numbering | đánh số chứng từ | UI | |
| print (document print) | in ấn chứng từ | UI | |
| report | báo cáo | UI |
3.3. Inventory
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| inventory, stock | kho, kho phụ tùng | UI | |
| stock on hand | tồn kho | UI | |
| stock movement | xuất nhập kho | UI | |
| goods receipt | phiếu nhập kho | UI | The document. The action that receives stock is “Nhập kho”. |
| stock issue | phiếu xuất kho | UI | The repair order’s stock-out document. |
| issue now (post a stock issue early) | xuất kho ngay | UI | |
| reverse receipt (cancel a completed goods receipt) | hoàn tác phiếu | UI | “Huỷ phiếu” cancels a draft. |
| stock count | kiểm kê kho | Proposed | |
| reorder threshold | ngưỡng cảnh báo tồn kho | UI | |
| low stock | sắp hết | UI | |
| SKU, part code | mã phụ tùng | UI | |
| unit, base unit | đơn vị, đơn vị cơ bản | UI / Proposed | |
| average cost | giá vốn bình quân | UI | Weighted average, per base unit. Not “giá bán” (selling price). |
| stock reservation | đã giữ | UI | The reserved quantity of draft stock issues; the screens show “đã giữ {quantity}”. |
| purchase order | đơn mua hàng | Proposed | |
| catalogue | danh mục | UI | Part catalogue → danh mục phụ tùng; job catalogue → danh mục công việc. |
| barcode | mã vạch | Proposed | |
| packaging unit | đơn vị đóng gói | Proposed | A unit of one part with a factor to its base unit: thùng = 24 lon. |
| conversion factor | hệ số quy đổi | Proposed | Base units per packaging unit. |
| entered quantity | số lượng đã nhập | Proposed | What the user typed, in the unit chosen; the stored quantity is in the base unit. |
| part category, brand | nhóm phụ tùng, thương hiệu | Proposed | |
| selling price | giá bán | Proposed | Per base unit; not the cost (giá vốn). |
| on hand, reserved, available | tồn kho, đã giữ, có thể dùng | UI | Available = on hand − reserved (Release 7.0). The screens say “Có thể dùng” for available. |
| stock card | thẻ kho | Proposed | The ordered list of a part’s movements. |
| write-off | xuất hủy | Proposed | |
| return to supplier | trả hàng nhà cung cấp | Proposed | |
| return of unused parts (repair order) | trả phụ tùng về kho | Proposed | A part line of a repair order given back to stock. Not a return to supplier. |
| counted, system quantity | số lượng đã kiểm, số lượng hệ thống | Proposed | The quantity typed on the shelf, and the stock on hand the system expects. |
| matched, over, short | khớp, thừa, thiếu | Proposed | The result of a count line: counted equals, is more than, or less than the system quantity. |
| uncounted (count line) | chưa kiểm | Proposed | No counted quantity typed yet. |
| merge (stock count drafts) | gộp phiếu kiểm kê | Proposed | Several drafts become one; the others are cancelled. |
| adjustment (stock) | điều chỉnh tồn kho | Proposed | A change made by a count, write-off or return. It is valued at average cost and never changes the average cost. |
| credit note number | số chứng từ giảm trừ | Proposed | The supplier’s own number for the credit on a return to supplier. |
| barcode | mã vạch | Proposed | The code on a part’s label, read by a scanner. A part can have several; a case barcode stands for a packaging unit. |
| scan | quét | Proposed | Read a barcode with the phone camera or a USB scanner. |
| Excel import | nhập từ Excel | Proposed | Creating parts, a goods receipt or a stock count from a template workbook. |
| job | công việc | Proposed | A type of work (an oil change) with a labor price, a duration and suggested parts; picked on a quote. |
| hidden consumable | vật tư tiêu hao ẩn | Proposed | A suggested part that is deducted from stock but not billed or shown to the customer. |
| waiting on parts | chờ phụ tùng | Proposed | The status of a repair order whose draft stock issue the stock on hand cannot cover. |
| cancel (a repair order) | huỷ (lệnh sửa chữa) | Proposed | Stop an order before work starts; its reservation is released. |
| template (Excel) | file mẫu | Proposed | The downloadable workbook an import is filled in on. |
| preview (import) | xem trước, kiểm tra file | Proposed | The check of a file that lists every problem and writes nothing. |
| opening stock | tồn đầu kỳ | Proposed | The quantity on hand a part starts with, posted as a completed goods receipt. |
3.4. Licensing and identity
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| subscription plan | gói dịch vụ | UI | |
| subscription (the record) | thuê bao | UI | Admin console wording. |
| trial | dùng thử | UI | |
| active | đang hoạt động | UI | |
| past due (read-only) | quá hạn (chỉ đọc) | UI | |
| suspended | tạm khoá | UI | |
| cancelled | đã huỷ | UI | |
| renew | gia hạn | UI | |
| payment request (a plan payment the owner submits for review) | yêu cầu thanh toán | UI | Release 5.2. |
| evidence (of a transfer) | chứng từ chuyển khoản | UI | The screenshot or PDF the owner attaches. |
| transfer reference | mã tham chiếu chuyển khoản | UI | VG-XXXXXX, written in the transfer note. |
| review queue | hàng đợi duyệt | UI | The admin’s list of submitted requests. |
| approve / reject (a payment request) | duyệt / từ chối | UI | |
| account credit | số dư tín dụng | UI | Money kept for the owner, applied to the next payment. |
| proration | quy đổi theo ngày chưa dùng | UI | Credit for the unused days of the period. |
| unused days | số ngày chưa sử dụng | UI | |
| amount due | số tiền phải thanh toán | UI | |
| payment details (platform) | thông tin thanh toán của nền tảng | UI | Bank account, QR code and transfer instructions. |
| usage, limit | mức sử dụng, giới hạn | UI / Proposed | |
| sign in / sign out | đăng nhập / đăng xuất | UI | |
| register | đăng ký | UI | |
| verification code (OTP) | mã xác minh (OTP) | UI | |
| password reset | đặt lại mật khẩu | UI | |
| consent to personal-data processing | đồng ý xử lý dữ liệu cá nhân | UI | Decree 13/2023 → Nghị định 13/2023. |
3.5. Architecture and engineering
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| modular monolith | monolith theo module | Proposed | Keep “monolith” and “module”. |
| module (code) | module | Proposed | Keep. |
| microservice | microservice | Proposed | Keep. |
| API gateway | API gateway | Proposed | Keep. |
| event, event bus | sự kiện, event bus | Proposed | Keep “event bus”, “outbox”, “consumer”, “topic” and “partition”. |
| outbox pattern | mẫu outbox (outbox pattern) | Proposed | Gloss on first use. |
| idempotency, idempotency key | tính idempotent, khoá idempotency | Proposed | Keep the header name Idempotency-Key. |
| rate limiting | giới hạn tốc độ truy cập (rate limiting) | Proposed | |
| authentication / authorization | xác thực / phân quyền | Proposed | |
| role-based access control | kiểm soát truy cập theo vai trò (RBAC) | Proposed | |
| multi-factor authentication | xác thực nhiều lớp (MFA) | Proposed | |
| audit log | nhật ký kiểm toán | Proposed | |
| snapshot (of a document’s data) | bản chụp | Proposed | The copy of the garage’s legal identity that an issued document keeps (FR-TEN-06); not “ảnh chụp” (a photo). |
| deactivate, reactivate | ngừng hoạt động, kích hoạt lại | UI | The delete-or-deactivate rule (FR-CAT-07). |
| void (a payment voucher) | huỷ (phiếu thu) | Proposed | The voucher stays on file; “xoá” (delete) is not used for it. |
| database, table, column, index | cơ sở dữ liệu, bảng, cột, chỉ mục | Proposed | |
| migration | migration | Proposed | Keep. |
| deployment | triển khai | Proposed | |
| environment (dev / staging / production) | môi trường (dev / staging / production) | Proposed | Keep environment names. |
| backup, restore | sao lưu, khôi phục | Proposed | |
| infrastructure | hạ tầng | Proposed | |
| container, image | container, image | Proposed | Keep. |
| pull request, branch, commit | pull request, nhánh, commit | Proposed | Keep “pull request” and “commit”. |
| design system, design token | hệ thống thiết kế, design token | Proposed | |
| sidebar | thanh bên | UI | |
| dashboard | bảng điều khiển | Proposed | UI uses “Tổng quan” for the home page. |
3.6. Process and document structure
| English | Vietnamese | Source | Notes |
|---|---|---|---|
| phase | giai đoạn | UI | The apps already say “Giai đoạn 4”. |
| release | bản phát hành | UI | “Release 10.2” → “bản phát hành 10.2” (help site). Keep the number. |
| release plan | kế hoạch phát hành | UI | |
| roadmap | lộ trình | Proposed | |
| version | phiên bản | UI | |
| scope, out of scope | phạm vi, ngoài phạm vi | Proposed | |
| requirement | yêu cầu | Proposed | |
| functional / non-functional | chức năng / phi chức năng | Proposed | |
| definition of done | tiêu chí hoàn thành (Definition of Done) | Proposed | |
| scenario | kịch bản | Proposed | |
| precondition | điều kiện tiên quyết | Proposed | |
| expected result | kết quả mong đợi | Proposed | |
| priority | mức ưu tiên | Proposed | |
| must have / should have / could have | bắt buộc / nên có / có thể có | Proposed | MoSCoW levels in the NFRD; keep the English in parentheses at the definition. |
| automation candidate | có thể tự động hoá | Proposed | |
| baseline (test data) | dữ liệu nền | Proposed | |
| test data | dữ liệu kiểm thử | Proposed | |
| test strategy | chiến lược kiểm thử | Proposed | |
| end-to-end test | kiểm thử đầu cuối (E2E) | Proposed | |
| staging | staging | Proposed | Keep. |
4. Document titles
Used for the page title, the sidebar label and the # TITLE heading of each Vietnamese page.
| English | Vietnamese |
|---|---|
| Vision & Scope Document | Tài liệu Tầm nhìn và Phạm vi |
| Functional Requirements Document | Tài liệu Yêu cầu Chức năng |
| Non-Functional Requirements Document | Tài liệu Yêu cầu Phi chức năng |
| Release Plan — Phase N | Kế hoạch phát hành — Giai đoạn N |
| UX Guideline | Hướng dẫn UX |
| UI Design Specification | Đặc tả thiết kế UI |
| Design System | Hệ thống thiết kế |
| UI/UX Audit and Redesign Proposal (Web) | Đánh giá và đề xuất thiết kế lại UI/UX (Web) |
| Software Architecture Document | Tài liệu Kiến trúc phần mềm |
| High-Level Design | Thiết kế mức cao |
| Low-Level Design | Thiết kế mức thấp |
| API Specification | Đặc tả API |
| Database Design | Thiết kế cơ sở dữ liệu |
| Event Design | Thiết kế sự kiện |
| Integration Design | Thiết kế tích hợp |
| Security Architecture | Kiến trúc bảo mật |
| Deployment Architecture | Kiến trúc triển khai |
| Infrastructure Architecture | Kiến trúc hạ tầng |
| Architecture Decision Records | Các quyết định kiến trúc (ADR) |
| Coding Standards | Chuẩn viết mã |
| Git Strategy | Chiến lược Git |
| Test Strategy | Chiến lược kiểm thử |
| E2E Test Scenarios (and per-module scenarios) | Kịch bản kiểm thử E2E (và kịch bản theo phân hệ) |
| E2E Test Data | Dữ liệu kiểm thử E2E |
| Deployment Guide | Hướng dẫn triển khai |
5. Order of translation
The order is chosen so that the documents people read first and the ones other documents depend on come first. Each batch is one pull request.
| Batch | Documents | Why |
|---|---|---|
| 1 | Vision & Scope, Non-Functional Requirements | Short, high-level, set the tone and the most terms. |
| 2 | Functional Requirements | The largest source of terms; every other document cites its IDs. |
| 3 | Release Plan, Phases 1–17 | Many short, repetitive files; mostly settled terms. |
| 4 | Architecture: SAD, HLD, LLD, ADR | Most technical vocabulary; gloss rules matter here. |
| 5 | Architecture: API, Database, Events, Integration, Security, Deployment, Infrastructure | Tables and code-adjacent text; least prose. |
| 6 | Design v2 (then v1 if still wanted) | Uses UI vocabulary heavily. |
| 7 | Testing and E2E scenarios, Development, Operations | Procedural; reuse the ID conventions. |
6. Decisions
Agreed October 11, 2026.
| # | Question | Decision |
|---|---|---|
| 1 | Default role names | quản lý, kế toán, cố vấn dịch vụ, thủ kho (the inventory role is “nhân viên kho” in running text). Revisit if garages report a different usage. |
| 2 | Payment vouchers | phiếu thu (money in) and phiếu chi (money out); choose by direction where the source says only “payment voucher”. |
| 3 | “Tenant” | Keep tenant / multi-tenant in English, glossed once as “đa người thuê (multi-tenant)”. |
| 4 | “Release” | bản phát hành, with the number kept (“bản phát hành 10.2”), as in the help site. |
| 5 | Spelling | Follow the UI: huỷ, xoá, tạm khoá (not hủy, xóa, khóa). |