Final Review - KartuStok User Guide V1
This maintainer-only review pack summarizes what is ready, what was checked, and where the owner should focus manual review before publishing.
Final Status
| Area | Status | Notes |
|---|---|---|
| Public guide structure | Review-ready | EN and ID have matching page sets. |
| Sidebar coverage | Review-ready | Every application sidebar menu is mapped in CONTENT_STATUS.md. |
| Truth evidence | Review-ready | Public claims are mapped to source evidence in FACT_CHECK.md. |
| Operational completeness | Review-ready | Core pages explain usage context, practical examples, checks, and common problems. |
| Screenshots | Review-ready | Referenced screenshots exist and have readable dimensions. |
| Sample import files | Review-ready | Referenced files exist and workbook headers match documented templates. |
| Build | Passed on final audit | npm run build completed successfully. |
10 Pages to Review First
Review these pages first because they affect the most users and contain the most business interpretation:
id/000-overview.md- product positioning and user mental model.id/015-new-company-quick-start.md- minimum first-day setup path for new companies.id/016-onboarding-wizard.md- in-app guided setup, redirect rules, initial stock option, and permission gate.id/030-company-settings.md- minimum stock, pricing, quantity display, and company setup impact.id/051-roles-and-permissions.md- operational role examples and price/dashboard/report access.id/043-master-data-item.md- item setup, barcode, minimum stock, pricing, and item form usage.id/064-transaction-category-and-custom-fields.md- Custom Fields, Item/Receipt/Issue/Move/Adjustment Form, and mandatory field guidance.id/060-transaction-receipt.md- document status, goods receipt form, import line note, and custom field recommendations.id/061-transaction-issue.md- production usage, customer shipment, internal request, and write-off examples.id/063-transaction-adjustment.md- stock opname, variance, correction, and shrinkage.
If these 10 pages feel correct, the rest of the guide should require only light review.
What Is Fact vs Recommended Practice
The guide intentionally separates application facts from operational recommendations:
| Type | Meaning | Example |
|---|---|---|
| Application fact | Verified from frontend/backend source, E2E flow, sample file audit, or screenshot. | Calendar Period locks transaction entry per month and transaction type. |
| Recommended practice | Practical business setup that the app supports, but does not create automatically. | Receipt custom fields such as PO Number, Supplier, QC Status, and Attachment. |
Custom field examples are recommendations. They are not built-in mandatory fields unless the company creates and assigns them through Custom Form.
The Custom Form chapter is intentionally more detailed than the first guide version because user-facing setup is different per form: Item Form enriches master data, while Receipt/Issue/Move/Adjustment Forms enrich transaction documents.
Sidebar Menu Coverage
All application sidebar areas are covered:
| Sidebar Area | Guide Coverage |
|---|---|
| Dashboard | Dashboard page |
| Receipt, Issue, Move, Adjustment | Four transaction pages |
| Report | Detail Stock Card, Daily Stock Pivot, Summary Stock Card, Minimum Stock reports |
| Master Data | Item, Item Category, Warehouse, Unit of Measure |
| Manage Settings | Company Settings |
| Users & Permissions | Users and Roles pages |
| Transaction setup | Transaction Category and Calendar Period |
| Import | Master data import, minimum stock import, transaction line import |
| Custom Form | Custom Fields, Item Form, Receipt Form, Issue Form, Move Form, Adjustment Form |
| Integrations | API Access |
| Others | Item Numbering, Email Template, Print Templates |
Final Validation Checklist
Use this checklist before publishing:
| Check | Expected Result |
|---|---|
| EN/ID parity | 32 EN pages and 32 ID pages, no missing pairs. |
| Asset link check | No missing screenshot or sample-file links. |
| Public safety scan | No public page mentions internal test tooling, demo tenants, or passwords. |
| Terminology scan | Menu/report/permission terms match the actual UI. |
| Screenshot audit | Referenced PNG files exist and have readable dimensions. |
| Sample file audit | Import sample headers match documented backend templates. |
| VitePress build | npm run build succeeds. |
| Optional app confidence | npm run test:e2e:core succeeds from frontend. |
Validation Run
Last validation run: 2026-05-22.
| Validation | Result |
|---|---|
| EN/ID parity | Passed: 32 EN pages and 32 ID pages. |
| Asset link check | Passed: no missing screenshot or sample-file links. |
| Public safety scan | Passed for EN/ID public pages. |
| Sidebar/menu term coverage | Passed. |
| Screenshot metadata audit | Passed: referenced PNG files exist and have readable dimensions. |
| Sample workbook header audit | Passed: all documented sample files have expected headers and data rows. |
| VitePress build | Passed. |
| Playwright core | Passed: 8/8 tests. |
| Playwright import coverage | Passed: 4/4 relevant import tests. |
Manual Sign-Off Questions
Answer these during owner review:
- Does the Indonesian guide explain the business process clearly enough for warehouse staff?
- Are the role examples aligned with how KartuStok should be sold and implemented?
- Are the custom field examples useful without implying they are default fields?
- Are pricing limits clear enough, especially that V1 pricing is informational and not accounting/HPP?
- Are import sample files acceptable as public examples?
Current Known Limits
- The guide is V1 user-facing documentation, not a complete technical API reference.
- Screenshots are a representative first set, not a screenshot for every single page.
- Recommended custom fields should be adjusted per company implementation.
- Pricing documentation intentionally avoids FIFO, moving average, journal, and official HPP claims.