Skip to main content
A tradesman puts together a quote in his software, needs material from your shop for it and has so far had to type in the item data by hand. IDS eliminates this: he switches from his software to the shop, fills the basket there and sends it back to his system. If his customer accepts the quote, he triggers the order from the same software, and the order data comes back to him. The benefit lies in this two-way exchange. Product and order data are recorded exactly once, namely in your shop.
The TAIFUN and LABELWIN systems are supported directly. For other systems that support IDS, contact your WEBSALE representative.

​
The four processes

All processes begin with the tradesman software calling the shop with parameters. The action parameter determines which process is meant.

​
Automatic login

The software appends the tradesman’s access data to the shop call.

​
Basket from the shop to the software

The software calls the shop with action=WKE and a return address.
The tradesman places products in the basket in the shop and goes through the checkout up to the order overview. There, next to “Zahlungspflichtig bestellen”, is a second button that sends the basket back to the hookurl.

​
Basket from the software to the shop

With action=WKS, the software sends a basket stored in it to the shop via POST, thereby triggering an order.
The hookurl parameter must always be included. Without it, no transfer back is possible, and the order data does not reach the tradesman software.
With action=ADL, the software links directly to a product. The access data may be included.
A detailed description of the process, including examples of the XML data, can be found in the technical interface documentation.

​
Setup

​
Step 1: Activation

The function must be technically activated by WEBSALE AG.

​
Step 2: Create the section in the shop.config

The Supplier details describe you as the supplier and are passed to the tradesman software.
For LABELWIN, the non-default value is mandatory for all parameters except WriteToOrderFile and ResetStateAfterSend.
Reference: Section IDSSchnittstelle

​
Step 3: Define error messages

Two cases need a message: unknown product numbers from the tradesman software and an incomplete call.
The IDS-PRNumbers tag outputs all product numbers that the shop could not find.

​
Step 4: Output the messages

The place for this is the basket page, because that is where the tradesman notices that items are missing. Reference: Section NotifyMessages-Txt · IDS-PRNumbers · MSG-IDS_Notify

​
Step 5: Send the basket back

There are three ways to do this. They differ in how much the tradesman has to do himself. Option A: a button on the order overview. The tradesman decides for himself when to go back.
Option B: redirect after a short wait. On the order confirmation, in the header area.
Option C: automatic transmission. Also on the order confirmation, in the body of the page.
The {ST-IDSSchnittstelle} bracketing only applies if the shop was called with action=WKE, WKS or ADL. A visitor who calls the shop normally sees neither notices nor button. Therefore always test via a call with the action parameter, otherwise you will be looking for a button that is not supposed to exist in this situation.
Reference: ST-IDSSchnittstelle · WS-IDSSentBasketLink · WS-TriggerIDSSent

​
Displaying the delivery address from the tradesman software

The delivery address passed by the software can be displayed, for example on the order overview.
This address is purely informative. It is included in the additional order information. Delivery is made to the default address stored in the shop.
The following suffixes are available following the same pattern: Name1, Name2, Name3, Name4, Street, PCode, City, Country, ILN, Contact, Phone, Fax, Email Reference: IDS-Delivery
  • Guide: Using the merchandise management info data interface
  • Guide: Order overview and order confirmation
  • Guide: Displaying the basket