seed-mapper

To convert supplier PDFs and CSVs into BOM seed rows, the skill parses source material and generates per-variant JSON files under supabase/seeds/glass-outlet/products. It enforces schemas and ensures data integrity during the mapping process.

Importing supplier data to add a new fencing system requires mapping source briefs or price sheets into QuickScreen seed JSONs. The generated files are then validated and upserted via the npm run seed:products repository tooling command.

Yes, natural-language briefs can be used to generate QuickScreen seed files. The mapping process accepts natural-language briefs alongside CSVs and price sheets, translating text into structured per-variant JSON seed rows.

You validate and upsert seed JSON files by running the npm run seed:products command. This repository tooling step ensures consistency with the seed schema and successfully imports the mapped product data into the database.

Yes, seed mapping supports extending existing product rules for supplier data. Its scope covers adding new fencing systems, extending existing rules, or importing supplier data while enforcing schemas to ensure data integrity.

The seed mapper outputs one JSON file per variant. These files are generated under the supabase/seeds/glass-outlet/products directory, conforming to the portable seed-data-mapping spec for database upserting.