The data template defines the data structure Vendavo Profit Advisor uses for opportunity analysis. It includes dimensions and dimension hierarchies as well as the waterfall elements and other numeric measures. Dimensions and dimension hierarchies describe a transaction, and the waterfall elements provide the quantifiable pricing-related information of a transaction.
Vendavo Profit Advisor provides the data template that you customize to fit the data model in your business. You customize the template on the Edit Template page. You download your customized template, fill in transaction data according to the template, and upload the data file to Vendavo Profit Advisor for profit opportunity analysis.
Making Changes to Data Template
The Edit Template page has the following sections:
- WATERFALL - The PRICE WATERFALL chart is at the top in the main section and is used for visual reference of a waterfall element in relation to the entire waterfall.
- FIELD - A list of the template fields below the waterfall chart is where you select the fields you want to use in Vendavo Profit Advisor analysis.
- LABEL - Next to the FIELD column, specify the label for each field you want to include in the data template.
- LEARNING CENTER - Reference information on the right-hand side of the page contains videos, whitepapers, and other information for you to better understand the Vendavo Profit Advisor data structure.
You customize the data template by selecting the fields and specifying the field labels.
- To add a field to your template, select the check box next to the field name.
- To omit a field from your template, clear the check box next to the field name. You can't clear the check box if a field is a required field.
- Specify a field label in the LABEL text box. When you click TAB out of a label field, your input is validated against the rules listed below. When a rule is violated, an error message appears directly under the label field.
Tooltips are available on waterfall fields. When you click on a waterfall element field or click on a waterfall element in the chart, the element is highlighted, and a tooltip about the element displays.
If you refresh the Edit Template page in the middle of field edits or when you navigate away from the page before saving, your unsaved changes will be lost.
Template Rules and Recommendations
Conform to the following rules and recommendations when editing your transaction data template.
Template Field Labels
Field labels are used throughout the application to denote specific values, such as on the Opportunity List and Opportunity Detail pages. You should give a careful consideration when labeling each template field to ensure a common understanding about the field among all users of the application.
Vendavo Profit Advisor uses each template field data for specific analyses. You can re-label fields to match the naming convention used in your business, but you should not repurpose a particular field, a dimension field or a waterfall element, to store different type of transaction data. It may result in misleading analyses. For example, you should not rename the Rebates field and use it for Volume Discount.
The following rules apply to field labels:
- A label must be unique among the selected fields in your template.
- A label can only contain alpha numeric characters and the space character.
- A label can't contain more than 50 characters.
- A label can't be empty.
Hierarchies
Vendavo Profit Advisor uses the organizational information given in the hierarchies when analyzing data for profit opportunities.
- In the hierarchy lists in the FIELD column, the general to specific levels are shown from top to bottom in each hierarchy. For example, in Customer Hierarchy, Global Customer is the most general level at the top, and Ship-to Customer is the most specific level at the bottom.
- All hierarchies should maintain a one-parent-to-many-children relationship when traversing down the hierarchy.
- Geography Hierarchy represents the geographic location of the transaction. It is NOT meant to represent the sales hierarchy.
- Three hierarchies are provided out of the box. You can't add more levels to a hierarchy, and you can't define new hierarchies.
- You don't need to use every level of a hierarchy. For example, you can choose to specify only two out of five Geography levels, and those two can be Region Level 3 and Region Level 5.
Dimensions
A minimum of nine dimensions fields are required in your template. Dimension fields are shown in the Transaction Identification, Product Hierarchy, Customer Hierarchy, and Geography Hierarchy sections on the Edit Template page.
Waterfall
A minimum of three waterfall adjustment fields are required in your template. Waterfall adjustments fields are shown in the Waterfall Element section between bold-faced pricepoints.
Field Descriptions
Waterfall Elements
The price waterfall consists of pricepoints and adjustments, which describe revenues, discounts, costs, and profits.
Field |
Description |
|---|---|
Market Price |
Starting price in the waterfall. This is typically a Region or Channel specific price, such as Country Price or Distributor Price. This can also be Base Price or List Price. |
Negotiated Discount |
Discount agreed upon with the customer. This discount is subtracted from Market Price. |
| Customer Negotiated Price Adjustments | Miscellaneous adjustments to Customer Negotiated Price. An example is a price protection/price cap cost. If you provide both Market Price and Customer Negotiated Price, system will calculate this placeholder adjustment. |
Customer Negotiated Price |
The negotiated price that the customer will pay. |
Freight Charges |
Fees charged for freight and logistics, for example, packing, unloading, and transportation. |
Surcharges |
Miscellaneous fees charged to cover costs of goods sold, for example, fuel surcharge, small order surcharge, hazard material processing surcharge. |
Service Charges |
Fees charged for services, for example, engineering and installation. |
Invoice Price Adjustments |
Miscellaneous adjustments to Invoice Price. If you provide both Customer Negotiated Price and Invoice Price, system will calculate this placeholder adjustment. |
Invoice Price |
Total price paid by the customer or total revenue for the company. |
Rebates |
Total rebates offered to the customer. |
Net Price Adjustments |
Miscellaneous adjustments to Net Price. If you provide both Invoice Price and Net Price, system will calculate this placeholder adjustment. |
Net Price |
Final price that remains after deducting all discounts, charges, and rebates. If you don't provide a value, the value is calculated. |
Payment Cost |
Cost of carrying extended payment terms. |
Freight Cost |
Cost of logistics to deliver the product. |
Service Cost |
Cost of the services provided. |
Pocket Price Adjustments |
Miscellaneous adjustments to Pocket Price. If you provide both Net Price and Pocket Price, system will calculate this placeholder adjustment. |
Pocket Price |
Net Price minus all costs-to-serve. If you don't provide a value, the value is calculated. |
Cost of Goods Sold |
Fixed and variable costs of goods sold, for example, a cost for creating a new mold or a package. |
| Pocket Margin Adjustments | Miscellaneous adjustments to Pocket Margin. If you provide both Pocket Price and Pocket Margin, system will calculate this placeholder adjustment. |
Pocket Margin |
Margin after all revenue and costs associated with the transaction have been accounted for. |
Transaction Information
The following attributes describe a transaction. Vendavo Profit Advisor uses these attributes to analyze and categorize transactions when looking for profit opportunities.
Field |
Description |
|---|---|
Transaction ID |
Unique ID for the transaction. Typically, it is a combination of Invoice ID and Line Item ID. |
Transaction Date |
Date of the transaction, typically the Invoice Date. Could be the Order Date or the Shipment Date if the Invoice Date is not available. |
| Transaction Type | Type of the transaction, for example, Standard Order, Credit, Return, Consignment. The transaction type may be similar or different from the order type. |
| Sales Representative | Person assigned as the representative for the account at the time of the sale and who has full access to all transactions for the account. |
| Channel | Route to market, for example, Direct, Indirect, Distributor, or Wholesale. |
| Freight Method | Transportation method for delivery, for example, Land or Sea. |
| Manufacturing Plant | Manufacturing plant for the product. |
| Payment Terms | Terms of Payment, for example, 1% 10 Net 30. |
| Order Currency | Transaction currency specified using ISO code. |
| Unit of Measure | Standard unit of measure, for example, Each, Piece, or LB. |
| Order Quantity | Quantity of product or service order, specified in Unit of Measure. |
Product Hierarchy
The Product Hierarchy represents products and their relationship. Both products and services may be represented in this hierarchy.
Field |
Description |
|---|---|
Product Level 1 |
Highest level in the Product Hierarchy, for example, Business Unit or Operating Unit. |
Product Level 2 |
Second level in the Product Hierarchy, for example, Product Line. |
Product Level 3 |
Third level in the Product Hierarchy, for example, Product Family or Product Grade. |
Product |
Lowest level in the Product Hierarchy, most likely the product sold. This is also typically known as Item or Material. |
Customer Hierarchy
The Customer Hierarchy represents customers and their relationship. Customers could be of the type specified in the Channel field, such as Direct or Distributors.
Field |
Description |
|---|---|
Global Customer |
Highest level in the Customer Hierarchy. Global customers are generally part of a specific sales program that may also be called National or Enterprise accounts. |
Sold To Customer |
Name of the customer and may correspond to a specific division or location where price and terms are negotiated. Bill-to customer may also populate this level in the hierarchy. |
Ship To Customer |
Customer to whom the product is shipped. Typically, the Ship-to Customer name has the Sold-to Customer name appended with a location. |
Geography Hierarchy
The Geography Hierarchy represents the customer geography.
Field |
Description |
|---|---|
Region Level 1 |
Highest level in the Geography Hierarchy, such as, Region. May also be known as Pole. Example values are Americas, Europe, Asia. |
Region Level 2 |
Second level in the Geography Hierarchy, such as, Sub-Region. Examples values are Eastern Europe, Western Europe. |
Region Level 3 |
Third level in the Geography Hierarchy, such as, Country. |
Region Level 4 |
Fourth level in the Geography Hierarchy, such as, Zone. Example values are New England, Mid-Atlantic, Southeast. |
Region Level 5 |
Fifth level in the Geography Hierarchy, such as, State or Province. In most cases, refrain from loading City or Zip Code into this field as these will have a large amount of overlap to the Ship-to Customer. |