Skip to main content

Specific prompt — teach the AI your format's business logic

Add a specific prompt to your target format and the AI generates rules that speak your business language — proprietary fields, conventions, and all.

Written by Stéphane Jauffret

The AI in the Rules editor is good at generic transformations: convert a date, round a price, concatenate two columns. But your target format isn't generic. It has proprietary columns, business conventions, and combinations of fields that must always go together — things the AI can't guess from column names alone.

The specific prompt fixes that. It's a text you write once on your target format, where you explain your format's specificities. From then on, every rule generated with AI on that format uses your explanations as context.

📍 Where to configure it

Open your target format's General settings and go to the Specific prompt tab. Write your instructions in the text area — plain language, in any language — and save.

🎯 Scope: rule generation only. The specific prompt guides the AI when it generates rules in the Rules editor. It does not affect column matching, value matching, or Autoclean.

🏭 Example — a marketplace inventory format

A marketplace management platform has an "inventory" target format with dozens of proprietary columns: promotion start and end dates per marketplace, promo prices, activation flags. Without context, a request like "create a promotion for Amazon" would leave the AI guessing which columns to touch.

Their specific prompt explains the logic once: which fields make up a promotion, which ones are mandatory together, what the naming convention per marketplace is, and how dates must be formatted. Now, when a user types "make a 20% promotion on Amazon for the next 30 days", the AI generates a rule that fills the right proprietary fields, all of them, correctly formatted — first try.

🚚 Example — a shipping format

A logistics format encodes shipping options across three linked columns: carrier code, service level, and cutoff time. The specific prompt states the combinations: "express means carrier DHL, service level EXP, cutoff 12:00 — the three fields must always be set together". When a user asks "ship all orders above 100€ in express", the generated rule sets all three fields consistently, instead of just one.

✏️ What to put in your prompt

  • The meaning of proprietary columns — what each non-obvious field is for

  • Fields that go together — "when you build a promotion, these fields are all mandatory"

  • Your conventions — date formats, decimal separators, flag values, per-partner variants

  • Recurring business operations — describe what "a promotion", "a delisting", or "a restock" means in terms of columns

💡 Write it like you'd onboard a new team member. There's no length limit, and the best practices are the same as for any prompt: be clear, be structured, use sections per topic, and state the non-negotiables explicitly. The more precise your explanations, the more precise the generated rules.

👉 What to do next

Did this answer your question?