How to configure Aramex (ARAMEXV2) in techSHIP [Guide]

Last updated: November 10, 2026

For B2C shipments imported into the European Union from outside the EU, Aramex requires product identifiers for each shipped item. These requirements are enforced in techSHIP for applicable shipments processed on or after November 1, 2026.

This guide explains how to add and configure this carrier connection, review its available carrier-specific settings, and understand the shipment requirements and operational constraints that apply.

Carrier Requirements and Specifications

This section summarizes onboarding requirements and lists confirmed carrier-specific constraints.

To review all supported carriers and their specific requirements, see: 📄 techSHIP supported Carriers - Master List [Guides List].

Onboarding Requirements

Information to be Provided

The following credentials and data points are mandatory to connect to Aramex. Ensure you have these items available before starting the setup:

DATA ELEMENT

SOURCE (HOW TO OBTAIN)

Username

Provided by Aramex for the shipping account.

Password

Provided by Aramex for the shipping account.

Account Entity

Provided by Aramex as part of the account credentials.

Account Number

Provided by Aramex as part of the account credentials.

Account Pin

Provided by Aramex as part of the account credentials.

Specifications and Constraints

Operational Details

Aramex supports domestic and international shipment processing according to the selected service and shipment route.

Test mode is not supported for this integration. Configure the Baseline Account with production Aramex credentials.

For applicable international shipments, Aramex may return a Commercial Invoice with the shipment. When provided by Aramex, techSHIP makes the document available with the processed shipment.

EU Product Identifier Requirements

For B2C shipments imported into an EU member state from a non-EU country, each shipped item must contain the required product identifiers.

techSHIP maps the item information to Aramex as follows:

ARAMEX IDENTIFIER

techSHIP SOURCE

MPID — Merchant Product Identifier

SKU

NSPID — Non-Standardized Product Identifier

Manufacturer Product Identifier

SPID — Standardized Product Identifier

UPC, when available

For applicable B2C EU imports:

  • SKU is required for every shipped item.

  • Manufacturer Product Identifier is required for every shipped item.

  • UPC should be provided when a standardized product identifier exists.

  • When no UPC exists, techSHIP sends Y081 to Aramex as the standardized-product-identifier exemption value.

  • Identifier values are trimmed before they are sent. techSHIP does not truncate the identifier values for Aramex.

  • Lines with a quantity of 0 are excluded from the mandatory product-identifier validation.

Configure the item values in the Client Item's International tab:

  • Manufacturer Product Identifier: Enter the manufacturer's model, part, or other non-standardized product identifier.

  • UPC: Enter the standardized product identifier when one is available.

The item's SKU is used as the Merchant Product Identifier.

For orders created through the API, provide the corresponding manufacturerProductIdentifier and upc item values.

B2C and B2B Determination

techSHIP determines whether the EU product-identifier validation applies using the shipment's receiver type and route.

The receiver type is resolved in this order:

  1. The Order's Receiver type, when specified.

  2. The Client Account's Default receiver type.

  3. Direct consumer when neither value is set.

A shipment is treated as a B2C EU import when:

  • the receiver type represents a consumer;

  • the destination is an EU member state; and

  • the origin is outside the EU.

For B2B shipments, set the Client Account's Default receiver type to the appropriate business value, or override it with the Order's Receiver type when required.

Configuring a Baseline Account

A Baseline Account serves as the fundamental connection point between techSHIP and the carrier's system. It acts as a template that holds the credentials and fundamental properties required to process shipments.

The techSHIP AI Assistant is available from the Carrier page for supported Carrier configuration tasks. For detailed conceptual information and advanced configuration, refer to 📄 techSHIP AI Assistant: Overview & Availability [Information].

Adding a Carrier

Before adding an account, you must ensure the Carrier entity is available for your location.

  1. Click My Carriers from the left menu under the Carriers category.

  2. Click Add Carrier.

  3. Select the desired Carrier.

You may encounter additional messages depending on the carrier status or your plan:

  • Subscription Required (⭐): If the carrier has a star icon, you will see a message stating "To use this carrier, a subscription upgrade is required." Press Contact to Upgrade to proceed.

  • Carrier Suspended: If the carrier has not been used for an extended period, you will see a message stating “This carrier is currently on hold...” Click Request Assistance to reactivate it.

  • Setup Fee Waived: If a carrier from the same carrier group is already installed in your location, you can add this carrier without incurring additional fees.

  1. If needed, update the carrier Name.

  2. Click Add Carrier.

If the purchase confirmation appears, complete the following steps:

  • Review the purchase notice and any applicable charge information.

  • Optionally enter a PO Number.

  • Select I am authorized to complete this purchase on behalf of my organization.

  • Click Purchase to confirm the Carrier addition.

