Table Rates CSV Import Troubleshooting
Use a fresh export from the same website and Table Rates condition as your import. This is safer than building headers from memory.
Magento cannot find the Bulkgood column
The added header must be exactly Bulkgood. Keep its spelling and capitalization and remove leading or trailing spaces.
Use 0 or 1 in every data row:
0for ordinary carts;1for carts containing a bulkgood.
Text such as Yes, No or Bulk is rejected. Negative values are also rejected.
Condition header is rejected
Magento changes the condition column according to the selected Table Rates condition. Export again after choosing the condition and retain the generated column name. Do not replace it with a generic header such as Condition.
Rows import but the method is unavailable
Confirm that the file was imported at the correct website scope and that a Bulkgood = 1 row matches all request dimensions:
- destination country;
- region or wildcard;
- postcode or wildcard;
- active condition threshold;
- website.
Remember that the matching row is required even when a product source supplies the final price.
Existing rates disappeared
Magento Table Rates import replaces the website's rate dataset. Add both ordinary and bulk rows to one complete file before importing it. Export immediately after import to verify the saved result.
Duplicate-row error
Rows must be unique across website, destination, condition, threshold and Bulkgood flag. Remove accidental duplicates. A matching Bulkgood = 0 and Bulkgood = 1 pair is valid because the flag differs.
File hygiene
- Save as a normal comma-separated file using the encoding accepted by your Magento environment.
- Keep decimal values unformatted, such as
45.0000. - Do not add currency symbols or thousands separators.
- Remove blank rows after the final record.
- Test a small file in a non-production environment before replacing a large matrix.
After a successful import, clear configuration cache and test ordinary, bulk and mixed carts.