EU Regulatory Updates

To comply with new EU regulatory mandates, EasyPost now supports the required shipping data through the shipment and orders API. Most of the required information was already supported through existing fields; a few new parameters cover specific regulatory additions.

  • Most of these parameters are carrier-agnostic and are designed to satisfy the regulations directly rather than any individual carrier's requirements. Any carrier-specific requirements that cannot be covered by these additions (such as UPS's business/consumer classification) are supported separately and detailed in the carrier sections below.
  • This guide is organized top-down: the carrier-agnostic, API-level fields you send to EasyPost come first, then carrier-specific behavior, followed by how FedEx, UPS, and USPS Ship render or transmit them.

Overview

Product Identifiers (PIDs)

Since November 1, 2026, EU customs requires product identifiers on customs documentation for qualifying shipments into the EU. Of the three identifiers below, the merchant (code) and manufacturer (manufacturer_product_id) IDs are always needed. The standardized ID (standardized_product_id) is needed only when the product has one, such as a UPC, EAN, or ISBN. If it doesn't, omit it from the USPS Ship request. USPS requires this field only when the item has one and the shipment is B2C to the destinations listed in the USPS Ship guide. For other carriers, see the carrier sections below.

EasyPost accepts all three as optional when you create a shipment. Each carrier decides what it requires when you buy the label, so see the carrier sections below. Shipments missing identifiers a carrier requires are rejected at purchase, or may not clear customs.

code
existing
M-PID — merchant product ID. No change. Max 128 characters.
manufacturer_product_id
new
NS-PID — manufacturer product ID. Max 64 characters.
standardized_product_id
new
S-PID — standardized ID / GTIN-EAN. Max 64 characters.

EU low-value duty (the "€150 de minimis" change)

Since July 2026, a €3 customs duty per item line applies to B2C shipments into the EU valued ≤ €150. This is a regulatory customs duty, not a carrier surcharge. EU customs classifies and routes each shipment using data you should already be passing through existing fields, or carrier-specific fields for carriers like UPS:

  • Tax identifiers — your IOSS or VAT registration on the commercial invoice.
    • IOSS marks a B2C shipment eligible for the flat-fee fast lane.
    • VAT marks a B2B shipment routed through full H1 customs processing.
  • B2B vs. B2C classification — whether the shipper and consignee are a business or a consumer.
    • This is carrier-specific today (see below).

The €3 duty vs. the €2 Union handling fee

The €3 customs duty is frequently confused with the €2 Union handling fee, a separate administrative charge covering the customs services involved in processing the declaration. The two come from different legal instruments, start on different dates, and both must be paid — neither one replaces the other.

Temporary customs duty
Union handling fee
Fee€3€2
Legal basisCouncil Regulation (EU) 2026/382Article 20(2) of the new Union Customs Code
Value scopeConsignments valued €150 or lessAny value, including above €150
Applies fromJuly 1, 2026Expected November 1, 2026
DurationTemporary, until July 1, 2028Permanent
  • Both are assessed per declaration line, not per article.
  • A declaration line is goods sharing the same tariff classification, description and, where required, country of origin.
  • So fifteen identical T-shirts under a single commodity code are a single line, while adding socks under a second code makes two.

Example

Consignment contents (€150 or less)
Declaration lines
€3 duty
€2 handling fee
Total fixed charges
15 identical T-shirts under a single commodity code1€3€2€5
15 T-shirts plus 6 pairs of socks under a second code2€6€4€10
Three products under three different codes3€9€6€15

Part 1 — API-Level (Carrier-Agnostic) Changes

These are the shipment-API fields you send to EasyPost, independent of which carrier ultimately moves the package.

These are the fields you send to EasyPost, whichever carrier you use. EasyPost validates their format when you create the shipment. Whether they are required is decided by the carrier when you buy the label; see the carrier-specific sections below.

1. Product Identifiers on Customs Items

Two new fields on each customs_item, alongside the existing merchant code, carry the three EU product identifiers. These are carrier-agnostic:

code
existing
M-PID (C127) — merchant product ID. Already supported. Max 128 characters.
manufacturer_product_id
new
NS-PID (C128) — manufacturer's product identifier. Max 64 characters.
standardized_product_id
new
S-PID (C129) — standardized identifier: GTIN/EAN. Max 64 characters.
  • code is the existing merchant product ID field. No change; for EU customs it now doubles as the M-PID (C127).
  • Only manufacturer_product_id and standardized_product_id are new.

How to use it:

