Price and Payment Related Object Types
Amounts
Amounts contain product prices.
Field definitions:
<object_guid>: Defines the products associated with this amount.<object_type>: Defines the type of object the amount represents.<quantity>: Defines the minimum number of items that this price tier applies to. For example, if the quantity is set to 10, a shopper buying 11 items will pay the specified price for each item.<list_price>: The list price for the product.<sale_price>: The sale price for the product.<recurring_list_price>: The list price that the shopper will be required to pay in each billing interval.<recurring_sale_price>: The sale price that the shopper will be required to pay in each billing interval.<price_list_guid>: Defines the price list assignment associated with this amount
Sample XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<amounts>
<base_amount>
<guid>47B01916-7E58-631C-5C72-E1603B5BD419</guid>
<object_guid>CANON_CAMERA_WITH_COLOR_CASE_AND_BACKPACK</object_guid>
<object_type>PRODUCT</object_type>
<quantity>1.00</quantity>
<list_price>300.99</list_price>
<sale_price>289.99</sale_price>
<recurring_list_price>12.00</recurring_list_price>
<recurring_sale_price>10.00</recurring_sale_price>
<price_list_guid>SNAPITUP_USD</price_list_guid>
</base_amount>
</amounts>
Price Lists
A price list contains a set of pricing information that can be related to different products. The conditions under which price lists are applied to products are stored in the Price List Assignment. The actual price of the product is stored in Amounts.
Sample XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<price_lists>
<price_list>
<guid>SeniorPL</guid>
<description>Price List with cheaper prices for selective Telescope products</description>
<currency_code>USD</currency_code>
<name>Senior Price List</name>
<hidden>false</hidden>
<agreement_code>Monthly1YearRollover</agreement_code>
</price_list>
</price_list>
Price List Assignment
A price list assignment links Price Lists to products for specific catalogs. Price list assignments also contain the pricing conditions that can provide customer prices for targeted shoppers.
Sample XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<price_list_assignments>
<price_list_assignment>
<guid>4C640BA5-A95A-B02D-503C-23239EBB381D</guid>
<name>Senior Shopper</name>
<description>Shoppers who are seniors will receive cheaper pricing on selected Telescope products.</description>
<priority>8</priority>
<catalog_guid>SNAPITUPUS</catalog_guid>
<price_list_guid>SeniorPL</price_list_guid>
<start_date>2014-03-07T23:00:00+00:00</start_date>
<end_date>2030-12-31T23:00:00+00:00</end_date>
<selling_context>
<guid>2054C56D-250F-E515-CA69-AC097DA371D5</guid>
<name>Senior Shopper</name>
<description>PLA SellingContext for Senior Shopper</description>
<priority>1</priority>
<conditions>
<condition>
<guid>394CEAE8-F46A-2633-4208-9F38600176FD</guid>
<name>name_PLA_SHOPPER</name>
<description>desc_PLA_SHOPPER</description>
<condition_string>{ AND { AND { CUSTOMER_AGE_YEARS.greaterThanOrEqualTo (65i) } } }</condition_string>
<dictionary_guid>PLA_SHOPPER</dictionary_guid>
</condition>
</conditions>
</selling_context>
</price_list_assignment>
</price_list_assignments>
For more information about the selling_context node, see Selling Context.
Payment Providers
A payment provider is a payment functionality provider and defines the payment methods and interactions that it supports. The <properties> in the Payment_Providers.xml depend on the type of payment provider that you select for your storefront.
Sample XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<payment_providers>
<payment_provider_configuration guid="demo-payment-provider-config" status="DRAFT">
<name>Demo Config</name>
<default_display_name>Demo Config display name</default_display_name>
<localized_names>
<value language="en">Demo Config_en</value>
<value language="fr">Demo Config_fr</value>
<value language="zh">Demo Config_zh</value>
</localized_names>
<payment_provider_id>happyPathPaymentProviderPlugin</payment_provider_id>
<properties>
<property key="Config B">Value of Config B</property>
<property key="Config A">Value of Config A</property>
</properties>
</payment_provider_configuration>
</payment_providers>