SAP OCI interface

for Adobe Commerce, Magento 1/2, Shopware 5/6, WooCommerce, OroCommerce, OXID eshop …

Does your customer want to integrate your online shop into their SAP system? Our straightforward solution puts your products directly into your customers' supplier catalogs and opens up new sales opportunities.

SAP OCI (Open Catalog Interface) is an interface defined by SAP through which an SAP procurement system opens a supplier's online catalog and gets back the cart filled there; the versions in use are OCI 4 and OCI 5. On the call, SAP passes login data and a return address, the HOOK_URL; the shop posts the items back to that address as form fields (NEW_ITEM-…). Our SAP OCI interface adds this to your shop as a plugin.

Delivery
Plugin, integrated directly into your shop system
Shop systems
Adobe Commerce, Magento 1/2, Shopware 5/6, WooCommerce, OroCommerce, OXID eShop
Buyer systems
SAP SRM, SAP S/4HANA and other OCI-capable systems
Protocol
SAP OCI 4 and 5 (Open Catalog Interface)

From SAP into your shop and back.

  1. Call from SAP

    The buyer picks your catalog in their SAP system and lands directly in your shop.

  2. Shopping

    The buyer sees your range with their terms and adds items to the cart.

  3. Return to SAP

    The cart is sent back to the customer's SAP system.

  4. Approval in SAP

    The lines arrive in SAP as a purchase requisition and go through approval and ordering there.

The plugin works in your shop backend: products, prices and units are handed over the way your customer's SAP system expects them.

More than the cart: being found in the procurement system.

Our SAP OCI plugins support the additional functions of OCI 4 and OCI 5 besides the cart. Two of them make your products, and you as a supplier, findable in your customer's procurement system without the buyer opening your catalog: DOWNLOADJSON and BACKGROUND_SEARCH. This carries more weight as more purchasing runs through the procurement system's search and through AI-supported procurement: what is not in its index is not found there.

  • DOWNLOADJSONOCI 5

    Catalog data for the search index

    The procurement system downloads your catalog data as JSON, page by page, and adds the items to its own search. The buyer then finds your products right in their procurement system, sees their details and adds them to the cart from there.

  • BACKGROUND_SEARCHOCI 4 and 5

    Cross-catalog search

    The buyer enters a search term once in their procurement system. The system queries your catalog in the background and lists your hits together with those of the other catalogs, even when the buyer does not open your shop on purpose.

  • DETAILOCI 4 and 5

    Show an item in the catalog again

    An item that is already in the procurement system, in a purchase requisition for example, can be opened in your catalog again from there, with the details the procurement system does not store itself, such as images and data sheets.

  • VALIDATEOCI 4 and 5

    Check price and item data

    When the buyer reuses an item from a template or an earlier cart, the procurement system asks your catalog in the background for the item's current data, with the current quantity so that scale prices are right too. No outdated price stays in the order.

  • SOURCINGOCI 4 and 5

    Find sources of supply

    The procurement system calls your catalog with a search term to find matching items for a requirement. The catalog opens straight on the hits, and the buyer picks and transfers the items as usual.

Which functions are used is up to your customer's procurement system: each one is switched on there for your catalog.

Connect it yourself, or have it connected.

punchout.dev

One script tag. Any shop system.

  • No plugins, no theme changes
  • OCI and cXML from the same tag
  • 28-day sandbox, no card
  • Optional go-live service, €490 once

orcamultimedia

A ready-made plugin, installed by our team.

  • Every additional OCI function, including DOWNLOADJSON and BACKGROUND_SEARCH
  • Order confirmation via cXML Purchase Order or IDoc ORDERS05
  • Connection to your ERP and existing catalogs
  • Extensions for Adobe Commerce, Magento 1/2, Shopware 5/6
  • Shopware Technology Partner and B2BSellers Technology Partner

Test your shop: SAP OCI Punchout Simulator

Which SAP systems use OCI?

SAP OCI is mainly used by SAP SRM and SAP S/4HANA for catalog calls. Other procurement systems support SAP OCI as well.

Which shop systems is the plugin available for?

orcamultimedia's SAP OCI plugin is available for Adobe Commerce, Magento 1/2, Shopware 5/6, WooCommerce, OroCommerce and OXID eShop. For other shop systems, get in touch.

Which OCI functions does the plugin support?

orcamultimedia's SAP OCI plugin supports the additional functions of OCI 4 and OCI 5 besides the cart: DOWNLOADJSON (catalog data as JSON for the procurement system's search index), BACKGROUND_SEARCH (background search across catalogs), DETAIL (show an item in the catalog again), VALIDATE (check price and item data) and SOURCING (catalog call with a search term). With DOWNLOADJSON and BACKGROUND_SEARCH the buyer finds your products in their procurement system without opening your catalog.

Who coordinates with my customer's SAP team?

The orcamultimedia team coordinates with your customer's SAP team up to the first productive punchout via SAP OCI.

Is there a solution without a plugin?

punchout.dev is the solution without a plugin: a single script tag turns your shop into an SAP OCI and cXML supplier, whatever the shop system.

Contact

Questions about your integration?

Get in touch and request detailed information. Or open the sandbox and try it yourself.