Skip to content
PROWERB
Services
Industries
Cases
Lab & Software
Company
DENeeds Check →
Services
Industries
Cases
Lab & Software
Company
LanguageDEEN
Start Needs Check →
PROWERB — Elevating Brands

Marketing Operations Backbone since 1979. Promotional products, logistics, kitting and digital commerce. One partner with its own operations in Kleve.

Elevating Brands — since 1979.Kleve · Düsseldorf · Dortmund · Lüdinghausen
Services
Logistics & fulfillmentPromotional products & merchandiseDigital commerce & marketplaceEvents & campaignsKitting, textile & ESGTech & AI
Company
About usLocationsHow we workSustainabilityCareersContactInternationalPress & news
Resources
GuidesInsights archiveGlossaryDownloadsTools & calculatorsCosts & calculationCompare operating models
Contact
PROWERB, Huissener Str. 7–947533 Kleve+49 (0)2821 7218-0info@prowerb.de
© 1979–2026 Prowerb GmbHLegal notice (German)Privacy policy (German)Terms (German)BrandDEEN

All rights reserved. Subject to change. Text and images on this website have in part been created or edited using artificial intelligence.

Agora Commerce
Overview
Topics
  • B2B shops and dealer portals
  • Employee shops
  • Catalogues and pricing
  • Procurement and approvals
  • Ordering models
FeaturesDemos
Technology & operations
  • Integrations
  • Shop operations and administration
  • Technology and access
OCI Punchout
  1. Software
  2. Agora Commerce
  3. Features
  4. OCI Punchout

Agora Commerce · PROWERB’s own B2B shop software

Planned: return the cart to the purchasing system.

Many companies start purchasing within a central procurement system. A Punchout workflow should open the appropriate shop and then return the selected items.

Discuss Punchout integrationExplore the example workflow
RheinwerkOur company catalogue

Planned procurement through OCI

The cart returns to the procurement system, where the intended order completion continues.

  1. Procurement systemAccess and company context
  2. AgoraChoose products and quantities
  3. Procurement systemReceive the cart

Project planning: agree OCI variant, fields and target system

Example view of an individually designed Agora shop. The steps explain the workflow using fixed example data.

OCI Punchout is a planned integration target for Agora. This page explains the intended workflow and its prerequisites: target system, company assignment, fields and further cart processing must be defined together.

How it works.

  1. Start in the purchasing system

    The intended entry passes the context required for product selection to the shop.

  2. Choose products in Agora

    The buyer sees the assigned catalogue and puts together the required items.

  3. Return the cart

    The planned return step transfers the agreed cart data to the target system.

  4. Continue processing there

    The purchasing system continues its intended procurement workflow. Returning a cart and placing a binding order are considered separately.

A concrete integration target for your procurement workflow.

This presentation describes the planned integration. It provides no ready OCI test login and does not present a customer system as already connected. We define the required exchange with your IT and procurement teams before implementing the connection.

What we configure for your shop.

Target system
Which purchasing system and specific OCI requirements should be supported?
Company context
How are entry, organisation and the correct catalogue mapped?
Cart data
Which product identifiers, quantities, prices and additional fields does the return need?
Acceptance
Entry, selection, return and acceptance by the target system are tested as one workflow.

Frequently asked questions.

Can I test OCI in this example?

OCI Punchout is planned. The public page explains the workflow; actual testing requires the agreed target system and an appropriate test environment.

Does returning the cart create an order?

Returning the cart transfers its intended contents. The procurement workflow defines when this becomes a binding order and which system owns it.

Fits your workflow.

IntegrationsCatalogues and contract pricesOrganisations and rolesIntegrations and webhooks

How should your shop use this feature?

We develop Agora and use it to build your individual B2B shop. Let us discuss the workflow, configuration and integrations you need.

Discuss your shop project