By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
A NetSuite DHL integration connects NetSuite fulfillment records to DHL’s APIs so rates, labels, pickups and tracking numbers move between the two. Oracle’s carrier integration documentation names FedEx, UPS and USPS, so a DHL connection comes from NetSuite Ship Central if it supports your DHL service, a third-party shipping app, middleware or a custom build.
This guide describes each route, what DHL’s APIs provide, the setup steps in order and what to test before go-live.
What does a NetSuite DHL integration do?
DHL’s Express API, MyDHL API, is a REST API for customers with a DHL Express account. DHL’s developer portal lists its services as rating, product, landed cost, shipment, pickup, tracking, address and identifier. In practice, an integration built on it can cover these tasks:
- Rates and transit times for a package before it ships.
- Shipment creation, returning a label and a tracking number.
- Pickup booking with a DHL Express courier.
- Tracking, so shipment status can come back to NetSuite.
- Landed cost, an estimate of duties and taxes for international shipments.
DHL runs other services with their own APIs, including eCommerce, Freight, Global Forwarding and Supply Chain, and the portal also offers a unified shipment tracking API that covers status across DHL shipment types. Which API applies depends on the DHL service you ship with and the account you hold with it.
On the NetSuite side, the integration reads the order and fulfillment records, sends the package details to DHL and writes the label reference and tracking number back. Confirm with whichever route you choose where it stores each piece of data.
What are the options for connecting NetSuite to DHL?
Oracle’s shipping integration documentation covers FedEx, UPS and USPS/Endicia and states that the integration is not available to new customers. Existing customers have it with limited support before they transition to NetSuite Ship Central, which is the standard shipping solution. Oracle’s Ship Central FAQ says Ship Central connects to carrier services through the ShipStation API and does not give a definitive list of supported carriers. DHL is not mentioned on that page, so confirm that your DHL service is supported before you plan around it.
| Route | How it connects | A good fit when | What you maintain |
|---|---|---|---|
| NetSuite Ship Central | Carrier services through the ShipStation API | Your DHL service is supported and you want the standard shipping solution | The Ship Central setup and the carrier accounts behind it |
| Third-party shipping app | A SuiteApp or connector built for NetSuite that lists DHL | You want packaged functionality and your rules are standard | The app’s configuration, its subscription and your NetSuite-side mappings |
| Middleware | An integration platform sits between NetSuite and DHL’s API | You already run an integration platform for other systems | The flows, the mappings and the platform’s schedules and credentials |
| Custom build | Code in NetSuite calls DHL’s API directly | Your rules, documents or volume exceed what an app supports | The code, the credentials and every change DHL or NetSuite makes |
For a custom build, Oracle’s SuiteTalk documentation states that SOAP web services are being discontinued, with the 2025.2 endpoint the last planned and support ending with the 2028.2 release. It recommends SuiteTalk REST web services for all new integrations, so a new build should use REST. Our guides to Boomi and NetSuite integration and to RESTlet-based integrations cover the middleware and custom code approaches in more detail.
How do you set up a NetSuite DHL integration?
The order below suits any of the four routes.
- Confirm the DHL service and account. The API depends on whether you ship with DHL Express, eCommerce, Freight or another service. A DHL Express account is required for the MyDHL API.
- Decide the NetSuite triggers. Choose the record that starts a shipment, usually the item fulfillment, and where the label, tracking number and shipping cost will be stored.
- Choose the route. Use the table above. Check the vendor’s current DHL support in writing for any app or service.
- Map the data. Match NetSuite ship methods to DHL products, and map package weights, dimensions and address fields. International shipments also need the customs data DHL requires.
- Set up credentials and a dedicated integration role. Use a service account with only the permissions the integration needs, and record who renews each credential.
- Test in a sandbox. Run domestic, international, multi-package and address-error cases, and check that tracking numbers return to the right record.
- Monitor after go-live. Send failed shipments to a person who can fix them, and review the integration when the carrier or NetSuite changes a requirement.
Who owns what in the integration?
A carrier integration has three owners: the shipping lead for the packing and label workflow, the NetSuite administrator for records, roles and mappings, and the IT or integration owner for credentials, schedules and monitoring. Integration and interface work made up 363 of 3,241 classified client requests (11.2%), the third-largest category. In 226 of them the root cause sat in the integration itself, and integration-caused requests that closed took a median of 39 days, against about 23 days for a configuration change.
Timing follows the same pattern. In our own resolved client requests, work that touched an integration or previously delivered custom code took roughly twice as long as a configuration change, so we pin down one owner and any outside dependency before scoping.
What does keeping a carrier connection running involve?
Carrier connections need upkeep after go-live. Our shipping work involves carriers other than DHL, and the pattern applies to any carrier. In a September 2026 assessment for an equipment manufacturer, our team flagged that FedEx now requires accounts used for label printing to re-register with multi-factor authentication, and set it as a first-priority item of about two to four hours so labels keep printing. Oracle’s FedEx page states that until the initial MFA registration is complete, even for existing FedEx accounts in NetSuite, label creation may fail. For a life sciences company we connected a shipping scale and label printer to its shipping app and confirmed weights flowed into each shipment. For a home goods distributor, we built a mapping record that translates each retail customer’s carrier service code on incoming EDI orders into the right ship method, so staff no longer choose it by hand.
How Nuage approaches carrier and warehouse integrations
The client examples above involve other carriers, and the same steps apply to a DHL connection. Our team follows these steps. The order changes with each account.
- Inventory the carrier accounts and their authentication requirements. We list each account the shipping app or integration uses and what the carrier now requires to keep labels printing.
- Name the owner of each side. For every connection, we agree who owns the NetSuite side and who owns the carrier or warehouse side.
- Map carrier service codes to ship methods. Where customers’ orders name a carrier service, we translate it into the right ship method so staff do not choose it by hand.
- Connect and test the shipping devices. Scales and label printers are checked so weights flow into each shipment.
- Check the first runs in a sandbox. Failed shipments and missing tracking numbers are easier to find before production.
Nuage’s NetSuite experts do this work as part of NetSuite optimization and managed services. For shipping and warehouse questions in food and beverage, see our guide to food distribution ERP, and for integration partners, our guide to NetSuite integration service providers.
NetSuite DHL integration FAQ
Does NetSuite integrate with DHL natively?
Oracle’s carrier integration documentation names FedEx, UPS and USPS/Endicia, and that integration is not available to new customers. Ship Central, the standard shipping solution, connects to carriers through the ShipStation API, and Oracle’s FAQ does not list carriers or mention DHL. Confirm DHL support for your service before you choose Ship Central, or connect DHL through an app, middleware or a custom build.
Which DHL API do I need?
It depends on the DHL service you use. The MyDHL API is DHL Express’s REST API for rating, shipment creation, pickup and tracking, and it requires a DHL Express customer account. DHL eCommerce, Freight and other divisions have their own APIs on the developer portal, and a unified tracking API covers status across DHL shipment types.
Should I buy a shipping app or build a custom integration?
Start from your rules and who will maintain it. A packaged app suits standard rate, label and tracking needs. A custom build suits unusual rules, documents or volume, and it leaves you owning the code, the credentials and each change either side makes. Any new custom build should use SuiteTalk REST web services, since Oracle is discontinuing SOAP.
Can I connect other carriers alongside DHL?
Yes, and ask for it up front. Some shipping apps and middleware platforms are built for several carriers, and Ship Central connects to carriers through the ShipStation API. Ask each vendor which carriers it supports today, and how a second carrier’s rules and ship methods are kept separate from DHL’s.
What should I test before go-live?
Test a domestic shipment, an international shipment with customs data, a multi-package shipment and an address the carrier rejects. Check that the label prints, that the tracking number lands on the right record and that a failure reaches a person. Confirm the integration’s credentials and who renews them, since an expired login stops labels.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work in this article is our team’s, and none of it involves DHL.
