What you can do
- Create walk-in and scheduled repair intakes.
- Record the customer, device, IMEI, damage, issue, approval, technician, parts, and services.
- Move a repair through processing, waiting for parts, QA, ready, and completion states.
- Collect payment and print the repair invoice or ticket from reachable repair entry points.
- Document condition with Device Damage Sketch and capture a signed Repair Agreement by QR code or email link.


Find the exact task
How do I create a repair intake?
Open Repairs → Create, select or add the customer and device, capture the issue and condition, then save the intake.
- Open Repairs and choose Create Repair.
- Select or create the customer and device.
- Record the issue, condition, approval context, and save.
How do I create a walk-in repair?
Start a new repair from the Repairs area, choose the walk-in intake flow, and capture the customer, device, issue, and condition at the counter.
- Open Create Repair.
- Choose the walk-in intake option when shown.
- Complete the intake fields and save the job.
How do I add a customer device?
Select an existing device from the customer record or add a new device during repair intake, then enter its identifying details.
- Open the customer or repair intake.
- Choose Add Device.
- Enter the device model and identifier details, then save.
How do I find a device by IMEI?
Use the device search field exposed by the customer or repair workflow and enter the IMEI to find the matching device record.
- Open the device selector or repair intake.
- Search using the IMEI.
- Choose the matching device and confirm the customer context.
How do I record device damage?
Record condition notes and mark visible pre-existing damage with Device Damage Sketch during intake. The sketch stays with the repair and can appear in the customer’s agreement review. It is a visual condition record, not photo management.
- Open the repair intake.
- Use the condition and damage fields.
- Review the notes with the customer before saving or requesting approval.
How do customers sign a Repair Agreement?
ActivePrepare a versioned Repair Agreement from the repair, then create a QR code or email signing session. The customer reviews the repair details, condition sketch, and consent before signing on their own device. No SpudgerHQ account is required. The signed snapshot stays in the repair history.
- Configure the shop’s Repair Agreement in Settings.
- Prepare the agreement from the current repair details.
- Create the QR or email signing session for the customer.
- Review the signed agreement in the repair history.
What happens if a repair changes after signing?
A signed agreement snapshot stays unchanged. Prepare a new current snapshot for review when the repair scope changes; the earlier signed record remains in history.
How do I assign a technician?
Open the repair detail or edit flow, choose the technician from the available staff list, and save the assignment.
- Open the repair detail.
- Choose Edit or the technician field.
- Select the technician and save.
How do I add repair parts and services?
Use the repair line-item actions to add stocked parts and service products, then review the repair estimate or total.
- Open the repair detail or edit page.
- Add the required parts and service lines.
- Review quantities, prices, and the updated repair total.
What does “waiting for parts” mean?
The repair is paused because one or more required parts are not yet available. Resolve the part requirement before moving the job forward.
How do I start or update a repair?
Open the repair detail, choose the next available status action, and save any technician notes or line-item changes before leaving the page.
- Open Repairs and select the job.
- Review the current status and available action.
- Update the status or details and save.
How do I complete QA checks?
Needs verificationReview the repair's QA checklist and mark completed checks as passed. If any check remains incomplete, SpudgerHQ can show a warning before Mark Ready; staff can cancel or continue. Completing QA before release remains a shop procedure.
- Open the repair detail after the work is complete.
- Review the QA checks and mark completed checks as passed.
- If QA remains incomplete, review the warning. Cancel to return to the repair or continue to attempt Mark Ready; other workflow conditions still apply.
How do I mark a repair ready?
Open an In Progress repair with no waiting repair parts, review its work and QA checklist, then choose Mark Ready. If QA is incomplete, a client-side warning may appear; staff can cancel or continue. Complete QA before pickup as your shop's release procedure.
- Open the In Progress repair detail.
- Resolve waiting repair parts and review the QA checklist; mark completed checks as passed.
- Choose Mark Ready. If QA remains incomplete, cancel to return to the repair or continue to attempt the action.
How do I collect payment for a repair?
Use the payment action from the repair detail or checkout handoff, review the repair total, and complete the payment.
- Open the repair detail.
- Choose Collect Payment.
- Select the payment method, confirm the amount, and complete the transaction.
How do I print a repair invoice or ticket?
Needs verificationUse the print action exposed by a reachable repair entry point after reviewing the ticket or invoice details.
- Open the repair detail.
- Choose Print Invoice or Print Ticket when available.
- Follow the browser or platform print dialog.
How do I cancel or delete a repair?
Needs verificationOpen an eligible repair, choose the available cancellation or deletion action, provide any requested reason, and confirm.
- Open the repair detail.
- Review the current status and available destructive actions.
- Confirm the action only after checking that the job should no longer continue.
Keep this context in mind
- Repair intake is the starting point for the repair job and its customer/device context.
- Waiting for parts means the job cannot continue until the required part availability is resolved.
- Contract and contract-template routes currently redirect to Repairs and are not standalone active workflows.
Talk to the SpudgerHQ team.
Tell us what you expected to see and which workflow you were trying to complete.
