Skip to content

EC Account Details ​


Table of Contents ​


1. Features ​

The EC account detail page is where you check, for a single e-commerce integration, "is it connected right now, what is configured, and do I need to trigger something manually". When operating on behalf of a merchant, this is where you confirm a platform account's connection status and masked credentials, review its order-fetch and stock-push settings, and — when needed — manually schedule one order fetch, sync product mappings, or overwrite platform stock. The left column shows connection information, the right column shows feature settings, and when the account is disconnected a red alert appears at the top so you can re-authorize or edit directly. The sync history at the bottom of the page is your first stop when someone asks why orders or return orders have not come in.

EC Account Detail - Overview

Quick jump: Connection Info (left) | Feature Settings (right) | Manual Actions | Automatic Real-Time Notification Check | Header Actions | Sync History

1.1 Connection Info (left column) ​

The left column is titled Connection, with the current connection status tag shown in the top-right corner.

There are three connection statuses, listed in full only here:

StatusMeaning
Not VerifiedThe account was just created, or its credentials changed and the connection has not been tested yet
ConnectedThe last connection test succeeded; order fetch and push work normally
DisconnectedThe last test failed, or the system marked it as disconnected

The basic info table lists the merchant, E-commerce Platform (platform tag), Display Name, and Channel Name.

The credentials section (title with a lock icon) shows the credential fields for that platform; fields differ by platform (for example: keys, account, shop code). **Sensitive fields such as secrets, tokens, and passwords are always masked with ********** — their real values never appear on screen.

The very bottom shows Created At and Updated At in small text.

When the account status is "Disconnected", a red alert appears at the top of the page with a repair button that depends on the platform type:

  • OAuth platforms (Shopify, Shopee, Liteshop): a Re-authorize button that takes you back to the platform to re-authorize.
  • API-key platforms: an Edit button that takes you to the edit page to update the credentials and re-test the connection.

1.2 Feature Settings (right column) ​

The right column is titled Settings and shows the settings supported by the platform.

Fulfillment Warehouse: At the top of the settings, showing which warehouse this account's fetched orders land in and which warehouse its pushed stock counts; "Use the merchant's default warehouse (currently: warehouse name)" means none is set, so orders land in the merchant's current default warehouse and the push counts only that warehouse's available quantity. Not shown for OneWarehouse accounts, nor when the merchant has only one available warehouse and this account has no fulfillment warehouse set. While neither order fetching nor stock push is on (only order fetching counts for platforms without stock push), the fulfillment warehouse has no effect and is marked with "Neither Fetch Orders nor stock push is enabled, so this setting has no effect for now" ("Takes effect only when Fetch Orders is enabled" for platforms without stock push). To change it, go to the edit page.

Order fetch settings: shows whether Fetch Orders is on or off, together with Fetch Schedule Times (the daily automatic-fetch time slots). Next Fetch Time is listed only while order fetch is on. Platforms with realtime notifications also show Realtime New Order Fetch: when on, a new-order notification from the platform schedules an extra fetch and the order usually reaches the system within a few minutes (about 5 minutes for Shopee); when off, new orders only arrive during the slots above.

When order fetch is off, the system will not automatically import this platform's orders into the warehouse, and of the notifications the platform sends only cancellations and buyer cancellation requests are applied; other order and return notifications are not processed. The slots you saved earlier are still listed so you can check what is configured, but they are marked with "Takes effect only when Fetch Orders is enabled". Realtime New Order Fetch does not run then, so it always shows the same grey "Inactive" tag as order fetching; if you saved it as on, it is also marked with "Takes effect only when Fetch Orders is enabled" and resumes once order fetching is turned back on. To check the saved realtime fetch value, open the edit page.

Stock push settings: shows the method currently chosen for Stock Push Method (a grey tag for "Off", a green tag for "Push on inbound" or "Scheduled sync (every 30 min)"), and the Push Percentage (the share of stock pushed to the platform). With "Off", the percentage you saved earlier is still listed, marked below with "Takes effect only after choosing a stock push method". While the push method is not "Off" and the platform persists its mappings, it also shows the mapped product count and Last Synced; before any sync it shows "No product mappings". When bundle mappings exist, an extra line below shows the bundle mapping count (counted separately from product mappings; hidden when there are no bundle mappings). When the push method is not "Off" and the platform supports manual stock sync or mapping sync, but the bound sales channel's "Product Mapping Rule" isn't by SKU, it shows "This sales channel doesn't map products by SKU, so bundle stock is not pushed" — when platform orders come back, only channels that map by SKU can recognize a bundle, so bundle quantities aren't pushed.

