A jointly scoped pilot with agreed systems, examples and acceptance criteria.
Connect sign-in and a customer-specific catalogue for one partner
Transfer items, quantities, units and prices to the partner's cart
Test return navigation, cancellation and invalid line items together
Scope, project price, schedule and required provider services are agreed before commissioning. Handover includes the agreed technical documentation and introduction.
Monitor one existing partner connection, investigate errors and plan changes to the shop or procurement system.
Technical takeover of the agreed existing solution
Agreed monitoring, troubleshooting and change maintenance
Documented handover of open issues and completed changes
Monthly price, allowance, service hours, term and cancellation are agreed separately. Infrastructure, licences and on-call support are included only when explicitly offered.
Partner requirements, test access and examples of the partner's item identifiers
A description is enough for your first enquiry. We will then agree suitable ways to exchange files and arrange access.
What the scope covers
OCI and cXML/PunchOut are different interfaces. One approach is agreed per project. Transferring a cart is not yet a binding order; the order return channel and provider fees are planned separately.
We check the package against your project. Your enquiry is non-binding; commissioning and scheduling are agreed afterwards.
UNDERSTAND THE TOPIC
Your major customer requires PunchOut: from shop to procurement system.
One possible workflow starts when a buyer opens the supplier's shop from their procurement software, selects items and returns the cart to the procurement system. Approval and ordering follow there. Separating these stages in advance lets you explain precisely which part the shop connection handles.