How E-Commerce Integration Works
Contents
1. What This Section Covers
GoWarehouse connects your order sources (Shopee, Momo, your own website, Shopify, Coupang…) directly to the warehouse: platform orders flow in automatically, tracking numbers and shipping status are reported back after fulfillment, and stock and product mappings sync on their own — no copying data between two systems. Each connected platform account is one "EC account"; you create, configure, and test connections on the EC integration page (merchant side: EC accounts (merchant); warehouse side: EC accounts (warehouse)).
But each platform integrates differently: some use an official authorization login, some take a set of keys, some require you to allowlist your server IP with the platform first; some push orders in real time, others poll on a schedule; some can push stock and tracking numbers back, others can only pull orders in. This section explains those differences in two pages:
- How it works (this page): the one shared end-to-end flow for every platform — connect → fetch → match → ship → push back — and where each step differs by platform. Read this first to get the big picture.
- Platform comparison & caveats: a side-by-side table of every platform's differences, plus the things to know before connecting each one (what to fill in, whether an IP allowlist is needed, whether shipping codes are customizable…). Jump straight to the platform you want.
This section is about e-commerce platform integration. Carrier integration (e.g. T-Cat Express) is covered separately in Shipping Integrations.
2. How Integration Works
Whatever the platform, an order goes from the platform into the warehouse and the result goes back to the platform through the five steps below. The difference is how each platform does each step — which is exactly why the per-platform caveats matter.
Jump to: Connect ｜ Fetch orders ｜ Match & order hold ｜ Ship & push tracking ｜ Stock & product sync
2.1 Connection & Authorization
Bind the warehouse system to a platform account. The connection methods fall into four types:
- Official authorization login (Shopify, Shopee, Liteshop): click authorize in the back office, get redirected to the platform to log in and consent — no keys to copy; once authorized you are connected.
- Keys / tokens (Shopline, Cyberbiz, WooCommerce, BvShop, EasyStore…): generate an API key or token in the platform's back office and paste it into the EC account settings.
- Account & password (Momo, EtMall, Yahoo): fill in the supplier credentials the platform gave you; some platforms also use them to decrypt recipient personal data in orders.
- Per-request signing (Coupang, Ruten): fill in a set of keys; the system signs each call to the platform on the fly.
Note: Momo, PChome, Mo+, and Coupang require you to give the platform your "system's fixed outbound IP" to allowlist before connecting — otherwise the connection fails even with correct keys. This is done on the platform side and cannot be solved by back-office settings. See Platform comparison.
2.2 Fetching Orders
Pull new platform orders into the warehouse. Two modes:
- Real-time push: the platform notifies the system the moment a new order arrives — almost no delay.
- Scheduled sync: the system periodically pulls orders from the platform, usually looking back over the last 7 days. There is a delay of a few minutes up to one cycle between order placement and arrival in the warehouse.
Most platforms use scheduled sync; a few support real-time push. Which platform uses which is in the comparison table. Either way, only orders that are "paid / cash-on-delivery and not yet shipped" are pulled in.
2.3 Matching & Order Hold
Once an order is in, the system maps the platform's products to your warehouse products and the platform's shipping method to your shipping types. There are two deliberate order-hold safeguards here — it would rather hold an order than get it wrong:
- Unknown payment method → hold: if the platform used a payment type the system doesn't recognize and there's no online payment record, the order is held and you're notified, to avoid "shipped but never collected the COD amount." A technician needs to classify that payment type, then re-fetch.
- Unmapped shipping method → hold: if the order's shipping method isn't yet mapped to one of your shipping types (or the order has no shipping method selected on the platform), the order is held and you're notified. Fix the mapping and re-fetch.
2.4 Shipping & Pushing Tracking Numbers
After the warehouse picks and ships, the result is sent back to the platform. Platforms fall into three types:
- Platform assigns number + prints label (Shopee, Shopline, Momo, Mo+, Cyberbiz, Coupang, Ruten, Yahoo, EtMall): on shipping, the system automatically gets a tracking number from the platform and downloads the shipping label. Some platforms' labels are encrypted PDFs that require a PDF password to print (Momo, Mo+).
- Self-ship, push tracking only (Shopify, WooCommerce, EasyStore, BvShop, PChome): the platform doesn't print labels; you ship with your own carrier, and the system reports the tracking number and status back so the buyer is notified.
- Read-only, no push-back (1shop): only pulls orders in; nothing is pushed back after shipping — delivery and tracking are entirely handled by your own process.
2.5 Stock & Product Sync
- Stock push-back: after putaway, available quantity syncs back to the platform to avoid overselling. When the same product sells on multiple platforms, you can set a push ratio to split it (see the inbound push on EC accounts). Almost every platform supports this; only 1shop does not.
- Product mapping sync: automatically maps the platform's products / variants to your warehouse products; unmapped ones can be mapped manually. Some platforms can also backfill your internal product code (SKU) to the platform. Which platforms support this and which are read-only is in the comparison table.
3. FAQ
3.1 FAQ
▪ What should I prepare before connecting a new platform?
Confirm three things: (1) what data this platform's connection method needs (authorization? keys? credentials?); (2) whether an IP allowlist must be arranged first; (3) whether the matching sales channel is already set up. Check them one by one in Platform comparison & caveats.
▪ Why didn't an order come in immediately?
Most platforms use scheduled sync (not real time), so new orders are delayed and usually arrive within one sync cycle. If it's been a long time, first check that the connection is healthy and that the order is in a "paid and not yet shipped" state.
▪ An order came in but is held and can't ship?
Usually a matching / order-hold safeguard triggered: an unknown payment method, or an unmapped shipping method. The system tells you the reason; fix the setting and re-fetch.
▪ Why is there no label to print for some platforms after shipping?
Those are "self-ship" platforms (e.g. Shopify, WooCommerce, PChome); the platform doesn't provide labels. Print with your own carrier's system — the system only pushes the tracking number back to the platform.
3.2 Notes
⚠️ Important
- IP allowlist is a platform-side prerequisite: until Momo / PChome / Mo+ / Coupang are allowlisted, the connection will always fail, and it cannot be solved by back-office settings.
- A held order is a safeguard, not a failure: a held order means a setting is still incomplete (payment type, shipping mapping), not a broken system; fix it and re-fetch.
💡 Tip: not sure how a platform differs? Go straight to the table on Platform comparison & caveats and compare cell by cell — it's the fastest way.
4. Related Features
| Feature | Description | Link |
|---|---|---|
| Platform comparison & caveats | Per-platform difference table and connection tips | 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 |
| Shipping integration (T-Cat) | Carrier integration, different from EC platform integration | Go |