Below you'll find most of the error messages you may find with those subscriptions that fail to import. Most of them are self-explanatory — however, we've provided an explanation where we think one could be needed.
Customer Data
Required Fields
|
Field |
Required |
Format |
|
merchant_user_id |
required |
string |
|
|
required |
string |
|
first_name |
required |
string |
|
last_name |
required |
string |
- Potential Error Messages
- merchant_user_id: Expecting string
- extra_data: Expecting a JSON object — if you provide a value for a field it must be a valid JSON object
- email: Missing @ sign
- email: Multiple @ signs
- email: Missing username
- email: Domain needs to have a . sign in it
- email: Empty string before "." in domain
- email: Empty string after "." in domain
Addresses
Required Fields
|
Field |
Required |
Format |
|
customer |
required |
string |
|
address_type |
required |
shipping_address or billing_address |
|
first_name |
required |
string |
|
last_name |
required |
string |
|
company |
string |
|
|
address_1 |
required |
string |
|
city |
required |
string |
|
state |
required |
string |
|
zip_code |
required |
string |
|
country |
required |
string |
|
phone |
string |
|
|
origin |
required |
string |
- Potential Error Messages
- address_type: Unsupported value. Expecting "shipping_address" or "billing_address"
- Explanation: Your address object does not have a correctly formatted address type value
- How To Resolve: use either "shipping_address" or "billing_address" as the field value
- country_code: Given country code is not supported
- Explanation: You've provided an invalid country code or a country code to a country to which Ordergroove does not support shipping.
- How To Resolve: You can see all of the countries that we accept here in Ordergroove look through your dataset and ensure you're not trying to ship to countries not on that list or an invalid 2 letter ISO country code
- state_province_code: Given state/province code for given country is not supported
- Explanation: You've provided an invalid state code for a country.
- How To Resolve: We validate states using this data which is based on Google’s i18n address repository. Please check to ensure that the code provided matches what is in this data.
- phone: phone_number_validation_error - format is incorrect
- Explanation: The phone number provided is either invalid or not in the correct format.
- How To Resolve: Please ensure that all phone numbers are in E.164 formatting. Often this just involves dropping leading 0s and adding + symbol.
- address_type: Unsupported value. Expecting "shipping_address" or "billing_address"
- ReCharge Specific:
- 'Untranslated country in billing address. Please change to 2 letter ISO code'
- 'Untranslated state/province in billing address. '
- 'Untranslated country in shipping address. Please change to 2 letter ISO code'
- 'Untranslated state/province in shipping address. '
- Explanation: The state and/or country code provided is either invalid or not in the correct format.
- How To Resolve: We validate states using this data which is based on Google’s i18n address repository. Please check to ensure that the codes provided match what is in this data.
Payment Methods
Required Fields
|
Field |
Required |
Format |
|
cc_holder |
String |
|
|
cc_type |
string |
|
|
cc_exp_date |
string |
|
|
token_id |
required |
string |
| origin | required | object |
- Potential Error Messages
- cc_exp_date: Expecting string or null
- How To Resolve: You can set this field to optional in Ordergroove or update your dataset and/or transformation process to ensure you're sending this value as a string or null (eg not an integer)
- cc_exp_date: Expecting MM/YYYY date format
- How To Resolve: You can set this field to optional in Ordergroove or update your dataset and/or transformation process to ensure you're sending this value in the expected format of MM/YYYY
- token: Missing stripe customer token
- Explanation: There is no stripe token for the payment method which is required to create a subscription using that payment method.
- How To Resolve: If the payment method is not used - remove it. Otherwise, you may need to look in Stripe's system or contact them (or ReCharge) directly
- cc_exp_date: Expecting string or null
- Only for JSON error file retries:
- origin: Billing address does not exist
- Explanation: The ID of the billing address associated with this payment method has not been created and/or does not exist within the current customer's migration data.
- How to resolve: double-check IDs and addresses in your system. If correct but you can't find the correct IDs provide your own IDs as long as they're sure to be unique and connect the billing address to the payment method correctly.
- origin: Billing address does not exist
Subscriptions
Required Fields
|
Field |
Required |
Format |
|
customer |
required |
string |
|
next_order_date |
required |
YYYY-MM-DD |
|
live |
required |
boolean |
|
merchant_order_id |
required |
string |
|
product |
required |
string |
|
every |
required |
string |
|
every_period |
required |
Days, Weeks, or Months |
|
price |
required |
string with two decimals |
|
quantity |
required |
integer |
|
offer_id |
required |
string |
|
origin |
required |
object |
- Potential Error Messages
- price: Expecting string representing a decimal number
- Explanation: In order to create a Shopify subscription contract you need to provide a price for the subscription. This price will not be used when charging the customer and currently is inconsequential to the operation of the subscription.
- How to resolve: Update the price on the subscription
- next_order_date: This is a required field for live subscriptions
- Explanation: This is required for both Shopify Subscription Contract creation as well as the Ordergoove import
- How to resolve:
- next_order_date: Expecting date string with format YYYY-MM-DD
- Explanation: You supplied a date but not in our required format
- How to resolve: Please update this field to be in the following format: YYYY-MM-DD
- next_order_date: Date is in the past
- Explanation: We don't have a time machine xD. This happens sometimes if the file hasn't been updated recently.
- How to resolve: Check your existing system to see what the current next order date is currently. If you've just done a dry run only -you can leave as is. If the error file was created during a live migration run you'll want to change the date in the error file to match the new date in your other system
- start_date: Expecting date string with format YYYY-MM-DD
- Explanation: You supplied a date but not in our required format
- How to resolve: Please update this field to be in the following format: YYYY-MM-DD
- canceled: Expecting date-time string with format YYYY-MM-DDThh:mm:ss
- Explanation: You supplied a date but not in our required format
- How to resolve: Please update this field to be in the following format: YYYY-MM-DDThh:mm:ss
- origin: Shipping address does not exist
- Explanation: The ID of the shipping address associated with this subscription has not been created and/or does not exist within the current customer's migration data.
- How to resolve: double-check IDs and addresses in your system. If correct but you can't find the correct IDs provide your own IDs as long as they're sure to be unique and connect the shipping address to the subscription correctly.
- origin: Payment does not exist
- Explanation: The ID of the payment method associated with this subscription has not been created and/or does not exist within the current customer's migration data.
- How to resolve: double-check IDs and addresses in your system. If correct but you can't find the correct IDs provide your own IDs as long as they're sure to be unique and connect the shipping address to the subscription correctly.
- price: Expecting string representing a decimal number
Generic
- field: Expecting string
- field: Whitespaces are not allowed