Waybill Layout: appears for Momo, Mo+, Shopline and Cyberbiz accounts only, showing which layout waybills are currently printed with — A4 (the platform's original layout) (the default) or Thermal Label (split into two sections). On Cyberbiz accounts thermal reads "Thermal label (two sections stacked on one page)" and applies to T-Cat quick store pickup only. Change it on the edit page.

Shipping Type Mappings: a table showing the "platform shipping code → warehouse shipping type" mapping. This table only appears when a mapping has been set up.

▸ Ragic Inbound Integration ​

Ragic shows "Fetch inbounds", "Inbound fetch times", and "Next inbound fetch time" so you can check when inbound documents will be imported. Inbound and order fetching have independent switches and schedules. The next inbound fetch time is not shown while fetching is disabled or the account is disconnected. While inbound fetching is off, the saved fetch times are still listed, marked with "Takes effect only when Fetch inbounds is enabled".

"Inbound field mapping and import condition" lists the inbound sheet path, import template, line-item subtable, and import condition. "Receipt completion write-back" lists the status field, completion value, and receipt-date field used for write-back. Unconfigured fields display "-". Change these settings on the Edit page.

Ragic currently does not support stock pushing, so "Stock Push Method" and "Push Percentage" are hidden. Writing receipt results back to the original inbound sheet is separate from pushing stock quantities to a platform. If inbound fetching is later disabled, receipt results for documents already imported are still written back as configured while the account is connected.

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. Of these, the fetch schedule is hidden on the edit page only: this detail page still lists the slots you saved, marked with "Takes effect only when Fetch Orders is enabled" so you can tell they are not in effect right now, not lost. 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. Each writeback fills only blank fields in the original sheet, preserving existing status and receipt-date values. 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.

Inbound items can use only inventory types currently enabled for the merchant. This also applies when an item falls back to the sales channel’s default type. If that type is disabled, the entire inbound is rejected. Correct the channel settings or enable the type, then fetch again.

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. Failed receipt writebacks receive up to 2 automatic retries, then stop with a notification. See Inbound Details for the result and follow-up steps.

When the account is connected and inbound fetching is enabled, users with permission to edit ecommerce accounts can select “Fetch Inbounds Now” without waiting for the next scheduled time. Check the integration log for results. Each account allows one manual inbound fetch every 10 minutes, independently of manual order fetching.

1.3 Manual Actions ​

The two setting sections in the right column each carry a manually triggered button. Whether these buttons appear depends on the account's current status and the platform — not every account shows them (reasons for them being hidden are in the FAQ).

▪ Fetch Orders Now ​

Immediately queues one order-fetch job without waiting for the next scheduled time slot.

  • When it appears: the account is connected and order fetch is on; OneWarehouse accounts have their orders pushed in by OneWarehouse and do not have this button.
  • Side effect: it only triggers one extra fetch early; it does not change the automatic schedule. After triggering, "Next Fetch Time" still shows the next automatic schedule time. If a scheduled slot arrives while it is fetching, that slot's scheduled fetch and scheduled sync move to the next round.
  • Limit: there is a 10-minute cooldown. If you click again during cooldown, the system shows "Too many requests. Please try again in N minute(s)."
  • Queuing: if the same merchant has a fetch in progress (scheduled or another manual fetch), it starts automatically within a few minutes after that one finishes, with no need to click again; while it waits the cooldown keeps being extended, and clicking again only shows "Too many requests". If it still cannot start within about an hour, this manual fetch is dropped and the next on-the-hour or half-hour round fetches the account instead.

▪ Sync Product Mappings ​

Pulls the product list back from the e-commerce platform to build the mapping between WMS products and platform products.

  • When it appears: the account is connected, "Stock Push Method" is not "Off", and the platform supports syncing product mappings.
  • Bundles: platform items whose SKU matches no single product but matches one of the merchant's bundle SKUs are mapped as bundles; manual stock sync pushes bundle quantities based on these mappings.
  • Shopline product status: only "active" and "hidden" products (not listed on the storefront, purchasable only via a direct link — e.g. group-buy products) are mapped; "unpublished" (draft) and deleted products are not mapped, and their existing mappings are removed during the sync. When one WMS product maps to both an active and a hidden product, the pushed stock is split evenly between them to prevent overselling.
  • 91APP sale pages: 91APP has no such button and keeps no mappings; every stock push looks up all of the SKU's sale pages on 91APP directly. The push writes the sale page's sellable quantity on 91APP, not its total stock: after inbound and other stock increases, the page's current sellable quantity is read and the increase added to it; the scheduled sync and "Manual Stock Sync" set the sellable quantity directly to the pushed quantity. When one SKU has several sale pages on 91APP, the pushed quantity (the increase pushed after inbound and other stock increases, and the sellable quantity pushed by the scheduled sync and "Manual Stock Sync", bundles included) is split evenly across the sale pages, with any remainder going to the pages with the lowest sale page IDs, to prevent overselling. If the merchant wants every sale page to sell the full quantity, split it into separate products with different SKUs in the WMS.
  • Result: once the mapping is built, the result appears in the notification at the top-right, and the mapped product count and last synced time at the top of this page update on their own — no refresh needed.

▪ Manual Stock Sync ​

Overwrites the stock numbers on the platform with the current WMS sellable quantity (absolute overwrite).

  • When it appears: the account is connected, "Stock Push Method" is not "Off", and the platform supports manual stock sync.
  • Side effect: it directly overwrites the stock quantity on the e-commerce platform and affects live sales (see Notes).
  • Scope: only the "Fulfillment Warehouse"'s available quantity counts, or the merchant's default warehouse when none is set. The push percentage and the channel's inventory type and expiry limits still apply. Right after changing the fulfillment warehouse, one click switches the platform to the new warehouse's figures.
  • Bundles: the same run also pushes bundle sellable quantities (see New Bundle for the calculation); if the bundle push fails, single products are still pushed. Bundles aren't pushed when the channel's product mapping rule isn't by SKU. On platforms with the "Sync Product Mappings" button, only bundles that have mappings are pushed, so sync mappings first; Liteshop and 91APP have no such button and target all of the merchant's bundles, skipping SKUs the platform doesn't have. Deactivated or deleted bundles are pushed as 0, unless the SKU is now used by another product or bundle. When the push method is "Scheduled sync (every 30 min)", bundles are also updated by the scheduled sync when their component stock counted for this account (the sales channel's inventory types or those specified in the bundle, in the fulfillment warehouse), contents, push ratio, or active status changes; "Push on inbound" doesn't include them.
  • Confirmation step: clicking opens a red confirmation dialog "Confirm manual stock sync"; it runs only after you confirm.
  • Sync already running: if another sync is already running for the same account, this manual sync runs automatically a little later; there is no need to click again, and clicking repeatedly while it waits still adds only one extra run. If the earlier sync is still running after about 30 minutes, this one is dropped without running; click again later.
  • If the sync fails: when the connection to the platform drops temporarily (timeout), this sync is recorded as failed and the account is not marked disconnected, so order fetching and other features keep working. The failure appears in sync history; it isn't pushed again automatically, so click again later. When the platform authorization has expired, the account is marked "Disconnected"; follow the red prompt at the top of the page to restore the connection. Shopee, Liteshop, Shopify, etmall, and Free Store accounts are only marked disconnected when the platform explicitly refuses an authorization update; if the account still shows connected but every round in sync history fails, what to do depends on the platform: for Shopee and Liteshop, go to the edit page and click "Revoke Authorization", then "Authorize & Connect"; for Shopify, click "Revoke Authorization" on the edit page, then return to this page and click "Re-authorize" in the red prompt at the top; for etmall and Free Store, update the connection parameters on the edit page, then click "Test Connection".
  • Automatic version: with "Stock Push Method" set to "Scheduled sync (every 30 min)", the system applies the same overwrite to products whose stock changed every 30 minutes; see feature settings on Create EC Account for how it works.

