Operalith / local working prototype

Product data preparation

Map a product CSV, review proposed corrections and export a traceable handoff.

Synthetic data only
500 rows · 8 columns · UTF-8 CSV

  1. 01 Source
  2. 02 Mapping + rules
  3. 03 Review
  4. 04 Handoff

Synthetic existing-product updates loaded. Review the target evidence, mapping and rules, then inspect the file.

01 / Source

Choose a fictional export

Processing runs in this tab. The prototype does not store your input; downloads stay on your device. Use synthetic data only.

Target export / exact update ID check

The default fictional source includes a manually prepared crosswalk. This checker compares the resulting update ID to the explicitly selected target column, with no trimming, case folding or numeric conversion. It does not build that crosswalk or verify other target fields.

Missing evidence, unknown IDs and duplicate target IDs hold updates. Each CSV is limited to 500 rows, 8 columns and 1 MiB. The supplied export is evidence only: a person must confirm its model, completeness and currency, then run native Odoo Test. Use synthetic data only.

02 / Mapping + rules

Define the target

The default update example uses five reference headers for the proposed existing-product job. All records are synthetic. The partner must verify the actual template, existing IDs and unchanged product types. Other examples use fictional contracts.

Explicit correction rules

  • Name · Trim outer whitespace
  • Sales Description · Trim outer whitespace
Add a rule or an explicit cell correction
Next / partner conversation

Would this remove recurring preparation work?

Describe the export, its target template and the corrections you repeat. Do not attach customer files to the first message.

Write to Dylan