Integration Overview
Integration
Shopify Admin - Order Details
| SYN_Order_Details.jpg | ✓ Order created as per customer transaction✓ Custom properties: Global-e order id✓ “Global-e Carrier Service” shipping source with the actual shipper✓ Global-e payment gateway✓ Fraud approval order tag✓ End-customer billing and shipping |
|---|
Integration Overview: With Global‑e
Limitations
- Available on Shopify Advanced and Plus plans.
- Refund an order using a gift card only in Shopify Plus plan.
Integration Details
Before beginning the setup, ensure the following conditions are met:- A Shopify Sandbox is available for pilot testing and rollout preparation.
- Fraud approval for export from Shopify must be fulfilled based on the order tag, not the “PAID” status.
-
Install the following Global‑e Apps:
- CrossBorder app
- Payment app
-
Set up Alternative Payment Methods: Enable Shopify Payments.
Scripts tags and theme includes (e.g. checkout) automatically added. This only applies to checkout for headless setups
Downstream Flow Behind Shopify
Order Flow Adjustments
| Item | Requirements |
|---|---|
| Order export from Shopify | Fraud approval order tag “Globale::Approved” |
| Order identification – Finance | Shopify Order payment gateway “Global‑e Payments” |
| Order identification – Shipping | Shopify Order shipping_lines “code“ contains “GLOBALE”: e.g. “123_GLOBALE_HIDDEN_DDP“ Or “title” will be service level such as “Standard Courier” Or “source”: “Global‑e Carrier Service“ |
| Order Processing - Shipping | Shopify order number required (not order name or id) for processing on GE PortalGlobal‑e order id stored as order note attribute “GEOrderId” Using SKU or UPC Shopify Product field for fulfilment? |
| Disable OMS updates to Shopify | If using GE Admin : Fulfilment updates – will be fed back by Global‑e Refund updates – will be fed back by Global‑e |
Update Product Details from Shopify to Global-e
This section described the Global-e flow for updating product details from Shopify to Global-e. To update product details from Shopify to Global-e:-
Each time a product is added or updated in Shopify, Global-e gets the
ProductUpdatedwebhook from Shopify. - Global-e writes the message to Kafka.
- A Global-e service reads the message from Kafka.
-
Kafka calls the following Shopify APIs:
GraphGetInventoryItemsGetProductService -
For each variant, Global-e creates a product based on Webhook Data (
apiProduct). -
After validation, the Global-e service calls the internal Global-e API
SaveProductListAPI(updatedProductsis the list of variants that was just created).
Shopify-to-Global-e Field Mapping
When performing an update, Global-e reviews the following fields. This process applies to all products.| Shopify Field | GE System Field | Description |
|---|---|---|
| Title | Name | The name of the product. |
| BodyHtml (HTML removed) | Description | Product description in plain text. |
| Variant ID | ProductCode | Unique identifier for each product variant. |
| Variant SKU or Variant Barcode | ProductCodeSecondary | Secondary identifier, often the SKU or Barcode, depending on the configuration on the Global-e side. |
| Product ID | ProductGroupCode | Identifier for the product group. |
| Variant Price | OriginalSalePrice | The sale price of the product. |
| Variant CompareAtPrice | OriginalListPrice | The original list price of the product. |
| Product Images | ImageURL | URL of the product’s primary image. |
| https://{AdminDomain}/products/{Product Handle}?variant={Variant ID} | URL | URL to the product page in your Shopify store. |
| Tags | Categories, ProductClassCode | Product categorization based on tags. |
| InventoryItem CountryCodeOfOrigin | OriginCountryCode | The country of origin of the product. |
| InventoryItem RequiresShipping | IsVirtual | Determines if the product is a virtual good. |
| InventoryItem HarmonizedSystemCode | GenericHSCode | Harmonized System Code for international shipping. |
| Options | Attributes | The product attribute. The product can have up to three attributes, for example, size + colour + material. |
| Title | productNameEnglish | When using translation, the Shopify title is translated to productNameEnglish. |
| BodyHtml (HTML removed) | productDescriptionEnglish | When using translation, the Shopify Product Description is translated to productDescriptionEnglish |
| Tags | IsBlockedForGlobalE | Global-e has blocked the product based on Global-e’s MAS internal parameter and Shopify tags. |
Integration Summary
- Global‑e creates an account for the merchant in the Global‑e system.
- Global‑e requests user access and permissions to the merchant’s site.
- The merchant installs the Global-e CrossBorder application.
- The merchant installs the Global-e Payment application.
- Optional: The merchant installs the required 3rd party applications (geolocation, search, analytics, and more).
- The merchant performs the required website adjustments (country selector, geolocation, and more).
- The merchant and Global-e gradually enable Global-e countries, first by validating the functionality of a few operated countries, and then adding the remaining countries.
Additional Integration Features
Analytics
Use the Shopify checkout object to map Shopify data to any Analytics party. Example of GA4 Mapping| Shopify Native | Google Analytics 4 | Description |
|---|---|---|
checkout.line_items[line_item_count].product_id | Item_id | Product SKU |
checkout.line_items[line_item_count].title | Item_name | Product name |
checkout.presentment_currency | Currency | Local currency |
checkout.line_items[line_item_count].price –``checkout.line_items[line_item_count] –``.discount_allocations[line_item_count].amount | Price | Product price in local currency.You must add the logic to deduct discounts from the product price. |
checkout.line_items[line_item_count].quantity | Quantity | Product quantity |
checkout.order_id | transaction_id | Order ID |
checkout.subtotal_price | Value | Order value (excluding shipping and tax) in local currency. |
checkout.total_tax | Tax | The customer paid the tax in local currency. |
checkout.shipping_rate.price | Shipping | The customer paid the shipping cost in local currency. |
Marketing Feeds (Liquid Storefronts)
Domestic Feeds To prevent price mismatches between the feed and the prices appearing on the storefront due to automatic geo-IP detection and redirection features, you must update the product links in their domestic feeds. All domestic product links should append the country parameter with the 2-letter country code of their domestic market. Example: For a US merchant: https://www.mystore.com/products/red-shirt?country=US Failure to do this may result in warnings from Google, after which they will prevent your from submitting marketing feeds. International feeds There are 3 main methods you can use to generate an international Marketing feed:- Using supported Shopify apps (recommended).
- Manually generating the feed yourself by writing a custom script or program, or creating an Excel sheet.
- Using a 3rd party service such as Feedonomics or Channel Advisor.
- https://shopify.dev/custom-storefronts/internationalization/international-pricing
- https://shopify.dev/api/admin-graphql/2022-01/queries/priceList
- Get the price data via Shopify Product Feeds feature. This is likely the most efficient method to retrieve all product pricing data. For more information see Developer Changelog, Product Feeds, and Unidirectional Product Synchronization
- Get the price data via Shopify storefront API. For more information see Query Product Prices.
-
Get the price data via Shopify Admin API.
-
Option 1:
- Step 1: Get the price ID for each market. For example, CA Price, AU Price etc. See Pricelists API.
- Step 2: Get the localized price for each product, using the price IDs. See Pricelist API
-
Option 2: use the
contextualPricingrequest to retrieve the price for each variant and country combination. For example, replacingProductVariantand country with each request:These queries can be set up as bulk operations which do not count against rate limits but may take significantly longer to complete.
-
Option 1:
- Merchants in PCE countries: You should generate your feeds at 5:00 AM UTC to ensure the daily FX price updates are completed. This configured time may shift to an hour earlier during daylight savings time.
- Merchants in CBS countries: You should generate your feed at 1AM UTC to ensure the updated country FX rate is in Shopify.
- Shopify’s Deep Linking feature: Include a country parameter in your product links (https://help.shopify.com/en/manual/markets/international-domains/directing-customers/deep-links) Example: [https://merchant_url/products/t-shirt?country=DE](http:// https://merchant_url/products/t-shirt?country=DE) [Product page for Germany]
-
Shopify’s subfolder feature. This feature is required if you plan to use the Shopify translation features and requires additional configuration by Global‑e.
Example:
- https://merchant_url/en-de/collections/products/t-shirt [Product page for Germany]
- https://merchant_url/en-ca/collections/products/t-shirt [Product page for Canada]
For headless merchants: Any country-specific URL logic for your Shopping feeds must be implemented by your development team, as the above-documented methods only work for Liquid-based storefronts out of the box. For more information, see the Headless section under Shopping / Marketing Feeds.
Fixed Price Management
Overview
The Fixed Price Management feature lets you manage your local market prices by uploading a file describing the fixed prices for specific products and territories. Note that these prices override Shopify pricelists set via API, ignoring country or currency restrictions. In the past you could only submit new prices to update immediately. Now you can select a date and time for your price submissions to go into effect. The following figure shows the Fixed Price Management screen:
Uploaded File Table
The following figure shows the uploaded file table:
Accessing Fixed Price Mangement
To access the Fixed Price Management feature- Navigate to Merchants > Product Management > Fixed Price Management from the top menu.
- Select a merchant from merchant menu located at the top of the page.
Setting Up Your Price Sheet
Price sheets you submit must be in CSV format, and you can download a sample CSV format to use as the basis for your submissions by clicking Download Sample. The sample file includes an example and explanation of each value. Price sheets require the following information:| Header | Description | Example |
|---|---|---|
| sku | Enter the Product SKU as it appears in your product catalogue. The SKU may not include spaces.If you are using barcodes instead of SKU, this field must contain the barcode. However, leave the column name as “SKU”. | AD-01-white-6 |
| variant_id | Enter the Product Variant ID, as assigned in your product catalogue.If this field is empty, the SKU field must be populated. | 36485954240671 |
| country_code | Enter the ISO-2 country code to indicate the country relevant to this price.For instance, DE (Germany), US (USA).If this field is empty, the currency_code field must be populated. | DE |
| currency_code | Enter the 3-char currency code (ISO-4271) to indicate the currency relevant for this change.For instance, USD (US dollar), AUD (Australian dollar), EUR (Euro), CHF (Swiss franc), and more.This field is required. | EUR |
| price | Enter the fixed price value for the product. This value can only contain numbers.CautionDo not include commas in the prices you list in the CSV file as the prices will not parse correctly.Keep empty to remove a previously set fixed price without setting a new one. In this case, the dynamic price conversion rules set for the current country apply. | 29.95 |
| compare_at_price | Enter the fixed price value of the product before the discount. This value can only contain numbers.CautionDo not include commas in the prices you list in the CSV file as the prices will not parse correctly.Keep empty to remove a previously set fixed price without setting a new one. In this case, the dynamic price conversion rules set for the current country apply. | 49.95 |
Populating Your File
Once you’ve set up your file, you can populate it.Global-e does not support uploading XLS files. Enabling Editing in your CSV file may cause your security settings to change the CSV file format to XLS. Before uploading a file, verify that you’ve saved it in the CSV format.
Including commas in your file will not upload.
- Add a list of products with one product per row.
- Save your file in CSV format.
Submitting Price Sheets
To submit price sheets-
Select one of the following:
- Submit Now – Skip to Step 2.
- Schedule Upload – Set your start date and time.
- Upload your csv file by clicking Upload CSV File.
- Click Submit. The file is added to the table showing all the uploaded price sheets.
- (Optional) If your file fails uploading, resolve the issue and continue with Step 5. See Fixing Validation Errors to identify and resolve the cause of your failed upload.
- Provide an email address.
You can sort the uploaded price sheets by date using the From Date and To Date fields to the right of the email field.
Rescheduling Your Upload Date
You can edit your upload schedule as long as your file in the Ready for upload stage and has not completed uploading. To reschedule your upload date- Click image3.png located at the far right in a row.
- Reschedule your upload and click Update.
Cancelling a Publish
You can cancel a publish as long as your file has not completely unloaded. You can do by this by clicking image4.png located at the far right in a row.Reviewing Current Fixed Prices
You can review your current fixed prices by downloading a CSV file containing the current fixed prices. To this, click image5.png located near the upper right corner of the table.Tracking File Status
The Fixed Price Management feature displays the file upload and file validation statuses when you upload your files. This section describes these statuses.File Upload Statuses
The file upload status describes whether your file has uploaded or not, due to an error. The file upload statuses are shown in the table below:| Status | Description |
|---|---|
| Ready for Upload | A submitted file containing some valid prices ready for upload on the scheduled date. |
| Uploading | A submitted file in the process of being uploaded. |
| Uploaded | An uploaded file with successfully updated prices. |
| Partially Uploaded | An uploaded file with a combination of successfully updated and invalid prices. |
| Failed | A completely invalid file. Invalid files are not uploaded. |
| Canceled | A submitted file that a user manually canceled. |
File Validation Statuses
The file validation status describes whether your file has been validated or not. The file validation statuses are shown in the table below:| Indicator | Status | Description |
|---|---|---|
| image6.png | Valid | File validated |
| image7.png | Partially Valid | Some validation errors were found |
| image8.png | Invalid | No prices were accepted |
Fixing Validation Errors
This section describes the validation errors that may occur when you upload your price lists.| Error | Error Message | Resolution |
|---|---|---|
| Too many rowshave the same group key. Duplicates of {Sku}_{VariantId} exceeded max allowed - 500 (near double size of countries count in the database). | The same SKU and Variant ID appear more than once for the same country on line [Line Number]. Delete duplicate rows and retry. | |
| Invalid SKU - SKU contains whitespace. | Invalid SKUs found in line: [Line Number]. The SKU contains whitespace. Amend the SKU and retry. | Make sure to use unique names for the Product Code and Secondary Product Code. If the file contains an SKU and not a variant_id and the SKU is duplicate, the row is skipped. If the file contains both, an SKU and a variant_id , and the SKU is duplicate or does not exist, the row is skipped. We recommend uploading a file with either the SKU or the variant_id, not both. It is best to use variant_id and not an SKU since variant_id is unique in the Global‑e database whereas SKU is not unique (can be a duplicate SKU). |
| Empty SKU and Variant ID - Both SKU and variant ID are missing. | Both SKU and Variant ID are missing in line: [Line Number]. provide at least one to proceed. | See Invalid SKU - SKU contains whitespace. |
| Empty Country and Currency Code - Missing country or currency code. | Both Country and Currency codes are missing in line: [Line Number]. Please provide at least one to proceed. | See Invalid SKU - SKU contains whitespace. |
| Invalid country code | Invalid or not operated country code: [Line Number]. Provide a valid ISO-2 code (e.g., DE for Germany, US for USA) and make sure the country is operated by Global-e, then retry. | If the country, currency, or prices are empty, the entire CSV file fails. Make sure the file contains the correct information. |
| Invalid currency code | Invalid currency code: [Line Number]. Provide a valid ISO-4217 code (e.g., USD, EUR) and retry. | If the country, currency, or prices are empty, the entire CSV file fails. Make sure the file contains the correct information. |
| Invalid price | Invalid price in line: [Line Number]. Prices must be numeric. Delete the field content to remove the previously fixed price stored and type the new value. | |
| Price cannot be set to zero (X2 for ListPrice/ SalePrice) - the price is zero. | Price cannot be zero, in line: [Line Number]. Ensure the price is greater than 0 or leave the field empty and retry | |
| Country-currency mismatch | Currency mismatch, in line: [Line Number]. The currency code does not match the country. Use the correct currency for that country and retry. | |
| Non-numeric product code | Non-numeric product code in line: [Line Number]. Provide a numeric product code and retry. | |
| Duplicated SKU | Duplicated SKU in line: [Line Number]. Remove the duplicate SKU and retry. | See Invalid SKU - SKU contains whitespace. |
| No matching SKU and variant product found in the database. | Missing SKU or Variant ID in line: [Line Number]. No matching product was found in the database. Check the SKU and Variant ID and retry. | Make sure that the SKU / variant_id exists in Shopify before uploading the CSV file to Global‑e. (Make sure you have uploaded the product to Shopify before uploading the CSV file to Global‑e). |
| Product code or secondary product code is not unique. | NA | See Invalid SKU - SKU contains whitespace. |
| The file is not in CSV format. | Make sure to save your file in CSV format. | |
| Wrong header | NA | Make sure the header is set as follows: sku,variant_id,country_code,currency_code,price,compare_at_price |
| Spaces in the data | NA | Make sure that the data and header in the file do not contain spaces. |
Fixed Prices Upload via API
The Upload Fixed Prices API lets you upload your list of fixed prices to Global-e. In addition, you can check the upload status and retrieve the error file.Prerequisites
Prepare your CSV file containing your list of fixed prices and populate it. Each column in your CSV file must have the following headers, respectively:- SKU
- Variant_id
- Country-code
- Price
- Compare_at_price
Authentication: MerchantGUID
To implement API calls with Global-e the only required information is themerchantGUID provided by Global-e.
For authentication, make sure to include your Merchant GUID as part of each call or as part of the header so that Global-e can verify your identity. Make sure to use the appropriate merchantGUID, depending on the Global‑e integration environment used for development or production purposes. See Global-e Environments.
MerchantGUID in URL
Add your MerchantGUID as part of each API URL.
MerchantGUID as part of the header
Add your MerchantGUID as part of the header as illustrated below.
Flow
- Call the UploadFile endpoint to upload your Fixed Prices CSV file to Global-e.
- Call the GetUploadedFileDetails to get the details of the file you uploaded and verify the Upload status.
- Call GetFileWithValidationErrors to retrieve the file containing the errors.
RunId (Global-e ID) is created.
UploadFile
Upload your Fixed Price CSV File to Global-e. MethodURL<Fixed Price CSV File> (from data)
Response
| HTTP Status Code | Message | Description |
|---|---|---|
400 | { “Message”: “CSV file contains rows with invalid data. Make sure the file has the correct format and contains the correct information.”, “Errors”: [ “,43416058200314,,PLN,201,201,400”, “,43416058200314,FR,EUR,301,401,400” ] } | This file has the wrong column format and/or values. Check the rows that returned the error. |
400 | ”Only one file should be uploaded. Make sure to upload only one file.” | This endpoint expects only one file per request. |
400 | ”The uploaded file is empty and cannot be processed. Make sure to populate the file correctly.” | The file is empty or did not load correctly. |
400 | ”The format of the uploaded file is incorrect. Please upload a CSV file. Make sure to save your file to .csv format.” | The uploaded file had the wrong extension. |
500 | ”Failed to upload the file. Please contact Support.” | This is an internal error. If it appears, please contact Support. |
GetUploadedFileDetails
This endpoint returns the details of the uploaded file, including the upload completion status. PATH: [https://<domain address> /PCE/GetUploadedFileDetails?merchantGUID=<Merchant GUID>&runId=<GUID provided by Upload file endpoint>](https://<domain address> /PCE/GetUploadedFileDetails?merchantGUID=<Merchant GUID>&runId=<GUID provided by Upload file endpoint>) TYPE:GET
RESPONSE:
| Parameter | Type | Description |
|---|---|---|
RunId | string | The Global-e file IdSample UID format: 84f9929c-1ea1-4edd-bc56-c4ef73a92e88 |
FileName | string | The file name given by the merchant in CSV format |
DateCreated | string | The file upload date. |
Status | string | Statuses:Submitted: When the file is first uploaded, the status is set to “Submitted”. (Submitted: 0%)Processing: As the file is being uploaded, the status changes to Processing. (Example: Processing: 64%)Completed: If the upload finishes without errors, the status changes to Complete. (Completed: 100%)Failed: If the upload fails due to an error, the status changes to Failed. See Errors to troubleshoot the issues. (Failed: 0%) |
HasErrors | bool | Whether the file upload has errors. |
CompletionPercentage | Integer | Shows the progress of the file upload completion in per cent.Note: The integer value is a number without the per cent symbol.Example: “CompletionPercentage”: 100 |
| HTTP Status Code | Message | Description |
|---|---|---|
400 | ”Cannot find the information for the current runId!” | The application cannot find the upload with this RunId.This can happen if the file did not upload correctly, the RunId is empty, or if the RunId has been modified.Verify that your file has uploaded correctly and returns a valid RunId. |
500 | ”Failed to get the uploaded file’s {runId} for PCE.” | Unexpected internal error during file upload. Please contact Support.PCE: Price Calculation Engine |
GetFileWithValidationErrors
This endpoint always returns a CSV file with the headers. If there are errors, the file contains the rows where errors were identified. PATH: [https://<domain address> /PCE/GetFileWithValidationErrors?merchantGUID=<Merchant GUID>&runId=<GUID provided by Upload file endpoint>](https://<domain address> /PCE/GetFileWithValidationErrors?merchantGUID=<Merchant GUID>&runId=<GUID provided by Upload file endpoint>) TYPE:GET
RESPONSE:
| HTTP Status Code | Message | Description |
|---|---|---|
400 | ”Cannot find the information for the current runId!” | The application cannot find the upload with this RunId.This can happen if the file did not upload correctly, the RunId is empty, or if the RunId has been modified.Verify that your file has uploaded correctly and returns a valid RunId. |
400 | ”Failed to get the validated file containing the rows with errors for PCE.” | Unexpected internal error during file upload. Please contact Support.PCE: Price Calculation Engine |
Set up a New Price List
The following procedure details the steps required to set up a new list of fixed prices and upload it to Global‑e.Step 1. Prepare your Price List in CSV Format
In your CSV file, make sure to name the columns headers A through F, as shown below:
Field Descriptions and Requirements
| Headers / Fields | Description |
|---|---|
| SKU | Enter the Product SKU as it appears in your product catalogue. The SKU may not include spaces.If this field is empty, the Variant ID field must be populated. |
| Variant ID | Enter the Product Variant ID, as assigned in your product catalogue.If this field is empty, the SKU field must be populated. |
| country_code | Enter the ISO-2 country code to indicate the country relevant to this price.For instance, DE (Germany), US (USA).If this field is empty, the currency_code field must be populated. |
| currency_code | Enter the 3-char currency code (ISO-4271) to indicate the currency relevant for this change.For instance, USD (US dollar), AUD (Australian dollar), EUR (Euro), CHF (Swiss franc), and more.If this field is empty, the country_code field must be populated. |
| price | Enter the fixed price value for the product. This value can only contain numbers.CautionDo not include commas in the prices you list in the CSV file as the prices will not parse correctly.Keep empty to remove a previously set fixed price without setting a new one. In this case, the dynamic price conversion rules set for the current country apply. |
| compare_at_price | Enter the fixed price value of the product before the discount. This value can only contain numbers.CautionDo not include commas in the prices you list in the CSV file as the prices will not parse correctly.Keep empty to remove a previously set fixed price without setting a new one. In this case, the dynamic price conversion rules set for the current country apply. |
Step 2. Populate your CSV File
When enabling editing in your CSV file, your security settings may change the CSV file format to Excel. Make sure to save your file back to CSV before uploading it to Global-e.
-
Add your list of products, one product per row with the relevant information in the relevant column, according to the Field Descriptions and Requirements detailed in ???.
To ensure optimal accuracy, make sure to use the following values when populating fixed price data in your CSV file. Caution Do not include commas in the prices you list in the CSV file as the prices will not parse correctly. **Price per country and currency:**Header: sku,variant_id,country_code,currency_code,price,compare_at_price Value: {{sku}},{{variant_id}},DE,EUR,6,6OR (based on
variant_id):Header: sku,variant_id,country_code,currency_code,price,compare_at_price Value: ,{{variant_id}},DE,EUR,6,6 **Price per currency (affects all countries with the same currency):**Header: sku,variant_id,country_code,currency_code,price,compare_at_price Value: {{sku}},{{variant_id}},,EUR,6,6OR (based onvariant_id):Header: sku,variant_id,country_code,currency_code,price,compare_at_price Value: ,{{variant_id}},,EUR,6,6 - When done, make sure to save your file as CSV.
Multi-Hubs
Shipping from Multiple Countries using a Single StoreOverview
You can use more hubs in various countries alongside your primary hub. This approach enables faster delivery times to customers and cost reduction for the merchant (Shipping, D&T). You can operate hubs from different Shopify stores, but this only allows a fixed setup (one hub per destination) and adds the overhead of managing multiple stores.Multi Hub Models
The Global-e Multi-hub solution for Shopify allows brands to fulfil orders to Global‑e operated markets from different locations worldwide. The following operational models are supported (depending on brand requirements).| Fixed model | Each warehouse serves only specific countries |
|---|---|
| Fallback model | Order fulfilment is performed at the local/regional warehouse used to serve specific countries but when stock is not available, order fulfilment falls back to the main warehouse. |
| Fully Dynamic model | Each warehouse can be used to fulfil orders to any country |
Currently, the Shopify routing logic prioritises the location based on the distance between the hub and the customer shipping address. Therefore, currently, orders must ship in their entirety from a single location.
- Operations Countries to be served from each hub Options available for outbound and inbound shipping
- Technical Order routing from checkout decision
- Legal & Finance The Merchant and Global-e both have a local entity or registration in the country Goods are owned by the merchant at the point of sale to Global-e Reconciliation and invoicing between the new contracting parties
Scenarios
| Title | Description | Known issues / limitations |
|---|---|---|
| Multi storefronts with multi merchants | Separate GE merchants, each configured on separate site/storewhen the origin is identified user is redirected to relevant store to complete checkoutCart and order history typically not maintained between sites which makes it a poor solution or create additional effort | catalog and restrictions configurations duplication |
| Single merchant no split | Single merchant on one site with relevant checkout and billing rules loaded based on the cart hub country. | dual setups with EU only currently 1 reconciliation currency for all orders |
Prerequisites
Make sure you have the Shopify new order flow configured. Provide the following information to Global-e:| Topic | Notes |
|---|---|
| Logistics map - origins and destinations | Countries with hubs/stores ship from: Mapping of destinations to ship to from each origin All locations are serving the same products With fallback from the central warehouse if not available locally Note that currently, Shopify does not support ship-to-store or pick-up API/Admin coverage or requirements from each new location (same usual rules regarding API / Full WYOL) |
| Carriers | The list of carriers for outbound and returns logistics |
| Storefront architecture | using one or multiple websites |
| Stock decision logic | Make sure to choose the country from which to ship the stock before checkout, except for locations within the EU. |
| Settlement Currency | Full order multi-hub: For a single site, the reconciliation currency must be the same as your default Merchant currency. |
| Legal/Commercial | Legal : The local entity or registration to be used for reconciliation Local stores and warehouses must be brand-owned; they may not be partners distributors, or franchises. |
Integration Flow and Responsibilities
This section details the activities that the Merchant and Global-e need to perform to prepare the setup for the feature. To prepare the setup for this feature:-
The Merchant:
- Sets up Shopify locations with product inventory in Shopify.
- Sets up Shipping Profiles in Shopify.
- Sets up Order Routing Rules in Shopify.
- Global-e configures the feature for you on the Global-e side.
- The Merchant and Global-e collaborate to align and address the financial and operational requirements.
Shopify Settings
Set up the Location of Each Hub
Create a location for each local hub. Setup Locations (Settings → Locations)
Set up Product Availability in Each Location
Define the stock availability of each product or variant per location. Products → For Each Product Variant

Set up Shipping Profiles
Assign the shipping profile to each location.- Define the markets to be fulfilled from the location
- Rate set a ‘Global-e Carrier Service’ (the relevant shipping services are configured on the Global-e side)


Set up Order Routing Rules
Define the order routing logic for the different locations as configured in your Shopify store, based on the selected operation model (fixed, fallback, or fully dynamic). Note that Global-e can request for this feature to be enabled if it is not already available in your store, Settings → Shipping and delivery → Order routingSince this is still an Early access feature, it requires that Shopify adds it to the merchant store. Shopify documentation: https://help.shopify.com/en/manual/shipping/setting-up-and-managing-your-shipping/order-routing


- Select Ship from the closest location OR Stay within the destination market
Set up Stock Availability for Each Hub
To make sure that the Shopify routing logic can decide based on the stock available in each hub, clear the option “Continue selling when out of stock”.
Taxes and Duties
Global-e configures the taxes and duties for Merchants with domestic sales in the US or Canada.Mapping Orders to 3rd Party Systems
Introduction
This guide provides instructions on how to import Global-e orders from Shopify to systems such as an OMS/ERP, WMS or middleware. Key Shopify order data and high-level downstream order flow are illustrated for mapping purposes. If you are currently running live Global‑e’s previous Shopify integration and upgrading to the new version integrated natively into Shopify’s checkout, see Migrating Global‑e to the Native App.Downstream Data Flow from Shopify
Starting with the checkout, international prices, duties & taxes, and shipping methods are calculated by Global‑e.| Downstream_Data_Flow_From_Shopify.svg | Downstream_Data_Flow_From_Shopify.svg |
|---|---|
| Downstream_Data_Flow_From_Shopify.svg |
- Presentment money: This is the currency that the international customer sees on the storefront, cart, checkout, and transactional emails.
-
Shop money: This is the main currency of your Shopify store; this currency is also used for reporting and analytics.
Shop money is what should be mapped downstream by your order management and accounting systems.
- Initial order creation has the payment status PENDING (financial_status property)
- When completed, the payment status gets updated to PAID . You can now submit orders for fulfilment.
For merchants who have configured Shopify to capture payment at fulfilment or manually, the “AUTHORISED” status assigned by Shopify at order validation will be updated automatically to “PAID” by Global-e after a few minutes.
Shopify Order Data
For illustration, this Shopify store is from a US merchant and the storefront currency is based on USD. A single product was purchased. Let’s examine two different order scenarios:- Duties & taxes paid by the customer – the checkout explicitly displays D&T-related line items.
- Duties & taxes inclusive/baked in the product prices – the merchant subsidizes the D&T costs.
Duties & Taxes Paid by the Customer
Market: Israel. The customer pays separately for all the D&T-related costs, including the customs clearance fee (CCF) represented here in the Additional Fee field.
The Additional Details section provides information; it is not required for data consumption.
CalculatedDutySubsidy represents the total order level subsidy in storefront currency. In this example, there is no subsidy for this order, hence the $0.
Duties & Taxes Included in the Product Price
Market: United Kingdom. Duties, taxes, and customs clearance fees are all-inclusive in the £500.00 product price in this example.

- Duty, tax, and customs clearance fees (CCF) are all part of the overall duties and taxes calculation.
- When a customer’s checkout displays duty & tax-related fees, these costs will appear as order line items.
- Any subsidized costs, whether both duties and taxes or just duty or just taxes – will appear in the note attributes
CalculatedDutySubsidyfield.
Accounting Perspective
From a Shopify view, orders are created per customer B2C transaction with Global‑e. From an accounting perspective, orders should be treated as domestic B2B orders booked against a Global‑e account. You may book any order line items to calculate gross revenue, and of course, bear in mind that Global-e is responsible for handling remittance and filing of local VAT and other taxes in most scenarios. For estimated net revenue, you can subtract theCalculatedDutySubsidy field.
For actual revenue, refer to the Global‑e financial reconciliation report.
Shipping Lines
When the Global-e CrossBorder app gets installed in Shopify, a shipping zone with Global-e operated countries is automatically added. The order shipping line data is standardized by Shopify and cannot be changed.-
Source: fixed value
Global‑e Carrier Service -
Title: For shipping from the US, two possible values only:
Express Courier (Air)orStandard Courier. For other countries, several possible values, depending on the suggested shipping service levels:- Standard Courier
- Express Courier (Air)
- Tracked Post
- Standard Delivery
- Virtual Goods
- Express Courier
- Untracked Post
- Store Collection
- Standard Post
- Express Shipping
- Standard Shipping
- Collection Point
- Tracked Standard
- Express Plus
- Premium Standard
- Tracked Post to Pickup location
-
Code: multiple permutations, depending on the service type.
Notes:
- For services in use for specific stores, contact a Project Manager.
- When shipping from the US, note that only Express Courier (Air) and Standard Courier mappings are applicable.
| Express Courier (Air) | 5 possible permutations:EXPRESS_GLOBALE_DDUEXPRESS_GLOBALE_OPT_DDPEXPRESS_GLOBALE_DDPEXPRESS_GLOBALE_HIDDEN_DDPEXPRESS_GLOBALE_TAX |
|---|---|
| Standard Courier | 5 possible permutations:STANDARD_GLOBALE_DDUSTANDARD_GLOBALE_OPT_DDPSTANDARD_GLOBALE_DDPSTANDARD_GLOBALE_HIDDEN_DDPSTANDARD_GLOBALE_TAX |
| Tracked Post | 5 possible permutations:PRIORITYPOST_GLOBALE_DDUPRIORITYPOST_GLOBALE_OPT_DDPPRIORITYPOST_GLOBALE_DDPPRIORITYPOST_GLOBALE_HIDDEN_DDPPRIORITYPOST_GLOBALE_TAX |
| Standard Delivery | 5 possible permutations:AIRMAIL_GLOBALE_DDUAIRMAIL_GLOBALE_OPT_DDPAIRMAIL_GLOBALE_DDPAIRMAIL_GLOBALE_HIDDEN_DDPAIRMAIL_GLOBALE_TAX |
| Virtual Goods | 5 possible permutations:VIRTUALGOODS_GLOBALE_DDUVIRTUALGOODS_GLOBALE_OPT_DDPVIRTUALGOODS_GLOBALE_DDPVIRTUALGOODS_GLOBALE_HIDDEN_DDPVIRTUALGOODS_GLOBALE_TAX |
| Express Courier | 5 possible permutations:EXPRESSCOURIERWITHOUTSAMEDAY_GLOBALE_DDUEXPRESSCOURIERWITHOUTSAMEDAY_GLOBALE_OPT_DDPEXPRESSCOURIERWITHOUTSAMEDAY_GLOBALE_DDPEXPRESSCOURIERWITHOUTSAMEDAY_GLOBALE_HIDDEN_DDPEXPRESSCOURIERWITHOUTSAMEDAY_GLOBALE_TAX |
| Untracked Post | 5 possible permutations:UNTRACKEDPOST_GLOBALE_DDUUNTRACKEDPOST_GLOBALE_OPT_DDPUNTRACKEDPOST_GLOBALE_DDPUNTRACKEDPOST_GLOBALE_HIDDEN_DDPUNTRACKEDPOST_GLOBALE_TAX |
| Store Collection | 5 possible permutations:STORECOLLECTION_GLOBALE_DDUSTORECOLLECTION_GLOBALE_OPT_DDPSTORECOLLECTION_GLOBALE_DDPSTORECOLLECTION_GLOBALE_HIDDEN_DDPSTORECOLLECTION_GLOBALE_TAX |
| Standard Post | 5 possible permutations:STANDARDPOST_GLOBALE_DDUSTANDARDPOST_GLOBALE_OPT_DDPSTANDARDPOST_GLOBALE_DDPSTANDARDPOST_GLOBALE_HIDDEN_DDPSTANDARDPOST_GLOBALE_TAX |
| Express Shipping | 5 possible permutations:EXPRESSSHIPPING_GLOBALE_DDUEXPRESSSHIPPING_GLOBALE_OPT_DDPEXPRESSSHIPPING_GLOBALE_DDPEXPRESSSHIPPING_GLOBALE_HIDDEN_DDPEXPRESSSHIPPING_GLOBALE_TAX |
| Standard Shipping | 5 possible permutations:STANDARDSHIPPING_GLOBALE_DDUSTANDARDSHIPPING_GLOBALE_OPT_DDPSTANDARDSHIPPING_GLOBALE_DDPSTANDARDSHIPPING_GLOBALE_HIDDEN_DDPSTANDARDSHIPPING_GLOBALE_TAX |
| Collection Point | 5 possible permutations:COLLECTIONPOINT_GLOBALE_DDUCOLLECTIONPOINT_GLOBALE_OPT_DDPCOLLECTIONPOINT_GLOBALE_DDPCOLLECTIONPOINT_GLOBALE_HIDDEN_DDPCOLLECTIONPOINT_GLOBALE_TAX |
| Tracked Standard | 5 possible permutations:TRACKEDSTANDARD_GLOBALE_DDUTRACKEDSTANDARD_GLOBALE_OPT_DDPTRACKEDSTANDARD_GLOBALE_DDPTRACKEDSTANDARD_GLOBALE_HIDDEN_DDPTRACKEDSTANDARD_GLOBALE_TAX |
| Express Plus | 5 possible permutations:EXPRESSPLUS_GLOBALE_DDUEXPRESSPLUS_GLOBALE_OPT_DDPEXPRESSPLUS_GLOBALE_DDPEXPRESSPLUS_GLOBALE_HIDDEN_DDPEXPRESSPLUS_GLOBALE_TAX |
| Premium Standard | 5 possible permutations:PREMIUMSTANDARD_GLOBALE_DDUPREMIUMSTANDARD_GLOBALE_OPT_DDPPREMIUMSTANDARD_GLOBALE_DDPPREMIUMSTANDARD_GLOBALE_HIDDEN_DDPPREMIUMSTANDARD_GLOBALE_TAX |
| Tracked Post to Pickup location | 5 possible permutations:TRACKEDPOSTTOPICKUPLOCATION_GLOBALE_DDUTRACKEDPOSTTOPICKUPLOCATION_GLOBALE_OPT_DDPTRACKEDPOSTTOPICKUPLOCATION_GLOBALE_DDPTRACKEDPOSTTOPICKUPLOCATION_GLOBALE_HIDDEN_DDPTRACKEDPOSTTOPICKUPLOCATION_GLOBALE_TAX |
Migrating Global‑e to the Native App
If you are currently running live on the legacy version of the Global‑e integration with Shopify, a.k.a the “hosted checkout”, you must migrate to the latest version where Global‑e is natively integrated into Shopify’s checkout, as detailed in this section. The key differences for the Shopify order data are as follows:- Order transaction is no longer per B2B transaction in a single currency; instead, it is per customer B2C transaction with presentment currency and shop currency. The B2B VAT is no longer reflected in Shopify.
-
Order id - the Shopify
order_nameno longer starts with ‘GE’ (e.g., GE2034304US). The Order name is now assigned by Shopify as done for domestic orders (e.g., #1234). The Global‑e order id is available. - Shipping lines/code is now standardized by Shopify as explained in the previous section.
- Shipment confirmation emails no longer come from Global‑e; instead, they are managed by Shopify and the merchant.
- Fraud approval no changes to this flow. This flow is still relying on the payment status pending (before the fraud check) and a subsequent update to paid status upon fraud approval with the addition of an order tag Globale::Approved.
-
Payment gateway no longer shows globale; instead, it shows:
- Global‑e Payment (INT) when installing the Global‑e payment method in the sandbox/staging mode.
- Global‑e Payments when installing the Global‑e payment method in production mode.
note_attribute, which is updated by the Global‑e Shopify app a few seconds after post-order creation.
Example:
Shopify Order JSON Example
Below is an example of an order JSON file. Alternatively, you can download this example from here.End-to-End Order Flow Interfaces
The following figure presents a general illustration of an order flow with Shopify to OMS to WMS and Global‑e.
- Order creation: created in Shopify with the initial payment status ‘
PENDING’ and order tagGlobale::Pending. - Fraud check: upon successful fraud check (asynchronous process), the payment status is set to ‘
PAID’ and the order tag is replaced withGlobale::Approved. - Export to OMS/WMS qualified orders: with
PAIDstatus or tagged withGlobale::Approved. - Pick and pack: the warehouse identifies orders via the Shopify order name/number and SKU/UPC.
- Label generation: Global‑e interface provides the final mile carrier label + tracking #
- End-of-day manifest: signals to Global‑e that the order is ready to be dispatched and generates an end-of-day document.
- *Fulfilment update to Shopify: in most scenarios, this event or the tracking # itself is provided by Global‑e. It is also expected for Shopify to send the shipment confirmation email when its fulfilment is created.

