Contractor purchasing teams need a dependable way to review what an item cost over time, by project, store, activity, and date. BlueberryERP’s Items Price History screen provides documented filters and item selection controls that can help finance, procurement, and project teams investigate purchase-price changes before using the information in a review.
Start with the item, not the full purchase list
When no item is selected, the price-history grid displays only the top 100 records. To see the relevant history, enter an item code and select the matching result from the autocomplete field. The grid then refreshes for that item. The selection panel also displays the item barcode, item name or description, and latest order price.
According to the BlueberryERP manual, the latest order price is based on the most recent unit price from any LPO, determined by the latest document date in the price history. Treat that value as a dated purchasing reference, not as proof that every supplier or project should use the same price.
Use filters to isolate a useful comparison
After selecting an item, narrow the history before drawing conclusions. The screen supports preset date filters for Today, This Week, This Month, and This Year. A Custom filter allows the reviewer to enter a From Date and To Date and apply the range.
Additional controls include activity and sub-activity, project code, and store code. Selecting an activity enables the related sub-activity filter. Project and store autocomplete fields help focus the review on the operational context that matters to the contractor.
| Stage | Documented control | Review question |
|---|---|---|
| 1. Select | Item Code autocomplete loads the selected item’s history | Am I reviewing the correct item or variation? |
| 2. Narrow | Date, activity, sub-activity, project, and store filters | Which period and operational context should be compared? |
| 3. Interpret | Latest Order Price is derived from the latest LPO document date | What does the most recent recorded purchase show? |
| 4. Trace | The screen can show full LPO details | What source document should be reviewed next? |
Turn a price difference into a controlled question
A price-history review is most useful when it leads to a specific follow-up question. For example, a project manager may compare the same item across two project codes, while a procurement reviewer may compare a defined date range or store. A finance team can then open the relevant LPO details where available and confirm the document context before recording an internal conclusion.
Keep the review bounded by the fields available in the system. The manual documents item, date, activity, sub-activity, project, and store filters; it does not establish that a price difference is caused by supplier quality, market movement, delivery terms, or an approved variation. Those explanations require separate business evidence.
Where an ERP workflow helps
An ERP workflow can give purchasing and project teams a shared record for item selection, date filtering, and document follow-up. BlueberryERP’s documented screen controls support that focused review. Teams can begin at the BlueberryERP website to learn more about the platform, then confirm the exact workflow and responsibilities for their own implementation.
For UAE construction and MEP companies, the practical objective is simple: select the correct item, limit the comparison to a meaningful period and context, inspect the underlying LPO when needed, and document the question that remains. That creates a clearer basis for purchase review without treating one displayed price as a universal benchmark.
