Order Creation
Create order object in Glopal's shipping solution at order confirmation
Last updated
Create order object in Glopal's shipping solution at order confirmation
Last updated
Glopal's cross-border shipping solution is pre-integrated into , and available for the most relevant e-commerce platforms:
Shopify: .
Magento 2:
Salesforce Cloud Commerce: B2C Commerce Cartridge listed on the Salesforce , supporting , , and
Alternatively, create an order object in Glopal's shipping system via API in one of two ways:
Pass all relevant order information in one single request.
If integrated with Glopal's tcc.calculate_order API service (see Duty & Tax Calculation), reference the earlier quote to join already provided order information with additional data (such as the buyer shipping address).
Client username (set by Glopal)
usernamePattern: ^[a-z0-9\-]{3,255}$Optional system username to enable separation of authentication credentials by integrated client system. (set by Glopal)
alias-usernamePattern: ^[a-z0-9\-]{3,50}$The authentication signature is created by using the concatenation of the login, the ‘@’ sign and the timestamp, transformed into a HMAC_256 signature using your secret access key.
40b976b35a08bb951439ea7bbfa0a7bd73dab7c813399a31d9d1a157bc08929bPattern: ^[0-9a-f]{64}$The authentication timestamp must be a decimal numeric representing the current POSIX time, extended to microsecond accuracy. If the requesting system does not provide high-resolution time, it is advised to use a 6-digit random number. It is important to have the requesting system synchronised with a reliable time source (f.i. a stratum 2 NTP server) to avoid request rejection.
1680010295.775523Pattern: ^[12]\d{9}\.\d{6}$0.68Pattern: (^0\.\d{2}$|^[1-9]\d*\.\d{2}$)Client username (set by Glopal)
usernamePattern: ^[a-z0-9\-]{3,255}$Optional system username to enable separation of authentication credentials by integrated client system. (set by Glopal)
alias-usernamePattern: ^[a-z0-9\-]{3,50}$The authentication signature is created by using the concatenation of the login, the ‘@’ sign and the timestamp, transformed into a HMAC_256 signature using your secret access key.
40b976b35a08bb951439ea7bbfa0a7bd73dab7c813399a31d9d1a157bc08929bPattern: ^[0-9a-f]{64}$The authentication timestamp must be a decimal numeric representing the current POSIX time, extended to microsecond accuracy. If the requesting system does not provide high-resolution time, it is advised to use a 6-digit random number. It is important to have the requesting system synchronised with a reliable time source (f.i. a stratum 2 NTP server) to avoid request rejection.
1680010295.775523Pattern: ^[12]\d{9}\.\d{6}$0.68Pattern: (^0\.\d{2}$|^[1-9]\d*\.\d{2}$)