When you share your target format with clients, they'll inevitably encounter errors — values that don't match your format's requirements. The question is: how hard do you make it for them to fix those errors?
WeTransform lets you pre-configure correction options so your clients never face a blank error and a dead end. Instead, they see clear solutions they can apply in one click.
🛡️ How error solutions work
For each column constraint you define, you can configure one or more solutions — pre-built correction options that WeTransform presents to your client when that constraint is violated.
When your client lands on Finalize and sees a red column, they click "Fix errors" and see the solutions you've configured — not a generic error message, but a tailored list of choices specific to your business context.
⚙️ Configuring solutions on a column
All constraints come with a pre-built solution by default.
And you can customize your own if you need.
In your target format, open a column and go to its error handling section. For each constraint, you can add solutions. Each solution has:
A name — internal label, only visible to you (e.g. "Add leading zero to EAN")
A question — what you ask your client (e.g. "What number do you want to add?")
A variable — stores the client's answer (e.g.
leading_number)A rule — the transformation applied automatically when the client chooses this solution
🤖 AI-suggested solutions appear automatically. Even without custom configuration, WeTransform always shows "Fix errors with AI" and "Fix errors in bulk" as default options. Your custom solutions appear alongside them — giving your client the most relevant option first.
🛒 A concrete example
Your target format requires EAN codes to be exactly 13 characters. A client regularly sends files with 12-character EANs — they forget the leading zero.
Instead of sending the file back with an error message, you configure a solution:
Solution name: "Add a leading zero to EAN" (internal)
Question to client: "Your EAN codes have 12 characters. Do you want to add a leading zero?"
Rule: IF EAN length = 12, THEN prepend "0" to EAN
When the client clicks this solution, all 12-character EANs are fixed automatically. No back-and-forth, no re-upload.
🔁 Solutions are remembered. Once a client chooses a solution, it's saved in their transformation configuration. Next time they upload a file with the same issue, the solution runs automatically — they don't even see the error anymore.
💡 Default transformation — skip the question entirely
If you're confident a correction should always apply — without asking the client — you can configure it as a default transformation rule on the target format. It runs automatically on every file, before the client even reaches Finalize.
This is the most seamless experience for your clients: errors are corrected silently, they submit a clean file without knowing there was ever an issue.
👉 What to do next