Check the source
Start with received Eccang inventory. Review warehouse coverage, source status, and the successful synchronization window. Resolve missing or stale dependencies first.
Eccang → Read-only intake
ANTCLOUD / INVENTORY COLLABORATION
Every allocation.
A clear calculation first.
From source inventory to a store’s target quantity. Bring mappings, rules, and execution results into a workflow your team can review.
Run an interactive trialFROM SOURCE TO RECEIPT
Four steps to a clear rule.
Make mappings explicit
Connect active channel listings, internal product SKUs, and source inventory. Bundles use explicit component quantities. Missing or conflicting links remain visible blockers.
Channel SKU ↔ Product SKU ↔ Source
Calculate and explain
Subtract safety stock, apply the allocation percentage, and round down. Review quantities, differences, and reasons for every SKU. Recheck the trial after changing settings.
Rule → Trial → Explanation
Review execution receipts
Use enabled platform capabilities for controlled execution, then review item-level results. A plan, queued task, or accepted request is not confirmation of platform success.
Controlled execution → Receipt
PUT A RULE TO THE TEST
See the quantity.
Understand the reason.
Adjust safety stock and allocation, toggle a SKU, or resolve a missing mapping. Run the trial to review single-product and bundle results, then export a snapshot of those exact settings.
Multi-SKU inventory trial
Eccang ERPRead-only source
Warehouse scopeSource SKUQuantity & observation time
Reviewable rule inputs
Relationship diagram, not live system status.
REVIEW THE DATA BEFORE THE QUANTITY
Know the source.
Trust the reasoning.
Eccang intake is read-only. Updates follow explicit source facts: an explicit zero can set inventory to zero, while an absent SKU retains its last known value. Absence alone does not imply deletion.
Rules also need checks for source freshness, warehouse coverage, and actual listing status. Missing data and conflicts stay visible for the team to resolve.
Explore product & SKU mappingsAFTER THE TRIAL
A plan is not a receipt.
Live publishing uses enabled, configured capabilities through a controlled process. Item-level states, platform receipts, and subsequent readback help confirm the result. CSV and JSON files from this page are local demo outputs and do not create publishing tasks.
Trial → Review → Controlled execution → ReceiptGOOD TO KNOW
About inventory rules.
Does a trial update platform inventory?
No. A trial calculates target quantities and explains differences and blockers. The demo on this page runs only in your browser. Live publishing is a separate controlled workflow that depends on platform capabilities, authorization, and execution gates.
Which platforms currently support live inventory publishing?
A controlled eBay store has completed live publishing and platform readback for a single listing. Request plans for other platforms are not evidence of live publishing. Availability must be confirmed for each platform and store.
How is bundle capacity calculated?
Divide each component’s available quantity by the quantity required per bundle, round down, and take the smallest result. In this demo, safety stock is then deducted in bundle units before allocation. An unmapped component blocks the bundle.
Why is export disabled after I change a setting?
Results belong to the rule and mapping snapshot at the time of the trial. Changing safety stock, allocation, enabled states, or mappings makes that snapshot outdated. Run the trial again to export results that match the current settings.
Does this include warehouse movements and shared-stock reservations?
The current scope covers source inventory, mappings, rules, and execution records. It does not include receiving, putaway, stocktakes, reservations, deductions, or a full WMS. The demo calculates each SKU independently and does not reserve shared components across SKUs.
BRING CLARITY TO YOUR TEAM