Skip to main content
There are two possible ways of implementing this model:
  • Retrieving the required information using Global-e’s GetOrdersDetails API.
  • Extracting the required information from the platform directly, which can be obtained through “custom attributes” when orders are exported to downstream systems (OMS / ERP / WMS).
Requirements
The third party or system responsible for generating shipping and customs documentation must build custom logic to:
  • Clear the shipment according to the defined configuration and order model, including using the right incoterm based on whether Duties and/or Taxes are included in the order or must be paid at delivery.
  • Retrieve and apply the correct product prices for customs from Global-e, ensuring that the declared customs values align with the tax calculation rule model (FOB or CIF) to prevent discrepancies.
  • Ensure Global-e information is accurately declared to carriers and customs documents whenever required.
Failure to implement these guidelines correctly may result in delays, tax liabilities, compliance and/or customer experience issues.
Preferred Approach
Implementing the GetOrdersDetails API is highly recommended because:
  • It ensures all required information is up to date and easily accessible.
  • It reduces dependency on the relevant data having to flow through multiple downstream systems, simplifying the integration process.
Global-e registration details will not be available through platform-based integration and will instead be provided separately in a file. These will need to be pre-configured by the merchant / 3PL in their own system.
Export Documentation Requirements
Destination-specific export documentation requirements apply. The exact list of applicable countries and required documentation will be confirmed during the project scoping phase, in alignment with the Global-e project team and the merchant / 3PL responsible for shipment execution.