This article contains a list of possible error codes that may appear after using the Bulk Actions Tool for validating migrations.
Before you start
- The chart contained in this guide is for use with the ReCharge Bulk Actions tool. To enable this tool, you can request access via the Integrations tab in the ReCharge Dashboard.
- Error and warning codes are listed in alphabetical order by error/warning code for easy browsing.
- If you have any issues or trouble fixing your errors, reach out to your Migrations team.
|Error Code||Description||How to fix it|
|billing_postalcode||The zip code must be the standard 5 digit number or the 5-4 format||US zip codes should all have 5 digits. Some spreadsheet software, like Excel, will remove any leading zeros from numbers. You will need to format the value to include the leading zero if it is only 4 digits.|
|charge_interval_frequency||Value ‘0’ must be greater than ‘0’||All active subscriptions should have a charge frequency and the value should be greater than 0. If these are set to zero or missing, then you'll either need to leave them off the import or change these to a valid frequency and import them as a cancelled subscription.|
|charge_interval_unit_type||Must be one of [‘day’, ‘days’, ‘week’, ‘weeks’, ‘month’, ‘months’], found ‘foo’||The only values allowed in this column are day, days, week, weeks, month, or months. If you have customers set to year or years, you’ll need to change this to month and change the charge_interval_frequency to 12. If the subscription is not prepaid, then change the shipping_interval_frequency to 12 as well.|
|charge_on_day_of_month||Value '41' must be less than or equal to 31"||This column should only be the day of the month. You should only fill this in if all your customers are charged on the same day of the month. Otherwise, you'll leave this field blank.|
|customer_created_at||‘'20-01-02' must be in ISO format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS)||Date formats must be formatted as yyyy-mm-dd.|
|customer_created_at||'2999-01-01' must be on or before today (2020-04-13)"||Date formats must be formatted as yyyy-mm-dd and date must be before today’s date.|
|Is_prepaid||Subscription is not prepaid, 'charge_interval_frequency' should equal 'shipping_interval_frequency'||If your charge_interval_frequency is greater than your shipping_interval_frequency then this is a prepaid subscription and you should mark is_prepaid as yes. Otherwise, you can leave is_prepaid blank and change the shipping_interval_frequency to match the charge_interval_frequency. See the Importing prepaid subscriptions guide.|
|last_charge_date||‘'20-01-02' must be in ISO format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS)||Date formats must be formatted as yyyy-mm-dd.|
|last_charge_date||must exist||You've marked the row as a prepaid subscription but left out the last_charge_date value. This date is required by our system to determine when their current prepaid cycle started.See the Importing prepaid subscriptions guide.|
|next_charge_date||Must be blank||If the status is "cancelled" then the next_charge_date should be blank.|
|quantity||Value 0 must be greater than 0||If your old platform supports a quantity of zero, you’ll need to decide how to handle these in ReCharge as a zero quantity is not allowed in our system. You can either import these as canceled subscriptions and the value to 1 or greater, or leave them off the import.|
|shipping_email||Email is not valid||The email address listed is not valid per MX records. You can try to edit these manually if it's a typo. Otherwise, you may need to leave these customers off ReCharge until you have the correct email address.|
|shipping_interval_frequency||Value '2' must be less than or equal to 1.0||The shipping_interval_frequency is higher than the charge_interval_frequency. We don't support charging more often than you ship so you'll need to change these values or leave these rows off the import CSV.|
|shipping_interval_frequency||Value ‘0’ must be greater than ‘0’||All active subscriptions should have a shipping frequency and the value should be greater than 0. If these are set to zero or missing, then you'll either need to leave them off the import or change these to a valid frequency and import them as a cancelled subscription.|
|shipping_interval_unit_type||Must be one of ['day', 'days', 'week', 'weeks', 'month', 'months'], found 'foo'"||The only values allowed are day, days, week, weeks, month, or months. If you have customers set to year or years, you'll need to change this to month and change the charge_interval_frequency to 12. Change the shipping_interval_frequency to 12 as well if it is not prepaid.|
|shipping_province||State does not match with specified address||There is an issue with the shipping address. Please validate that the province/state is a valid address.|
|external_product_id||Must be a valid Product ID in your new platform, ID 1234 not found in 555||The Product ID doesn’t match any of the products in your new store. Make sure you have formatted this column to remove any special characters and ensure the ID is for the original item in the new platform.|
|external_variant_id||Must be a valid product variant ID in your new platform, ID 1234 not found in store 555||The Variant ID doesn’t match any of the variants in your new store. Make sure you have formatted this column to remove any special characters and ensure the ID is for the original item in the new platform.|
Warnings are informational messages that do not affect the ability to import the row.
|Warning Code||Description||How to fix it|
|customer_stripe_id||A payment processor token has not been provided||This warning indicates that you are importing a row that does not have a payment customer ID. We can import the subscription without this ID, but we won't be able to charge the customer until we have a card on file for the customer. The customer will need to re-enter a card after they are imported into the ReCharge system.|
|next_charge_date||'2020-12-01' should be within 3.0 months from today (value in column 'charge_interval_frequency')||This warning indicates that the next_charge_date may be too far into the future. It is expected to be charged within the charge_interval_frequency. If the customer skipped a shipment or changed their charge date then you can ignore this warning. Otherwise, confirm their charge date is correct.|
|recurring_price||Value '0' should be greater than 0||This warning indicates that you've set the recurring price to $0 for this subscription which means the customer will NOT be charged for their subscription.|