Give the routine a brief.

A completed example to start from.

This synthetic supplier-price routine shows how to turn a repeated task into a brief someone can check. It uses our before CSV and after CSV; neither file contains customer records.

Task

Compare supplier prices every Friday and report what changed.

Inputs

Two UTF-8 CSV files with SKU and Price columns. Match products by their exact SKU. Each file must have one row per SKU.

Required output

A downloadable change report with old and new prices, added products, removed products, and a separate count of unchanged products. Preserve the source files.

Frequency

Weekly, after the new supplier file arrives.

Checks that define a useful result.

• A1 changes from 10 to 11; B2 stays at 5.
• C3 is removed and D4 is added at 9.
• The summary has one changed, one added, one removed, and one unchanged product.
• A duplicate or empty SKU stops this example's comparison and identifies the input to correct.

You can try this sample in the browser CSV comparer and inspect the report. These checks define the example's expected output; they do not promise that every supplier file will be valid.

Make the brief specific to your task.

Name the columns or IDs used to match records. Describe the format of the result, who reviews it, and what should happen when an input is missing or ambiguous. Replace the sample checks with examples from your own routine before agreeing on a build.

The downloaded brief is a starting document. It does not connect accounts, schedule a workflow, or send a request. Review it locally, then decide what to share with your team or a builder.