CRM KitsAuto repair shops
Every repair order. Approved and on the lift.
A repair shop does not run on a funnel or a calendar. It runs on the repair order. Gasket makes that ticket the work surface: a stack of printed-looking shop tickets that open their whole record inline, with the two things that actually stall a shop, approvals and parts, given their own views.
One ticket per vehicle, top to bottom.
Each repair order reads like a printed shop ticket: a large monospace RO number, the vehicle, the plate or VIN reference, the recorded odometer, the lift label and a red status stamp. Beside it sit the promised date, the approved total, how many line items are still awaiting an answer and how many recorded parts have arrived.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Repair order ticket stack with perforated shop tickets that expand inline
- Approvals queue for line items recorded as awaiting, approved or declined
- Parts on order tracker with vendor labels, ordered and expected dates and a received flag
- Lift board and vehicle records grouped from the repair orders themselves
- Shop insights drawn from recorded workspace data
- White, gray and red Gasket application frame with full CRM tools
four pipelines
- Repair orders · 8 stages
- Diagnostics and estimates · 7 stages
- Fleet accounts · 7 stages
- Warranty and comebacks · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Diagnosis write-up
- Approval follow-up
- Parts order note
- Parts arrival check
- Quality control checklist
- Pickup note
- Promised date check
- Comeback follow-up
- Fleet account review
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional repair orders sitting at different status stamps, with twenty-four line items across awaiting, approved and declined, nine recorded parts, lift labels including one recorded conflict, and one vehicle that has been in twice. Example edits stay in the current page’s memory and reset on navigation or reload; sample repair orders are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original repair order helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps stable line item and part IDs, archives child rows instead of dropping them, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One repair order is a native contact-linked opportunity with a repair order number, the vehicle, a plate or VIN reference, an odometer reference, the customer complaint, the recorded diagnosis, a lift label, a promised date and a status stamp. Line items and parts are stable-ID child records. Unrelated custom fields are preserved and stale record versions are rejected.
Status stamps, approvals, parts receipts and lift labels are all staff entered; nothing advances on its own. The kit reads no parts catalog, checks no availability, contacts no vendor and places no order. It has no labor guide and no flat rate times. It does no VIN decoding, registration lookup or vehicle history report. It sends no customer message, opens no approval link and collects no signature. It produces no invoice, takes no payment and calculates no tax. It books no appointment, reserves no lift and assigns no technician; a lift carrying two open repair orders is flagged for review, not prevented. Line item amounts are recorded references, separate from native opportunity value, estimates and payments.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory repair orders with recorded line items and parts.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Auto Repair Shop Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Gasket keeps its repair shop navigation across the original views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More automotive & fleet kits
Browse all 220 kits
Follow the repair-order workflow
Use the auto-shop demo to work through customer approvals, parts status, and the next handoff.
Read the auto repair CRM workflow guide →