1.4 Automatic Real-Time Notification Check ​

Whenever someone opens this page, the system automatically checks with the e-commerce platform whether this account's real-time notification is set up, and fixes it on the spot if it is missing or no longer working. The check runs in the background, so it does not slow the page down, and there is no button to press.

Real-time notification is what makes the platform tell us the moment an order changes, so orders no longer have to wait for the next scheduled fetch. Accounts that were integrated before real-time order intake shipped — and accounts whose notification permission was granted later — used to need someone to go back and press the connection test again; now one visit to this page fixes them automatically.

Result of this checkWhat you see
Not on the platform yet → createdA floating message saying it is now enabled, listing which notification events are covered
Expired or missing some events → rebuiltA floating message saying the previous setup had stopped working and has been recreated, with the same event list
Already present and correct → nothing doneNo message at all. Reloading the page still runs a real check, but with no new change there is no repeated message
The key lacks real-time notification permissionA message that does not close by itself, guiding you to grant the permission on the platform and regenerate the key
The platform refuses this system's connection source (our IP is not on its allowlist)A message that does not close by itself, saying to contact support. Regenerating the key does not help here — this system's connection IP has to be added to the platform's allowlist
Platform timeout, error, or rate limitNo message at all. Scheduled order fetching is unaffected and the next visit retries automatically

