A catalogue built for the buyer, inside their procurement portal.
cXML PunchOut lets an enterprise buyer shop from their own procurement portal into a DataFlow catalogue tailored to them — their negotiated prices, their allowed items, your branding. They build a basket, send it back, and confirm a cXML Order Request that creates a sales order. They never log into DataFlow directly.
The problem
When enterprise buyers cannot buy your way.
Large buyers purchase through their own procurement portals. If you cannot meet them there, their orders arrive by hand and their catalogue is never quite right.
Buyers will not leave their portal
Enterprise purchasing runs through procurement systems such as Ariba and BravoSolution. Asking a buyer to log into a separate supplier site is a non-starter, so their orders come in some slower way instead.
One catalogue does not fit everyone
Each buyer has their own negotiated prices and their own list of allowed items. A single public catalogue shows the wrong prices to the wrong people and lists things they are not meant to order.
Re-keying the confirmed order
Even when a buyer sends an order, someone has to read it and type it into your system as a sales order — a delay on every order, and a chance to get a line wrong.
No record when an order is queried
When a buyer disputes what they submitted, there is nothing kept of the exact message their procurement system sent, so settling the query comes down to whose email to trust.
How it works
A dedicated service that meets the buyer where they buy.
The portal punches out; DataFlow serves the catalogue and takes the order.
The PunchOut Setup Request and session
The buyer punches out from their procurement portal to start a session. A PunchOut Setup Request opens the session without a separate login.
No loginbuyers never sign into DataFlow
In-portalshopping stays in their system
A catalogue tailored to each buyer
Their negotiated prices and their allowed items, not a public list. Presented with your branding so it reads as your catalogue.
Negotiatedeach buyer sees their prices
Allowed itemsonly what they may order
From PunchOut Order Message to a sales order
The basket returns to the portal as a PunchOut Order Message. A final cXML Order Request creates the sales order in DataFlow.
Order Requestcreates a sales order
No re-keyingstraight from the basket
Enterprise portals and an audit record
Built for enterprise procurement portals such as Ariba and BravoSolution. The original cXML payload is retained for audit.
Aribaand BravoSolution and the like
Retainedoriginal cXML kept for audit
Explore more
More integrations.
Other ways DataFlow takes orders in and connects to your customers automatically.
It lets an enterprise buyer shop from their own procurement portal into a DataFlow catalogue tailored to them. The buyer punches out, builds a basket, and their procurement system sends a cXML Order Request that creates a sales order in DataFlow — all without the buyer logging into DataFlow directly.
How does the flow work?
The buyer’s portal sends a PunchOut Setup Request; DataFlow serves a catalogue with the buyer’s negotiated prices, allowed items and your branding; the buyer returns their basket as a PunchOut Order Message; and a final cXML Order Request creates the sales order.
Do buyers need a DataFlow login?
No. Buyers never log into DataFlow directly. They stay in their own procurement portal — such as Ariba or BravoSolution — and punch out to a catalogue that is tailored to them.
Is there an audit record of what was ordered?
Yes. cXML PunchOut runs as a dedicated background service and retains the original cXML payload, so there is a record of exactly what the buyer sent.
See it on your catalogue
Meet enterprise buyers on their procurement portal.
