How Lapasar connects to SAP Ariba
SAP Ariba runs PunchOut over cXML. When a requisitioner selects the Lapasar catalogue, Ariba posts a PunchOutSetupRequest to Lapasar's endpoint; Lapasar validates the credentials and returns a session URL into the live marketplace. The buyer shops normal e-commerce style — live stock, organisation-specific contract pricing, only the catalogue views their company has approved.
On checkout, the cart posts back to Ariba as a PunchOutOrderMessage: structured requisition lines with prices, quantities and classification codes. The requisition then routes through your existing Ariba approval chain, and the approved purchase order is transmitted to Lapasar as a cXML OrderRequest for fulfilment.
Level 1 or Level 2 PunchOut in Ariba
Level 1 takes buyers to the Lapasar storefront to search and shop — fastest to deploy and suited to a marketplace-scale catalogue. Level 2 shares item index data with Ariba so Lapasar products appear directly in the buyer's own catalogue search and deep-link to the product page. Many organisations start at Level 1 and graduate to Level 2 for their highest-volume categories.
- Level 1 — store-level PunchOut, live in weeks
- Level 2 — item-level results inside Ariba search
- Organisation-specific catalogue views & pricing
- cXML OrderRequest PO transmission
Why Malaysian Ariba customers add a marketplace supplier
Enterprises running SAP Ariba in Malaysia typically have strategic categories under contract but a fragmented long tail — thousands of low-value purchases across dozens of ad-hoc vendors, each needing supplier onboarding, quotes and manual requisitions. Adding Lapasar as a single PunchOut supplier channels that entire tail through one governed connection: one enablement project, one supplier record, one invoice relationship — and a marketplace of 2 million SKUs behind it, fulfilled from Lapasar's own warehouses and delivery fleet.