The check is not triggered at all when: the account is not "Connected" (never tested or disconnected accounts never call the platform), you only have read-only permission (no call and no message), or the platform has no real-time notification we can configure.

The platforms checked automatically are Shopline, Shopify, WooCommerce, Liteshop, EasyStore, and Free Store. BV SHOP, Shopee, and Yahoo are out of scope; opening this page does not configure anything for them.

A check also runs automatically every night: in the early morning the system runs the same check on every "Connected" account, without anyone opening this page. After repeated delivery failures, a platform removes the notification on its own (Shopify) or disables it (WooCommerce, Shopline); from then on nothing is pushed and orders only arrive at fetch times. The nightly check recreates or re-enables it when it finds this, so the gap lasts at most one day.

  • Only accounts that were registered before get a notice: when this account's real-time notification had been set up successfully and was later removed or disabled by the platform, rescuing it sends a "webhook subscription repaired" system notification to both the warehouse side and the merchant's admin. One that was never set up successfully and is only now added is still fixed, but without a notice; nothing is sent when everything was already fine.
  • WooCommerce webhooks paused by hand are left alone: only webhooks the platform disabled automatically (Disabled) are re-enabled. If the merchant sets a webhook to Paused in the WooCommerce admin, the system treats it as intentional and does not turn it back on.
  • A failed check (platform timeout or error) sends no notice and is retried the next night.

1.5 Header Actions ​

The top-right corner always offers two account-level actions:

  • Edit: go to the Edit EC Account page to change the display name, credentials, order-fetch and push settings, "Shipping Type Mappings", and so on.
  • Delete: clicking opens a confirmation dialog; after you confirm, the account is deleted. Before removing the account, the system first attempts to clear the automatic notifications it previously set up on the platform. This cannot be undone (see Notes).

1.6 Sync History ​

"Sync History" at the bottom of the page lists this account's most recent automatic syncs, one row per run. When a merchant asks why orders or return orders have not come in, start here. Order fetching, return order syncing and stock pushing leave no record when there was nothing to process and nothing failed, so an empty list for those three does not mean something is broken ("Scheduled sync (every 30 min)" leaves one "Stock Push" row for each round that pushed products, which looks the same as a row left by "Manual Stock Sync" — the history does not distinguish the two; a round with no stock changes since the previous one leaves no record); an order fetching or return order syncing round that only handled platform cancellations (cancelled locally, or — for an order already in fulfillment — placed under a "Platform Cancel" hold instead) still leaves a "Success" row; "Product mapping" leaves a row whether it succeeded or failed, and the only silent case is the daily incremental run finding no product changes on the platform at all, which is a normal result. Pressing "Sync Product Mappings", or the first full sync right after connecting, also leaves a row when no product list could be retrieved at all — and an account that has never yet retrieved a product list still has its sync progress at the starting point, so the daily run is treated as a full one and keeps leaving a row every night until it first retrieves products. For "Yahoo Shopping Center" the product file comes back asynchronously: a failure to trigger the export leaves a row immediately, while a successful trigger only writes its row once the platform sends the product file back, so it takes a few minutes to appear after the button is pressed; if that returned file cannot be downloaded or read, no row is written at all and the failure shows up as a notification instead.

ColumnWhat it tells you
TypeWhat was synced: "Order Fetch" fetches platform orders, "Return Order Sync" turns platform returns into return orders, "Stock Push" pushes stock to the platform, "Product mapping" rebuilds product mappings. They run independently — a failed return order sync does not drag order fetching down with it
Status"Success" everything went through; "Partial Failure" some failed; "Failed" nothing succeeded in this run: either a credential or connection problem cut the whole run short, or every record failed individually (for example, a shipping method with no mapping) — expand the row to tell which. "Product mapping" has one more state, "Cleanup Skipped": the run did not get a complete product list, so the system left every existing mapping untouched (and when it did not get any product list at all, the sync progress is not advanced either); the next run tries again
ResultFor Order Fetch, Return Order Sync and Stock Push, how many succeeded and how many failed in this run. For order fetching and return order syncing, successes include records the platform cancelled that were handled locally (cancelled, or — for an order already in fulfillment — put on hold instead), and the same record is not counted again in later rounds; a local cancellation that was refused counts only as a failure, even though the system placed a hold instead; Product mapping has no per-record outcome and instead shows how many products were scanned, how many mappings were updated, and how many were removed

