...
- Creating a Customer Type Pricing Matrix
- Creating a Time Period Pricing Matrix
- Creating a Currency Type Pricing Matrix
- Creating a Derived Foreign Currency Pricing Matrix
Anchor Creating a Customer Type Pricing Matrix Creating a Customer Type Pricing Matrix
Creating a Customer Type Pricing Matrix
| Creating a Customer Type Pricing Matrix | |
| Creating a Customer Type Pricing Matrix |
To create a product pricing matrix that allows only members of an organization to receive discounted rates on a product, the product needs to have at least two Prices records. The following table represents the data for two Prices records that sell a product to a member for $50.00 and the same product to a non-member for 20% more. In this scenario, the member's price record is defined as the base type and the non-member's price record is based on 120% of the base. The non-member price is specified as the default.
...
When a change in the base price is deemed necessary but the same percentages are to remain, only a change to the Price field in the base record is required. The other records that calculate their prices based on the base price continue to use the same percentage.
| Anchor | ||||
|---|---|---|---|---|
|
A pricing matrix that varies the Start Date and End Date fields allows prices to fluctuate during specific time periods. For instance, to offer a price at a 25% discount during a specific month, create two Prices records. The first price record is for the regular price during the product's existence. The second price is for the time period during which the discount is offered. When creating a pricing matrix to control prices during specific time periods, the date fields determine which price to use when ordering the product.
...
In the above matrix, the discounted price is during the month of October. The results of this structure allow the product to be sold to members during the month of October at a 25% discount. Even though the dates overlap, the Aptify Order Entry system finds the best price from the matrix during the overlap period for the specified member type based on the order's Order Date.
| Anchor | ||||
|---|---|---|---|---|
|
To create a product pricing matrix that allows different prices to be selected based on the currency type of the order, the product needs to have at least two Prices records. The following table represents the data for two Prices records that sell a product in the US with a value of $100. The same product sold in euros is valued at €85.
...
| Note |
|---|
The matrix supports one base price per currency type. Therefore, in the scenario above, the Euro price cannot be a percentage of the US Dollar base price, and vice versa. To derive a price in one currency based its price in another currency, use the Derived From Currency field on the Prices record's Currency tab. See Creating a Derived Currency Price or Creating a Derived Foreign Currency Pricing Matrix, for details. |
Anchor Creating a Derived Foreign Currency Pricing Matrix Creating a Derived Foreign Currency Pricing Matrix
Creating a Derived Foreign Currency Pricing Matrix
| Creating a Derived Foreign Currency Pricing Matrix | |
| Creating a Derived Foreign Currency Pricing Matrix |
Another way to configure products that can be taken and paid for in a foreign currency is to derive the foreign currency price from a price in the functional currency. For instance, if your organization records transactions in US dollars, to determine the price of Widget A in Japanese Yen at the time of the purchase, the flexibility exists to derive the Japanese Yen price by converting the US Dollar price to Japanese Yen at the time the order is taken and paid using the most current currency spot rate. The following matrix demonstrates the data required to derive a Japanese Yen price or a Canadian Dollar price when only a US Dollar price is defined.
...