A 45-day pilot. Up and running within 30 days.
Start with a few products. Collect supplier data once. Reuse it across teams, customer requests and product passports. Target: your first live workflow within 30 days, then validate the value through day 45. Timing depends on agreed scope, data access and supplier participation.
Prove it on a few products first
Choose your hero SKUs, load their data, and run the full loop end to end, collect from suppliers, calculate, verify, and publish a DPP or file EUDR, in weeks. You see the workflow on products you know before committing across the catalogue.
Three ways to get the data in
- API and MCP, for a live two-way sync with ERP (Dynamics 365, SAP), PIM, PLM and DAM
- AI-assisted import, to pull your existing spreadsheets and documents into the model
- Manual entry, for the data that only lives in someone’s head today
Importing from SAP standard formats
If you run SAP, you do not need a custom integration to begin. Keystone reads the standard exports your team can already produce, so a first import is a file, not a project.
- Material master and classification data
- Bill of materials, including multi-level explosions
- Purchasing and vendor master records
- Batch and characteristics data where used
We have a guide to the common cases, generalised from real migrations, showing how each SAP standard format maps into the Keystone record. Rather than send a document, we walk you through it on your own exports.
No restructure
Keystone maps your existing fields into one consistent model, so your systems of record stay authoritative and nothing has to be rebuilt. That is why a pilot is measured in weeks, not quarters.
Our AI understands your product structure. It recognises what is a product, a component, a variant or SKU, and a batch, so each piece of information goes to the right place and is reused properly across every product that shares it.
- A component used in twenty products is stored once and linked twenty times, not copied
- Variant and SKU attributes stay with the variant; shared specifications stay with the product
- Batch-level facts, such as origin or test results, stay with the batch they describe
- Certifications and documents are attached at the level they actually cover, then reused wherever that component or material appears
The long game
The alternative to a pilot is buying a segregated tool for each new regulation, which only deepens the data fragmentation and the cost. A pilot proves the opposite: one foundation that every future rule reuses. Waiting, or adding point tools, simply raises the bill and spreads the problem across every team.