Editing Prices on Orders That Span Multiple Price List Date Ranges

If you find that the price field on a quote or order is grayed out and cannot be edited directly, this is expected behavior — not a bug. It happens when a quote or order spans across more than one price list date range (for example, a price update went into effect on May 1st, and the order was created before that date but is still open).

In this situation, the system locks the price field on the quote or order itself. Any price edits need to be made through the Scheduled Price Change tab instead.

Why Does This Happen?

When a price list update creates a new date range, BulkSource keeps track of each date range separately. If an order was placed before the new date range started, the system recognizes that the order now crosses two different pricing periods.

To keep pricing accurate across those date ranges and avoid conflicting edits, the system requires that price changes be entered through the Scheduled Price Change tab. This ensures that:

• The original price for the earlier date range is preserved as a reference point.
• Any adjustments are applied cleanly to the correct date range going forward.
• Percentage-based escalators that may compound over time are calculated correctly.

How to Edit a Price Using the Scheduled Price Change Tab

Follow these steps when you need to update a price on an order or quote that is locked:

1. Open the order or quote you need to update.
2. Navigate to the Scheduled Price Change tab (instead of trying to edit the price directly on the order).
3. Locate the material line item you need to adjust.
4. Enter the delta — this is the difference (change amount) you want to apply, not the new total price.
5. Set the effective date for the change (e.g., May 1st).
6. Save your changes.

Example: If the current price is $23.00 per ton and the correct price should be $16.50 per ton, you would enter -$6.50 as the delta — not $16.50.

Why Enter the Delta Instead of the New Price?

The system is designed to accept the change amount (the delta) rather than the new final price. This is intentional and supports how many price updates work in practice:

• Price changes are often percentage-based and compound over time (e.g., 5% increase on top of a previous 5% increase).
• Entering a delta lets the system calculate the correct running price across multiple date ranges without overwriting historical pricing data.
• It also ensures that tickets already processed under the old price are not retroactively affected.

Note: Tickets that have already been created will not be changed retroactively. When a ticket is created, the price at that time is copied and locked in. Only future tickets generated under this order will reflect the updated price.

Frequently Asked Questions

Q: Will changing the price here affect invoices that have already been processed?

No. Invoiced tickets retain the price that was in effect when they were created. Only future tickets tied to this order will pick up the updated price.

Q: I edited the ticket price manually as a workaround — will invoicing pull the wrong price?

If you updated the ticket price directly, that ticket-level price will be used when invoicing. The invoicing process should reflect what is on the ticket, not the original order price that was locked.