Click a row with failure details to expand it; each expanded row is one failure. "Target" points at the item (for return order syncing it is the platform's return order number), "Error" is the reason, and where a "View API Log" link is shown you can open the full record of that call. A row marked "Entire run" means the whole run was cut short or one of its requests failed, not a single item.

If the "Error" column on a "Order Fetch" or "Stock Push" row shows "Updating the platform authorization, please try again later" or "The platform could not update the authorization right now, please try again later", the platform authorization update did not finish this round: the first means another job is updating this account's authorization, the second means the platform could not complete the update this time. The round stops, the account is not marked disconnected, and the next round tries again, so no action is needed when you see it. Act only if every round shows it, as described under the stock sync action.

"Product mapping" has no per-item failures: when the platform blocks it, the row is "Failed" and expanding it shows a single "Entire run" line. The "Error" column reads one of three ways. Whenever the system itself stopped the run (the product data coming back unreadable, or the product list not being read all the way through), and for credential and connection problems, you get a readable explanation on its own. When the platform explicitly rejected the product list request, that explanation is followed by the platform's own wording (usually with some English technical text in it, and the only place the platform's actual reason shows up). Anything else the platform reported that the system could not classify (for example, the platform being busy) is shown exactly as it came. Where a "View API Log" link is shown you can open the full record of that call. This kind of failure almost always happens while reading the platform's list, before any existing mapping is touched, and it does not advance the sync progress — ask the merchant to press "Sync Product Mappings" again later.

Failures under "Return Order Sync" and what to do about them:

FailureWhat to do
A returned item could not be matched to a productThe whole return order is not created, but the goods still come back to the warehouse physically. Go to "Unknown Products" and map the unmatched item on the source order to a system product, or ask the merchant to press Sync Product Mappings to rebuild the mapping. Once that is done, any return order updated on the platform within the last 7 days is created on the next run — no manual creation needed
A returned item has no inventory typeThe system does not know which inventory type these goods should come back into. Open the sales channel this account is bound to and make sure a primary inventory type is set; the return order is created on the next run
The whole run failed (Entire run)Read the "Error" column — there are three cases. "Platform authorization expired" means the credentials or API key no longer work; the account is also marked "Disconnected" automatically, so ask the merchant to update the credentials and test the connection again. "The platform rejected this system's connection source" means our connecting IP is not on the platform's allowlist; reauthorizing does not help, so contact support to get the IP allowlisted. When the column shows the platform's own wording instead, these credentials most likely lack return-related permission, which the merchant needs to confirm in the store admin

2. FAQ ​

Quick jump: FAQ | Notes

2.1 FAQ ​

▪ Why don't I see the "Fetch Orders Now" button? ​

This button only appears when the account is "connected" and "order fetch is on". If the account is currently "Disconnected" or "Not Verified", or order fetch is off, the button is hidden. First bring the account back to connected (see disconnected handling below), then turn on order fetch on the edit page. OneWarehouse accounts have their orders pushed in by OneWarehouse, so they have no order fetch settings and never show this button.

▪ Why don't I see the "Sync Product Mappings" or "Manual Stock Sync" buttons? ​

Both buttons share the conditions "connected + "Stock Push Method" is not "Off" + platform supports it". If any condition is not met, the button is hidden. Some platforms do not support syncing product mappings or manual stock sync, so the corresponding button won't appear even when connected with a push method chosen.

▪ What is the ******** in the credentials section? ​

That is a masked sensitive field. For security, credential parameters such as secrets, tokens, and passwords never show their real values on screen and are always displayed as ********. To update them, go to the Edit EC Account page and re-enter them.

▪ The account shows "Disconnected" — what should I do? ​

The red alert at the top of the page gives the matching repair button: for OAuth platforms (Shopify, Shopee, Liteshop), click Re-authorize to re-authorize on the platform; for API-key platforms, click Edit to update the credentials on the edit page, then test the connection once more after saving. Order fetch and push resume only after the connection is restored.

▪ Will the platform's orders still come in while the account is disconnected? ​

