Skip to main content
“General” here means: independent of the content of the shopping cart, of the shipping and billing address, and of all other conditions that determine actual availability during the order process. This is exactly the difference to the order process. There, the customer only sees the payment and shipping methods that apply to their specific shopping cart. On an overview page, on the other hand, they see the entire offering of the shop, supplemented with notes about exceptions.
How to set up payment and shipping methods in the first place is described in the “Order process” chapter. This page assumes that the methods are already configured.

​
How an overview page is created

For payment methods and shipping methods, the procedure is identical and consists of three steps. Only the affected section of the shop configuration differs.
  1. In the shop configuration shop.config, define which methods appear in the overview and which notes belong to them.
  2. Create an information template that outputs the overview.
  3. Place a link to this template in the shop.

​
Step 1: Adjust the shop configuration

Via the DisplayInList-Flag parameter, you control per method whether it appears in the overview. The parameter has two values: Only the value no is evaluated. So you only need to set the parameter where you intentionally want to keep a method out of the overview, for example a payment method that is only available to a single customer group.

​
Payment methods

For payment methods, set the parameter in the <PaymentXXX-Txt> sections.
Reference: PaymentXXX-Txt section

​
Shipping methods

For shipping methods, set the same parameter in the <+Deliverer> sections.
Reference: +Deliverer section

​
Describing exceptions and special cases

Because the overview is independent of the shopping cart, it can show a method that would not actually be selectable in the specific case. So that the customer learns this in advance, you store a free description text in the optional subsection <Dependencies>. It is output next to the respective method in the overview. The following example shows the “Credit card” payment method:
Reference: PaymentCreditCard-Txt section If the text of a line starts with HTML code, prepend {WS-TplComment}{/WS-TplComment} for technical reasons. Without this prefix, HTML code at the beginning of a line is not adopted as intended.
Reference: WS-TplComment

​
Step 2: Create the information template

Create a new template for displaying the overview and save it in your template directory. WEBSALE provides a template for both overviews that you can adopt as a starting point. Dedicated tags that exist only for this purpose take care of outputting the individual methods. Materials: Template example for the global display of payment methods
  • Materials: Template example for the global display of shipping methods
  • Reference: Tags for the global display of payment and shipping methods
Place a link to your information template anywhere in the shop, usually in the footer. The WS-LoadTpl() tag generates the path.
Reference: WS-LoadTpl()