Connect DHgate: pull orders in, push fulfillment out
Copy the API gateway URL and App Key from the DHgate developer console, get the access token through the DHgate OAuth flow, paste them into Integration, test, map, activate — orders flow in and fulfillment flows back.
The DHgate connector pulls orders from your DHgate seller account into OMS, and pushes fulfillment back to DHgate. It can also push products and inventory, so orders, listings, stock, and shipping stay in sync on both sides.
Prerequisites#
- A DHgate seller account — the access token is issued for that seller account.
- Access to the DHgate developer console, where your app, its App Key, and the API gateway URL are shown.
- Ability to complete the DHgate OAuth authorization flow for that seller account — the access token comes from that flow.
Get your credentials#
- Copy the API gateway URL: in the DHgate developer console, copy the API gateway URL exactly as shown there. Do not type it from memory — it is not hardcoded, and one wrong character breaks every call.
- Copy the App Key: in the DHgate developer console, open your app and copy the App Key.
- Get the access token: complete the DHgate OAuth authorization flow for your seller account, then copy the access token from that flow. Save it somewhere safe — you will paste it into the Access token field in Integration.
- Note the endpoint paths you will use: the orders, products, inventory, fulfillment, and probe paths are in the DHgate Open Platform docs, relative to the gateway URL. You only need them if you change the advanced endpoint fields in the next step.
Fill it into Integration#
- Open Integration → Connector Marketplace → DHgate → New connection.
- API gateway URL (base_url) — required: paste the gateway URL you copied from the DHgate developer console, exactly as shown there, for example https://… . Do not add an endpoint path at the end — the endpoint fields below are relative to this URL.
- App Key (app_key) — required: paste the App Key from DHgate developer console → your app.
- Access token (token) — required: paste the access token for your DHgate seller account from the OAuth authorization flow. It is stored as a secret and never shown back after you save.
- Orders endpoint (ep_orders) — optional, advanced: the path of the “list unshipped orders” API, relative to the gateway URL, for example /order/list, per the DHgate Open Platform docs. Leave it as provided unless the docs for your app say otherwise — a wrong path means no orders can be pulled.
- Products endpoint (ep_products) — optional, advanced: the path of the product list API, relative to the gateway URL, per the DHgate Open Platform docs. It is used when products are pushed or read.
- Inventory endpoint (ep_inventory) — optional, advanced: the path of the inventory update API, relative to the gateway URL, per the DHgate Open Platform docs. It is used when inventory is pushed to DHgate.
- Fulfillment endpoint (ep_fulfillment) — optional, advanced: the path of the shipment / tracking submit API, relative to the gateway URL, per the DHgate Open Platform docs. It is used when fulfillment is pushed back to DHgate.
- Probe endpoint (ep_me) — optional, advanced: the path of a lightweight read API used for the “test connection” probe, relative to the gateway URL, per the DHgate Open Platform docs. If this path is wrong, the test can fail even when your credentials are correct.
Test the connection#
Click Test connection. The test uses the probe endpoint to check the gateway URL, the App Key, and the access token together, then shows a document-level preview with one real order so you can see platform fields next to the standard order. If there are no unshipped orders yet, place a test order first — the preview needs one real document. If the test fails, note the error and check the FAQ below before changing anything else.
Mapping / pick a template#
Pick the DHgate standard template. It maps order number, line SKUs, quantities, ship-to address, and fulfillment status. Check the mapping preview with one real order before activating — especially that every DHgate SKU is paired to an OMS product, so orders, products, and inventory line up on both sides.
Activate#
After activation, Integration pulls new unshipped orders on the schedule you set, pushes fulfillment with tracking numbers back to DHgate, and pushes product and inventory changes to DHgate. Watch the first few orders in Runs / Logs before trusting it unattended.
FAQ#
Test fails with an authentication error
The App Key or the access token is wrong or no longer valid. The App Key may have been copied from a different app, or the access token from the OAuth flow has expired, so DHgate refuses the call.
In the DHgate developer console, open your app and copy the App Key again. Then complete the DHgate OAuth authorization flow again, paste the new access token into the Access token field, and test again.
Connected but no orders are pulled in
The connection itself is fine. The seller account simply has no new unshipped orders in the pull range, so there is nothing to import yet.
Place a test order that will appear as unshipped, check that its time falls inside the pull range, then run a manual pull and confirm the order appears in the preview or in Runs / Logs.
Test fails or no data comes back after an endpoint path was changed
An advanced endpoint path no longer matches the DHgate Open Platform docs. The gateway URL and credentials can be correct, but if the probe path is wrong the test fails, and if the orders path is wrong no orders can be pulled.
Restore each changed endpoint field to the path in the DHgate Open Platform docs for your app — orders, products, inventory, fulfillment, and probe are each relative to the gateway URL — then save and test again. Change only one path at a time so you can see which one was wrong.
Orders pull in but fulfillment, products, or inventory do not push back
Pulling and pushing use different endpoint paths. Orders can work while the fulfillment, products, or inventory path is wrong, so that direction fails on its own.
Check the failing direction in the connection: compare the Fulfillment endpoint, Products endpoint, and Inventory endpoint fields with the DHgate Open Platform docs, fix the wrong one, and check Runs / Logs for the next push.