{
  "customs_item": {
    "description": "Women's 100% Cotton T-Shirt, Navy, L",
    "quantity": 1,
    "value": "12.00",
    "hs_tariff_number": "6109.10.0012",
    "code": "123456",
    "manufacturer_product_id": "SH123456",
    "standardized_product_id": "00012345600012"
  }
}
  • All fields are optional / nullable at shipment creation. Max length is 128 for code and 64 for manufacturer_product_id and standardized_product_id.
  • Carrier-agnostic — the same two fields also serve US CPSC (see the companion CPSC guide).

2. Tax Identifiers: VAT and IOSS

The existing shipment.tax_identifiers[] array takes the list of tax registration numbers (VAT, IOSS, EORI, UKIMS, EIN, …) associated with the sender or recipient.

  • This array is unchanged.
  • If you have an IOSS number (or VAT, if applicable), it's important to add it now.
  • For EU-bound shipments these numbers are now surfaced on the commercial invoice where customs expects them (see the carrier-specific sections below), in various places depending on the carrier.

How to use it (unchanged shape):

{
  "shipment": {
    "tax_identifiers": [
      { "entity": "SENDER", "tax_id": "IM4420000191", "tax_id_type": "IOSS", "issuing_country": "IE" },
      { "entity": "SENDER", "tax_id": "GB362459274", "tax_id_type": "VAT", "issuing_country": "GB" },
      { "entity": "SENDER", "tax_id": "GB205672212000", "tax_id_type": "EORI", "issuing_country": "GB" }
    ]
  }
}

EasyPost passes through the numbers you provide and makes sure they appear correctly.

EasyPost does not infer, generate, or choose between your tax IDs.

If you provide both an IOSS and a VAT number for a FedEx shipment entering the EU under the new regulations, EasyPost will not choose between them — both will appear on the commercial invoice. It is your responsibility to understand the constraints and provide the correct information.


3. Tax Identifier Address

A new optional address on each entry of tax_identifiers lets you supply the registered address (and, through it, the registered name) tied to a tax registration — for example, the address behind an IOSS or VAT registration.

  • Carriers such as UPS now expect associated information such as Number + Name + Address for eligible EU-bound shipments. Previously tax_identifiers only accepted the ID number and type.
  • It is carrier-agnostic by design (it lives on the shared tax-identifier object, not under carrier_options), even though UPS IOSS is currently the only carrier that requests it explicitly. You can provide it in two ways:

How to use it:

Inline:

{
  "shipment": {
    "tax_identifiers": [
      {
        "entity": "SENDER",
        "tax_id": "IM1234567890",
        "tax_id_type": "IOSS",
        "issuing_country": "DE",
        "address": {
          "name": "ACME GmbH",
          "street1": "Friedrichstraße 1",
          "city": "Berlin",
          "zip": "10117",
          "country": "DE"
        }
      }
    ]
  }
}

Reference an existing saved address, the same convention as to_address:

{
  "tax_identifiers": [
    {
      "tax_id": "IM1234567890",
      "tax_id_type": "IOSS",
      "issuing_country": "IE",
      "address": { "id": "adr_5843b8dd903611f19a3d0022480b361d" }
    }
  ]
}
  • address reuses EasyPost's standard Address model.
  • It is optional; omitting it preserves prior behavior.

4. Commerce Type

options.commerce_type sets the type of transaction: B2B, B2C, C2B, or C2C.

  • Lowercase values are accepted and normalized.
  • An unknown value is rejected with a 422 (SHIPMENT.OPTIONS.INVALID) when you create the shipment, whatever the destination.
  • Omitting it is accepted when you create the shipment and request rates. A carrier that needs it rejects the purchase if it is missing. See the carrier sections below for what each one requires.

Part 2 — Carrier-Specific Implications

How each carrier renders or transmits the API-level data above. Nothing here is a new field you send — it describes carrier behavior.

FedEx

Further reading:

Important — make duty handling explicit.

By default, FedEx bills the recipient for duties and taxes on international shipments. Rather than relying on that default, set who pays and make sure the recipient is reachable:

  • Include the recipient's email in to_address.email when possible, so FedEx can contact them about any duties and taxes they're responsible for.

  • Say who pays duties and taxes with options.duty_payment — separate from options.payment, which bills shipping, not duties.

    • Set type to SENDER, RECEIVER, or THIRD_PARTY.
    {
      "shipment": {
        "options": {
          "duty_payment": {
            "type": "SENDER",
            "account": "123456789",
            "country": "US",
            "postal_code": "94104"
          }
        }
      }
    }
  • State the terms with the incoterm in customs_info.incoterm (DDP = shipper pays, DDU / DAP = recipient pays).

  • Provide your IOSS number in tax_identifiers[] if you have one (see Part 1).

    • The EasyPost equivalent of FedEx's shipper.tins[].

VAT / IOSS on the Commercial Invoice

