Works with PeakingYour IFS Cloud is the record. Peaking works with that.
Your data keeps living in IFS Cloud. What changes is that the customer request stops waiting for somebody to have time to look it up, price it and key it in.
Today the request comes in by email or by phone, somebody translates it into IFS Cloud part numbers, checks price and availability, builds the quote outside the system and then keys it back in.
That path is what gets shorter. The data keeps living where it lives.
Your IFS Cloud current, with no extra work.
Every answer goes out with that customer price list and with what is on the shelf today, exactly as it stands in IFS Cloud.
When the customer confirms, the sale is already in your IFS Cloud. Nobody types it again.
Your customer knows when what they bought arrives, without calling your team.
Your specialists stop searching and keying, and spend the day closing.
From the customer message to the order written.
Your customer is recognized with their history, without repeating who they are.
The option you actually have, not the one that ran out.
On that customer price list, with no keying errors.
The sale written into your IFS Cloud without anyone typing it.
Your customer knows when their order arrives.
Your IT group decides.
The connection is reviewed in the discovery session and turned on when your team authorizes it, in stages and with a record of every action.
Reviewed in the discovery session and turned on when your IT group authorizes it.
Only what is needed to operate, with its own user and a record of every action.
Every customer runs in its own environment, and your data is yours.
Peaking operates from the first day on its own catalog, before IFS Cloud is connected.
What your IT group asks first.
What permissions does it write with in IFS Cloud?
Its own user, with the minimum permissions needed to operate, defined by your IT group. Every action is recorded with its user, its timestamp and its origin.
What happens while IT has not authorized the connection?
Peaking answers, quotes and leaves the sale ready from day one on its own catalog. Writing into IFS Cloud gets turned on later, when your team decides.
Can we test against a sandbox first?
Yes, and that is normal on projects this size. It connects to your test environment first and moves to production when your team validates the result.
Does it work with our version and our modules?
In the discovery session we review your version, your installation and which modules you have licensed, and tell you what is connected on day one and what is not.
What is logged for each operation?
Every read and every write, with its origin, its user and its result. Your IT group can audit it whenever they want.
Other systems it works with.
Peaking works with the ERPs industrial distribution runs on.
What your systems team will ask.
Verified against IFS documentation.
IFS Cloud publishes each functional area as an OData projection with entity sets and actions, documented in OpenAPI in the API Explorer.
OAuth 2.0 and OpenID Connect with the IFS Identity and Access Manager (IAM): a service IAM client is created and Peaking obtains a Bearer token with client credentials; permissions follow your service user.
Cloud or your own server. Peaking works the same either way, and the connection route is decided in the discovery session.
A service IAM client in IFS Cloud with client credentials. A service user with permissions over the sales, inventory and customer projections. The projections active on your IFS Cloud version, checked in the API Explorer.
Industrial distributors already running this way.
You've got this.
Peaking shows up to the session already running on your catalog, so you watch one of your own requests land in your IFS Cloud.