Hello ServiceNow Community,
I hope you are doing good.
As part of our ongoing ServiceNow Sourcing and Procurement Operations (SPO) implementation to replace our legacy procurement platform, we configured the Amazon Business PunchOut Integration according to the official documentation.
While the outbound PunchOut flow works as expected, we are currently facing a critical issue on the inbound path: the callbacks for Order Confirmation and Shipping Confirmation are failing due to an authentication error on the ServiceNow inbound REST endpoint.
Inbound Path (Failing)
When Amazon sends a Shipping Confirmation with corrext URL incl SysID, the request reaches our ServiceNow instance but fails at the authentication layer. Surprisingly, the Order Confirmation is not logged at all.
Under ServiceNow’s standard PunchOut setup, the Supplier Configuration only needs cXML credentials—no ServiceNow user account is required since authentication happens directly through cXML.
Outbound Path (Working in general)
The entire outbound workflow functions correctly:
The user launches the Amazon PunchOut catalog from ServiceNow.
Items are selected and returned to ServiceNow to create a cart.
A Purchase Requisition / Purchase Order is generated in ServiceNow.
Amazon receives the purchase order, processes it, and generates the order confirmation email.
We suspect this is driven by an underlying API / Security Restriction, where ServiceNow requires specific web service permissions.
We are actively in touch with ServiceNow Support on this matter, but we are also reaching out to the community for any insights or past experience, as the overall success of our project heavily depends on resolving this inbound integration issue.
I would greatly appreciate any support and insights from your expertise!
BG
Martin
