Create EC Account
Table of Contents
1. Feature Overview
This page lets you create an e-commerce platform account for a specific merchant, connecting platforms like Shopee, Shopify, and MOMO into the warehouse system. Once connected, the platform's orders are automatically fetched in as fulfillment work, and warehouse stock can be pushed back to the platform based on your settings. The creation flow is a single line: pick the merchant, fill in the connection details, test the connection or authorize, unlock the function settings on the right once connected, then save.

Quick Jump: Pick the Merchant | Connection Info (left column) | Function Settings (right column) | Field Reference
1.1 Pick the Merchant First
When you open the create page, the system first asks you to choose which merchant to create the account for. An e-commerce account must belong to a merchant, and reference data such as sales channels loads based on the merchant you pick. The connection form below only appears after a merchant is selected.
1.2 Connection Info (left column)
The left column holds the connection settings needed to link a platform, in three steps:
▸ Pick platform, enter name, bind channel
First pick the E-commerce Platform (one of 17 connectable platforms), enter the Display Name, then bind a Channel Name. All three are required. The sales channel can only be one that belongs to this merchant; if the merchant has no channel yet, the dropdown shows "No sales channels created" with a link to go set one up.
▸ Fill in connection info (credentials)
After you pick a platform, the left column shows different credential fields for that platform (for example API key, token, store login, store domain). Fill them in using the data from the platform's own admin panel.
For Shopify, enter the Shopify-provided store domain, such as shop-name.myshopify.com. You can also paste the full store URL; the system keeps the domain portion. A custom branded domain or another host cannot be saved.
▸ Test connection / Authorize & connect
After entering credentials, establish the connection using the method that matches the platform type:
- API-key platforms: A Test Connection button appears in the left column. Clicking it saves the account first, then verifies the credentials against the platform. On success the connection status becomes Connected and the button switches to "Connection test succeeded".
- Authorization platforms (Shopee / Shopify / Liteshop): An Authorize & Connect button appears in the left column. Clicking it leaves the warehouse system and redirects to the platform's authorization page; once you approve on the platform and return, the account is treated as connected — no manual credential testing needed.
There are three connection statuses: Not Verified (just created, not yet tested), Connected (connection succeeded), Disconnected (connection failed).
1.3 Function Settings (right column)
The right column holds the order-fetch and stock-push settings. Before the connection test or authorization passes, the right column is locked and shows "Complete connection setup first". Once connected, the right column unlocks and you can configure:
- Fulfillment Warehouse: At the top of the settings, listing only this merchant's assigned warehouses; several accounts can pick the same warehouse. Once set, orders this account fetches from then on are fulfilled from this warehouse, and the stock pushed to the platform counts only this warehouse: "Manual Stock Sync" and "Scheduled sync (every 30 min)" use only this warehouse's available quantity, and inbounds and stock-take gains are pushed to this account only when they happen in this warehouse; the push percentage and the sales channel's inventory type and expiry limits still apply. Platform return orders that cannot be matched to the original order also land in this warehouse. Left empty, the field shows "Use the merchant's default warehouse (currently: warehouse name)": orders land in the merchant's default warehouse and the push counts only the default warehouse's available quantity; if you later change the default warehouse in the merchant settings, accounts without one switch to the new default warehouse. The field is hidden when the platform is OneWarehouse, and also when the merchant has only one assigned warehouse and the account has no fulfillment warehouse set; an account with one set still shows it, so it can be cleared back to the merchant's default warehouse. It can still be set while both "Fetch Orders" and stock push are off, with a note below it that the setting has no effect for now. If you pick a warehouse other than the merchant's default after testing the connection and then save, a dialog reminding you to sync manually appears when the account supports "Manual Stock Sync"; see Edit EC Account.
- Fetch Orders: When on, the system automatically fetches platform orders into the warehouse based on your schedule. When on, you must set at least one fetch schedule.
- Realtime New Order Fetch: Shown only for platforms with realtime notifications (see the platform matrix), on by default. When on, the platform notifying us of a new order schedules an extra fetch and the order usually reaches the system within a few minutes (about 5 minutes for Shopee), so it does not wait for the next fetch slot. When off, new orders only arrive during the fetch slots you set.
- Stock Push Method: Shown only on platforms that support "Manual Stock Sync"; choose one of three, "Off" by default on a new account. Any method other than "Off" uses the push percentage to control what percentage to push.
- "Off": no stock is pushed to the platform, and the detail page does not show the product mapping sync or manual stock sync buttons.
- "Push on inbound": when an inbound or a stock-count gain is completed, the added quantity times the push percentage is pushed to the platform; shipping, order allocation, and other changes are not reflected on the platform.
- "Scheduled sync (every 30 min)": while the account is connected, the system runs a round every 30 minutes (on the hour and half hour): each product whose stock changed since the previous round is overwritten on the platform with its current available quantity times the push percentage — the same calculation as "Manual Stock Sync"; products with no changes are not pushed. Any kind of change counts: shipping, order allocation and release on cancellation, relocation, putaway, stock takes, and stock adjustments (including write-offs). When the same merchant has accounts with a scheduled order fetch in that slot, the push waits until those fetches finish (successful or not) so that freshly fetched orders finish allocating first. Inbounds and stock-count gains do not push a separate increment; the next round updates them. The first round after switching to this method syncs everything once, the same as pressing "Manual Stock Sync".
- Dependent settings need their master switch on before you can edit them: "Fetch Schedule" and "Realtime New Order Fetch" follow "Fetch Orders", and "Push Percentage" follows "Stock Push Method". While a master switch is off (or the push method is "Off"), the fields under it are greyed out and cannot be clicked, and a note beside them says which switch to turn on or that a push method must be chosen first. On a new account "Stock Push Method" is "Off" by default, so "Push Percentage" is greyed out as soon as the page opens; choose another push method to edit it.
- Waybill Layout: Shown for Momo, Mo+, Shopline and Cyberbiz accounts only, A4 by default. With thermal, the system splits the platform's A4 waybill into a left and a right section, each printed as its own page so a label printer can print it directly; it affects home-delivery waybills only (Momo: T-Cat / Pelican / HCT / Kerry TJ; Mo+: T-Cat / HCT; Shopline: T-Cat only, including cash on delivery) — convenience-store pickup labels stay A4 and are not split, and so do Shopline's HCT and cross-border labels. Cyberbiz's thermal layout applies to T-Cat quick store pickup only: it takes two sections of the A4 waybill Cyberbiz provides and stacks them on one page of about 95×195 mm, and other Cyberbiz carriers are not affected. Carriers may reject and return a split waybill, so confirm with the platform and the carrier before switching.
- Shipping Type Mappings: Shown only for some supported platforms. Maps the platform's shipping options to warehouse-side shipping types so the system knows which shipping to use when shipping out. For a Cyberbiz account, the warehouse-side dropdown lists Cyberbiz's integrated shipping types (for example Cyberbiz T-Cat and Cyberbiz HCT) on top of the merchant's own shipping types; accounts on other platforms are unchanged and list only the merchant's own shipping types. Cyberbiz shipping method codes can be edited by the merchant in their back office, and once a code changes, incoming orders raise an "Unmapped Shipping Type" notification; map the new code to the correct Cyberbiz integrated shipping type here and the orders resume automatic conversion, tracking-number requests, and label printing — no need to ask the merchant to restore the old code.
1.4 Field Reference
Fields marked with * are required
| Field | How to fill | Notes |
|---|---|---|
| *E-commerce Platform | Pick an e-commerce platform to connect from the list | Cannot be changed after creation; a wrong choice means deleting and recreating |
| *Display Name | Enter a name to identify this account inside the warehouse system, e.g. "Shopee-main" | When a merchant has multiple platform accounts, this name tells them apart |
| *Channel Name | Pick a sales channel that belongs to this merchant | Only channels under this merchant are available; if missing, create one first at Create Sales Channel |
| Connection info (credentials) | Fill in the fields shown for the chosen platform, e.g. API key, token, store login, store domain | Authorization platforms obtain credentials via Authorize & Connect instead of manual entry |
| Fulfillment Warehouse | Pick one of this merchant's assigned warehouses; leave empty to use the merchant's default warehouse | Affects only orders fetched from then on; orders already in the system do not move. Hidden for OneWarehouse accounts, or when the merchant has only one assigned warehouse and none is set; see 1.3 for what it affects |
| Fetch Orders | When on, automatically fetches platform orders | Can only be set after the connection passes |
| Fetch Schedule | Choose the times to fetch orders from the slot list, up to 3 | Required when "Fetch Orders" is on; pick at least one |
| Realtime New Order Fetch | Decides whether new orders are fetched as soon as the platform notifies us (usually within a few minutes, about 5 minutes for Shopee), on by default | Shown only for platforms with realtime notifications (see the platform matrix); when off, new orders only arrive during the fetch slots, and syncing of orders already in the system (such as cancellations and status updates) is unaffected |
| Waybill Layout | Choose whether waybills print as A4 or thermal, A4 by default | Shown for Momo, Mo+, Shopline and Cyberbiz accounts only; thermal splits the A4 waybill into a left and a right section, each on its own page. It affects home delivery only (Momo: T-Cat / Pelican / HCT / Kerry TJ; Mo+: T-Cat / HCT; Shopline: T-Cat only, including cash on delivery) — convenience-store labels and Shopline's HCT and cross-border labels stay A4. Cyberbiz applies it to T-Cat quick store pickup only, stacking two sections on one page; other Cyberbiz carriers are not affected. Carriers may reject and return a split waybill, so confirm with the platform and the carrier before switching |
| Stock Push Method | Choose one of "Off", "Push on inbound", or "Scheduled sync (every 30 min)"; "Off" by default | Can only be set after the connection passes; see 1.3 for how the methods differ |
| Push Percentage | Enter the stock percentage to push to this platform, range 0–100, default 100; required and cannot be left blank | A merchant's platforms totalling over 100% carries oversell risk |
| Shipping Type Mappings | Map the platform's shipping options to warehouse-side shipping types | Shown only for some platforms; each mapping must pick a warehouse-side shipping type. A Cyberbiz account also offers Cyberbiz's integrated shipping types; accounts on other platforms list no platform integrated shipping types |
When done, click Save at the bottom of the page. After a successful save you return to the EC Account List.
Ragic does not offer "Stock Push Method" or "Push Percentage" settings. Inbound imports use "Fetch inbounds" and a separate "Inbound fetch times". While "Fetch inbounds" is off, "Inbound fetch times" is greyed out and cannot be edited, and since "Fetch inbounds" is off by default on a new account, it starts out greyed as soon as the page opens; turn the switch on to edit it. For the first connection, enter either an order sheet path or an inbound sheet path. An inbound-only account does not require an order sheet. Once connected, configure the import template, line-item subtable, import condition, and receipt write-back. After saving, check the Ragic inbound integration on the detail page.
For inbound-only use, turn off order fetching. The order sheet path, fetch schedule, import template, import conditions, shipment writeback, and "Shipping Type Mappings" are hidden. Turning order fetching back on restores these fields; saving while disabled preserves the existing order settings. Retesting an existing account saves the current inbound switch and settings together. If inbound fetching is turned off, it stays off even when you also change the API key or source sheet. After switching inbound sheets, matching record IDs on the new sheet can still be imported (document numbers must remain unique). Existing inbounds write back to their original sheet using the writeback fields saved at import. Closing receipt again in the same receiving cycle preserves the first completion time; reopening and completing creates a new writeback cycle. If a populated item lacks its SKU or an explicit date is invalid, the entire inbound is rejected. Correct the source data using the sync log.
Custom attribute defaults apply even without a mapped source column; an existing source value takes priority. Yes/no attributes accept Y/N or 1/0, and numbers and dates are converted according to the attribute type. Invalid values reject the entire inbound; correct them using the sync log, then fetch again. If Ragic rejects a receipt writeback or its service fails temporarily, the system retains the retry instead of marking the writeback as successful.
2. FAQ
Quick Jump: Common Questions | Important Notes
2.1 Common Questions
▪ Why are the function settings on the right greyed out and unclickable?
The function settings on the right unlock only after the connection on the left passes. Before that, the screen shows "Complete connection setup first". First fill in the credentials in the left column and complete Test connection or Authorize; once the connection status becomes Connected, the right side can be configured for fetching and pushing.
▪ I can't find the channel I want to bind in the sales channel dropdown — what now?
The sales channel dropdown only lists channels under the merchant you currently selected. If that merchant has no channel yet, the dropdown shows "No sales channels created". Create a channel for this merchant first at Create Sales Channel, then come back to create the e-commerce account.
▪ I picked the wrong platform — can I change it after creating?
No. The e-commerce platform (E-commerce Platform) cannot be changed after creation; this field is locked on the edit page. If you picked the wrong platform, delete this account and create a new one.
▪ How do I connect platforms like Shopee and Shopify?
Shopee, Shopify, and Liteshop are authorization platforms that use the Authorize & Connect button — no manual credential testing needed. Clicking it redirects you to the platform's authorization page; once you approve on the platform and return, the account is treated as connected.
▪ Test connection failed and I see a platform error message — what does it mean?
A failed test means the platform rejected the credentials you entered when the system verified them, usually because the credentials are wrong or lack sufficient permissions. If the message includes the platform's raw response (e.g. unauthorized, no permission), follow that message back to the platform's admin panel to confirm the API key or token is correct and has the right read/write permissions, fix it, then test again. On failure the status becomes Disconnected.
▪ I turned on Fetch Orders but can't save?
When "Fetch Orders" is on, "Fetch Schedule" must have at least one slot selected, otherwise you can't save. Pick 1 to 3 fetch times from the slot list.
▪ I set fetch times, but new orders still arrive outside those slots?
Platforms with realtime notifications (see the platform matrix) have "Realtime New Order Fetch" on by default, so a new-order notification from the platform schedules an extra fetch and the order usually reaches the system within a few minutes instead of waiting for your slots. Shopee waits about 5 minutes before fetching, and that wait is deliberate: Shopee has not assigned the shipping details the moment an order is placed, and fetching any earlier would leave the recipient phone as Shopee's redacted placeholder instead of the delivery contact number Shopee issues along with the shipping details. If you want new orders to arrive only during the slots you set, turn this switch off. Syncing of orders already in the system (such as cancellations and status updates) still runs as usual.
▪ Why don't I see the "Fulfillment Warehouse" field?
The field appears when the merchant has two or more assigned warehouses—with a single warehouse, orders and push-back use that warehouse anyway, so choosing makes no difference. The exception is an account that already has a fulfillment warehouse set: it still shows the field when the merchant has only one assigned warehouse left, so you can clear it and go back to the merchant's default warehouse. OneWarehouse accounts don't show it either, because their orders are pushed in by OneWarehouse and no stock is pushed back. To give the merchant another assigned warehouse, select it in Merchant Details & Settings.
▪ What should the push percentage be?
The push percentage defaults to 100, meaning all available stock is pushed to this platform. If a merchant sells across multiple platforms, you can lower the percentage to split the allocation. Note: across all of a merchant's connected platforms whose "Stock Push Method" is not "Off", if the percentages total at or above 100%, the system shows an oversell-risk warning after saving. When the accounts use different warehouses, the check runs per warehouse instead: accounts are grouped by the warehouse they actually use (accounts without a "Fulfillment Warehouse" count toward the merchant's default warehouse), and the warning appears only when some warehouse reaches or exceeds 100%.
▪ How does "Push on inbound" differ from "Scheduled sync (every 30 min)"? Which should I choose?
"Push on inbound" only pushes the added quantity to the platform when an inbound or a stock-count gain is completed; shipping, order allocation, relocation, stock-count losses and other changes never reach the platform, so over time the platform figures drift from the warehouse. "Scheduled sync (every 30 min)" overwrites changed products with their current available quantity every 30 minutes, closing that gap; inbounds are changes too, so with it completed inbounds no longer push an increment and the next scheduled round updates them with the latest quantity instead. The two are alternative push methods and cannot be combined. Read the overselling risk under Important notes before choosing "Scheduled sync (every 30 min)".
2.2 Important Notes
⚠️ Key Reminders
- E-commerce Platform cannot be changed after creation; a wrong choice means deleting and recreating the account, so confirm the platform before creating.
- An e-commerce account must bind a sales channel that belongs to the merchant; without a channel it cannot be created.
- Across a merchant's connected platforms whose "Stock Push Method" is not "Off", keep the total push percentage under 100% to avoid oversell risk; count per warehouse actually used (accounts without a "Fulfillment Warehouse" count toward the merchant's default warehouse).
- After setting a "Fulfillment Warehouse", order allocation and tracking-number requests follow that warehouse's stock and shipping settings, so confirm that warehouse's shipping settings are ready before choosing it.
- "Scheduled sync (every 30 min)" does not deduct platform orders that have not been fetched into the system at push time, so the pushed figure can add already-sold quantity back onto the platform and cause overselling (scheduled sync waits for the same slot's scheduled fetches to finish before pushing, but orders placed after the fetch, or not fetched until a later fetch slot, are still not deducted); "Manual Stock Sync" carries the same risk. Platforms with realtime notifications can pair it with "Realtime New Order Fetch"; on other platforms, set more frequent fetch slots to narrow the gap.
- "Scheduled sync (every 30 min)" only reacts to stock changes. In these cases the stock does not change but the figure the platform should show does, so it is not updated automatically; press "Manual Stock Sync" once after the change: a batch's expiry crosses the sales channel's expiry threshold, a single product's push percentage or push switch is changed, the sales channel's expiry rules or allowed inventory types are changed, or a platform product is newly mapped
- While the push method is "Scheduled sync (every 30 min)", inbounds do not push an increment and wait for the next scheduled round; if you switch to another push method after an inbound but before the next scheduled sync push, that inbound quantity never reaches the platform, so after switching to "Push on inbound" press "Manual Stock Sync" once
💡 Tip: Authorization platforms (Shopee / Shopify / Liteshop) leave the system and redirect to the platform's authorization page; after authorizing they return automatically, so do not close the window during the process.
3. Related Features
| Feature | Description | Link |
|---|---|---|
| Create Sales Channel | Create the sales channel that an e-commerce account must bind to | Go |
| EC Account List | View and manage the merchant's e-commerce accounts | Go |
| EC Account Detail | View a single e-commerce account's connection and settings status | Go |
| Shipping Types | Set up warehouse-side shipping types for shipping code mappings | Go |