For shipments into the EU, EasyPost now surfaces your VAT and IOSS numbers on the FedEx commercial invoice in two places:

  1. The Tax ID field on the CI (exporter / importer tax ID).

    • FedEx prints only the first tax ID on the CI that is sent, so a VAT or IOSS listed after another ID (e.g. an EORI) previously never appeared.
    • EasyPost now floats VAT/IOSS to the front of the tax IDs sent to FedEx for EU destinations, so it prints in the exporter or importer tax ID field.
  2. Declaration statement line on the CI.

    • For EU-bound shipments, VAT and IOSS numbers are included within the commercial invoice's declaration statement. (UKIMS continues to be included on the declaration statement for all destinations, matching previous behavior.)
    • Since this field has no character limit, any combination — one, two, or all three identifiers — can be displayed.
    • If a shipment contains conflicting tax ID declarations (such as both IOSS and VAT for a flat-fee shipment to the EU), both are printed on the declaration statement. As noted, EasyPost does not make automated determinations on your behalf.

One caveat — US-origin shipments: for shipments originating from the USA, VAT/IOSS still print in the tax ID field on the CI PDF, but not in the declarationStatement field.

This is FedEx's rendering behavior, not an EasyPost limitation. Non-US origins (e.g. GB → DE, FR → DE) print as described.

Note: This change only applies to shipments entering the EU:

  • If you don't send tax_identifiers, nothing changes.
  • If you already do, you simply start seeing VAT and/or IOSS on the CI for your EU shipments — no code changes required.

UPS

When possible, include the recipient's email in to_address.email so UPS can contact them about any duties and taxes they're responsible for.

Shipper & Consignee Type

Two UPS-specific carrier options, shipper_type and consignee_type, classify the shipper (sender) and consignee (recipient) as a business or a consumer. Because this is specific to UPS, it lives inside carrier_options.

  • EasyPost maps them to UPS's GlobalTaxInformation/ShipperTypeValue and GlobalTaxInformation/ConsigneeTypeValue. These are the values UPS has told customers it now requires.
  • UPS uses them for EU de minimis customs routing and handling, since the B2B/B2C indicator routes the shipment into the correct customs lane. UPS may hold or return EU-bound shipments that omit them.
  • They are found under options.carrier_options.ups; each is independent (send either, both, or neither).

How to use it:

{
  "shipment": {
    "options": {
      "carrier_options": {
        "ups": {
          "shipper_type": "business",
          "consignee_type": "consumer"
        }
      }
    }
  }
}
  • Accepted values (both): business, consumer, not_applicable. Anything else is rejected with a clear validation error.
  • Both are optional and independent; omitting both leaves the shipment unchanged (no GlobalTaxInformation sent).
  • Shared wire code set: business → 01, consumer → 02, not_applicable → NA. UPS-only for now; mirrors the existing carrier_options.ups.premier pattern.
  • Capture-and-transmit only — EasyPost passes the values through; it does not infer or override them from your residential/company values.

How it appears:

<GlobalTaxInformation>
    <ShipperTypeValue>02</ShipperTypeValue>
    <ConsigneeTypeValue>02</ConsigneeTypeValue>
</GlobalTaxInformation>

Tax Identifier Address → IOSS Name / Address

  • The carrier-agnostic tax_identifiers[].address field was added initially for UPS's IOSS requirements. While it is carrier-agnostic, UPS is currently the only carrier using the data.
  • UPS exposes structured IOSS fields (Number + Name + Address) on the ShipConfirm request. When an IOSS tax identifier carries an address, EasyPost emits it as an IOSSContact under ShipFrom/VendorInfo.

How to use it:

<ShipFrom>
  <VendorInfo>
    <VendorCollectIDTypeCode>0356</VendorCollectIDTypeCode>  <!-- IOSS -->
    <VendorCollectIDNumber>IM1234567890</VendorCollectIDNumber>
    <IOSSContact>
      <Name>ACME GmbH</Name>
      <Address>
        <AddressLine1>Friedrichstraße 1</AddressLine1>
        <City>Berlin</City>
        <PostalCode>10117</PostalCode>
        <CountryCode>DE</CountryCode>
      </Address>
    </IOSSContact>
  </VendorInfo>
</ShipFrom>

Worldwide Economy → Germany: Duty-Unpaid Suspended

A temporary guard rejects UPS Worldwide Economy duty-unpaid (DDU) rate and buy requests bound for Germany (DE). WWE duty-paid (DDP) and every non-WWE UPS service are unaffected. Under the new EU rules, UPS has communicated that WWE can no longer clear duty-unpaid volume into Germany, and such packages would be returned to sender.

UPS has asked us to stop sending WWE DDU to DE for both BYOA and the DAP program. EasyPost rejects these up front with a 422 at rate/buy time, before any UPS call, so you don't buy labels that would just be returned to sender. UPS has not provided an ETA for when this restriction will be lifted.

