Fishbowl has two features that are closely tied together: the ability to export pricing rules and the ability to import that same type of data. You could use the Export feature to create a file containing your pricing rules. You could then send that file to a franchise who could Import it into their version of Fishbowl to update their pricing rules. An Import will create/update any Pricing Rules having the same name as those in the import file.
You must create a CSV file formatted in a way that Fishbowl knows what to do with the data. This is easiest to do with a spreadsheet program.
When the pricing data is Exported it will be formatted according to the table below. If you are Importing the data file must be formatted according to the table below.
All fields will be one of two types:
Column Name | Type | Description |
name | Text | The pricing rule's name. (30 character limit) |
description | Text | The pricing rule's description. |
isActive | Text | "TRUE" if the pricing rule is active. "FALSE" otherwise. |
productInclType | Text | Describes how the pricing rule affects products. Possible values are:
|
product | Text | The name of either the product or product tree node the pricing rule affects. See productInclType above. |
paApplies | Text | "TRUE" if the pricing rule applies a price adjustment. "FALSE" otherwise. |
paType | Text | One of the following
|
paPercent | Numeric | When the paType field is "Percent Price Adjustment" this field is used to adjust the price by this percent. |
paBaseAmountType | Text | Which price should the adjustment be made on. The following are valid values:
|
paAmount | Text | When the paType field is "Amount Price Adjustment" or "Set Unit Price" this field is used to adjust/set the price by/to this amount. |
rndApplies | Text | "TRUE" if the pricing rule rounds the price. "FALSE" otherwise. |
roundType | Text | How prices are rounded. Valid values are as follows:
|
rndToAmount | Numeric | The amount to round to. |
rndIsMinus | Text | Whether you subtract (TRUE) or add (FALSE) to the rounded amount. |
rndPMAmount | Text | The amount to add/subtract from the rounded amount. When zero, only rounding occurs. |
customerInclType | Text | Describes how the pricing rule affects customers. Possible values are:
|
customer | Text | The name of either the Customer or Customer Group the pricing rule affects. See customerInclType above. |
dateApplies | Text | "TRUE" if the pricing rule is applied only between certain dates. "FALSE" otherwise. |
dateBegin | Text | The beginning date the pricing rule is in effect. |
dateEnd | Text | The ending date the pricing rule is in effect. |
qtyApplies | Text | "TRUE" if the pricing rule is applied only for certain quantities. "FALSE" otherwise. |
qtyMin | Numeric | The minimum quantity that must be purchased before the pricing rule is in effect. |
qtyMax | Numeric | The maximum quantity that can be purchased for the pricing rule to be in effect. If this is zero, then there is no upper limit on quantity. |
isAutoApply | Text | "TRUE" if the pricing rule is to be applied automatically as products are added to a Sales Order. "FALSE" otherwise. |
isTier2 | Text | "TRUE" if the pricing rule is used to calculate a Tier 2 price. "FALSE" otherwise. When the pricing rule is based off of the "List Price" (see paBaseAmountType above) it can be calculated using Tier 2 type of rules. These rules are applied first to establish a list price which other rules can then be based off of. |
dateCreated | Text | The date the pricing rule was created in the system. This value exported but is not imported. |
dateLastModified | Text | The date the pricing rule was last modified in the system. This value exported but is not imported. |
The file must contain column names in the first row, using the column names in the table above.