English

中文

English

中文

Appearance

Platform Comparison & Caveats ​

Contents ​

1. How to Read This ​

Every platform follows the same end-to-end flow (connect → fetch → match → ship → push back; see How E-Commerce Integration Works), but each platform does each step differently. Before connecting a platform, use the matrix below to quickly compare its connection method, whether an IP allowlist is needed, whether orders are real-time, and whether it can push stock back and customize shipping codes; then read its entry in Per-Platform Caveats for the things to prepare first. You create accounts on EC accounts (merchant) or EC accounts (warehouse).

2. Platform Capability Matrix ​

PlatformConnectionIP allowlistOrder fetchStock pushProduct mappingCustom shipping code
ShopifyAuthorization—Real-time✅✅✅
ShopeeAuthorization—Scheduled✅✅❌ Fixed
ShoplineKey—Scheduled✅✅✅
LiteshopAuthorization—Real-time✅❌✅
91APPKey—Scheduled✅❌✅
MomoCredentials✅Scheduled✅✅❌ Fixed
WooCommerceKey—Real-time✅✅✅
CyberbizKey—Scheduled✅✅✅
Yahoo SCMCredentials—Scheduled✅✅✅
PChomeKey✅Scheduled✅✅✅
Mo+Key✅Scheduled✅✅❌ Fixed
EasyStoreKey—Scheduled✅✅✅
BvShopKey—Scheduled✅✅✅
CoupangSigned key✅Scheduled✅✅❌ Fixed
RutenSigned key—Scheduled✅※✅✅
1shopKey—Scheduled❌❌✅
EtMallCredentials—Scheduled✅✅❌ Fixed
  • Connection: Authorization = click to authorize and log in on the platform; Key / Signed key = paste a token generated on the platform; Credentials = supplier account & password. See How it works §Connection.
  • Order fetch: "Real-time" = the platform pushes, almost no delay; "Scheduled" = the system pulls periodically, looks back ~7 days, has a delay. Real-time push is still being rolled out for some platforms marked "Scheduled"; treat them as scheduled for now.
  • Product mapping: ✅ = platform products / variants can be mapped automatically; ❌ = unmapped products must be mapped manually.
  • Custom shipping code: ❌ Fixed = shipping methods are mapped by the system from a built-in list and cannot be customized; you usually only handle "self-delivery."
  • ※ Ruten: stock can be pushed, but the platform minimum quantity is 1 — it cannot be pushed to 0; when sold out, the system notifies you to delist on Ruten yourself.

3. Per-Platform Caveats ​

Only the things that matter most before connecting and that differ across platforms are listed; the shared flow is in How it works.

Shopify ​

  • Two connection modes: install the public App from the Shopify App Store (just select the store, authorize, then claim it in the back office — no domain to fill in), or bring your own Custom App and fill in domain + keys then authorize.
  • The platform doesn't provide labels; after you ship with your own carrier, the system creates the fulfillment, pushes the tracking number, and notifies the buyer.
  • COD is detected by payment-gateway name; an unusual / custom COD gateway may fail to import the first time — test one COD order before going live.
  • Removing the App on Shopify auto-disconnects the account; you must re-authorize.

Shopee ​

  • Official-authorization connection, no keys needed; enterprise (main) accounts are not supported — authorize an individual shop account.
  • Shipping codes are not customizable; Shopee's carriers (store-to-store, home delivery, convenience stores, T-Cat, HCT…) are mapped automatically by the system.
  • Labels occasionally need to wait (up to ~15 minutes); a "try again later" prompt during that window is normal, not an error.

Shopline ​

  • A single merchant key connects it; the key is long-lived and must be re-entered if it expires.
  • Supports integrated-carrier (7-11 / FamilyMart / T-Cat / HCT / cross-border) online tracking-number assignment and label printing; 7-11 labels redirect to the 7-11 print page.

Liteshop ​

  • Official-authorization connection. Shipping is reported item by item; bundle products are reported as "number of sets." The platform provides no tracking number or label — your own warehouse tracking number is used.
  • Product mapping does not sync automatically: unmapped products must be mapped manually, and the back-office "mapped product count" won't change on its own.
  • Only "paid / cash-on-delivery" orders are pulled in; orders in other payment states are skipped.

91APP ​

  • Connect with a "customer code" and an "API Key."
  • The product catalog cannot be synced in from 91APP: product mapping relies on manually mapping unmapped products plus code backfill.
  • Orders sync on a schedule looking back ~7 days; new orders are delayed.

Momo ​

  • Required before connecting: give Momo your system's fixed IP to allowlist, or the connection fails even with correct credentials (the screen lists the IP to provide).
  • Fill in business ID, store code, store password, and the last 3 OTP digits (required); the PDF password is optional, used to unlock Momo's encrypted shipping labels.
  • One order may be split into several; the system merges them automatically and attempts box-merging; shipping codes aren't customizable — choose "self-delivery" for your own carrier.
  • Backfilling the warehouse code to Momo requires review; after submitting, it takes effect only after Momo's back office approves.

WooCommerce ​

  • Generate the API key with Read/Write permission in WooCommerce; a read-only key works but can't sync in real time — it only polls.
  • Enter the store root URL — don't add /wp-json.
  • Self-ship platform: doesn't push tracking numbers or print labels; shipping only updates the order status to "completed."
  • Mapping uses WooCommerce's shipping method code (method_id); the 5 common ECPay-plugin values are pre-filled, and other plugins can be filled in manually.

Cyberbiz ​

  • Fill in the Access Token (required) + email; T-Cat / Kerry customer codes are only needed when shipping with that carrier.
  • T-Cat and Kerry waybills are generated locally by the warehouse system — fill in the customer codes first or you can't print them.
  • POS-version stores reconcile stock via stock adjustments to avoid overselling.