No. While the account is "Disconnected", the system will not automatically fetch and import this platform's orders, and the "Fetch Orders Now" button will not appear; "Scheduled sync (every 30 min)" stops as well. Restore the connection first.

▪ What happens when I click "Manual Stock Sync"? ​

The system takes the current WMS sellable quantity as the source of truth and overwrites the stock of every mapped product under this account (bundles included) onto the e-commerce platform (absolute overwrite). In other words, it changes the platform's stock numbers directly to the WMS numbers. This affects live sales and cannot be reverted automatically. Always confirm that the WMS stock is correct before running it. Also note that platform orders not yet fetched into the system at push time are not deducted; see Important notes.

▪ With the push method set to "Scheduled sync (every 30 min)", how often do the platform figures update? ​

While the account is connected, a round runs every 30 minutes (on the hour and half hour): 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 freshly fetched orders are deducted from the available quantity first; with no scheduled fetch it pushes right away. So a change in the warehouse reaches the platform within about 30 minutes, later if the fetch runs long. The first round after switching to this method syncs everything once; after that, each round pushes only products whose stock changed since the previous round; for bundles, it checks whether the component stock counted for this account (the sales channel's inventory types or those specified in the bundle, in the fulfillment warehouse), contents, push ratio, or active status changed. A few situations delay it:

  • If a "Manual Stock Sync" run or the previous round is still pushing, this round is skipped and the next round catches up
  • If the same merchant's scheduled fetch from the previous slot is still running when the next hour or half hour arrives, that slot's scheduled fetch moves to the following slot, and the scheduled sync is pushed by the still-running round once its fetch finishes; if what is running is a "Fetch Orders Now" fetch, both that slot's scheduled fetch and scheduled sync move to the following slot
  • With scheduled sync chosen, inbounds and stock adjustments no longer push an increment; the next scheduled round updates them with the latest quantity, and the inbound history shows "Stock push skipped (left to stock sync)". With "Push on inbound", increments are pushed as before; if a "Manual Stock Sync" run is in progress, the push triggered by the inbound waits, retrying every minute for up to 30 minutes before being recorded as failed in the inbound history
  • If bundle quantities can't be calculated or the whole bundle push fails, single products are still updated; the round is recorded as failed and the next round recalculates the same period
  • If the platform rejects some products (bundles included), the others are still updated. Rejected products are retried automatically in the next two rounds even without new stock changes; if they still fail, they wait until their stock changes again. Check the failure reason in the sync history. On 91APP, individually rejected products are not retried automatically; they are pushed again only when their stock changes. When Liteshop or 91APP has a platform-side failure (Liteshop rejects a whole batch, or the platform returns a server error or rate limit), the round is recorded as failed and the next round pushes the same period again
  • If the platform is temporarily unreachable (timeout), the round is recorded as failed and retried next round without marking the account disconnected; if the platform authorization has expired, the account is marked "Disconnected" and scheduled sync stops; once the connection is restored per the red alert at the top, the next round catches up on the changes made while disconnected

▪ The merchant says a bundle's stock on the platform isn't updating? ​

Check in order: the bound channel's "Product Mapping Rule" is by SKU (if this page shows "This sales channel doesn't map products by SKU, so bundle stock is not pushed", it isn't); on platforms with the "Sync Product Mappings" button, the stock push block should show a bundle mapping count — if not, sync mappings once and make sure the bundle's SKU matches the platform; finally click "Manual Stock Sync". Bundles don't update with "Push on inbound"; when the push method is not "Scheduled sync (every 30 min)", a change to a bundle's contents or push ratio needs one manual sync to take effect, and with "Scheduled sync (every 30 min)" the next scheduled round updates it.

▪ How do I stop pushing a product's stock to the platform (e.g. when a group buy ends)? ​

Turn off "E-commerce Stock Sync" on the product's edit page. From then on the product is no longer pushed (inbound, scheduled sync, and "Manual Stock Sync" all skip it), but the platform quantity is not pushed to 0 — the platform keeps the last pushed quantity, so if the platform product is still purchasable, the remaining quantity can still be ordered. The switch is at the WMS product level: every platform product mapped to that WMS product (e.g. an active and a hidden product with the same SKU, or products on other EC accounts) stops being pushed together. To stop only a Shopline hidden product, unpublish or delete it on Shopline, then click "Sync Product Mappings" once to remove its mapping.

▪ I clicked "Fetch Orders Now" but nothing happened, and it said "Too many requests"? ​

Manual order fetch has a 10-minute cooldown. If you trigger it again on the same account within 10 minutes, the system shows "Too many requests. Please try again in N minute(s)." Wait for the cooldown to end and trigger it again, or let the next automatic schedule slot fetch it for you. If the same merchant has a fetch in progress, the previous manual fetch is still queued and the cooldown keeps being extended, so there is no need to click again; if it cannot start within about an hour, it is dropped and the next on-the-hour or half-hour round fetches the account instead.

▪ The merchant says the fetch slot has passed but the orders are not in yet? ​

For channels under the same merchant, the automatic fetches that run at the configured slots go one at a time, never simultaneously — this stops two channels from importing orders that contain the same product at the same moment and both being judged out of stock. A configured slot is the earliest start time, not a guaranteed one: a channel waits for the one before it to finish. Different merchants run independently and never wait for each other.

The merchant pressing "Fetch Orders Now" is part of this ordering too: if the same merchant has a fetch in progress, it starts automatically within a few minutes after that one finishes, and the button stays in cooldown while it waits; if it still cannot start within about an hour, this manual fetch is dropped and the next on-the-hour or half-hour round fetches the account instead; conversely, if a manual fetch is still running when a scheduled slot arrives, that slot's scheduled fetch and scheduled sync move to the following slot. Single-order refetches triggered by a platform's real-time push are outside this ordering and may run alongside a scheduled fetch.

Do not judge "is a fetch running" by whether a new row appeared in Sync History — a fetch round with nothing to process and no failures leaves no record. Look at Next Fetch Time instead: for a scheduled round it only moves forward once that round finishes, so a time that has already passed usually means a fetch is in progress (exception: when a queued manual fetch is dropped after about an hour, this time is pulled back to that moment and stays in the past until the next on-the-hour or half-hour round fetches the account). Note that when the merchant presses "Fetch Orders Now" this time jumps forward immediately (see Manual actions), so it does not apply to manual fetches.

▪ What is "Return Order Sync" in the sync history? ​

It is the record of Shopline return orders being brought in automatically. For a Shopline account that is connected and has order fetching on, Shopline notifies the system the moment a return is raised, completed or canceled, and the system reads the return order back from the platform and turns the ones buyers requested or confirmed into return orders; it also checks the platform every 30 minutes to pick up any notification that went missing. These notifications are registered with Shopline automatically when a connection test succeeds, so the merchant has nothing to set up, and neither the warehouse nor the merchant has to create the return orders by hand. Verifying and converting them works exactly like any other return order; see the Return List.

▪ Why isn't a refunded SHOPLINE order in the system? ​

When a SHOPLINE order's payment status is "refunded" or "refund in progress", order fetching does not import it: a new order is not created, so it is not in "Order List"; Sync History also does not show the reason, because skipped orders leave no failure details and that run may leave no row at all, so Sync History cannot be used to investigate (a refunded order that is already in the system and gets stopped is different; see the next paragraph). A paid order whose payment status is neither "completed" nor "partially refunded" (for example a failed payment) is not imported either. An order with a partial refund (for example a price-difference refund) is imported as usual.

To investigate, ask the merchant to check the order's payment status in the SHOPLINE admin. If the payment status changes later, an order updated within the last 7 days is evaluated again on the next fetch. An order already in the system is handled differently:

  • Refunded or refund in progress: the next fetch holds it as "Refunded on Platform", whether picking has started or not. It's never cancelled automatically and isn't updated while held. A shipped order is left untouched. After release it follows platform updates again, but the system no longer changes the collection amount, so check and edit it yourself. A released "refunded" hold isn't held again; after a "refund in progress" hold is released, the order isn't held again while the refund stays in progress, but it's held again if the platform moves to "refunded", and both holds stay if the first hasn't been released.
  • Paid, with a payment status that is neither "completed" nor "partially refunded" (for example a failed payment): it keeps following platform updates until picking starts, and is held as "Other Reason" only when the update would set the collection amount to 0.

A refunded order that is partly shipped, with items still to go, is held too: refunded orders are fetched by a separate query that does not depend on the order's status on the platform (when the system ships, it pushes the order's status on the platform to "confirmed", which takes it out of the range the regular fetch queries, but this query still finds it). That query has two limits: it only covers orders updated within the last 7 days, and a refund that happens after the previous fetch is only caught on the next fetch. QC isn't interrupted because an order is refunded; see Fulfillment QC. In Sync History, the run that creates the hold records one extra success, without saying the cause was a refund (check the hold entry on the order for that); an order already on hold is not recorded as a success again.

