Skip to content

EC Account Detail ​


Table of Contents ​


Section 1: Features ​

The EC account detail page presents an account's integration status and settings in full: the left half is "Connection", the right half is "Settings". Beyond viewing, you can run several manual sync actions here (schedule fetch, sync mapped products, manual stock sync), as well as enter Edit or delete the account. The sync history at the bottom of the page lets you look back at the result and failure reasons of every automatic sync.

EC Account Detail - Page Overview

Quick Jump: Connection Info | Function Settings | Manual Sync Actions | Automatic Real-Time Notification Check | Sync History

1.1 Connection Info (left half) ​

Shows the account's basic details and integration credentials: the platform, Display Name, the bound sales channel, and the platform's integration info (key fields are masked to protect secrets). The tag in the top right shows the current connection status; for the meaning of the three states, see EC Integrations list.

When the account is "Disconnected", a red alert appears at the top of the page: authorization-based platforms offer a "Re-authorize" button, key-based platforms offer an "Edit" button, so you can restore the connection directly.

1.2 Function Settings (right half) ​

BlockWhat It Shows
Fulfillment WarehouseAt the top, showing which warehouse this account's orders ship from and which warehouse its pushed stock counts; when none is set it shows "Use the merchant's default warehouse (currently: warehouse name)", meaning orders ship from the default warehouse and the push counts only the default warehouse's available quantity. Not shown for OneWarehouse accounts, nor when the warehouse has enabled only one warehouse for you 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)
Order FetchingWhether enabled and the configured fetch slots; the next fetch time is listed only while it is on. Platforms with realtime notifications also show "Realtime New Order Fetch" (when on, new orders usually reach the system within a few minutes, about 5 minutes for Shopee, instead of waiting for a fetch slot). While order fetching is off, the saved slots are still listed and marked with "Takes effect only when Fetch Orders is enabled"; realtime fetch does not run then, so it always shows the same grey "Inactive" tag as order fetching, and 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 PushThe 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; with "Off", the saved percentage is still listed and marked with "Takes effect only after choosing a stock push method". The mapped product count and last sync time are listed only while the push method is not "Off"; when bundle mappings exist, an extra line shows the bundle mapping count. 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"
Waybill LayoutShown for Momo, Mo+, Shopline and Cyberbiz accounts only (for Cyberbiz it applies to T-Cat quick store pickup only): the layout currently used when printing waybills (A4 (the platform's original layout) or Thermal Label (split into two sections))
Shipping Type MappingsThe list mapping platform shipping codes to warehouse-side shipping types

Adjustments to these settings happen on the Edit page; the detail page is for viewing and running the manual syncs below.

▸ 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 Sync Actions ​

The detail page offers three manual actions, shown depending on the account's status and settings:

ActionWhen It AppearsEffectReversibility
Fetch Orders NowConnection healthy, order fetching enabled, and the platform is one the system fetches orders from (OneWarehouse accounts have their orders pushed in by OneWarehouse and do not have this button)Queues a fetch immediately, without waiting for the next scheduled slot; if the same merchant has a fetch in progress, it starts automatically within a few minutes after that one finishes, and pressing again while it waits shows "Too many requests"Just fetches earlier; if a scheduled slot arrives while it is fetching, that slot's scheduled fetch and scheduled sync move to the next round
Sync Product MappingsConnection healthy, "Stock Push Method" is not "Off", and the platform supports itRe-matches the relationship between platform products and warehouse products; platform items whose SKU matches a bundle SKU are mapped as bundlesUpdates the mapping table only; doesn't touch stock
Manual Stock SyncConnection healthy, "Stock Push Method" is not "Off", and the platform supports itOverwrites platform stock in batch with current warehouse stock, by push percentage; bundle sellable quantities are pushed in the same run; only the "Fulfillment Warehouse" counts, or the default warehouse when none is setDirectly rewrites platform stock; a confirmation dialog appears before it runs

If another sync is already running for the same account, this "Manual Stock 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.

When "Manual Stock Sync" hits a temporary connection drop to the platform (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".

📌 Note: "Manual Stock Sync" differs from day-to-day "Push on inbound" — "Push on inbound" only increases platform stock on restock, while manual sync overwrites the platform's numbers in batch with current stock, suitable for a one-time correction when the figures don't match. With "Stock Push Method" set to "Scheduled sync (every 30 min)", the system automatically applies the same overwrite to products whose stock changed, every 30 minutes; see Stock Push settings on Create EC Account for how it works.

Which orders come in ​

Scheduled fetching, "Fetch Orders Now" and real-time platform notifications all follow the same rule: 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 follows the platform until picking starts. An order is canceled automatically when the platform confirms the cancellation; situations that need a person's judgment, such as a full refund, a buyer's cancellation request or an order shipped on the platform, hold the order instead of canceling it, and it isn't updated until the hold is released. For per-platform exceptions, see "Why didn't an order on the platform come in?" in the "Platform Comparison & Caveats" document.

91APP order fetching ​

An order marked “Created” in 91APP may already have shipped. Scheduled and manual fetching only import uncancelled items that have no shipping number or have a number allocated but have not shipped. Items already being processed by logistics, delivered to a pickup store or delivered to the recipient are excluded. When an order that has not been imported yet is partially shipped, only the remaining eligible items are imported; orders with no eligible items are skipped.

Items of an order that has already been imported are never removed because of the platform's shipment status. If picking hasn't started in the warehouse but the platform shows some or all of its items as shipped (the sub-order is finished, or confirmed for shipping with a shipment status past unshipped; for example, shipped by another system), the order is held automatically with the reason "Shipped on Platform" and isn't updated in that round. A sub-order that is only "confirmed for shipping", with a shipment status still unshipped or no shipping number (the warehouse's own custom-carrier number request does this too), isn't held, and the order isn't updated in that round either. The hold note lists the triggering item's TS number, shipping number and platform shipment status. Check on the platform first: if all items have shipped, cancel the order; if only some have, edit the order to remove those items before releasing it, otherwise the shipped items will be shipped again. Once released, the same order is not held automatically again; but it doesn't follow platform updates while any sub-order is finished or confirmed for shipping, and it's still canceled if every sub-order is canceled. Orders that are being picked or are partially shipped are not checked.

If an item to be imported has an allocated shipping number with no matching shipment status, or the status lookup fails, that order is not imported in this round. Confirm the shipment status on the platform before fetching again. If the lookup fails only while checking items that were already imported, the order still syncs and the hold check is skipped for that round. Batch-fetch failures are listed in Sync History. Updating these fetch rules does not automatically cancel orders imported previously.

Each fetch reads the cancelled order list first, then the new order list. If a page of a list cannot be fetched because the connection times out or cannot be established, the platform's response cannot be read, or the platform returns an error message, the rest of that list is skipped for this round; pages already read are processed as usual, and the other list is still fetched. The sync history then shows a "Entire run" row. When the connection times out, cannot be established or the platform's response cannot be read, the row states which list, which page and why; when the platform returns an error message, the row shows the platform's original wording. If the credentials are no longer valid, the whole run stops without fetching the other list, and the account is marked "Disconnected". Every round rereads the last 7 days of each list, so the next round picks up the orders missed this time.

Bundles in manual stock sync ​

See Add Bundle for how the quantity pushed for a bundle is calculated. This step has a few conditions:

  • The bound sales channel's "Product Mapping Rule" must be by SKU (unset counts as by SKU); when platform orders come back, only channels that map by SKU can recognize a bundle.
  • On platforms with the "Sync Product Mappings" button, only bundles that have mappings are pushed, so sync mappings once first; Liteshop and 91APP have no such button and target all your bundles, skipping SKUs the platform doesn't have.
  • Deactivated or deleted bundles are pushed as 0, clearing their platform stock, unless the SKU is now used by another product or bundle.
  • If the bundle push fails, single products are still pushed.
  • When the push method is "Scheduled sync (every 30 min)", bundles whose 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 are also pushed in the next scheduled round; "Push on inbound" doesn't include bundles.

1.4 Automatic Real-Time Notification Check ​

Every time you open 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 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), your account only has view permission for e-commerce integrations, 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. 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 you set a webhook to Paused in the WooCommerce admin yourself, 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 Sync History ​

"Sync History" at the bottom of the page lists the results of this account's most recent automatic syncs, one row per run. Order fetching, return order syncing and stock pushing leave no record when there was nothing to process and nothing failed, so every row you see for those three means the system actually did something or ran into a problem ("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 on the warehouse side, 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; 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" pulls platform orders in, "Return Order Sync" turns platform returns into return orders, "Stock Push" pushes stock to the platform, and "Product mapping" rebuilds the product mapping. The four run independently — a failed return order sync does not affect order fetching
Status"Success" everything went through; "Partial Failure" some succeeded and 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 on the warehouse side (cancelled, or — for an order already in fulfillment — put on hold instead), and the same record is not counted again in later rounds; a warehouse-side 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

Rows with failure details can be expanded. Each expanded row is one failure: "Target" points at what failed (for return order syncing this is the platform's return order number, which you can look up directly in the store admin), "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, rather than one item failing. You also get a notification when a sync fails; opening it brings you back to this page with that run expanded.

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 — press "Sync Product Mappings" again later to retry.

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. The message contains the platform item codes that could not be matched, which you can look up in the store admin. Fix the mapping — press Sync Product Mappings to rebuild it, or go to "Unknown Products" and map the unmatched item on the source order to your product — and then do nothing else: any return order updated on the platform within the last 7 days is created on the next run
A returned item has no inventory typeThe system does not know which inventory category 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 reauthorize or update the credentials per the red alert at the top of the page 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 for help. When the column shows the platform's own wording instead, these credentials most likely lack return-related permission on the platform, which you need to confirm in the store admin

Section 2: FAQ ​

Quick Jump: FAQ | Notes

2.1 FAQ ​

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

This button appears only when the account is "connection healthy" and "order fetching enabled". If the account is disconnected, restore the connection first; if order fetching is off, enable it on the Edit page. OneWarehouse accounts have their orders pushed in by OneWarehouse, so they have no order fetching settings and never show this button.


▪ Could "Manual Stock Sync" mess up platform stock? ​

It overwrites the platform's numbers in batch with the warehouse's current actual stock, by push percentage. If the platform had stock from other channels (not managed by this system), the overwrite makes this system's numbers authoritative. So confirm the push percentage is correct before running; the system also shows a confirmation dialog for you to confirm again. Also note that platform orders not yet fetched into the system at push time are not deducted; see 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 previous slot's scheduled fetch 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 you restore the connection per the red alert at the top, the next round catches up on the changes made while disconnected

▪ A bundle's stock on the platform isn't updating? ​

Check in order: the sales 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 first and make sure the bundle's SKU matches the platform; finally click "Manual Stock Sync". 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 reach the platform; with "Scheduled sync (every 30 min)", the next scheduled round updates it.


▪ What does "Sync Product Mappings" do? ​

It re-matches the relationship between platform products and warehouse-system products. After you add products on the platform or fix a platform SKU, run a manual sync so the mapping updates immediately, preventing orders from becoming unknown products for lack of a match. It only updates the mapping table, not stock.

On Shopline, 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 warehouse product maps to both an active and a hidden product, the pushed stock is split evenly between them to prevent overselling.

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 every sale page should sell the full quantity, split it into separate products with different SKUs in the warehouse system.


▪ 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 product level: every platform product mapped to that warehouse 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.


▪ Is "No mapped products" normal? ​

When you've just chosen a stock push method and haven't synced mappings yet, it shows no mappings. Click "Sync Product Mappings" once to build them. Some platforms use real-time lookups and don't store a mapping table; for these, no mapped-product count is shown, which is normal.


▪ The account is disconnected — do I fix it on this page? ​

The red alert at the top guides you: authorization-based platforms click "Re-authorize" to re-authorize; key-based platforms click "Edit" to enter Edit, update, and re-test the credentials.


▪ What is "Return Order Sync" in the sync history? I never set it up ​

It is the record of Shopline return orders being brought in automatically. For a Shopline account that is connected and has order fetching turned 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 your 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 — no setup from you, and neither you nor the warehouse has to create the return orders by hand. For the full behavior see the Return List.


▪ How do I stop return orders from coming in automatically? ​

Return order syncing follows the "order fetching" switch. Turn order fetching off on the Edit page and this account stops fetching orders and stops creating return orders, and of the notifications the platform sends only cancellations and buyer cancellation requests are applied. Return orders already created are not removed — process or cancel them as usual.


▪ The scheduled slot has passed but the orders are not in yet — why? ​

For your channels, 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 therefore the earliest start time, not a guaranteed one: a channel waits for the one before it to finish, and the more channels you have (or the slower the platform responds), the more noticeable the delay.

Pressing "Fetch Orders Now" yourself 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, with no need to press again — while it waits the button stays in cooldown, and pressing it 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; 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 not subject to it and may run alongside a scheduled fetch.


▪ The sync history is empty — does that mean nothing is syncing? ​

Not necessarily. Order fetching, return order syncing and stock pushing leave no record when there was nothing to process and nothing failed, so an empty list is normal right after connecting or when nothing changed on the platform. Pressing "Sync Product Mappings", on the other hand, always adds a row — success or failure alike (for "Yahoo Shopping Center", a failure to trigger the export shows up immediately, while a successful trigger is written once the platform sends the file back; if that returned file cannot be downloaded or read, no row is written at all and the failure shows up as a notification instead) — so if no row appears, that run never started. The daily incremental sync, by contrast, leaves no row when nothing changed on the platform. "Scheduled sync (every 30 min)" works the same way: if stock did not change between two rounds, no new "Stock Push" row appears. To tell whether order fetching is running, look at Next Fetch Time in the settings panel: 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, not that it is stuck (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).

Pressing "Fetch Orders Now" behaves differently — that time jumps forward the moment you press it, so it cannot tell you whether the manual run has finished. Judge a manual fetch by the sync history instead (a new row appears only when there were orders to process or something failed).


▪ 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? ​

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 page and test the connection. The next visit to this page completes the setup automatically and shows the success message. Until the permission is granted, orders keep arriving on the configured schedule — nothing is lost.


▪ What happens when I delete the account? ​

The account is removed from the list, its product mapping data is cleared along with it, and this cannot be undone. Before deleting, confirm this platform's orders no longer need to be handled through the system.

▪ 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 in batch — confirm the push percentage is correct before running
  • Deleting an account also clears its product mapping data and cannot be undone
  • While an account is disconnected, orders stop importing and scheduled stock sync stops too — restore the connection promptly per the top alert
  • "Scheduled sync (every 30 min)" and "Manual Stock Sync" do 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 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
  • Turning off order fetching also stops Shopline return orders from being created automatically — both follow the same switch
  • Return verification results are not written back to the platform; handle refunds and store credit yourself in the store admin

💡 Tip: When platform stock figures don't match the system, first confirm the push percentage and mapped products are correct, then run "Manual Stock Sync" once for a batch correction.


FeatureDescriptionLink
EC Integrations (Edit)Adjust the account's credentials, fetch and push settings, and "Shipping Type Mappings"Go
EC Integrations (List)View and manage all EC accountsGo
Platform API LogsView this account's order-fetch and stock-push call records and failure reasonsGo
Return ListSee the return orders created automatically from the platform and their progressGo

Last updated 2026-11-16 19:57