The Adjustment field on each order, memo, or repair line lets you subtract a fixed dollar amount from that line’s price. The customer’s UnitPrice on the invoice stays at the original number; the adjustment is recorded separately and reduces the line subtotal.
When to use Adjustment vs changing the price
- Adjustment — use when you negotiated a markdown but want the original price visible on the invoice (“$1,200 list, $200 off, $1,000 net”). The customer sees what the item would have sold for and what they saved.
- Change the UnitPrice — use when there is no “list price” being marked down, just a different sale price. Requires the Override Price at POS permission.
If you’re inflating a price to fund a trade-in over-credit, that’s neither — see the Trade-In Negotiation article. Adjustment is for ordinary discounts.
How to enter it
- Add or edit a line item.
- Type the discount amount (positive number) into the Adjustment field next to UnitPrice.
- Save. The line’s effective price becomes
qty × UnitPrice − Adjustment.
The Adjustment field only appears for users who have the View Order Discounts permission (ShowOrderItemDiscount), set per user at Settings → Team → [user] → Access & Permissions (or via their permission group). This is per-user authorization — one salesperson can apply adjustments while another can’t. If you don’t see the field, an admin needs to grant you that permission. It’s also enforced on save: a user without it can’t add or change an adjustment, and editing a line never wipes one someone else already applied.
What gets affected by the discount
Adjustment flows through to every realized-revenue calculation:
- Sales tax — computed on the adjusted (post-discount) subtotal, not the gross
- Gross profit — uses the adjusted revenue, so margins reflect what was actually realized
- Partnership splits — partners receive their share of the discounted revenue, not the list price
- Reports — Sales Register, Daily Sales Summary, Sales Tax Liability, etc. all show post-discount totals
- Payments / balance — the customer owes the discounted total
A “Pricing Realization” report exists if you want to see the gap between list and realized revenue across a date range.
Work order lines
A work order’s line on an invoice takes its price, quantity and description from the work order, so those can’t be changed on the invoice. The Adjustment can. Click the line: the drawer shows the work order’s figures read-only, a link to open the work order, and the Adjustment field.
- The adjustment stays put when the work order’s price changes later.
- The work order’s money summary shows it as Adjustment (on invoice), and its printed ticket, envelope and pickup email subtract it, so nothing shows the customer more than the invoice charges.
- Repair Profitability counts the job’s revenue after the adjustment, the same way Gross Profit does.
Without the View Order Discounts permission, or once the invoice is finalized, clicking the line opens the work order as before.
A legal note worth knowing
The label is Adjustment, not “Cash Discount,” on purpose. In a number of US jurisdictions, surcharging-style “Cash Discount Programs” — where the same item is shown at one price for cash and a higher price for card — have specific disclosure requirements and have generated litigation. Calling per-line markdowns “Adjustment” keeps the language neutral. The internal column name is CashDiscount for legacy reasons, but no UI surface uses that label.
If you want a real Cash Discount Program (price varies by tender), check with a tax attorney first — JewelTrak doesn’t currently model that as a separate concept, and using Adjustment to fake it could create disclosure problems.
Tips
- Adjustment is per-line. Multi-line discounts mean entering the per-line amount on each line.
- Negative adjustments aren’t allowed — to add to a line’s price, change UnitPrice instead, or use a separate misc line item.
- If you remove a discount, set Adjustment back to 0 (not blank).
- Adjustment shows on the invoice the customer receives; if you don’t want it visible, change UnitPrice instead.