---
title: "Area Pricing"
canonical: "https://kb.myframeworks.com.au/space/PROSTIXV48DOC/31102013/Area%20Pricing"
format: markdown
---
Therefore, whatever is entered within an area is applied to the relevant product branch records within that area (That is, for all branches defined for that area).  To maintain Area Prices for a product, perform the following: 1. Assign each branch to an area in  Branch Maintenance . 2. Setup branch security for your users if you want cost visibility to be restricted. In ' Stock Enquiry ', the user can only see costs for the area(s) where they have access to branches in User Security. 3. To simplify the maintenance of product data across all branches of a regional area, programs have been written to maintain area costs, sell preferred supplier, and so on. 4. The same business rules that govern applying the supplier cost to the standard and branch costs have been used when applying area pricing where the effective date is today. Note : when a GP% or loading is applied, the wastage is applied before adding any other percentage loading in order to calculate the sell price. 5. The  Effective Date  is to be used for future pricing when rolling the product area data through to the appropriate branch product records for that area. The only fields supported are the  Existing Future Pricing  fields of  Nett Supplier Cost ,  Cost Loading  (although the type of loading cannot be changed),  GP  and  Sell . The new data is loaded into the existing future pricing fields. 6. For a mass update, the only pre-populated field is the  Effective Date  which defaults to today. The business logic performs slightly differently. It updates all product area records (and then the branch product records) for the mass update selection range and only updates those values that have been entered (That is, not those left with a  '?' ). The mass update has an option of whether to create the branch product records or not. The default for this field is based on the value of the System Tailoring Flag  'InvCrBrDef'  however may be overridden if required. When the branch product records are created the  Branch Product Type  is based on the  Product Group stock control option  for the branch.