Connection you approve
Reviewed in the discovery session and turned on when your IT group authorizes it.
Works with PeakingYour Sage X3 stops running a day behind.
Your data keeps living in Sage X3. What changes is that the customer request stops waiting for somebody to have time to look it up, price it and key it in.
How it works today
Today the request comes in by email or by phone, somebody translates it into Sage X3 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.
The walkthrough
From the customer message to the order written.
What happens at each step, with your system.
Entendido
Your customer writes the way they write.
Result
Your customer is recognized with their history, without repeating who they are.
Encontrado
It finds the answer in your catalog.
Result
The right option from your catalog, on the first try.
Cotizado
It builds the quote with your rules.
Result
On that customer price list, with no keying errors.
Capturado
The customer confirms and the order gets written.
Result
The sale written into your Sage X3 without anyone typing it.
Listo
Your customer asks and has the answer instantly.
Result
Your customer knows when their order arrives.
Sales · QuotesNewDraft
- Customer
- ·
- Price list
- ·
- Delivery
- ·
ItemQtyAmount
Total$ 21,660.00
Illustration with sample data
With your Sage X3
Your Sage X3 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 Sage X3.
When the customer confirms, the sale is already in your Sage X3. 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.
Start today. Connect when you decide.
Peaking answers, quotes and writes from day one. Once your IT group authorizes it, the quote and the order queda escrito into your Sage X3.
How it connects
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.
Scoped permissions
Only what is needed to operate, with its own user and a record of every action.
Isolated environment
Every customer runs in its own environment, and your data is yours.
Running from day one
Peaking operates from the first day on its own catalog, before Sage X3 is connected.
See it run on your own catalog.Peaking shows up to the session already working with your products, so you see the result before you decide.
Preguntas
What your IT group asks first.
What permissions does it write with in Sage X3?
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 Sage X3 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 platforms
Other systems it works with.
Peaking works with the ERPs industrial distribution runs on.
The Sage X3 fact sheet
What your systems team will ask.
Verified against Sage documentation.
Official Sage X3 web services exposing published objects such as quotes (SQH), orders (SOH), deliveries (SDH), items and customers for read, save and update, plus the GraphQL interface with product, stock, order and delivery nodes.
SOAP web services with a Sage X3 user on the Syracuse server; GraphQL with a connected application that signs JWT tokens with its secret.
Cloud or your own server. Peaking works the same either way, and the connection route is decided in the discovery session.
Objects SQH, SOH, SDH, ITM and BPC published as web services in GESAWE, and a web services pool configured in Syracuse. For GraphQL, a Sage X3 version with the GraphQL interface and a connected application with its id and secret. An integration user with functional rights over sales, stock and customers.
Customers
Industrial distributors already running this way.
$27.8 Min quotes created, in a single operation
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 Sage X3.