Preview

Once the Carrier is added, you will be automatically redirected to the Carrier page to continue setting it up.

  1. Enter the Code of the Carrier as it appears in your host system.

The Code of the Carrier must match exactly the value defined in the host system. Any discrepancy (including casing or extra spaces) may prevent the carrier from working correctly.

  1. Click Save.

If your facility utilizes the centralized Pickup Schedule, we highly recommend adding this new carrier to your calendar now. While not required to process labels, this ensures accurate induction metrics for your Insights dashboards. To learn more, see 📄 Understanding the Centralized Pickup Schedule & Expected Induction Logic [Information].

Adding a Baseline Account

From the Carrier page, click Add Account to create a new Baseline Account.

You will be redirected to the Baseline Account page to complete the setup.

Entering incorrect values will prevent the system from generating shipping labels.

General Tab

In the General tab, define the administrative properties:

  • Name: Enter a descriptive name for the account.

Enter a descriptive name based on unique properties. E.g.:

  • Carrier Name - Account Number (CarrierX - 123456789)

  • Carrier Name - Consolidator Name (CarrierY - MyConsolidator)

  • Carrier Name

  • Usage: Select the most suitable option:

    • Test: Used for sandbox or onboarding purposes.

    • Production: Used for live shipping.

Keep the Status field set to its default Active value. An account must be Active to remain fully editable. For detailed conceptual information on account statuses, refer to 📄 How to Inactivate and Activate a Carrier Baseline Account [Step-by-Step Guide].

Carrier Tab

Aramex Credentials

Configure the Aramex account credentials:

  • Username: Enter the Aramex account username.

  • Password: Enter the Aramex account password.

  • Account Entity: Enter the account entity supplied by Aramex.

  • Account Number: Enter the Aramex shipping account number.

  • Account Pin: Enter the PIN associated with the Aramex account.

All five credential values must belong to the same active Aramex account.

Label Template

Use Label Template to select the Aramex label layout required for the account. Available templates include standard 4 × 6, A4, COD, and no-weight variants.

Options

  • Pickup Location: Enter the location reference that must be sent with shipments when applicable.

This field does not enable Aramex pickup creation in techSHIP.

Sender Address

Configure the sender address used by the Baseline Account. Ensure that the sender Country is populated because Aramex uses the origin country when processing shipments and determining applicable international requirements.

Labels Tab

Aramex supports the following label output formats:

  • PDF

  • PNG

Select either PDF or PNG as the label Mode.

Finalizing the Setup

Once you have entered the required information, click Save.

After you save the Baseline Account, check whether the Registration tab or a registration status badge is available.

If neither is available, the Carrier does not use this Registration workflow in techSHIP. If registration is still pending, open the Registration tab and press Registration, then complete 📄 How to Register a Carrier Baseline Account [Step-by-Step Guide] before creating shipments.

From the Carrier page, you can now see the Baseline Account listed with the administrative status Active. The Active status is separate from the account's registration status.

The Baseline Account configuration is now saved. You can continue with Configuring a Client Account below to assign the Baseline Account to a specific Client.

Configuring a Client Account

Adding an Account

Before adding a Client Account, ensure that the Client has been created. For instructions creating a Client, see: 📄 10 - How to create a Client profile [Step-by-Step guide].

  1. Click Clients from the left menu under the Clients section.

  2. Click the Edit icon for the desired Client.

  3. Click Add Accounts.

  4. Optionally, use the Search box to search by Baseline Account Name or Carrier.

  5. Select the Baseline Accounts that will serve as the foundation for your new Client Accounts.

  6. Click Add Accounts.

    A toast notification will confirm the accounts were successfully assigned. Click the Refresh icon if recently added accounts are not displayed.

  1. Click Edit on each newly created account.

  2. Configure the available options in each tab (except Carrier).

For complete instructions on configuring this settings, see 📄 How to configure the Billing Account General Options tab [Step-by-Step guide].

Carrier Tab

The Carrier tab contains the Aramex-specific settings applied to this Client Account.

Shipment Defaults

  • Service code: Select the Aramex service used by the Client Account.

  • Override WMS Service Code: Enable this option when the Client Account must use the configured Aramex service instead of the service received from the WMS.

  • Currency: Select the currency used for applicable Aramex shipment values.

  • Payment Type: Select Prepaid, Collect, or Third Party as required.

  • Payment Options: Select the applicable Aramex payment option.

  • Sender IOSS number: Enter the sender's IOSS number when applicable. When supplied, techSHIP sends the value to Aramex as a customs-clearance property.

  • Default receiver type: Select the receiver classification used when the Order does not specify its own Receiver type.

