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
| Platform | Connection | IP allowlist | Order fetch | Stock push | Product mapping | Custom shipping code |
|---|---|---|---|---|---|---|
| Shopify | Authorization | — | Real-time | ✅ | ✅ | ✅ |
| Shopee | Authorization | — | Real-time | ✅ | ✅ | ❌ Fixed |
| Shopline | Key | — | Real-time | ✅ | ✅ | ✅ |
| Liteshop | Authorization | — | Real-time | ✅ | ❌ | ✅ |
| 91APP | Key | — | Scheduled | ✅ | ❌ | ✅ |
| Momo | Credentials | ✅ | Scheduled | ✅ | ✅ | ❌ Fixed |
| WooCommerce | Key | — | Real-time | ✅ | ✅ | ✅ |
| Cyberbiz | Key | — | Scheduled | ✅ | ✅ | ✅ |
| Yahoo SCM | Credentials | — | Scheduled | ✅ | ✅ | ✅ |
| PChome | Key | ✅ | Scheduled | ✅ | ✅ | ❌ Fixed |
| Mo+ | Key | ✅ | Scheduled | ✅ | ✅ | ❌ Fixed |
| EasyStore | Key | — | Real-time | ✅ | ✅ | ✅ |
| BvShop | Key | — | Real-time | ✅ | ✅ | ✅ |
| Free Store | Key | — | Real-time | ✅ | ✅ | ✅ |
| Coupang | Signed key | ✅ | Scheduled | ✅ | ✅ | ❌ Fixed |
| Ruten | Signed key | — | Scheduled | ✅※ | ✅ | ✅ |
| 1shop | Key | — | Scheduled | ❌ | ❌ | ✅ |
| EtMall | Credentials | — | 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 notifies us of new orders and order changes and the system fetches right away, so new orders usually arrive within a few minutes (about 5 minutes for Shopee); accounts on these platforms have a "Realtime New Order Fetch" switch, and turning it off makes new orders arrive only at the fetch slots you set, while orders already in the system keep syncing. "Scheduled" = the system pulls periodically, looks back ~7 days, has a delay. Real-time platforms are also fetched on schedule as a backstop. BvShop's real-time notifications need extra setup; see its notes below.
- Product mapping: ✅ = platform products / variants can be mapped automatically; ❌ = unmapped products must be mapped manually.
- Custom shipping code: ❌ Fixed = shipping types are mapped by the system from a built-in list and cannot be customized; you usually only handle "self-delivery" (for PChome, the single "預設物流(default)" entry).
- ※ 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. When the gateway name isn't on the system's list, orders marked as paid (for example, a bank transfer you "Mark as paid" after receiving it) are pulled in as usual, with nothing to collect on delivery.
- Orders created at a POS store are skipped and never pulled into the warehouse.
- Authorized but uncaptured orders (manual-capture payment settings) are not pulled in until you capture payment on Shopify. Shipped orders and prepaid orders still awaiting payment are not pulled in either.
- The order amount and item quantities follow the current values on Shopify, excluding refunds and items removed with "Edit order"; the COD amount is the balance still unpaid on Shopify (anything already paid, such as with store credit, isn't collected, and once you mark the order as paid on Shopify the COD amount becomes 0). An unpaid cash-on-delivery order with no outstanding balance can't tell how much to collect, so it isn't pulled in (an existing order that hasn't started picking isn't updated this round); it is logged in the sync record and the merchant is notified.
- Orders that are partially refunded or edited ship as usual; an order that hasn't started picking has its amounts, COD amount and item quantities updated to the platform's current values on the next fetch, and the scheduled fetch also picks up unshipped partially refunded orders. If every item to ship has been refunded or removed with "Edit order" (only shipping remains), it is treated as a full refund whether or not it has been paid (including unpaid cash-on-delivery orders); a fully refunded order is held as "Refunded on Platform" and never canceled automatically (see Why didn't an order on the platform come in?).
- Removing the App on Shopify auto-disconnects the account; you must re-authorize.
- If the account has not synced with Shopify for more than about 90 days (for example, it is disconnected, or both order fetching and stock sync are turned off), the Shopify authorization expires and the connection can no longer recover on its own; 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.
- Only new orders waiting to ship are imported. An order the buyer asked to cancel, with no seller response yet, is not pulled in; an unshipped order already in the warehouse is held as "Buyer Requested Cancellation" and is canceled only once Shopee confirms the cancellation. If the seller declines, release the hold yourself.
Shopline
- A single merchant key connects it; the key is long-lived and must be re-entered if it expires.
- A successful connection test registers real-time notifications with Shopline automatically — you never enter a notification URL yourself, and new orders and cancellations arrive within seconds. If the key lacks webhook permission, the connection still succeeds and simply falls back to scheduled fetching, with no impact on shipping.
- 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.
- The waybill layout can be A4 or thermal, A4 by default. With thermal, the system splits Shopline's T-Cat A4 waybill (including cash on delivery) into a left and a right section, each printed as its own page so a label printer can print it directly; HCT, cross-border and convenience-store pickup labels stay A4 and are not split. Shopline labels are produced the first time a waybill is printed, so any waybill first printed after the switch gets the new layout. ⚠️ Thermal cuts up the A4 waybill, and carriers may reject and return such shipments — confirm with Shopline and the carrier first. See Edit E-commerce Account for where to set it.
- For custom shipping methods (anything other than the integrated carriers above), use the shipping method name shown in the Shopline back office as the shipping mapping code; each custom shipping method gets its own mapping and can point to a different carrier. Until it's mapped the order isn't imported, and the sync record's error message shows the exact code to enter — copy it into the mapping as is.
- Orders created at a POS store are skipped and never pulled into the warehouse.
- New orders with a refund in progress are not pulled in; unshipped orders already in the warehouse are held as "Refunded on Platform", aren't canceled automatically, and aren't updated while held. Platform quantities don't subtract the refund, so confirm how much to ship before releasing the hold.
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.
- Orders are imported only when the platform marks them as new and ready to ship, with payment either paid or cash on delivery. This applies to scheduled fetching and real-time notifications. New orders that are partially shipped, shipped or received are skipped to prevent duplicate shipping; a new order whose status can't be read is not imported, and the sync record shows why and the merchant is notified. Orders already in the warehouse keep updating until picking starts; an order shipped on the platform but not yet picked is held as "Shipped on Platform". Platform cancellations are synced; an order with a cancellation request is held as "Buyer Requested Cancellation" and canceled only once the platform confirms it (if the seller declines, release the hold yourself); a fully refunded order that isn't canceled is held as "Refunded on Platform" and never canceled automatically.
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.
- The warehouse order is canceled only when every sub-order of the parent order is canceled; when only some are canceled, those items are removed from the order.
- If picking hasn't started but the platform shows a sub-order as actually shipped, the order is held as "Shipped on Platform" and its items stay untouched; a sub-order that is only confirmed for shipping, or an order entirely awaiting payment, isn't held and isn't updated in that round. See 91APP order fetching.
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 unlocks Momo's encrypted shipping labels. The field can currently be left blank, but without it printing shipping labels fails, with a prompt to make sure the PDF password is filled in.
- 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.
- The waybill layout can be A4 or thermal, A4 by default. With thermal, the system splits Momo's A4 waybill into a left and a right section, each printed as its own page so a label printer can print it directly; this affects only home-delivery waybills (T-Cat, Pelican, HCT, Kerry TJ) — convenience-store pickup labels stay A4 and are not split. ⚠️ Thermal cuts up Momo's A4 waybill, and carriers may reject and return such shipments — confirm with Momo and the carrier first. See Edit E-commerce Account for where to set it.
- Backfilling the warehouse code to Momo requires review; after submitting, it takes effect only after Momo's back office approves.
- Known limitation: platform cancellations do not sync back to the warehouse. Momo's order API doesn't expose cancellation status, so after a buyer cancels on Momo, cancel the order manually in the system or it will ship as usual.
WooCommerce
- Generate the API key with Read/Write permission in WooCommerce; a read-only key can't sync in real time, and with stock push enabled the rejected write marks the account "Disconnected".
- If that happened, switch to a Read/Write key and reconnect to resume fetching orders.
- 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.
- Only new "processing" orders are imported; on-hold, pending-payment and completed orders are not pulled in. Orders canceled or refunded on the platform cancel the warehouse order (or hold it once picking has started): on WooCommerce, refunded is the order status itself.
Cyberbiz
- Fill in the Access Token (required) + email; T-Cat / Pelican customer codes are only needed when shipping with that carrier.
- T-Cat (including cold chain) and Pelican waybills are generated locally by the warehouse system — fill in the customer codes first or you can't print them.
- HCT needs no customer code: the number is booked under Cyberbiz's own carrier contract and Cyberbiz returns the waybill too, so the warehouse system only requests the number and prints it; convenience-store pickup likewise needs no customer code.
- T-Cat quick store pickup supports room-temperature only: room-temperature quick-pickup orders (cash on delivery or prepaid) are imported as the "Cyberbiz 黑貓快速到店" shipping type, not as T-Cat home delivery. Quick-pickup orders of any other temperature (frozen, refrigerated and so on) are not imported, and are not silently shipped as T-Cat home delivery: the sync record shows "Unmapped shipping method code:" followed by the shipping method name from the Cyberbiz back office, and both the merchant and the warehouse side receive one fetch failure-summary notification (the failures of one fetch run are combined into a single notification, not one per order; no repeat within 6 hours while it keeps failing). To handle such orders, map that shipping method name to a warehouse-side shipping type in the shipping mapping.
- T-Cat quick store pickup waybills are provided by Cyberbiz: once the number is requested you can print directly at the QC station; a reprint reuses the file obtained the first time and does not fetch it from Cyberbiz again. No T-Cat customer code is needed, and you don't have to print from the Cyberbiz back office. The waybill number shown on screen is the ID of the Cyberbiz shipment record, not T-Cat's physical waybill number. If Cyberbiz doesn't return a usable waybill, the screen tells you to print it from the Cyberbiz back office.
- The waybill layout can be A4 or thermal, A4 by default, and it applies to T-Cat quick store pickup only. With thermal, the system takes the left and right sections of the A4 waybill Cyberbiz provides and stacks them on one page of about 95×195 mm; waybills of the other Cyberbiz carriers (7-ELEVEN, FamilyMart, Hi-Life, T-Cat home delivery, T-Cat cold chain, Pelican, HCT) are not affected. A quick-pickup waybill is produced the first time it is needed (the first print, or the pre-generation when a shipment enters QC), so only waybills first generated after the switch get the new layout. If the layout fails, A4 is not printed instead; the waybill is marked as a print failure and the screen shows "Thermal layout failed; please print again. If it keeps failing, change this CyberBiz account's waybill layout back to A4". The waybill number is kept, printing again fetches the file from Cyberbiz and lays it out once more, and if it keeps failing you can set the account's layout back to A4 and print again. So if a quick-pickup waybill still prints as A4 after you switched, its label was already generated before the switch and the reprint reuses the existing file; it is not a malfunction. See Edit E-commerce Account for where to set it.
- The package size of T-Cat quick store pickup is decided once, when the number is requested: the system declares one of three tiers, 60, 90 or 105, to Cyberbiz, and it cannot be corrected afterwards. The tier is based on the length + width + height (cm) of the packaging marked "Use as Shipping Volume Basis" (the outer box) on each box: up to 60 is 60, up to 90 is 90, anything larger is 105. With several boxes, the box with the smallest three-side sum is used — it prefers to send a lower tier rather than overestimate; if a box has more than one outer box marked, or no box has an outer box marked, the smallest tier, 60, is always sent. The number is usually requested before packing (both the batch number request after picking finishes and the advance request when a shipment enters QC happen while no box exists yet), so what is actually sent is mostly 60; only a shipment whose number is requested after packing is graded by its boxes. See Edit Consumable for setting the outer box.
- For custom shipping methods (anything other than the integrated 7-ELEVEN / FamilyMart / Hi-Life / T-Cat / T-Cat quick store pickup / Pelican / HCT logistics), use the shipping method name shown in the Cyberbiz back office as the shipping mapping code; until it's mapped the order isn't imported, and the sync record's error message shows that name verbatim — copy it into the mapping as is.
- 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; shipping codes cannot be customized. On the edit page, click the suggested code "預設物流(default)" (shown in Chinese in every language) under "Shipping Type Mappings" and pick one warehouse-side carrier that can be pushed back (T-Cat, HCT, Pelican, Kerry TJ, Tong Ying); every PChome order uses this one mapping, and until it is set, order import fails and you are notified. "PAYUNi 黑貓宅配" (PAYUNi T-Cat, shown in Chinese in every language) does not count as T-Cat: you can pick it in the dropdown, but it cannot be pushed back.
- Without a tracking number, or with a carrier outside the list above, the system does not report the shipment to PChome: the system reports once, about 10 minutes after shipping. If the order has no tracking number at that point, or its carrier can't be mapped to a PChome carrier code, you receive a "Shipment Error" notification with the order number, and the order history gets an entry. The system does not report again later, even if the number is added or the carrier is corrected, so check the order in the PChome back office.
- 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.
- The waybill layout can be A4 or thermal, A4 by default. With thermal, the system splits Mo+'s A4 waybill into a left and a right section, each printed as its own page so a label printer can print it directly; this affects only home-delivery waybills (T-Cat, HCT) — convenience-store pickup labels (7-ELEVEN and FamilyMart, both warehouse-to-store and store-to-store) stay A4 and are not split. Waybills produced by "batch tracking numbers" in a picking wave are split too, so there's no need to reprint. ⚠️ Thermal cuts up the A4 waybill, and carriers may reject and return such shipments — confirm with Mo+ and the carrier first. See Edit E-commerce Account for where to set it.
EasyStore
- Generate an access token in the EasyStore back office and enter it together with the store URL (must be https://, no /api).
- If the access token has no write permission, the platform rejects stock pushes as an authorization error and the account is marked "Disconnected" — reconnect with a token that has write permission.
- 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.
- Only new paid or cash-on-delivery orders that haven't shipped are pulled in. A new partially refunded order isn't pulled in; only a system log is kept and no notification is sent. An unshipped order already in the warehouse is held as "Refunded on Platform" and isn't updated while held. Platform quantities don't subtract the refund, so confirm how much to ship before releasing the hold. A fully refunded order is held as "Refunded on Platform" when the platform sends an order update, and never canceled automatically.
BvShop
- Connecting only takes the API Token (request it from BVSHOP support); there is no URL to fill in, because the system connects to BVSHOP's API on its own. A URL saved on an existing account is no longer used; an account that could not connect because of a wrong URL only needs its connection tested again.
- Real-time fetching needs a webhook set up separately: ask BVSHOP support for the webhook secretKey (not the API Token), enter it in "Webhook signing secret (optional)", save, then test the connection again (changing credentials resets the connection status to untested). After saving, the edit page shows "Webhook URL"; copy it into the Webhook URL field under 「商店設定 > 基本設定 > Webhook 設定」 in the BVSHOP admin and tick 「訂單」 (Orders) under subscribed events. Without it, orders are fetched on schedule.
- When a real-time notification arrives: orders canceled on the platform are canceled in the system; paid, not-yet-shipped orders, and orders in the system that haven't finished shipping, are checked with the platform right away. Orders already canceled in the system are not restored by later platform changes; resume them manually if needed. New cash-on-delivery (unpaid) orders still arrive through scheduled fetching.
- Splitting or editing an order on the platform: if the order hasn't started picking, its items are updated to the platform's contents and the new order from the split comes in as usual. If picking has already started, the order is not changed but held as "Items Changed on Platform" (see Order Holds for how to handle it); the new order still comes in as usual. Name or price changes alone don't hold the order. If the original order has already shipped, the system cannot stop it and the new order still ships — check before splitting.
- 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.
- For a deposit order (deposit paid up front, balance paid on delivery) with cash on delivery, the COD amount is the unpaid balance and doesn't include the deposit already paid; the order amount stays the order total. A cash-on-delivery order whose order type can't be read, or whose balance doesn't match "order total minus deposit" or is negative, isn't pulled in (an existing order that hasn't started picking isn't updated this round); it is logged in the sync record and the merchant is notified (the payment method is followed by orderType to help identify it). If the balance is later paid online on the platform, an order that hasn't started picking has its COD amount changed to 0 on the next fetch.
- Only orders placed on the online store, created manually in the back office, or created via API are pulled in; orders created at a POS store are skipped and never pulled into the warehouse (the store handles them separately).
- When the platform's response is missing the payment or order status, or the order status is none of established, pending confirmation, completed, abnormal or canceled, the system can't tell whether the order can ship, so it is skipped, logged in the sync record, and the merchant is notified.
- A fully refunded order that isn't canceled (when the platform reports this status) is held as "Refunded on Platform" and never canceled automatically; an order whose status is "Abnormal", "Pending confirmation" or "Completed" is handled the same way, see the next item.
- A new order whose order status is "Pending confirmation" (待確認), "Completed" (已完成) or "Abnormal" (異常單) isn't pulled in; only a system log is kept and no notification is sent. A pending-confirmation order is pulled in only after the platform changes it to "Established" (已成立), and scheduled fetching only looks back ~7 days: an order changed to "Established" after that is pulled in only if it is paid and real-time notifications are set up. An unshipped order already in the warehouse that is changed to one of these three statuses is held as "Buyer Requested Cancellation" with "order_status=" followed by the platform's order status code in the note (2 = pending confirmation, 4 = completed, -1 = abnormal), never canceled automatically, and not updated while held; release the hold after checking and the order follows platform updates again. The same status isn't held again, but if the platform moves the order to a different status (for example from pending confirmation to abnormal) it is held once more and needs to be checked again. A shipped order isn't held.
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.
- Each carrier needs its own setting: 7-11 orders need the 7-11 return center, FamilyMart orders the FamilyMart return center, and Kerry / HCT orders the outbound place. If it isn't set, requesting a tracking number for that carrier's orders fails right away without contacting Coupang, and the failure reason names the setting to add; print again once it's set.
- Requesting a tracking number first checks the order's current status on Coupang and picks up from there: an order already acknowledged isn't acknowledged again, so an order whose last request failed partway gets its tracking number when you print again. If Coupang has already arranged shipment (for example you arranged it in the Coupang seller center, or the last request timed out but Coupang processed it), the system brings back Coupang's tracking number when the carrier matches; if the carrier differs or Coupang hasn't assigned a number yet, printing fails and the parcel still needs to ship — print the label in the Coupang seller center, then ship it in the system without a tracking number. An order Coupang shows as in delivery or delivered fails right away.
- 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.
- Customers can cancel items of the same order in separate requests. The warehouse order is canceled only when every item is canceled on Coupang (once picking has started, it's held as "Platform Cancel" instead); when only some items are canceled, an order not yet picked drops those items, while an order already in picking isn't updated and the canceled items still ship as originally listed.
- When the system can't retrieve or read Coupang's current cancellation status, the order stays unchanged. If the response can't be read, the sync record lists this order; if Coupang returns an error, the sync record gets an error entry that doesn't say which order it was (the error is in this order's history), and new orders still come in; if Coupang can't be reached (timeout), this fetch stops and new orders don't come in this round either. Later fetches check again, but only while the order's cancel request is still within the 7-day look-back; after 7 days it isn't checked again, so confirm in the Coupang back office and handle the order yourself.
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.
- Seller self-ship orders are confirmed on Ruten only when the warehouse ships and the system pushes the tracking number back, so on Ruten they go straight from awaiting confirmation to shipped and don't show as ready to ship beforehand.
- 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.
- An order the buyer asked to cancel, with no seller response yet, is not pulled in; an unshipped order already in the warehouse is held as "Buyer Requested Cancellation" and is canceled only after the seller approves or the system cancels it. If the seller declines, release the hold 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 under "Shipping Type Mappings", or order import gets stuck.
- Scheduled fetching only covers orders waiting to ship, 1shop has no real-time notification, and the system doesn't check an individual order again. When an order already in the warehouse is moved back to "awaiting payment" or "payment to be confirmed", fully refunded or shipped on 1shop, the system doesn't see it and doesn't hold the order for now, so check on 1shop yourself.
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
4.1 FAQ
▪ Why didn't an order on the platform come in?
A new order comes in only when it is paid or cash on delivery, hasn't shipped, and hasn't been canceled. An order already in the warehouse keeps following the platform until picking starts. Scheduled fetching and the check the system runs after a real-time notification follow the same rule; per-platform exceptions are in Per-Platform Caveats.
| Order on the platform | No such order in the warehouse | Order already in the warehouse |
|---|---|---|
| Paid or cash on delivery, not shipped | Creates the order | Updates as usual until picking starts |
| Created at a POS store (Shopline, Shopify, BV SHOP) | Skipped; system log only, no notification | Orders pulled in by fetching before POS orders were skipped: don't follow platform updates; a platform cancellation still cancels them (a Shopline full refund is still held too; a Shopify full refund is not held). BV SHOP orders created by the store-side app aren't affected by platform fetching, and platform cancellations don't sync to them |
| Unpaid | Skipped; system log only, no notification | Updates as usual until picking starts; not canceled or held |
| Shipped on the platform | Skipped; system log only, no notification | Not picked yet: held as "Shipped on Platform", items untouched, and not updated in that round; picking started or shipped: not held. Statuses that only mean "shipment arranged" or "processing" don't count as shipped and update as usual |
| Cancellation requested by the buyer | Skipped; system log only, no notification | Not shipped: held as "Buyer Requested Cancellation", never canceled automatically, and not updated in that round; canceled only once the platform confirms it. If the seller declines, release the hold yourself. Supported platforms: Shopee, Liteshop, Ruten, BVSHOP (when the order status is pending confirmation, completed or abnormal, see BvShop) |
| A cash-on-delivery order changed to unpaid and no longer cash on delivery | Skipped; system log only, no notification | Not shipped: the collection amount isn't updated and the order is held as "Other Reason" with the platform's payment status in the note for you to check. A paid order setting the amount to 0 is a normal update and isn't held |
| Partially shipped on the platform (Shopify) | Not created, logged in the sync record, merchant notified | Not picked yet: held as "Shipped on Platform" |
| Canceled | Skipped | Not yet picking: canceled automatically, and holds created by the platform sync are released (manual holds and other system holds stay); picking started: held as "Platform Cancel", added alongside any existing hold (such as a manual one), so releasing the other hold doesn't let the order ship; shipped: stays shipped, returns go through the return flow |
| Partially refunded, and platform quantities don't subtract the refund (EasyStore, Shopline refund in progress) | Skipped; system log only, no notification | Not shipped: held as "Refunded on Platform" and isn't updated while held; updates resume after release and it isn't held again while the refund stays partial. Moving to a full refund holds it again, and both holds stay if the first hasn't been released |
| Fully refunded but not canceled | Skipped | Not shipped: held as "Refunded on Platform", never canceled automatically, and not updated in that round; shipped: stays shipped, returns go through the return flow |
| Payment or order status the system can't read | Skipped, logged in the sync record, merchant notified | Not updated, logged in the sync record, merchant notified; when the warehouse order has already shipped or been canceled and no order was copied from it, only a system log is kept and no notification is sent |
| Shipping status the system can't read | Skipped, logged in the sync record, merchant notified | Updates as usual until picking starts |
A full refund takes effect only when the platform reports that status: Shopify and BVSHOP through real-time notifications, EasyStore through real-time notifications or the next scheduled fetch, Liteshop through update notifications or scheduled fetching. Other platforms may not report refunds, so rely on canceling the order on the platform. WooCommerce's "refunded" is an order status and is treated as a platform cancellation.
While a hold created by the platform sync is active, the order doesn't follow platform updates, even if the platform status returns to normal; warehouse staff need to confirm it ("Items Changed on Platform" too: after picking is canceled, release the hold first for the order to update). After you release "Refunded on Platform", "Buyer Requested Cancellation" or "Shipped on Platform", the order follows platform updates again until picking starts and isn't held for that reason again (91APP exception: after you release "Shipped on Platform", the order isn't updated while any sub-order is shipped or confirmed for shipping, and it's still canceled if every sub-order is canceled). A released partial refund hold is followed by a new hold if the order moves to a full refund; a released full refund hold isn't held again. After you release "Refunded on Platform", the system no longer changes the order's collection amount, so check and edit it yourself. An "Other Reason" hold caused by the payment status stops updates after release while the platform still reports that payment status, so the collection amount isn't changed.
⚠️ Known limitation: an order is held only when the platform clearly reports the goods have left. Statuses such as "shipment arranged" or "processing" may come from the system's own tracking-number request, so they aren't held. This hold doesn't trigger on these platforms for now: 1shop, Ruten, Cyberbiz, Mo+, Momo, Yahoo SCM and EtMall only fetch orders waiting to ship and the system doesn't check an individual order again, so a shipped status isn't seen; Coupang shows handover to the carrier, but the system doesn't treat it as the goods having left. Avoid shipping the same order from both the platform and the warehouse.
▪ 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+, PChome, Coupang, and EtMall, shipping types are mapped from a fixed list by the platform or system; you usually only set up "self-delivery" (for PChome, the single "預設物流(default)" entry). Other platforms can be mapped yourself under "Shipping Type Mappings".
▪ 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 "Stock Push Method" set to "Push on inbound" with a ratio set; after putaway the system splits the quantity back to each platform by ratio, pushing only to accounts whose "Fulfillment Warehouse" (the merchant's default warehouse when none is specified) is the inbound's warehouse. See EC accounts. Only 1shop doesn't support stock push-back; stock-transfer inbounds (warehouse-to-warehouse moves, not new stock) are excluded and never trigger push-back.
▪ My stock sits in several warehouses. Can a platform sell only one warehouse's stock?
Yes. Pick a warehouse in the EC account's "Fulfillment Warehouse": orders this platform fetches then ship from that warehouse, and the pushed stock counts only that warehouse—for example, store warehouse stock is not listed on your online shop. Several platforms can pick the same warehouse; one account picks only one warehouse, so an online shop whose stock must come from several warehouses is not covered by this setting. Accounts without one use the merchant's default warehouse for both fetched orders and pushed stock. See Create EC Account (warehouse) or Create EC Account (merchant).
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.
5. Related Features
| Feature | Description | Link |
|---|---|---|
| How E-Commerce Integration Works | The shared end-to-end flow for every platform | Go |
| EC accounts (merchant) | Merchants manage their own platform accounts | Go |
| EC accounts (warehouse) | Warehouse manages accounts on behalf of merchants | Go |
| Sales channels | Set up the matching channel before connecting a platform | Go |