AssetShop reads across the systems you already run — ERP, procurement, warehouse, transport — and surfaces the leakage, variance, and working-capital signals inside them. It never changes those systems. This walkthrough shows the path from connecting a source to your first insight, on a synthetic demo tenant.
Read-only by default. We read; we never write to your systems of record. The only thing AssetShop can ever write back is an audit / approval entry — and only if you switch it on.
Choose a source to start with — most teams begin with their ERP. The connection is read-only and ships with a conformance certificate your security team can review.
SAPSAP S/4HANA ERP
ORAOracle ERP Cloud ERP
NSNetSuite ERP
D365Dynamics 365 ERP
Every connection declares exactly what it reads, and what it does not. You can disconnect at any time.
Step 3 · Scope & residency
You decide what we read, and where it stays.
Review the read-only scopes for this source and confirm your data residency region. Nothing is read outside what you approve here.
Purchase ordersread
Invoices & APread
GL postingsread
Supplier & material masterread
Not read: payment execution, user credentials, or any write-enabled transaction path.
Your data stays in the region you choose, inside your own tenant. The only write path is an audit / approval entry — off by default.
Step 4 · Map & validate
Let’s confirm we understand your data.
We’ve mapped your records to the AssetShop model. Review the matches and validate — this makes every later insight traceable and trustworthy.
Source field
AssetShop entity
EKKO / EKPO
→
Purchase order
···
RBKP / RSEG
→
Invoice
···
LFA1
→
Supplier
···
MARA
→
Material
···
Canonicalisation is deterministic — the same source state always yields the same result and the same anchored lineage.
Step 5 · First insight
Here’s the first thing worth your attention.
Based only on what your systems hold, here’s an early signal — with the lineage of exactly where it came from.
$2.4MSynthetic · demo
Off-contract spend identified across DET-01, STG-02, OSK-03 over the trailing 12 months.
1,184
maverick POs
3.1%
of observed spend
17
suppliers, off-contract
Provenance
Derived from 1,184 PO records + contract master, read-only.
Anchor: sha256:7f3a9c2e…b1d4 (synthetic)
Every figure is traceable to the source records it came from. Figures shown are synthetic (Meridian Industrials demo tenant).
Step 6 · Invite your team
Bring the people who act on this.
Invite colleagues with role-appropriate access. Each person sees what’s relevant to their role.
Role-based access throughout — people see only what their role should see.
You’re set up.
This was a preview of the AssetShop activation path on a synthetic tenant. In a real deployment, you’d now be looking at insights drawn from your own systems — read-only, residency-bound, and fully traceable.