How to check whether a product catalog has the fields you need
A completeness check shows which records lack required information before an import or publication step. It is useful when a catalog has inconsistent fields across products or variants.
Start with the right material.
- What you provide
- a loaded catalog table with visible fields.
- The intended result
- Report missing names, descriptions, prices or identifiers in the selected rows.
How the workflow works.
Define the required columns and any conditional rules, then mark missing values by record. Keep a blank field distinct from a meaningful zero, an intentional empty value or an attribute that does not apply.
What to check in the result.
Review the reasons for each flagged field before correcting it. Completeness is not the same as accuracy, so a filled-in catalog still needs factual checks against the source.
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: Product, Missing field, Review action. 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.