How to build a product specification table people can compare
A specification table makes technical and practical product details easier to find. Its value comes from consistent labels and units rather than from making every row appear equally complete.
Start with the right material.
- What you provide
- a product page with unstructured technical details.
- The intended result
- Normalize displayed specifications into attribute-value rows with units preserved.
How the workflow works.
Map the supplied facts into attribute and value pairs, preserving units and variant context. Group similar attributes while retaining distinctions such as product dimensions versus packaging dimensions.
What to check in the result.
Check numbers and units against the source before publishing. If a value is missing or ambiguous, mark it for review instead of borrowing a value from a similar product.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Attribute, Value, Unit. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.