Field mapping converts the columns in your source file into SortingGo fields. Required fields must be mapped; optional fields can be added depending on your plan and workflow.
Steps
- Map required fields first
Product name and quantity are the core fields. If your workflow needs customer or order information, map those as well. - Check the app's suggestions
The app may suggest mappings based on column names, but you should still confirm each one is correct. - Set up product short name rules
For long product names, you can create short-name rules using the first N characters, segments, brackets, or a regex. - Check the summary and the warning
Once a rule is chosen, the app shows how many different product names the sample has and how many short names they become. An orange warning means different products share a short name, which is easy to mix up when picking; adjust the rule. - Test a custom regex
With “Custom regex”, paste any product name into “Try a product name” to see its short name at once. An invalid regex is reported as you type. - Let an AI assistant write it
Tap “Copy AI prompt”, paste it into an AI assistant such as ChatGPT, Gemini or Claude, then paste the regex it replies with into the field and test it.
Notes
- The same SortingGo field cannot be mapped from more than one source column.
- The AI prompt holds only product names from your sample (up to 30), with no order or buyer data. The app sends nothing by itself.
- Steps: several actions applied one after another, for example remove the text in brackets, then take the first word.
- If the file has no quantity column (one row per piece bought), turn on "This file has no quantity column: count each row as 1" under the quantity field. Rows of the same order with the same product and spec are merged into one line and their quantities added up.
Limitations
- Some fields are restricted by plan; if the screen shows a field as locked, you'll need to upgrade before that field's data can be saved.