archMCP
Use case / Availability & delivery

“Can you get it to us
by next Thursday?”

An example using your existing product and shipping API endpoints. The answers it can give depend on what those endpoints return.

What the experience could look like.

ILLUSTRATIVE CUSTOMER SCENARIO
Can you get the XR-400 valve to Rotterdam by next Thursday?

This example queries your product and delivery endpoints. We confirm they exist and return reliable information before anything is switched on.

ILLUSTRATIVE ANSWER, SAMPLE DATA

In stock: 14 units, confirmed by your stock API, updated 10 minutes ago.

Delivery to Rotterdam: an estimate of 3 to 5 working days from your carrier data, not a commitment.

The answer should distinguish confirmed information from estimates, and identify the source. It should not invent missing stock or delivery dates.

What needs to be connected.

Product identification

A reliable way to match the requested product to the correct item in your system.

Stock information

An authorised source of availability, with an understood update frequency.

Delivery information

The source of applicable lead times, destination rules or carrier estimates.

What we would agree before building.

  • Which products, customers and locations are in scope.
  • Whether stock is informational or can be reserved. Reservation is a separate capability.
  • How old information and unavailable source systems are handled.
  • What is an estimate and what can be treated as a commitment.
  • Which questions and permission checks must pass before launch.

How we would measure it.

Compare the existing enquiry process with the connected experience: answer correctness, time to obtain information and whether customers can complete the intended task. Set a baseline before claiming improvement.

No measured customer outcome is claimed for this illustrative scenario.

Which of your customers’ questions looks like this one?

Tell us what you run and what you want to make possible.

Talk to our team