Skip to Content
Search
Your Cart
Loading...
Categories
Loading...
Home Search 0 Wishlist
0 STASTO Store

STASTO × YOUR PROCUREMENT SYSTEM

Select in the store.
Continue in your ERP.

Open the STASTO catalogue from your procurement system. Find the right components and return your cart to your purchasing workflow.

Discuss your integrationGo to technical setup
Your procurement systemStart the catalogue session
OCI
STASTO STOREFind. Select. Add to cart.
PneumaticsValves
Cart transfer
Back in your purchasing workflowReview and continue in the ERP

01 / PUNCHOUT

From catalogue to procurement in four steps.

  1. 01

    Start from your ERP

    Launch the STASTO catalogue from your procurement system. Your catalogue login and return address are passed to the store.

  2. 02

    Select components

    Search by article number or keyword, browse product images and narrow down variants with technical filters.

  3. 03

    Transfer the cart

    Start PunchOut in the cart. Check the transfer overview, then confirm the return to your ERP.

  4. 04

    Continue purchasing

    Review the imported items in your procurement system and continue with your internal approval and ordering process.

Transferring the cart does not itself place an order with STASTO. The next purchasing steps take place in your procurement system.

02 / SETUP

Ready for your technical team.

Catalogue entry point

POSThttps://www.stasto.eu/oci/catalog

Production endpoint. Agree a separate test environment with STASTO before your integration test.

Parameters for opening the catalogue
ParameterMeaning
HOOK_URLRequired. The return address supplied by your procurement system for the current session.
usernameThe agreed catalogue user login. Required with parameter-based authentication.
passwordThe password for this catalogue login. Required with parameter-based authentication.
Request example · POST

Illustrative request with placeholders. Send the values URL-encoded in the request body; replace all placeholders in your integration configuration.

POST /oci/catalog HTTP/1.1
Host: www.stasto.eu
Content-Type: application/x-www-form-urlencoded

HOOK_URL=https%3A%2F%2Ferp.example%2Foci%2Freturn&username=STASTO_LOGIN&password=STASTO_PASSWORD
Alternative authentication and session handling

HTTP Basic Authentication is also supported. In that case, omit username and password parameters and send the credentials in the Authorization header. HOOK_URL is still required.

GET is accepted for compatible systems. Prefer HTTPS with POST so credentials do not appear in URL history and URL logs. After login, the browser is redirected to /shop; keep the same browser session for cart transfer.

03 / DATA

Know what your ERP receives.

The return form sends item data to your HOOK_URL by browser POST. Fields are indexed from 1 for each cart line. The table shows the default mapping; agreed customer settings can override individual values.

Articles & quantities

Reference, description, quantity and agreed unit code.

Prices & delivery time

Discounted unit price, currency and delivery time in whole days.

Classification & customer data

Material group, optional customer reference and product image.

OCI field reference
Exact field names for the first cart line
FieldDefault content
NEW_ITEM-VENDORMAT[1]STASTO article number.
NEW_ITEM-DESCRIPTION[1]Product name.
NEW_ITEM-LONGTEXT_1:132[]Sales description, or product name as fallback.
NEW_ITEM-QUANTITY[1]Quantity from the cart line.
NEW_ITEM-UNIT[1]Customer-specific unit mapping, otherwise the maintained OCI unit; fallback C62. Strict checks can block an invalid mapping.
NEW_ITEM-PRICE[1]Unit price from the cart after discount.
NEW_ITEM-PRICEUNIT[1]1 (price per unit).
NEW_ITEM-CURRENCY[1]Cart currency, for example EUR.
NEW_ITEM-VENDOR[1]Name of the selling STASTO company.
NEW_ITEM-LEADTIME[1]Delivery time in whole days, rounded up.
NEW_ITEM-MATGROUP[1]Configured eClass code or category fallback. See classification notes below.
NEW_ITEM_ATTACHMENT[1]Absolute product image URL, if an image is maintained.
NEW_ITEM_ATTACHMENT_TITLE[1]Product title for the image.
NEW_ITEM-CUST_FIELD1[1] … NEW_ITEM-CUST_FIELD4[1]Empty by default; fixed customer-specific values can be configured.
NEW_ITEM-CUST_FIELD5[1]Customer article number, if maintained, or a configured fixed value.

The return form also sends ~OkCode=ADDI, ~target=_top, ~ForceTarget=yes and ~caller=CTLG. Match these control fields with your receiver during acceptance testing.

eClass, material groups and unit mapping

eClass 7.1 is the default. eClass 8.1 requires the corresponding field and maintained data. The first assigned website category supplies the classification; separators are removed from the code.

If the selected code is unavailable, the configured fallback version is checked, followed by the internal category or General. Disabling classification sends General. Agree which values your ERP accepts.

Unit codes and fixed field values are configured for the customer company. The supplier field always identifies the selling company. Product images are links; the cart transfer does not include a document package.

04 / CHECK

Test one complete purchasing journey.

Use an agreed test environment and a small sample cart before enabling the catalogue for your buyers.

  1. Open the catalogue from the ERP and verify the correct customer context and prices.
  2. Select two different articles and change at least one quantity.
  3. Check article numbers, quantity, unit, currency, price and delivery time in the transfer overview.
  4. Confirm the transfer and compare all imported items in the ERP, including classification and customer fields.

The cart has an option to clear its contents, selected by default. Clearing happens when the transfer overview is created, before the ERP confirms receipt. Take this into account when testing a retry.

05 / SUPPORT

Questions about the connection?

For a support request, include your procurement system, the time of the attempt and the error message. Share credentials only through an agreed secure channel.

Discuss your integration
HOOK_URL is missing — what does it mean?

Your ERP must supply the return address when opening /oci/catalog. Check the exact uppercase parameter name HOOK_URL and URL encoding.

The login fails. What should we check?

Verify the agreed catalogue login, password and authentication method. A successful HTTP status alone does not prove login succeeded: check that the browser reaches the shop.

There is no PunchOut button in the cart.

Start the session from your ERP through /oci/catalog and add an article. Opening the shop directly does not establish a PunchOut return address. Avoid switching browser sessions.

The cart does not arrive in the ERP.

Confirm the second transfer step in the overview. Check that the return URL accepts the form POST, and review session expiry and browser restrictions in embedded windows. If the cart was cleared, check the ERP before submitting again.

An item is rejected because of its unit or material group.

Compare the transmitted UNIT and MATGROUP with the values allowed in your ERP. Agree the customer-specific unit mapping, eClass version and fallback with STASTO.

Does this guide also cover cXML?

This guide describes the implemented OCI interface. For other protocols or system-specific requirements, contact STASTO before configuration.

First get to know the store.Open the store guideBrowse the catalogue