Purpose
This page explains how collecting the project deposit after scope validation leads to the job being released to manufacturing.
Who owns it
CSR (Danielle), with Project Manager oversight through to manufacturing release.
Trigger
Scope has been validated (see /help/workflows/scope-validation) and the job is ready for its project deposit.
Steps
- Confirm the opportunity's stage on
/opportunitiesshows scope validation complete. - Generate and send the project deposit payment link (
/pay/...) to the customer. - Confirm the deposit payment on
/payments. - Once paid, update the opportunity stage to project deposit and prepare the job for manufacturing release.
- Confirm the job's line items push correctly to ServiceTitan (the system of record for jobs/estimates). Check
/admin/servicetitan-mappingif any push fails. - If a job includes a "Door / slab" material, note that pushes for this bucket are currently blocked — ServiceTitan SKU 39723877 was deleted and no active replacement is mapped yet. Escalate to an admin to fix the mapping in
/admin/servicetitan-mappingbefore manufacturing can proceed for that item. - Once all items push successfully (or the mapping issue is resolved), mark the job as released to manufacturing.
- Notify the Project Manager and log the update in
/communications.
Done when
The project deposit shows paid on /payments, all line items have successfully pushed to ServiceTitan, and the opportunity stage reads manufacturing release.
Handoff to
Project Manager (Sergio + PMs) and installation scheduling, which is tracked going forward on /projects.
Common mistakes
- Releasing to manufacturing before confirming the deposit actually cleared on
/payments. - Not checking
/admin/servicetitan-mappingwhen a push fails, assuming it's a one-off glitch. - Forgetting that "Door / slab" items are currently blocked at SKU 39723877 — pushing ahead without fixing the mapping will cause the job to fail silently in ServiceTitan.
Warning: As of this writing, any job with a "Door / slab" material is blocked from pushing to ServiceTitan because SKU 39723877 was deleted. Escalate to an admin to map an active replacement SKU in /admin/servicetitan-mapping before assuming manufacturing has started.
