Proposed $750 job · scope confirmed after sample review
Hand off the product cleanup before your next import.
When an existing product export still needs corrections after your spreadsheet and Odoo tools, Operalith can scope the preparation: a candidate CSV, every change explained, and the decisions that need your team.
Start with a description. No file, credentials or call required. Dylan confirms fit and availability in writing before work is accepted.
A usable candidate, with the evidence to review it.
You supply existing raw exports through an agreed private route. We propose the identifier crosswalk and approved corrections; you resolve ambiguous business meaning and identity.
- 01 / CSV
The prepared candidate
Agreed target columns and reviewed values. Existing target identifiers are reconciled against your export. Uncertain matches stay out until resolved.
- 02 / Decision list
Specific questions for your approver
Conflicting identifiers, missing required values and unresolved business decisions, tied to source rows. You receive the questions that need judgment.
- 03 / Trace + handoff
Every source row accounted for
Original values, approved changes, rules, exclusions, totals and file hashes, with instructions for your native staging Test. An incomplete subset is not a completed job.
Try the preparation mechanics on fictional data.
The working prototype maps a CSV, holds unsafe or ambiguous rows, applies reviewed text corrections and downloads the three artifacts. It does not connect to Odoo or establish that a customer import succeeds.
Open the synthetic workspacePreparation your team would actually prefer to hand off.
Best suited to one product-master batch with repeatable text corrections and a named partner approver. If native Odoo tools, a straightforward spreadsheet cleanup or your existing implementation scope already cover it, keeping the work in-house may be better.
Agree the actual target before quoting
The reference scope is Odoo 19.0, English, one company and product.template: External ID, Name, Product Type, Internal Reference and optionally Sales Description. Your installed build and export must confirm the mapping.
One UTF-8 comma CSV, up to 1 MiB. No new products, variants, prices, costs, inventory configuration, accounting, production access or import execution. Other versions or requirements need a fresh fit decision.
A written path, with a named person at each step.
- 01 / Describe
Email Dylan about the remaining work
Share the approximate batch size, target and timing. Existing headers can help. You do not need to manufacture sample data or clean the export first.
- 02 / Qualify + agree
Review an existing sample through a private route
First agree end-customer disclosure permission, confidentiality, handling and retention. Then we inspect existing source and target records, propose the crosswalk, and confirm written scope, price, payment method and a delivery slot.
- 03 / Prepare + Test
Review the package in your actual context
We apply agreed rules and ask for unresolved decisions. Your team verifies mappings and runs native Odoo Test in staging. One consolidated correction round returned within five business days is included; our deviations are corrected without an extra fee.
- 04 / Accept + pay
Accept the whole agreed batch in writing
Acceptance covers the final file, source reconciliation, approved exclusions and successful native Test evidence. We invoice afterward. If we cannot complete the batch and exclusions are unacceptable, no final fee is due. Production import and ongoing support are excluded.
Is there one batch worth taking off your team’s list?
Dylan Becchetti operates Operalith, bringing manufacturing continuous-improvement and operational-reporting experience. Email is the customer channel; there is no unattended support desk or instant-response promise.