Prices and stock that stay in sync — everywhere at once
Oversells and stale price lists share one root cause: numbers living in more than one place. InventaCloud makes your inventory and pricing data the single source — apply an update once and every reseller's portal view, download, and feed reflects the applied update, with a change log behind every number.
How a sync round-trips
- Send the update Upload inventory or price files (CSV/XLS) directly, or deliver them through FTP where configured — partial updates are fine; only the SKUs in the file change.
- Records update by SKU Quantities, restock ETAs and quantities, price roles, and discontinuation status land on the product record.
- Catalogs rebuild Affected catalogs rebuild after the update is applied, with Catalog Rules re-applied — downstream surfaces reflect the applied update.
- Partners see the result Every reseller's next portal view, download, or feed pull carries the new numbers — with the catalog's latest update date shown in their portal.
Why teams use it
Resellers see live quantities and restock ETAs instead of last week's export — stock surprises stop being your support queue.
Price, cost, MSRP, and custom roles update together, so wholesale, dealer, and retail numbers never drift apart.
Per-SKU price and discontinuation overrides apply on top of every rebuild — partial corrections without waiting on the vendor.
Stock, price, and status changes are recorded — who, what, when — and rollback undoes an import that shouldn't have happened.
Flag SKUs with an optional future date; resellers see it in their portal with time to sell through or re-source.
FTP-delivered update files enter the same import workflow — with automated processing available once your ingestion schedule is configured.
What's included
Good to know
Sync updates the source numbers; each catalog's rules still compute what it delivers — markups and adjustments apply to the new values on every rebuild, with MAP and MSRP traveling alongside as current price data.
The same current data drives publishing — together with Multi-Channel Publishing, price and stock changes carry through to connected storefronts keyed by SKU.
Works together with
Related written guides
Common questions
Do I have to send full files every time?
No — partial updates are the normal case. Send only the SKUs that changed; everything else keeps its current values. Uploads are scoped per brand so multi-brand vendors stay organized.
What if an update file was wrong?
Every change is logged with its previous value, and rollback restores it. A bad price file is an undo, not an incident.
How fast do resellers see changes?
Affected catalogs rebuild after the update is applied, and each reseller's next portal view, download, or feed pull reflects the applied update — the catalog's latest update date confirms it in their portal.
Build one catalog that works everywhere.
Start a 14-day free trial and see it working on your own catalog — onboarding call included.