You may use the forms in this module to enter new products and update existing products. If you are just starting out with CompuPlants and doing an initial setup, please refer to Set Up Inventory in the New User Guide for a step-by-step guide to setting up your product catalog.
The Products section contains all the components you need for building your product catalog. Exercising logic and consistency when establishing product ID conventions will ensure that your product catalog is well organized, contains no duplicates, and can accommodate enough unique product IDs for a large, diverse inventory.
Each unique product ID is a string containing the plant code plus at least one secondary code: size, type, grade.
Usually, the breadth and depth of your inventory determines which codes to use and in which order to use them:
Nurseries with few product sizes may find that a combination of plant and size codes is sufficient.
Nurseries with several sizes may find that a combination of plant and grade codes is sufficient. In this case, "grade" would refer to the bottom and/or top size.
Nurseries with numerous sizes would benefit from using plant plus all three secondary codes. To create the greatest number of permutations, switch the order of the codes on the product catalog entry form so that "grade" comes before type. Our Technical Support team may do this for you upon request.
Tip: When entering codes, use the same number of characters by code to allow data to sort properly on grids and spreadsheets. For instance, when sorting a grid by ascending size, "3" (for 3 feet) will appear below "10" (for 10 feet). Using a consistent format ("03") allows data to sort in the right order.
Create a database of common plant traits that you can use to describe plants when building the product catalog. Associate each trait with an alpha-numeric code.
| Trait | Description and/or Code Requirements |
|---|---|
| Colors | 8 characters |
| Bloom Times | 6 characters |
| Plant Types | used for characterizing plants; examples can be trees, deciduous trees, flowering shrubs, etc. (16 characters) |
| Zones | 2 characters |
| Sun-Shade | single character |
| Spread | the plant's width at maturity; 5 characters |
| Height | the plant's height at maturity; 5 characters |
| Soil Type | 5 characters |
| Search Group | Create groups according to your sales analysis approach. The Plant Summary tab in the allocations program organizes sales data into three levels: product sales, plant sales, and search group sales. A search group could encompass all trees, for instance, or only specialty maples. After creating them, go to Product Setup > Plants and assign plants to a search group (you may save only one search group per plant). |
In this section, assign plant codes by botanical taxonomy. We recommend a 4-character code for every plant, though the application permits up to 7 characters. You may let the application automatically assign plant codes, or you may initialize a sequence number for the key "plantracklog."
After entering a code and plant name, modify plant traits as desired, along with other optional fields. See the table below for an explanation of less obvious fields.
| Field | Description |
|---|---|
| Class 1 | "Class 1" and "Class 2" fields give you added flexibility for grouping products under user-selected categories; often used for product reports. |
| Class 2 | See above; also, this field is required in order to perform a price increase by amount. |
| Host Plant | Reference for truck certificates program, which supports compliance with state regulations regarding the shipment of plant crops. If the plant is a host for a plant disease, enter one of the following values: |
| Picture | Indicates that a picture is on file and interacts with the labels program. |
| Photo Name | If you're linking a photo to this plant, enter the file name here. All plant photos should be stored in *Note: This form allows you to save only a single file per plant. If you would like to save multiple images per plant, use the Plant Pictures form. |
Plant & Product Notes
The Notes icon activates a rich-text editor where you can add detailed plant notes and photos. These notes are not stored in a searchable format, but they are saved by username and could prove very useful for logging important plant information, such as propagation history.
If you'd like to add product-specific notes, you may do so in the "Comments" column on the product catalog grid. These notes appear on the "Notes" form on the order entry detail page (see Enter a Shipping Order, Part II, Step 4).
"Size" refers to the size of the container in which the plant is grown, or the bottom size. The code may be 2 characters and contain letters, numbers, and/or special characters, such as a decimal. We recommend using a 2-character code for all size categories, using 0 as a placeholder where necessary (the code for a 1 gallon container size, for example, would be "01").
| Field | Description |
|---|---|
| Size | 2-character code. |
| Name | A description of the size (7 characters). |
| Alternate Description | A more detailed description of the size (15 characters) that replaces "Name". |
| Tag Color | Reference for pull reports and tags/labels. |
| Eqv. | Currently not used. |
| PDA | If checked, the application transmits data to your PDA device. |
| Net Contents | For weights and measures; prints on customer labels. |
Type refers to the form in which the plant is sold, such as grafted or espaliered. Like size, it may contain 2 characters with letters, numbers, and/or special characters.
| Field | Description |
|---|---|
| Type | 2-character code. |
| Name | A description of the size (7 characters). |
| Alt Name | A more detailed description of the size (15 characters) that replaces "Name. |
| For PDA | If checked, the application transmits data to your PDA device. |
Grade typically refers to the height (top size) at which you plan to sell a plant (as opposed to the height of a plant at its maturity). This code can be 4 characters and use a combination of numbers, letters, and special characters. We recommend that you use minimally a consistent 3-character code with zeros as placeholders where necessary. For example, the code for "2-3 feet" would be "023". If using a 4-character code, it would be "0023". This not only allows data to sort correctly, but also gives you the greatest possible permutations for product IDs.
| Field | Description |
|---|---|
| Grade | 4-character code, e.g. "0015" |
| Name | a detailed description (20 characters), e.g. "1.5 inches" |
| Tag Color | not used |
| For PDA | If checked, the application transmits data to your PDA device. |
With plant, size, type, and grade codes set up, you're ready to build a product catalog.
Tip: After saving a product, you may add product-specific notes to the "Comments" column on the product catalog grid. These notes appear on the "Notes" form on the order entry detail page.
| Field | Description |
|---|---|
| Shipping Unit / Weight / Freight Group | Used for calculating freight charges ; see freight setup. |
| Catalog Price | The product price, excluding or including royalties. If price excludes the royalty, check "Exclude Royalty" under Setup > Inventory > Inventory Setup Options to ensure accurate totals on invoices. |
| Future Price | Next year's price. If entered, set an end date for the current price with the admin option "oestopcatprice". |
| Date Price | Usually for promotional pricing; enter a price then apply a date range. The shipping order will automatically use this price for any orders with a "want date" in the specified range. |
| Royalty Amount | The amount to be paid to the licensing organization. |
| Discountable | Default setting that determines whether or not a product may be discounted in order entry. |
| Taxable | Default setting that determines whether or not a product may be taxed. |
| Assessable | Informational only. |
| Patent | Informational only. |
| Picture Label | Informational only. |
| Tag Cost | Enter a default price for the customer label. |
| Commissionable | Set to "1" if you want to include this product in commissions calculations (for those who have purchased the Commissions module. |
| Commission rate per plant | Enter a percentage; this rate overrides all other commission rates (for those customers who have purchased the Commissions module). |
| UPC | The program automatically assigns this number to a product using the information provided in Setup > Inventory > UPC #s. |
| Alternate UPC | If you wish to have an alternate UPC, you may provide one here. Also, with a programming tweak, we can link this UPC to your customer labels. Contact us for more information. |
| Assortment | Associate the product with an assortment; for substituting and assorting products in Inventory > Allocations. Create assortment labels in Setup > Inventory > Assortments. |
| AR Product Account | If posting plant sales to multiple GL accounts based on product, select the appropriate AR Product. Learn more in Setup > Financials > Post Sales to the General Ledger. |
| Items | If the product is an accessory—holiday decoration, vase, etc—you must associate it with the proper item from Setup > Inventory > Items. Products associated with an item appear on the Decorations tab in order entry. Like regular products, those associated with items can be broken down by size, color, type, and/or grade; they can be included in the cost of the plant or have a separate charge. |
| Product Type | Associate this product with a product type for discounting an order by product type. Set up product types in Setup > Inventory > Product Types. Also, designate a discount rate for PT Discount 1, 2, and/or 3 in the customer file. |
| Price Group | Refers to price groups created in Inventory > Products > Price Group |
| Sub Group | Type the name of a sub group associated with the Price Group Table (see Price Group); up to 15 characters |
| Plan Group | Applicable only to customers with the NRP module. |
| Retail | The retail price often prints on customer labels. It carries over to the order detail page. |
| Measure | For determining how many racks or pallets the product will occupy on a truck; from Setup > Inventory > Measures. |
Many times, customers wish to mix and match various cultivars in bulk quantities, but the volume discount setting only applies to large quantities of the same product. Fortunately, CompuPlants offers another discount tool to accommodate this need: Price Groups. Price groups may be as vast or as focused as you wish. For example, you could set up a price group for all one-gallon container plants or for just a single promotional product with a few different sizes.
You must link the price group to a Discount Type. Its code may contain up to 15 characters. Check the box labeled "Add up quantites" if you wish to lump all cultivars together when determining the volume bracket. Leave unchecked if you want to separate cultivars into their own brackets.
After establishing a price group, go to the Price Group Table in Inventory > Entry Forms > Products. Delineate volume brackets ("Break Quantity") and prices for each level ("Break Price"). If you wish, you may identify a subgroup for special products within the price group, and assign a separate pricing program for it (see an example of a price group table below). Lastly, designate a price group for each applicable product in the product catalog.
Before entering an order, enable the Price by Group icon in the toolbar by setting the "oepricebygroup" admin option to "1". On the order header form, select the discount type associated with the Price Group. After adding products to the order, click the Group icon in the toolbar. Those products associated with the discount type will display an adjusted price.
Notes:
* The product must be marked as "discountable" in order for the price group discount to apply.
* The "Want Date" on the order must be equal to or greater than the "Effective" date on the price group table.
* The subgroup always overrides the price group, even if the effective date on the subgroup is older than that of the price group.

The Plant Pictures form allows you to link an unlimited number of images to the same plant, making it possible to vary images by size, color, customer, and so on. FastReport supports file types .jpg, .gif, and .bmp for printing labels. Additional file types may be supported by NiceLabel. Vector graphics are NOT supported. Images should be stored in the following directory:
u/compuplants/graphics/plants
At any given time, only one image may print on a tag/label. If you have multiple images linked to a single plant, the program looks at the image file name to determine which image to print. The file name must exactly match the plant number. For instance, plant number 1000, abelia grandiflora, has three images linked to it: 1000.jpg, 1000a.jpg, and 1000b.jpg. The program will print the first image, 1000.jpg, because it matches the plant number. When you want to change the printed picture, you would first need to rename the appropriate file.
This section of the menu pertains primarily to your location setup, but includes some related concepts such as transaction types, reason codes, production types and methods. CompuPlants offers several descriptors to distinguish levels of locations: division, section, area, location segment, and inventory category. The first two, division and section, combine to form a specific location ID and are required set up components. The rest, however, are optional. They factor into a product's unique track ID when entering your beginning inventory.
| Menu Item | Description |
|---|---|
| Transaction Types | These are pre-defined transactions for recording inventory changes by plant and by location. |
| Divisions (Required) | A division is equivalent to a farm or ranch. It represents a large, usually separate, geographical location with its own manager. If your nursery operates on a single farm or ranch, you would have a single division. Assign a one- or two-character code. |
| Sections (Required) | Divisions can be broken down into sections. The section code can contain up to six characters. CompuPlants combines this with the division code to form a unique location ID. "Land Type" and "Square Feet" apply only to those customers with the NRP module. Though not required, you may associate the location with a larger area, which then allows you to run the Mass Pull by Order and Mass Pull by Product reports. The "active" flag is informational only; CompuPlants does not support inactive locations at this time. |
| Location Segments (Optional) | Use location segments to break down locations into lots (or another term that your nursery uses). |
| Reason Codes | Supply reasons for transaction types. You may save multiple reason codes per transaction type. This form can also be found in Setup > Inventory > Reason Codes. |
| Areas (Optional) | An area is a way to group locations that typically grow the same kind of plant. Though not required, it does factor into two popular pull reports: Orders > Documents > Mass Pull by Order and Trucks > Mass Pull Reports > Mass Pull by Product. Enter a one- or two-character code. Note: CompuPlants has an internal area code, "p", that's used in order entry for offsetting purchase orders. |
| Inventory Categories (Optional) | This user-defined attribute serves as another way to qualify a location, such as how close the plants are to one another ("can tight" v. "spaced"). |
| Production Types | Applicable only to field inventory/NRP module: Identify all sizes/forms applicable to your nursery's production: 3" pot, 8-pack, 128-cell, etc. "Unit type" may be bedfeet, trays, or plants. |
| Production Methods | Applicable only to field inventory/NRP module: Refers to the method used to propagate the plant: seed, graft, bud, etc. |
With CompuPlants' Allocations program, you can quickly assess product availability and edit several orders at once, minimizing the time you spend processing orders. It includes not one, but two allocation tools with slightly different designs, providing our users with the flexibility they need.
| Products | Assortments |
|---|---|
|
|
The Products form offers detailed information to support product analysis and allocation. The interface is divided into three main sections: the product grid (top), availability panels (middle), and product information tabs (bottom). The following topics are designed to familiarize you with each component of the Products form so that you can comfortably and confidently analyze product data before allocating quantities.
Product Grid: Two Views
Availability Panels
Tabs: Product Information and Analysis
See also related Admin Options and User Options.
The product grid offers two views: Plant and Search Group. With plant view, query a plant number and the product grid below shows all products associated with the plant. Or, toggle "Group" to see all products associated with the search group.
Plant View:

Search Group View:

As you highlight rows on the product grid, the panels below respond with current availability data. The Inventory panel sums up quantities for each transaction type, while the For Sale panel shows all current order activity for the selected product. The right-most column tallies open purchase order quantities along with any open shipping/master order quantities set against those purchase orders. The "Received" field denotes how many items have been marked as received on purchase receipts. As receipts are posted to inventory, this quantity transfers to the Inventory panel's "Received" field.
FAQ: How does CompuPlants calculate availability?
CompuPlants maintains accurate, up-to-date availability data by first calculating the on hand quantity, then the salable quantity (for sale), and finally availability (left), as the following equations illustrate:
On hand quantity:
on hand quantity = beginning inventory +/- transactionsSalable quantity:
salable quantity = on hand quantity - unsalable - reserve
Availability:
availability = salable quantity - open order quantities (SO and SM) - master order quantities
Confirmed quantity - shipped quantity - open order quantity - canceled quantity = master order quantitySome notes on shipping and master orders as they relate to availability:
| Tab | Description |
|---|---|
| Inventory Tab | Draws data from the Inventory Edit table, summing up the number of products available by location. |
| Purchase Orders Tab | Lists any purchase orders associated with the selected product, including "Received" and "Left" quantities for partially shipped orders. |
| Orders Tab |
Content Customization Totals Grid |
| Preliminary Orders Tab | Shows any preliminary orders with this item (remember: preliminary orders do not count against availability). |
| History Tab |
The "Current Year" and "Last Year" panels allow you to quickly compare this year's sales to last year's sales (based on calendar year only). Open order quantities are based on the Want Date while closed order quantities are based on the Shipped Date. The "Aged" panel uses the "Plant Date" from the Inventory Edit table and today's date to determine the age of each product you have on hand. Where no plant date has been provided, the program sums up these quantities in the oldest bracket, (144 weeks). Where the plant date matches today's date or falls on a future date, the program sums up these quantities in the youngest bracket (0-12 weeks). |
| History Grid Tab | This grid compares the current YTD sales to last year's YTD sales (based on calendar year only), and highlights the current month in either green or red. Green indicates that you've sold more of the product in the current YTD than you sold during last year's equivalent YTD period. Red indicates that last year's YTD sales are greater than the current year's sales. |
| Plant Pictures Tab | View all pictures you have linked to this plant. Note that this data comes from the Plant Pictures form, not the plant setup form in the Inventory module (Entry Forms > Products > Plants). |
| Estimates Tab | Sources data from Field Inventory > Estimates form (Sales tab). |
| Final Grades Tab | Sources data from Field Inventory > Grade by Field ID/Estimate ID. |
| View All Orders Tab | This grid shows all shipping orders (SO/SM) and preliminary orders for this product and has no date restrictions. It includes orders where substitutions were made (confirmed product does not match the product selected on the product grid). |
| Plant Summary Tab |
Compare the selected product's sales to sales data for all sizes associated with the plant number and for all products associated with the search group (if one exists). In the Current Plant area, the "Product" field shows an orange background if the product is oversold. In the "Orders" column, a red background in the current field indicates that unnecessary substitutions have been made; there is sufficient supply to meet all customers' demands. A blue background indicates that there is not enough of the product to fill all orders, but there is enough of the plant number and substitutions can be made. The graphs provide additional sales and availability data:
|
Examine the information under the product tabs, particularly the Orders tab, and assess demand for a product. Where a product is oversold, decide how you will make substitutions and/or modify quantities. All changes are made from the Orders tab. You may edit quantities in the "Cur Qty" column but, more than likely, you'll need to make substitutions as well. This procedure varies according to which source you want to use—the product catalog or an assortment, and whether you wish to make a full or partial substitution.
Repricing works from the Edit Order detail page or the Reprice button.
This tool allows users to quickly distribute a product's want quantity across several orders at once. The product must belong to an assortment group, which usually consists of similar plants that vary in color and size.
1. Product Catalog
Sort the assortment group in ascending order. The first product in the group always serves as the lead assortment product. Adding a different product from the assortment will result in an error when using the Assortments grid.

2. Assortment Grid:
The top row always contains the lead assortment product, and quantities must be allocated from this row.

An assortment batch makes the orders available to you in the Assortments program. Complete this process after entering several orders, but before executing a pick list. If avsource is set to "master", you must create a separate assortment batch for each master order. If the option is set to "prdtl2", you may create a single batch for all orders with the same allocation method (percentage v. template). If multiple assortments are included in a batch, then you can toggle between them in the Assortments tool. You cannot compile a batch of orders distributed by both percentage and template.

CompuPlants allows you to easily update your records after a loss, adjustment, shift, or other transaction type. You can record changes by plant or by location.
See the table below for a brief description of each transaction type.
| Transaction Type | Description |
|---|---|
| Loss | always a reduction to inventory, must enter a reason code |
| Adjustment | can be an addition or reduction (entered as negative number); must enter a reason code |
| Move | a transfer of some of a plant product from one location to another (*note that a move automatically updates both the "to" and "from" locations) |
| Move All | a transfer of a plant's total quantity from one location to another (again, the system automatically updates both the "from" and "to" locations) |
| Shift | a change in the grade (or size) designation of a plant |
| New Inventory | propagated or acquired inventory(not through a purchase order) |
| Release to Sales | a transfer of growing inventory to salable inventory |
Complete this procedure during the setup stage or any time you're adding new products.
*Alternatively, you may import your beginning inventory.
While most values are self-explanatory, some may be ambiguous. Those values are clarified below.
Before uploading a spreadsheet, make sure it is formatted in the same manner as the model header row displayed on the import page, or the import will fail.
Note: If a transaction contains errors, you cannot delete it after posting. Instead, execute another transaction to rectify the issue.
Use this feature for recording additions and reductions by location (you may also find the Location Count Sheet to be a helpful tool at this time). The steps are the same as those for recording changes by plant, with one exception:
Alternatively, any time you count inventory, you can import those changes under Imports > Import Recount Inventory form. When a quantity is updated via an import, the application records an inventory adjustment. Use the Inventory Edit Quick-Change grid to expedite this process:
This grid stores all of your most current salable inventory information. Located under Inventory > ICT, you may use it for:
More information to come.
Users typically import field inventory, but have the option to enter products manually, as the instructions below explain. CompuPlants will automatically assign a field ID but, if you prefer, you may start a sequence number that the program will adopt.
Note: If you modify quantity on a field inventory entry form, you must enter a reason code. After clicking "Save," a dialog window will appear with a drop down list of reason codes to select from.
The Unit Type is used to calculate a product's total quantity. Plants is set as the default unit, but you may set bedfeet or trays as the default unit with the "estdefaultunittype" admin option.
| Unit Type | Plants | Ex. | Bedfeet | Ex. | Trays | Ex. |
|---|---|---|---|---|---|---|
| units | N/A | N/A | length of bed | 600 feet | # trays | 80 |
| base | N/A | N/A | length of sample size | 20 feet | # trays per unit | 5 |
| qty/base | N/A | N/A | # plants per base | 400 | # plants per unit | 100 |
| quantity | # of plants | 120 | qty/base x # bases | 400 x 30 = 12,000 | qty/base x # bases | 100 x 16 = 1600 |
Use the model row provided under Imports > Import Field Inventory to correctly align your columns. Make sure that you:
Then, follow the remaining instructions for importing inventory spreadsheets.
Use this feature to project future availability based on current inventory. You may associate a single Field ID (or row) or multiple Field IDs with each estimate. Additionally, to accommodate multiple estimating periods, you may enter up to three separate estimates for the same group of Field IDs. The process varies slightly by unit type.
During the harvesting season, you may need to modify an estimate, especially if you perform a series of estimates for a row or group of rows. CompuPlants accommodates subsequent estimates by offering additional estimate columns on the Estimate grid. Enter as many as three estimates for a single Estimate ID (see instructions below). Or, for less involved estimating practices, simply update the amounts or percentages for the original estimate, then click the Sales tab to post the information to inventory.
To enter subsequent estimates:
In this feature, record actual quantities harvested by size. When you do, the Sales tab in the Estimate entry form reflects this data, providing you with an accurate view of your available inventory. You may enter graded inventory in phases. When you're finished, be sure to check "Final Graded Inventory" on the Estimate entry form.
There are two options for recording your final graded inventory. Grade by Field ID suits those growers estimating one row at a time, while Grade by Estimate ID suits those growers estimating many rows at once.
Note: Under Entry Forms > Field Inventory, you will find a separate destination for posting graded inventory: Estimated & Graded to Sales. This tool was used at one time, but since posting has been integrated in the Estimates procedure, this option is no longer utilized.
Access this feature under Entry Forms > Field Inventory > Grade by Estimate ID. After doing so, this process mirrors that for entering grades by Field ID, but requires a separate entry for each size associated with the EstimateID.
For instance, if one Estimate ID includes 20 Field IDs for tilia cordata, and size ranges consist of both 2-3' and 4-5", you'll need to enter a final grade for those plants sized at 2-3 feet, and another final grade for those plants measured at 4-5 feet. Be sure to correctly enter quantities for each size.
Most grids provide all the information you may be searching for, with the added advantage of being able to sort data and manipulate columns according to your needs. Nevertheless, you may prefer to run a report in some cases. This section familiarizes you with several reports and points you to a grid that may be used instead of a report where applicable.
These reports display a single quantity for each product over the specified date range. The end date does not need to coincide with the end date in Setup > Inventory > Inventory Setup Options.
The product catalog grid offers all of the information you can find in these reports; nevertheless, the reports are available to you should you prefer them to the grid in some cases.
Alternative grids: Inquire Location/Product Grid and Inquire by Transactions Grid.
These reports display plant size, type, and grade information horizontally rather than vertically, and may be more commonly used among bare root growers.
Review every transaction over a specified date range. Narrow the results by plant number, product number, or tracking ID. "Transaction Type," in the left-most column, is an internal code that is stored each time the user records a standard inventory transaction (loss, shift, adjustment, etc.), edits a pick list (PK), or posts an order to receivables (SA). Note that this grid does not provide transactions recorded on the field inventory table; use the Field Changes report to obtain this information.
This procedure typically occurs once a season, either at the beginning or end. Steps should be completed in sequential order, with the first 5 steps leading you through necessary preparation. All steps take place within the Inventory module unless otherwise noted.
Note: The following process includes more steps than those numbered 1-6 under Physical Inventory Procedures; as a result, those steps are assigned different numbers below. Please do not let this confuse you.
All procedures take place in Inventory > Physical Inventory unless otherwise noted.
| Step-by-Step Procedures |
|---|
| 1. Back up your current inventory data under Reset and Save the Beginning Count. |
| 2. Identify locations for counting. |
| 3. Run a report of the "before" counts for comparison. |
| 4. Create a Physical Count File (used for updating physical count). |
| 5. Print a Location Count Sheet and send to the field for counting (in Inventory > Documents). |
| 6. Update Physical Count with totals from the field. |
| 7. Print Estimate Sheet and return to field for sell date estimates (in Inventory > Documents). |
| 8. Update Physical Count once again to include sell date estimates. |
| 9. Print physical inventory reports to compare field totals against database totals. |
| 10. If necessary, adjust physical count once more. |
| 11. Move New Count to Sales Inventory to make live. |
| 12. Clear Zero Counts to delete locations for any product where quantity is zero. |
| 13. (Optional) Update product prices in Inventory > Products > Price & Product Quick-Change grid. |
| Document Type | Description |
|---|---|
| Location Count Sheet | This document prints the selected location at the top and a grid for writing plant names, plant date, length and width of rows, plus/minus inclusions, and first extension. Before previewing and printing, highlight a row, or press Control-A to highlight all rows. |
| Estimate Sheet | This document prints a count for each product in the selected location, followed by multiple columns for splitting quantities by projected sell dates. |
| Variety/Date/Count | This document supports a physical count for a single product with multiple locations. |
Before updating your physical inventory, execute this command to back up your current inventory data. Select the appropriate year, check the box labeled "Run Process," then select "Execute." Should you make a mistake while updating inventory, contact us and we will restore your previous year's inventory.
For an added safety measure, you could also export the Inventory Edit grid, which stores all of your most current inventory data, into an Excel file. Right-click on the grid to access the grid popup menu.
Use this grid to mark each product/location you want to include in the next count (in the column labeled "Count"). The system uses the selections you make here to create files, forms, and reports for the subsequent Physical Inventory procedures.
We recommend you count all locations at the same time, as products could be moved from one location to another and inadvertently be excluded from the count or counted twice.
To mark multiple rows at once:
This step creates a report of the "before counts" for each of your count selections.
This step generates and stores a table that the system uses for recording changes in Step 4 Physical Count.
After the count sheets and estimate sheets are returned, enter those updates here. Select a location at the top of the screen, or click "Find" to display all count selections.
We recommend updating counts first, then returning at a later time to update estimates (the document used for estimates displays current product totals by location to ensure that you have the most accurate data for your estimate).
To update counts, simply change relevant fields in the "Counts" section.
To update product grade and sell-by dates, modify fields in the Product Information and Schedule Information sections.
*If you have estimated multiple grades or sell dates for a product in a single location:
After updating your physical inventory and running related reports to verify the new counts, use this command to activate the updated inventory data. Check the box labeled "Post Process" and post one location at a time.
For any product/location where the count is negligible, this command clears those records and removes them from the system. This command does not affect other products in the same location or other locations with the same product.
The following reports allow you to compare your new physical inventory count with existing database records. Run these reports before posting the updated numbers so that you can check for any major disparities and conduct another count if necessary.
| Report Name | Description |
|---|---|
| Physical by Product | This report lists all locations associated with a selected product, along with before count, new count, and variances for each location. |
| Physical by Location | This report lists all products associated with a selected location, along with before count, new count, and variances for each product. |
| Physical by Size with Detail | This report offers an option for cross-tab formatting, which is helpful for organizing product data by size, type, and/or grade. |
CompuPlants offers several methods for updating the prices for multiple products at once.
FAQ: How does the application determine the correct product price?
This grid can be found under the Products section. Apply price changes directly to the grid and save. Or, export the grid to Excel and save to your computer. Apply changes and save, then re-import under Imports > Product Catalog.
This command sets your ending inventory for the previous year to the beginning inventory for the upcoming year, and clears all transactions for a fresh start (you may retrieve them in the future if necessary). Enter the year (four digits) that the records should be saved under.
Warning: This command erases all current inventory data (Inventory Edit grid) and should not be used.
Run this command when you are transitioning to a new year and wish to make the previous year's ending inventory the upcoming year's beginning quantity.
If you prefer to clear all previous year's inventory data, run this command.
Clears all final grade estimates (by field ID and estimate ID) for the upcoming year.