Connector directory: sales channels & EDI platforms
Every sales-channel and EDI connector: what it syncs, exactly which fields the connection wizard asks for, and where to get each value in the platform’s own admin.
This directory lists every sales-channel and EDI connector you can connect in Docklify. For each one you get three things: what it syncs, the exact fields the connection wizard asks for (required / optional, taken from the connector registry — nothing more, nothing less), and where to find each value in the platform’s own admin or developer portal. Two connectors have full step-by-step guides: Shopify and (in the shipping directory) UPS; here they appear as field summaries with a pointer to the full guide.
Standalone stores#
Shopify
Pulls orders into OMS and pushes inventory and fulfillment back. One connection per store. The full step-by-step guide is “Connect Shopify” in this section; the field summary:
| Field | Required? | Where to get it |
|---|---|---|
| Store domain | Required | Shopify Admin → Settings → Domains, e.g. my-store.myshopify.com (no https://) |
| Client ID | Required | Shopify Dev Dashboard → your app → API credentials (new model) |
| Client Secret | Required | Same page; shown once. The system exchanges it for a 24-hour token automatically |
Older connections that store an Admin API access token (shpat_…) instead of Client ID + Secret keep working — either credential set is accepted.
WooCommerce
Pulls orders from your WordPress store into OMS and pushes inventory and fulfillment back, via the WooCommerce REST API.
| Field | Required? | Where to get it |
|---|---|---|
| Store URL | Required | Your store’s full address including https:// |
| Consumer Key | Required | WordPress admin → WooCommerce → Settings → Advanced → REST API → Add key (starts with ck_) |
| Consumer Secret | Required | Shown once when the key is created (starts with cs_) — copy it immediately |
BigCommerce
Pulls orders into OMS and pushes inventory and fulfillment back, via the BigCommerce Store API.
| Field | Required? | Where to get it |
|---|---|---|
| Store Hash | Required | The hash in your API path: Settings → API → API accounts shows /stores/<hash>/… |
| Access Token | Required | Settings → API → Create API account; grant Orders / Products / Inventory scopes |
Marketplaces#
Amazon SP-API
Pulls Amazon orders (FBA and merchant-fulfilled) into OMS and pushes fulfillment back. Uses the Selling Partner API with LWA OAuth plus AWS SigV4 signing — the field list is longer than most, and every field below is needed.
| Field | Required? | Where to get it |
|---|---|---|
| Seller ID (Merchant Token) | Required | Seller Central → Settings → Account info → Merchant Token |
| Marketplace ID | Required | US marketplace: ATVPDKIKX0DER; other countries per the SP-API marketplace list |
| LWA Client ID | Required | Seller Central → Apps and Services → Develop apps → your SP-API app |
| LWA Client Secret | Required | Same app page as the Client ID |
| Refresh Token | Required | Authorize your app in Seller Central (Apps and Services → Authorize); the token starts with Atzr| |
| AWS Access Key ID | Required | AWS console → IAM → Users → Security credentials; the IAM policy must allow SP-API calls |
| AWS Secret Access Key | Required | Shown once when the IAM access key is created |
| IAM Role ARN | Optional | Only if you sign via STS AssumeRole (cross-account); leave empty to sign directly with the keys above |
Walmart Marketplace
Pulls Walmart orders into OMS and pushes inventory and fulfillment back. Authentication is a Consumer ID plus an RSA private key you generate.
| Field | Required? | Where to get it |
|---|---|---|
| Consumer ID | Required | Walmart Developer Portal → My Apps → your app |
| Private Key (PKCS#8 PEM) | Required | Generate an RSA key pair, register the public key in the Developer Portal, paste the PKCS#8 PEM private key here |
eBay
Pulls eBay orders into OMS and pushes inventory and fulfillment back, via the eBay Sell APIs.
| Field | Required? | Where to get it |
|---|---|---|
| Client ID (App ID) | Required | eBay Developers Program → Application Keys → your app |
| Client Secret (Cert ID) | Required | Same page; shown once |
| User Token | Optional | Only for flows that act as your seller account (OAuth user flow; valid ~2 hours). Leave empty and the system exchanges an application token automatically |
| Sandbox | Optional | Enter "true" to use the eBay sandbox; leave empty for production |
Etsy
Pulls Etsy receipts (orders) into OMS and pushes inventory back, via the Etsy Open API v3.
| Field | Required? | Where to get it |
|---|---|---|
| API Key (KEYSTRING) | Required | Etsy Developers → Your apps → your app (the keystring) |
| Shop ID | Optional | The numeric ID in your shop’s Etsy URL; speeds up shop lookup |
| OAuth Token | Optional | Obtained after you authorize the app in Etsy; needed for scopes beyond open-only reads |
Target Plus
Pulls Target+ orders into OMS and pushes inventory and fulfillment back. Target+ is invitation-only and its Partner API is not publicly documented — the API base URL and credentials come from your Target+ onboarding; follow the onboarding material if anything differs from this summary.
| Field | Required? | Where to get it |
|---|---|---|
| Partner API Base URL | Required | From your Target+ onboarding email / Partner Portal — it is tenant-specific, not a public address |
| Client ID | Required | Issued during Target+ onboarding |
| Client Secret | Required | Issued during Target+ onboarding |
| Supplier ID | Optional | Your Target+ supplier identifier, if onboarding assigned one |
Best Buy (Mirakl)
Pulls Best Buy marketplace orders into OMS and pushes inventory and fulfillment back. Best Buy’s marketplace runs on Mirakl, so the credential is a Mirakl API key from your seller account.
| Field | Required? | Where to get it |
|---|---|---|
| API Key | Required | Best Buy seller admin (Mirakl) → top-right username menu → API Key → Generate / copy |
Newegg
Pulls Newegg orders into OMS and pushes inventory and fulfillment back, via the Newegg Marketplace API.
| Field | Required? | Where to get it |
|---|---|---|
| Seller ID | Required | Seller Portal → Data Feed Settings → API Settings (4 characters) |
| API Key | Required | Same page; if empty, click REGISTER to apply. Enable API first |
| API Secret | Required | Same page (sent as the SecretKey header) |
Wayfair
Pulls Wayfair (CastleGate) orders into OMS and pushes inventory and tracking back, via the Wayfair Partner API.
| Field | Required? | Where to get it |
|---|---|---|
| Client ID | Required | Wayfair Partner Home → API settings |
| Client Secret | Required | Same page as the Client ID |
| Access Token | Optional | Leave empty — the system exchanges Client ID + Secret for a 12-hour token automatically |
| Supplier ID | Optional | Needed for inventory / tracking pushes |
| Sandbox | Optional | Enter "true" to use the Wayfair sandbox |
Home Depot
Pulls Home Depot supplier orders into OMS and pushes inventory and fulfillment back. Home Depot does not publish a public REST API — access is provisioned per supplier, and the base URL and API key come from your supplier onboarding. Follow the onboarding material if details differ.
| Field | Required? | Where to get it |
|---|---|---|
| API Base URL | Required | From your Home Depot supplier onboarding (tenant-specific) |
| API Key | Required | Issued during onboarding (sent as the X-API-Key header) |
| Supplier ID | Optional | Your Home Depot supplier identifier, if assigned |
Lowe’s (Mirakl)
Pulls Lowe’s marketplace orders into OMS and pushes inventory and fulfillment back. Lowe’s marketplace runs on Mirakl.
| Field | Required? | Where to get it |
|---|---|---|
| Mirakl Base URL | Required | Your Lowe’s Mirakl environment address, e.g. https://<env>/api — from your seller onboarding |
| API Key | Required | Lowe’s seller admin (Mirakl) → your profile → API key |
Overstock
Pulls Overstock partner orders into OMS and pushes inventory and fulfillment back. There is no public REST spec — the base URL and key come from Overstock’s partner integration documents.
| Field | Required? | Where to get it |
|---|---|---|
| API Base URL | Required | From Overstock’s partner integration documents |
| API Key | Required | Issued with the integration documents (sent as the x-api-key header) |
DHgate
Pulls DHgate orders into OMS and pushes inventory and fulfillment back, via the DHgate Open Platform. Note this connector also asks for the endpoint path of each API group — copy them from the Open Platform docs for your app rather than guessing.
| Field | Required? | Where to get it |
|---|---|---|
| Gateway Base URL | Required | DHgate developer console → your app → gateway address |
| App Key | Required | Same app page |
| Access Token | Required | Obtained via the DHgate OAuth flow for your seller account |
| Endpoint paths (orders / products / inventory / fulfillment / account) | Optional | Relative path of each API group, exactly as listed in the Open Platform docs for your app |
AliExpress
Pulls AliExpress orders into OMS and pushes inventory and fulfillment back, via the AliExpress Open Platform (TOP gateway).
| Field | Required? | Where to get it |
|---|---|---|
| Gateway Base URL | Required | AliExpress Open Platform console → your app → TOP gateway address (paste exactly as shown) |
| App Key | Required | Same app page |
| API Secret | Required | Same app page (used to sign requests) |
| Session Token | Required | Obtained via the AliExpress OAuth authorization for your seller account |
Wish
Pulls Wish orders into OMS and pushes inventory and fulfillment back, via the Wish Merchant API.
| Field | Required? | Where to get it |
|---|---|---|
| Access Token | Required | Wish merchant admin → API settings / OAuth authorization (valid 30 days — renew before it expires) |
| API Base URL | Optional | Default https://merchant.wish.com/api/v2; only change for the China region or sandbox |
Social commerce#
TikTok Shop
Pulls TikTok Shop orders into OMS and pushes inventory and fulfillment back, via the TikTok Shop Partner API.
| Field | Required? | Where to get it |
|---|---|---|
| App Key | Required | TikTok Shop Partner Center → App management → your app |
| App Secret | Required | Same app page |
| Access Token | Optional | Obtained after the shop authorizes your app |
| Warehouse ID | Optional | Required for inventory sync: without it, inventory pushes are rejected to prevent overselling |
Temu
Pulls Temu orders into OMS and pushes inventory and fulfillment back, via the Temu Open Platform.
| Field | Required? | Where to get it |
|---|---|---|
| App Key | Required | Temu Partner / Open Platform → your app |
| App Secret | Required | Same app page |
| Access Token | Required | Temu Seller Center → Authorization management → authorize the app |
| Region | Optional | us (default) / eu / global — must match your shop’s region |
Shein
Pulls Shein orders into OMS and pushes inventory and fulfillment back, via the Shein Open Platform.
| Field | Required? | Where to get it |
|---|---|---|
| Open Key ID | Required | After authorizing in Shein Seller Center, exchange the tempToken for the open key pair (Open Platform → get-by-token) |
| Open Key Secret | Required | Issued with the Open Key ID (decrypted with your app’s secret key; used for HMAC-SHA256 signing) |
| Store Code | Optional | Your Shein store code, if you run several stores |
EDI platforms#
Docklify connects to EDI platforms over their REST APIs and exchanges standard documents (850 purchase orders, 856 ASN, 810 invoices, 940/945 warehouse orders) through them. You bring your own account with the EDI platform; Docklify does not replace your trading-partner setup with each retailer — see “Traditional retail EDI” below.
SPS Commerce
Exchanges EDI documents with your retail trading partners through SPS Commerce (RSX / API), using an OAuth2 client-credentials pair issued for your SPS account.
| Field | Required? | Where to get it |
|---|---|---|
| Client ID | Required | Issued by SPS for your account’s API access (ask your SPS account team) |
| Client Secret | Required | Issued together with the Client ID |
TrueCommerce
Exchanges EDI documents through TrueCommerce (Foundry / Transaction Manager). Connection details are tenant-specific — your TrueCommerce account manager issues the base URL and either an API key or an OAuth pair.
| Field | Required? | Where to get it |
|---|---|---|
| Base URL | Required | Ask your TrueCommerce account manager — it is tenant-specific |
| API Key | Optional | If your account uses API-key auth; leave empty if you use OAuth below |
| Client ID | Optional | Required when there is no API key (OAuth pair) |
| Client Secret | Optional | Required when there is no API key (OAuth pair) |
Rithum (CommerceHub / Dsco)
Exchanges orders and inventory with retailers on the Rithum network (Dsco API v3), using OAuth2 client credentials from your Rithum supplier account.
| Field | Required? | Where to get it |
|---|---|---|
| Client ID | Required | Rithum supplier account → API / developer settings (or ask your Rithum onboarding contact) |
| Client Secret | Required | Issued together with the Client ID |
Cleo
Exchanges EDI files through your Cleo partner mailbox: Docklify pulls new files from the mailbox’s download folder and uploads outbound files to the upload folder.
| Field | Required? | Where to get it |
|---|---|---|
| Mailbox Username | Required | Issued by your Cleo administrator when the partner mailbox was set up |
| Mailbox Password | Required | Issued together with the username |
B2BGateway
Exchanges EDI documents through B2BGateway (TrueCommerce EDI). The base URL is tenant-specific and the API key is sent as the X-API-Key header.
| Field | Required? | Where to get it |
|---|---|---|
| Base URL | Required | Ask your B2BGateway account manager — it is tenant-specific |
| API Key | Required | Issued by your account manager (sent as the X-API-Key header) |
Traditional retail EDI#
Big-box and chain retailers — Costco, Target (EDI), Kroger, CVS, Walgreens, Dollar General, Family Dollar, Dollar Tree, Bed Bath & Beyond, Kohl’s, JCPenney, Nordstrom, Macy’s, Dick’s Sporting Goods, Academy Sports, Tractor Supply, PetSmart, Petco, Ulta, Sally Beauty, AutoZone, Advance Auto, O’Reilly, Genuine Parts, Best Buy (EDI), GameStop, Foot Locker, H-E-B, Albertsons, Ahold Delhaize, Meijer and similar — are not connected one retailer at a time. They are reached through an EDI platform above (SPS Commerce, TrueCommerce, Rithum, Cleo or B2BGateway): the retailer is set up as a trading partner on your EDI account, Docklify maps the standard documents (850/856/810/940/945) to and from that partner, and the connection is switched on per customer as needed. If you are onboarding a new retailer, connect the EDI platform first, then ask for the trading-partner mapping to be enabled for that retailer.
Manual channels#
Two catalog entries are not API connections at all: “Manual” (orders typed in or uploaded by file) and “Portal” (orders placed by your customers in the client portal). They need no credentials — they exist so manual and portal orders follow the same OMS/WMS flow as API orders.