Shipping with Non-Global-e Carriers
This guide is intended for merchants using their accounts to ship Global-e-operated orders through carriers not integrated with Global-e. It outlines the fundamental guidelines for building the relevant clearance documents (shipping labels and commercial invoices).
In this context, the merchant is the “Shipper of Record, while Global-e remains the merchant and exporter of record.
It is important to ensure that the information declared to the authorities is accurate, providing a positive customer experience and a seamless customs clearance.
Shipping Service Identification
The shipping method service values need to be agreed on during the implementation of the project.
When an order is created, Global-e provides the platform with details of the service level selected at checkout by the customer. The warehouse team then retrieves this information when preparing a shipment. This data can be passed in the shipping lines.
The merchant must also provide a breakdown of services per market (shipping service, DDP enablement) in order to align carrier capabilities with the customer’s experience during the checkout.
Implementing Shipments with Non-Global-e Carriers
Select one of the following methods to implement the solution for shipping with non-Global-e carriers.
Retrieve the information using the Global-e API our,
GetOrderDetails
.Extract international information directly from the platform through custom attributes, when orders are exported to the downstream system (OMS/ERP/WMS).
GetOrderDetails API
To implement API calls with Global-e
Have your Global-e
merchantGUID
on hand.Access the relevant integration environment:
URL Parameters
Parameter
Type
Required/Optional
Description
MerchantGUID
String
Required
Unique Merchant Identifier and API token Different for Test and Live environments.
Body Parameters
Parameter
Type
Required/Optional
Description
OrdersDetailsFilter
List<OrderIds>
Required
Global-e order ID or merchant order ID.
Sample
Body:
{ "OrderIds": ["GE2794623GB","GE2794622GB", "GE2794621GB"] }
API response:
If success: List of Merchant.Order classes.
The API methods returns a list of order details. In case of producing shipping documentation, the below fields should be considered:
Exporter details (relevant EIN / EORI / VAT #) | Commercial invoices should list Global-e as the exporter. For specific destinations such as NO/UK/EU(Cross border)/CH/AU/NZ/SG/MY, our local registration must be included.
Note: Global-e’s IOSS number should NOT be displayed on the Commercial Invoices. |
Importer and import type mention |
|
Shipper name/address | If there is no specific section to declare Global-e as Exporter of Record, the shipper’s section must at least mention Global-e as the exporter. |
Currency |
|
Incoterm (DAP/DDP) |
|
Products | <List> |
COO | n/a – to be taken from own systems |
HS Code | n/a – to be taken from own systems |
Price exclusive of D%T | Merchant.Order.Products[i].InternationalDiscountedPriceForCustoms |
Shipping Cost |
|
Destination Tax calcu-lation rule |
|
Total shipment declarative value for customs |
|
If failure: ErrorInfo
Parameter | Type | Description |
---|---|---|
Code | string | Error code that is returned when an error occurs. |
Error | string | In case of an error, this property indicates the error message text. |
Description | string | In case of an error, this property indicates the error message description. |
Platform Mapping
SFCC mapping
Exporter details (relevant EIN / EORI / VAT #) | The commercial invoice should list Global-e as the Exporter. For specific destinations such as NO/UK/EU(Cross border)/AU/NZ/SG/CH, our local registration must be included. The relevant details for each destination are provided separately to allow for it to be stored in the relevant system as part of the integration. NOTE: Global-e’s IOSS number should NOT be displayed on the Commercial Invoices. |
Importer and import type mention |
|
Shipper name/address | If there is no specific section to declare Global-e as Exporter of Record, the shipper’s section must at least mention Global-e as the exporter |
Currency |
|
Incoterm (DAP/DDP) |
|
Products | <product-lineitem> data from SFCC order record |
COO | n/a – to be taken from own systems |
HS Code | n/a – to be taken from own systems |
Price exclusive of D&T |
|
Shipping Cost |
|
Destination Tax calculation rule |
|
Total shipment declarative value for customs |
|
Shopify mapping
Exporter details | The commercial invoice should list Global-e as the Exporter. For specific destinations such as NO/UK/EU(Cross border)/AU/NZ/SG/CH, our local registration must be included. The relevant details for each destination are provided separately to allow for it to be stored in the relevant system as part of the integration. NOTE: Global-e’s IOSS number should NOT be displayed on the commercial invoices. |
Importer and import type mention | If (shipping country = Switzerland) “Private Import Mention” for B2C shipment Else Importer details should have the Mention "Business Importer" Note: Importer details to Switzerland will be communicated in a separate file |
Shipper name/address | If there is no specific section to list Global-e as Exporter of Record, the shipper’s section must mention Global-e as exporter. |
Currency |
|
Incoterm (DAP/DDP) |
|
Products |
|
COO | n/a – to be taken from own systems |
HS Code | n/a – to be taken from own systems |
Price exclusive of D&T | order.note_attributes [ InternationalOrderProductsForCustoms ] |
Shipping Cost | order.note_attributes [DiscountedShippingPrice] |
Destination Tax calculation rule | order.note_attributes [TaxCalculationRule] |
Total shipment declarative value for customs | order.note_attributes [TotalValueForCustoms] |
GEM mapping
Exporter details (relevant EIN / EORI / VAT #) | The commercial invoice should list Global-e as the Exporter. For specific destinations such as NO/UK/EU(Cross border)/AU/NZ/SG/CH, our local registration must be included. The relevant details for each destination are provided separately to allow for it to be stored in the relevant system as part of the integration. NOTE: Global-e’s IOSS number should NOT be displayed on the Commercial In-voices. |
Importer and import type mention |
|
Shipper name/address | If there is no specific section to declare Global-e as Exporter of Record, the shipper’s section must at least mention Global-e as the exporter. |
Currency |
|
Incoterm (DAP/DDP) | Build logic using: InternationalDetails. DutiesGuaranteed IF false:
If true:
|
Products | Use products data |
COO | n/a – to be taken from own systems |
HS Code | n/a – to be taken from own systems |
Price exclusive of D&T | Products[i]. InternationalDiscountedPriceForCustoms |
Shipping Cost | InternationalDetails. DiscountedShippingPrice |
Destination Tax calculation rule |
|
Total shipment declarative value for customs |
|
Special Destination Cases
Switzerland
Shipments to Switzerland should be handled as business imports and cleared using our ZAZ account.
The merchant/3PL must confirm whether their carrier supports delivery as Business Import, as not all carriers accommodate this model, and if they can clear goods with a ZAZ account.
The invoices sold to the party (not the consignee) must be in Global-e's name and include Global-e’s local VAT registration number – shipments must be handled as DDU shipments cleared on Global-E’s name.
Example: Swiss customer (from US)
Singapore
In compliance with Singaporean regulations, the commercial invoice should include the following elements :
OVR GST Number
GST payment indication for each line item:
“Y”, for orders below the threshold (SGD 400), taxes are paid by Global-E to the authorities.
“N”, for orders above the threshold (SGD 400), taxes are paid by the Shipper upon import.
Example: Singaporean customer (from UK)
Norway, United Kingdom, Australia, New Zealand and EU (Crossborber)
Global-e local registrations must be used under duties thresholds
Shipper VOEC/EIN : must be Global-e’s local registration number
Example