▪ The merchant says a return exists on the platform but I can't find it — how do I check? ​

First confirm the account is Shopline, connected, and has order fetching on — if any of the three is missing, return orders will not come in. If all three are fine, open Sync History, expand the "Return Order Sync" rows and read the failure reason; most often a returned item could not be matched to a product, so the whole return order was not created.

▪ A message about real-time notification popped up as soon as I opened this page — did I click something? ​

No. Opening this page runs one automatic check of the account's real-time notification setup and fixes what is missing; the message appears only after something was actually fixed (see Automatic Real-Time Notification Check). The message lists which events the notification now covers. Nothing changed means no message at all, so seeing it tells you this visit really did complete the setup for this account.

▪ The message says the key has no real-time notification permission — what do I do? ​

Ask the merchant to go to the e-commerce platform's admin, tick the real-time notification (webhook) permission on the authorization page, and regenerate the key. Then update the key on the Edit EC Account page and test the connection. After that, the next visit to this page by anyone completes the setup automatically and shows the success message. Until the permission is granted, orders keep arriving on the configured schedule — nothing is lost.

▪ Can I recover an EC account after deleting it? ​

No. Deletion cannot be undone. Before removing the account, the system first attempts to clear the automatic notifications it previously set up on the platform. If you want to stop using an account but worry about deleting it by mistake, consider turning off order fetch and push on the edit page instead.