Yahoo SCM ​

  • Connect with several keys the platform provides (token, key value, IV, salt, version).
  • Three delivery behaviors differ: convenience stores and third-party logistics get auto-assigned numbers and labels from Yahoo (labels are asynchronous, wait a moment); home delivery requires you to set a default carrier, fill in the number yourself, and provides no platform label.
  • Product mapping can be synced in from Yahoo, but the warehouse code cannot be backfilled to Yahoo.

PChome ​

  • Required before connecting: give PChome your vendor outbound IP to allowlist.
  • Connection only takes the vendor ID + two encryption keys.
  • Transfer-order platform: no number assignment or labels; ship with your own carrier and push the tracking number back; map "default" and the supported carriers first.
  • Stock push is capped at 1200, and the warehouse code cannot be backfilled to PChome (maintain it in the PChome back office).

Mo+ ​

  • Required before connecting: apply to Momo to allowlist the system IP.
  • Fill in Token + PDF password; labels are encrypted PDFs, so the PDF password is required.
  • Shipping codes aren't customizable — you only handle "self-delivery"; the warehouse code cannot be backfilled.

EasyStore ​

  • Generate an access token in the EasyStore back office and enter it together with the store URL (must be https://, no /api).
  • Self-ship platform: labels come from your own carrier; after shipping the system pushes the tracking number back so the platform marks it shipped and notifies the buyer.
  • The product code (SKU) is store-wide unique; a backfill collision is rejected by the platform.

BvShop ​

  • Connect with the API URL + API Token (request from BVSHOP support); whether the URL includes /api/v2 affects every request, so fill it in correctly.
  • Self-ship platform: no labels; ship with your own carrier and push the tracking number back.
  • A payment name customized in the platform back office that the system doesn't recognize will hold the order; a technician must register it, then re-fetch.

Coupang ​

  • Required before connecting: apply to Coupang to allowlist the server IP.
  • Connect with the vendor code + two keys, then set return centers (7-11 / FamilyMart) and the outbound place.
  • Shipping codes are fixed to 4 (7-11 / FamilyMart / Kerry / HCT) and aren't customizable.
  • One order may split into several boxes; the system automatically splits it into multiple fulfillments; on shipping it auto-assigns numbers and you can download each carrier's label.

Ruten ​

  • Connect with three keys; the server clock must be within 5 minutes of Ruten's.
  • Two logistics types to set up separately: integrated logistics (7-11 / FamilyMart / Hi-Life / T-Cat / i-Post) auto-assigns numbers and prints waybills; seller self-ship requires mapping Ruten shipping codes to your own carrier before tracking numbers are pushed back.
  • Don't merge-ship integrated-logistics orders: merging causes all but the first order to never receive a scan on the platform and never turn to shipped.
  • Stock can't be pushed to 0; when sold out, delist on Ruten yourself.

1shop ​

  • Connect with appid + secret.
  • Read-only integration: only pulls orders in; after shipping it pushes nothing back — no tracking number, no stock, no product sync — delivery and waybills are entirely your own process.
  • Shipping codes must first be mapped from 1shop codes to your own carrier in the shipping-mapping settings, or order import gets stuck.

EtMall ​

  • Connect with the supplier account, password, and encryption key (all required); a wrong encryption key won't error on the connection test, but order recipient name / phone / address will be empty.
  • Two logistics types: store pickup gets numbers and labels from EtMall automatically; home delivery requires shipping with your own carrier, your own mapping, and provides no platform label.
  • Shipping codes aren't customizable — you only map "home delivery" to your own carrier; the warehouse code must be set up in EtMall beforehand and isn't backfilled.

4. FAQ ​

Jump to: FAQ ｜ Notes

4.1 FAQ ​

▪ Which platforms need an IP allowlist before connecting? ​

Momo, PChome, Mo+, and Coupang. Until allowlisted, the connection fails even with correct keys / credentials, and it can't be solved by back-office settings — it must be arranged on the platform side.

▪ Why can't I customize shipping codes on some platforms? ​

For Shopee, Momo, Mo+, Coupang, and EtMall, shipping methods are mapped from a fixed list by the platform or system; you usually only set up "self-delivery." Other platforms can be mapped yourself in the shipping-mapping settings.

▪ Which platforms won't print a waybill for me after shipping? ​

Self-ship platforms: Shopify, WooCommerce, EasyStore, BvShop, PChome, and the read-only 1shop. These ship with your own carrier and print your own labels; the system only pushes the tracking number back (1shop doesn't even push that).

▪ My product sells on multiple platforms — will stock clash? ​

No, as long as each platform account has inbound push enabled with a ratio set; after putaway the system splits the quantity back to each platform by ratio. See EC accounts. Only 1shop doesn't support stock push-back.

4.2 Notes ​

⚠️ Important ​

  • A wrong key on encryption-based platforms doesn't always error: e.g. EtMall's encryption key or Momo's store password — when wrong, the connection looks fine but recipient data or encrypted labels break. Double-check when entering them.
  • Avoid merge-shipping integrated-logistics orders: on platforms like Ruten, merge-shipping leaves some orders unable to turn to shipped on the platform.

💡 Tip: before connecting each platform, read its "caveats" entry end to end — confirm the common blockers (IP allowlist, PDF password, non-customizable shipping) up front to save round trips.

FeatureDescriptionLink
How E-Commerce Integration WorksThe shared end-to-end flow for every platformGo
EC accounts (merchant)Merchants manage their own platform accountsGo
EC accounts (warehouse)Warehouse manages accounts on behalf of merchantsGo
Sales channelsSet up the matching channel before connecting a platformGo