Source & order

Start the purchase with the right records.

Vendor and item information sits behind purchasing. Master data brings those records into the procurement process so teams can refer to the context behind a requirement, quotation or order.

Organise the information behind the work.

The item and supplier records your business uses need a clear place in the process. Start with the information teams rely on to identify what they need and who they buy from.

Keep records close to the purchase.

Master data should be useful when work is being done, not only when someone maintains a spreadsheet. Connect the record with the purchasing activity it supports.

Define ownership across systems.

Agree which records are maintained in Kraya and which remain elsewhere. Where another system is involved, review the available integration and the responsibilities for maintaining the data.

Questions

Which records should we bring to the demo?

Start with your vendor and item structures, plus any other masters your process depends on.

Can we retain another system as the source for some records?

Discuss the intended split and available integration with the team before defining the implementation.

Build around the records your team uses.

Bring a sample of your current master-data structure.