▪ What should I do if LiteShop shipment reporting fails or its result is unknown? ​

The system reports the actual shipped quantities separately for each order. Bundle quantities use complete sets based on the bundle contents recorded on the order (how many of each product make one set). Components of the same product must still meet the original total pieces per set even if their inventory types are changed to match. Total reported sets cannot exceed the quantity originally ordered for that platform item. When a bundle's components ship in separate fulfillments, a set is reported only after all of its components have shipped, so LiteShop may show fewer shipped sets until the remaining components ship. If the total quantity of a component product on the order exceeds its recorded pieces per set times the number of sets (for example, the bundle contents were changed and the platform order was synced again), that bundle item is not reported while the other items are reported as usual, and you are notified that the bundle's component quantities don't match the bundle contents recorded on the order. It will not be reported automatically later: check the bundle contents on the order, then update the item's shipped quantity manually in LiteShop. Temporary errors before sending are retried up to 10 times without blocking other orders; if they still fail, you are notified that shipment reporting failed after repeated retries. Check the LiteShop account authorization and connection, then contact support to report it again.

If you see a message that the shipment result is unknown, automatic resending stops to avoid counting shipped quantities twice. Check the shipment details in LiteShop, then give support the order and fulfillment numbers; do not ship the order again on the platform yourself. The completed warehouse shipment is not canceled.

2.2 Notes ​

⚠️ Important ​

  • Manual stock sync overwrites platform stock, affects live sales, and cannot be reverted automatically. Confirm that the WMS sellable quantity is correct before running it, to avoid pushing wrong numbers to the e-commerce platform.
  • Both scheduled and manual stock sync can add sold quantity back: platform orders not yet fetched into the system at push time are not deducted, so the pushed figure can add already-sold quantity back onto the platform and cause overselling. Scheduled sync does wait 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. Platforms with realtime notifications can pair them 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
  • Deleting an EC account cannot be undone. Once deleted, the account's integration settings are gone and cannot be recovered.
  • Do not manually fulfill orders or change order status on the e-commerce platform after integration. Shipping status between the warehouse and the platform is kept in sync by the system; operating on both sides separately causes status inconsistency.
  • Turning off order fetching also stops return orders from being created automatically — both follow the same switch, so check with the merchant before changing it.
  • Return verification results are not written back to the platform. After the warehouse receives and converts the goods, nothing changes on the platform side; refunds and store credit are the merchant's job in their own store admin.

💡 Tip: When the account shows disconnected, orders are not imported automatically. If you notice missing orders, come back to this page first to check the connection status, re-authorize or edit-and-retest per the red alert, then use "Fetch Orders Now" to fetch the missed batch once.


FeatureDescriptionLink
Edit EC AccountModify credentials, order-fetch and push settings, "Shipping Type Mappings"Go
EC Integration ListView the connection status and settings of all EC accountsGo
Sales Channel DetailView the sales channel settings this account maps toGo
Order ManagementView orders fetched from each e-commerce platformGo
Return ListSee the return orders created automatically from a platform and their verification progressGo

Last updated 2026-11-16 19:57