Shopify data requirements
Learn what data from your Shopify store we require, so that you can ensure your returns are handled smoothly.
Our Shopify integration can only sync data that is available in your Shopify store. Depending on your ReBound product setup, more or less data will be required.
For example:
- Product (item) information is needed to display it to your consumers or CS agents in our portals.
- Product (item) information is required for generating customs documentation when cross-border shipments are needed for your returns. Common examples include shipments between the US and the UK or EU countries and their non-EU neighbors (such as the UK, Switzerland or Norway).
- The consumer’s data (e.g., address, contact info) is used to pre-fill their details in our portal and determine the available carrier options for their return. This data must be collected when the consumer is placing the order.
Ensure data completeness
To avoid manual work, exceptions, delays or additional costs, please ensure this data is complete and accurate. This allows us to execute our processes smoothly and quickly.
How to update product data in Shopify
A few options include:
- Export, Edit in CSV, Re-import: Shopify allows you to export product data to a CSV file, make edits, and re-import the updated file.
- Use uther apps: Utilize third-party apps from the Shopify App Store to manage and edit product data. If you use a PIM (or other software to manage your product catalogue), you may be able to update the product data and sync it back to Shopify.
- From the Shopify admin: Edit product details directly in the Shopify admin for each individual product. The screenshots in each section below show where each relevant data attribute can be found.
Reading this article
Below you will find tables with the product and consumer data that is required. Each table has a few columns:
- No. This column assigns a number to each field. The screenshots below show where each field can be edited, identifying fields using this number.
- Shopify field. Which field in Shopify this data is retrieved from.
- Relevance for ReBound. How we use this data.
- Required? This column explains whether a field is mandatory or optional. Some fields are always mandatory, while others are only required if certain ReBound products are enabled.
Each table is accompanied by screenshots showing you where the data is stored in Shopify, so you can find it or update it easily.
Product data
Data about the items (products) in an order is required for many of our solutions, including returns initiation (registering a return, generating a return label), hub processing and cross-border shipments.
Products without variants
This applies to products without variants (i.e., no different sizes or colors).
| No | Shopify field | Relevance for ReBound | Required? |
|---|---|---|---|
| 1 | Product name | Product name, needed to display in consumer portal and hub software. | Mandatory - Always required. |
| 2 | Product SKU | Unique item identifier, needed for many internal processes. | Mandatory - Always required. |
| 3 | Product EAN | Product barcode, needed to scan product in hub. | Mandatory - Always required. |
| 4 | Product size | Displayed in consumer portal to help consumers identify their product during return registration. | Mandatory if consumer portal enabled. |
| 5 | Product color | Displayed in consumer portal to help consumers identify their product during return registration. | Mandatory if consumer portal enabled. |
| 6 | Product price and currency (presentment money) | Price of the item (what the consumer paid). Displayed in the consumer portal. | Mandatory if consumer portal enabled. |
| 7 | Currency for the cost above. | Mandatory if consumer portal enabled. | |
| 8 | First picture for the product | Product picture. Shown to consumer in the consumer portal and to hub operator in | Mandatory if consumer portal enabled. Mandatory for processing level 2+ (item-level processing) |
| 9 | Product cost and currency (different from price) | Cost of the item. This is the value declared to the authorities for customs clearance. | Mandatory for cross-border lanes. |
| 10 | Currency for the cost above. | Mandatory for cross-border lanes. | |
| 11 | Harmonized system (HS) code | HS code. Required for customs documentation. | Mandatory for cross-border lanes. |
| 12 | Region / country of origin from product / product variant. | Product country of origin (where it was produced). Required for customs documentation. | Mandatory for cross-border lanes. |
| 13 | Product weight | Product weight. Required for customs documentation. | Mandatory for cross-border lanes. |
| 14 | Product category | Used for Item Sorting decisions | Optional, depends on client’s level of processing and processing decisions |
| 15 | Product vendor | Used for Item Sorting decisions | Optional, depends on client’s level of processing and processing decisions |
Updating this data in the Shopify admin:
Products with variants
This applies to products with variants (i.e., different sizes or colors).
| No | Shopify field | Relevance for ReBound | Required? |
|---|---|---|---|
| 1 | Product variant name | Product name, needed to display in consumer portal and hub software. | Mandatory - Always required. |
| 2 | Product variant SKU | Unique item identifier, needed for many internal processes. | Mandatory - Always required. |
| 3 | Product variant EAN | Product barcode, needed to scan product in hub. | Mandatory - Always required. |
| 4 | Product variant size | Displayed in consumer portal to help consumers identify their product during return registration. | Mandatory if consumer portal enabled. |
| 5 | Product variant color | Displayed in consumer portal to help consumers identify their product during return registration. | Mandatory if consumer portal enabled. |
| 6 | Product / Product variant price and currency (presentment money) | Price of the item (what the consumer paid). Displayed in the consumer portal. | Mandatory if consumer portal enabled. |
| 7 | Currency for the cost above. | Mandatory if consumer portal enabled. | |
| 8 | First picture of the product / product variant. | Product picture. Shown to consumer in the consumer portal and to hub operator in | Mandatory if consumer portal enabled. Mandatory for processing level 2+ (item-level processing) |
| 9 | Product / Product variant cost and currency (different from price) | Cost of the item. This is the value declared to the authorities for customs clearance. | Mandatory for cross-border lanes. |
| 10 | Currency for the cost above. | Mandatory for cross-border lanes. | |
| 11 | Harmonized system code from product / product variant. | HS code. Required for customs documentation. | Mandatory for cross-border lanes. |
| 12 | Region / country of origin from product / product variant. | Product country of origin (where it was produced). Required for customs documentation. | Mandatory for cross-border lanes. |
| 13 | Weight from product / product variant. | Product weight (in grams; if required, will be converted by the Shopify integration). Required for customs documentation. | Mandatory for cross-border lanes. |
| 14 | Product category | Used for Item Sorting decisions | Optional, depends on client’s level of processing and processing decisions |
| 15 | Product vendor | Used for Item Sorting decisions | Optional, depends on client’s level of processing and processing decisions |
Updating this data in the Shopify admin:
Adding customs information
Customs data is disabled by default in Shopify. You can enable it by clicking on "Add customs information" (in the product or product variant screen).
Customer data
A second set of data that is required is the consumer's (i.e., the end customer who purchased the products from your store).
| Field | Relevance for ReBound | Required? |
|---|---|---|
| Email address | Required for ReBound API. Used to identify orders for a consumer in our portals. | Mandatory - Always required for ReBound API. |
| Country | Required for ReBound API. Used to determine carrier services for a return. | Mandatory - Always required for ReBound API. |
| Name (first + last) | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory if consumer portal is enabled. |
| Phone number | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory if consumer portal is enabled. |
| Street & house number | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory if consumer portal is enabled. |
| Postcode | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory if consumer portal is enabled. |
| City | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory if consumer portal is enabled. |
| Province | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Mandatory for some countries (e.g., US, CA, AU) |
| Company | Used to pre-fill consumer data for a return or use it in case of incomplete data during return registration. This data missing will increase friction in the consumer experience. | Optional. |
Updated 4 months ago