No. ATUM still owns the inventory schema, the purchase order workflows, the supplier records and the underlying business logic. SleekView Charts is a read layer on top of the same tables. Disable it tomorrow and Stock Central works exactly the same way.

Yes. The Multi Inventory location data becomes a first-class group-by axis, so per-location stock cards can show value, count or status mix per warehouse. Location filters apply across the whole dashboard at once.

Yes. Card layouts save per user and can be shared by capability. A common pattern is a shared purchasing dashboard and a separate warehouse dashboard, each opening as the landing screen for the right role.

No. SleekView Charts only queries when an admin opens the dashboard screen. Stock Central, the editor and any front-end behavior continue to run unchanged. Heavy aggregations cache briefly so reopening the dashboard stays fast.

Yes. Click any chart segment and SleekView opens the corresponding filtered table view of the same rows. Edits routed through that view still hit ATUM's own hooks so audit logs and stock change triggers fire as expected.

Each card reads live from the database on dashboard open. There is no separate sync layer to drift out of date. Lightly cached aggregations refresh on each load for snappy navigation between cards.

Yes. Any custom meta or column you have added to ATUM products can be exposed as a group-by or value column in chart cards. Country-of-origin, brand, internal tier tags all become axes for chart layouts.

Individual chart data exports to CSV with the columns visible. Dashboards themselves are JSON configurations that can be exported and imported, useful for staging-to-production parity or for sharing layouts across multisite installations.