Add rework pricing type (Fixed vs Per-Item) and inline rework flow on Job Details
Adds a PricingType enum to ReworkRecord (FixedPrice | PerItem), surfaces the choice in the rework modal on Job Details, and wires the resulting unit/total price display. Includes migration AddReworkPricingType, updated repository query for rework history, and help article updates. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -475,12 +475,41 @@
|
||||
actual hours vs. estimated hours for costing and productivity analysis.
|
||||
</p>
|
||||
|
||||
<h3 class="h6 fw-semibold mt-3 mb-2">Rework</h3>
|
||||
<h3 class="h6 fw-semibold mt-3 mb-2">Rework (also called Redo)</h3>
|
||||
<p>
|
||||
If finished parts fail quality inspection or need to be re-coated, create a rework record
|
||||
from the Job Details page. Rework records track the rework type, the reason (adhesion failure,
|
||||
color mismatch, damage, etc.), and the resolution. This data helps identify recurring quality
|
||||
issues over time.
|
||||
If a finished part fails quality inspection or a customer returns it damaged, open the original
|
||||
job’s Details page and use the <strong>Rework Log</strong> section to record it. Rework
|
||||
and redo mean the same thing throughout the system.
|
||||
</p>
|
||||
<p>Each entry captures the type (internal defect, customer damage, warranty), the reason (adhesion
|
||||
failure, color mismatch, runs/sags, insufficient coverage, etc.), a defect description, who
|
||||
discovered the issue, and pricing responsibility.</p>
|
||||
|
||||
<h4 class="h6 fw-semibold mt-3 mb-1">Pricing Responsibility</h4>
|
||||
<ul>
|
||||
<li><strong>Shop Fault — no charge:</strong> All copied item prices are set to $0.</li>
|
||||
<li><strong>Customer responsible — reduced rate:</strong> Prices are copied from the original job; edit them down after creation.</li>
|
||||
<li><strong>Customer responsible — full price:</strong> Prices are copied as-is.</li>
|
||||
</ul>
|
||||
|
||||
<h4 class="h6 fw-semibold mt-3 mb-1">Creating a Rework Job</h4>
|
||||
<p>
|
||||
Toggle <strong>Parts are back — create a Rework Job</strong> at the top of the log form.
|
||||
Select the items that need to be redone and choose the pricing responsibility. The system will:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Create a new job with a sub-number (e.g., <code>JOB-2605-0001-R1</code>)</li>
|
||||
<li>Copy the selected items with their coats and prep services</li>
|
||||
<li>Auto-record intake — parts are already on hand when rework is logged</li>
|
||||
<li>Set the job description to the defect type, reason, and pricing so it is visible at the top of the job</li>
|
||||
</ul>
|
||||
|
||||
<h4 class="h6 fw-semibold mt-3 mb-1">Automatic Resolution</h4>
|
||||
<p>
|
||||
When the rework job reaches a terminal status (Completed, Delivered, etc.), the linked rework
|
||||
record on the original job is automatically marked <strong>Resolved</strong> — no manual
|
||||
follow-up needed. If the rework job is <strong>Cancelled</strong>, the record is marked
|
||||
<strong>Written Off</strong> instead.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user