For EU product-identifier processing, leave Default receiver type as a consumer type for B2C shipments. Set it to the applicable business type for B2B shipments.

Sender and Consignee References

Configure the Aramex reference mappings as required:

  • Sender Reference 1

  • Sender Reference 2

  • Consignee Reference 1

  • Consignee Reference 2

These fields determine which techSHIP order reference values are sent in the corresponding Aramex sender and consignee reference positions.

Payment Accessorials

Use Payment accessorials to configure the applicable default customs-payment behaviour for the Client Account.

Sender and Billing Information

Complete the sender contact and address information used by Aramex as required, including applicable Contact Phone, Contact Phone Extension, and Contact Email values.

Specifying Rate Shopping Service Codes

Aramex rates can be requested through techSHIP. Use the standard Client Account rate-shopping service filters when only specific Aramex services should participate in Rate Shopping.

For detailed instructions on how to configure this, see: Include or exclude Service Codes when Rate Shopping [Step-by-Step Guide].

Label References

Aramex provides four carrier-specific package reference mappings on the Client Account:

  • Sender Reference 1

  • Sender Reference 2

  • Consignee Reference 1

  • Consignee Reference 2

Configure these fields on the Client Account's Carrier tab using the required techSHIP reference values.

For a comprehensive guide on how to use label references, see: Using order References in your labels [Step-by-Step guide].

Finalizing the Setup

Once you have entered the required information, click Save.

With the account configured and requirements verified, you can now proceed to process orders as described below.

Configuring an Order

The steps described in this section are not required for carrier setup, and they are offered as an optional review if further order-level configuration is required.

Follow the UI Navigation steps in 📄 05 - How to edit an order’s information - [Step-by-Step guide], using the carrier-specific values provided in this guide.

The Order's Carrier Options contain Aramex-specific settings that apply only to the selected shipment.

Service

  • Service code: Select the Aramex service for the Order.

  • Currency: Select the shipment currency.

  • Ship date: Enter the shipment date.

  • Deliver before date: Enter the requested deliver-before date when applicable.

  • Accounting Instructions: Enter applicable accounting instructions.

  • Payment Options: Select the payment option for the shipment.

  • Sender IOSS number: Enter the sender IOSS number when required.

  • Receiver type: Select the receiver classification for this Order.

The Order-level Receiver type overrides the Client Account's Default receiver type. For a B2B EU import, select the appropriate business receiver type so techSHIP does not process the shipment as a consumer import.

Accessorials

Configure the applicable Aramex shipment options:

  • Insurance

  • First delivery

  • Hold for pickup

  • Noon Delivery

  • Signature required

  • Payment accesorials

When Insurance is enabled, a Declared Value must be provided at package level.

EU Product Identifiers

For a B2C shipment imported into the EU from outside the EU, verify that every shipped item has both:

  • SKU

  • Manufacturer Product Identifier

Provide UPC whenever a standardized identifier exists. If an applicable B2C EU-import item has no UPC, techSHIP automatically sends Y081 to Aramex.

Click Save to apply the order-level changes. After the Order is updated, continue with the standard shipping workflow.

Troubleshooting

  • B2C EU shipment fails before being sent to Aramex: Review the affected Client Items and verify that every shipped line contains both SKU and Manufacturer Product Identifier. For items maintained in techSHIP, update the Manufacturer Product Identifier in the Client Item's International tab. The validation message identifies the affected items: Aramex requires a SKU and a Manufacturer Product Identifier for every item on EU-bound consumer shipments (effective Nov 1, 2026). Set them, or set the order receiver type to business for B2B shipments. Missing for: ...

  • A B2B shipment is being validated as a consumer shipment: Verify Receiver type on the Order. If no Order override is required, verify Default receiver type on the Client Account and select the appropriate business value.

  • An item does not have a UPC: For applicable B2C EU imports, no manual placeholder is required. Leave the UPC empty when no standardized identifier exists; techSHIP sends Y081 to Aramex automatically. Do not enter Y081 as the item's UPC.

  • Aramex authentication fails: Verify Username, Password, Account Entity, Account Number, and Account Pin on the Baseline Account and confirm that all values belong to the same active Aramex account.

  • Label generation fails because of the selected format: Verify the Baseline Account's Labels configuration. Aramex supports PDF and PNG output through this integration.

  • Insurance processing fails: If Insurance is selected on the Order, verify that a non-zero Declared Value is available for each applicable package.

  • Shipment uses the wrong receiver classification: Remember that Receiver type on the Order takes precedence over Default receiver type on the Client Account. When neither is configured, techSHIP treats the receiver as Direct consumer.