What's blocked vs. kept:

  • Blocked: WWE duty-unpaid (DDU / DAP incoterm) to DE for all account types (BYOA and the DAP program).
  • Kept: WWE duty-paid (DDP) to DE, and all non-WWE UPS services.

What you'll see:

  • Rating or buying a WWE DDU shipment to DE returns a 422.
    • UPS Worldwide Economy is temporarily unavailable for duty-unpaid (DDU) shipments to Germany (DE)
    • On the DAP-program rate path the same rejection surfaces as SHIPMENT.RATES.UNAVAILABLE.

A note on the two "DAP"s: "duty-unpaid" here is the incoterm (DDU / DAP = "Delivered At Place"), not the UPSDAP account type. The block keys off destination + duty status only, so it applies to BYOA and the DAP program WWE DDU / DAP only, not WWE DDP.


USPS Ship

USPS Ship requires options.commerce_type on commercial shipments (merchandise or sample) to the destinations listed in the USPS Ship guide. For B2C shipments it also requires product identifiers on every customs item. For the full details, see the USPS Ship — EU Regulatory Updates guide and the USPS product identifier requirements(opens in a new tab).

  • Commerce type: set options.commerce_type to B2B, B2C, C2B, or C2C. It is required for these shipments, and the buy is rejected without it. B2C and B2B are sent to USPS as the commercial classification on the customs declaration. C2B and C2C mean the shipment is not commercial, so no classification is sent.
  • Product identifiers: for B2C, code (up to 50 characters) and manufacturer_product_id (up to 64) are required on every customs item. standardized_product_id (up to 50) is sent only when the item has one. Values cannot contain [, ], ;, or =, or control characters. For B2B, C2B, and C2C, product identifiers are not sent.
  • No truncation: USPS Ship does not transliterate or truncate identifiers. Invalid or over-length values are rejected so you can correct them.

Carrier Support for Product Identifiers

Product identifier support rolls out carrier by carrier. You can send code, manufacturer_product_id, and standardized_product_id today for any carrier — EasyPost stores and returns them on the customs item — and they are transmitted to the carriers marked Supported below.

Statuses as of November 19, 2026. If a carrier you ship EU-bound volume with isn't listed and you think it should be, contact our Support team.

  • Supported — EasyPost transmits the product identifiers to this carrier today.
  • In development — implementation is underway at EasyPost.
  • Planned — scheduled, not yet started.
  • Awaiting carrier — the carrier has not yet published a way to accept the product identifiers, so there is nothing for EasyPost to send them to.
Supported
APC
Asendia USA
Australia Post
DHL eCommerce Solutions
DHL Express
DHL Paket
DPD UK / Interlink Express
ePost Global
Evri
FedEx
FedEx Cross Border
Passport Global
Purolator
Royal Mail
RR Donnelley
UPS
USPS Ship
In development
GLS Group (EU)
USA Export PBA
Planned
PC Postage
Awaiting carrier
Canada Post
DAI Post
Deutsche Post UK
Hailify

Summary

Change
Layer
What it does
Why it's required
VAT / IOSS tax identifiersAPI (agnostic)Existing tax_identifiers[]; no new field to sendEU de minimis clearance
tax_identifiers[].addressAPI (agnostic)Optional address on each tax_identifiers[] (inline or { "id": "adr_…" }); reuses Address modelCarrier IOSS name/address requirement
manufacturer_product_id + standardized_product_idAPI (agnostic)New manufacturer_product_id (NS-PID) + standardized_product_id (S-PID) on customs_item; code = M-PID.EU PID mandate
VAT / IOSS on FedEx CIFedExFloats VAT/IOSS to front of tax IDs (prints in CI Tax ID field) + adds to declaration statement; EU onlyEU de minimis clearance
shipper_type / consignee_typeUPScarrier_options.ups.shipper_type / consignee_type (business/consumer/not_applicable) → UPS ShipperTypeValue / ConsigneeTypeValueEU B2B/B2C customs routing
Tax Identifier Address → IOSSUPSIOSS address → VendorInfo/IOSSContact (Name + Address) on ShipFromUPS IOSS name/address
WWE → Germany DDU blockUPSTemporarily blocks WWE duty-unpaid (DDU) rate/buy to DE (422); keeps DDPUPS WWE DDU clearance into DE
commerce_type + product identifiersUSPS ShipRequires commerce_type (B2B/B2C/C2B/C2C) on merchandise/sample shipments to the destinations listed in the USPS Ship guide; B2C requires code and manufacturer_product_id on every item (standardized ID only when the item has one)USPS EU customs declaration; EU PID mandate