---
title: "Service Workshop"
space: "ServiceMS"
url: "https://support.aakvatech.com/ServiceMS/service-workshop"
updated: "2026-07-22"
---



---

## 1. **Overview**

The **Service Workshop** DocType is a central component within the **Service Management** module. It represents a physical or virtual workspace where service operations such as vehicle or equipment repairs, maintenance, or part replacements take place. This master record holds critical configuration data like associated warehouses, company, and operational preferences.

---

## 2. **Key Features**

- Unique **Workshop Name** with identification.
- Direct linkage to a **Company** and **Warehouses** (for parts and workshop inventory).
- **Location** tagging for logistical or branch management.
- Option to toggle between using **Spare** parts instead of regular **Items**.
- Integration-ready for downstream modules (like Work Orders, Job Cards, Inventory).
- Clean UI with section and column layout for clarity.

---

## 3. **Pre-Requisites**

Before creating a **Service Workshop**, ensure the following are set up:

- ✅ At least one **Company** exists in the system.
- ✅ Relevant **Warehouse** records have been created (Parts Warehouse & Workshop Warehouse).
- ✅ Appropriate **User Role** (like System Manager) is assigned for access and creation.

---

## 4. **Step-by-Step Usage**

### A. **Creating a Service Workshop**
1. Navigate to:  
   **Service Management > Service Workshop**
2. Click **"New"**.
3. Fill in:
   - **Workshop Name** (Required, unique)
   - **Company** (Required – Link to existing Company)
   - **Location** (Optional – branch or area identifier)
   - **Parts Warehouse** (Required – for consumables)
   - **Workshop Warehouse** (Required – tools, WIP items)
4. Optionally, check **“Use Spare not Item”** if your workflows depend on alternate spare records.
5. Click **Save**, then **Submit** if submission is enabled.

### B. **Viewing Workshops**
- Go to list view to see all workshops.
- Use filters like **Company** or **Location** to narrow down results.

---

## 5. **Script Customizations**

For advanced behavior, the following customizations can be implemented:

### Example 1: Auto-fill Location based on Company
```js
frappe.ui.form.on('Service Workshop', {
  company: function(frm) {
    // Custom logic based on company selected
    if (frm.doc.company === "ABC Pvt Ltd") {
      frm.set_value('location', 'Mumbai');
    }
  }
});
```

### Example 2: Validation to ensure warehouse naming standards
```js
frappe.ui.form.on('Service Workshop', {
  validate: function(frm) {
    if (!frm.doc.parts_warehouse.includes("Parts")) {
      frappe.throw("Parts Warehouse should include 'Parts' in the name.");
    }
  }
});
```

---

## 6. **Troubleshooting (Common Errors and Resolutions)**

| **Issue** | **Cause** | **Solution** |
|-----------|-----------|--------------|
| `Warehouse not found` | Invalid warehouse link | Make sure the selected warehouse exists and is active |
| `Duplicate Workshop Name` | Workshop name already used | Use a unique name for each workshop |
| `Permission Denied` | User role lacks access | Ensure user has "System Manager" or custom role with write permissions |
| `Form Not Submittable` | DocType isn’t set as submittable | Enable “Is Submittable” from DocType settings if needed |

---

## 7. **User Roles and Permissions**

Currently, full access is granted to:

- **System Manager**
  - Can create, read, write, delete, export, share, and print
  - Has visibility into all workshop configurations

For granular control, consider defining roles like:

- **Workshop Manager** (Read/Write only)
- **Service Planner** (Read only)
- **Inventory Officer** (Read-only warehouse fields)

---

## 8. **Key Notes**

- `use_spare_not_item`: This toggle affects item selection behavior in related processes like Job Cards or Service Orders.
- Ensure **Warehouses** are properly categorized to avoid mismatched inventory transfers.
- Custom workflows can be added via Workflow module to require approval or multi-step verification.

---

## 9. **What Business Process Pain Point Does It Help Remove**

This DocType helps eliminate the **chaos of decentralized service tracking** and **manual warehouse linking**. It enables:

- Streamlined **service workshop setup** per location or branch.
- Reduced **inventory mismatch** with pre-linked warehouses.
- Enhanced **operational clarity** with toggles and location markers.
- Integration-ready setup to connect service, inventory, and financial flows.

It forms the backbone of service-related operations, ensuring your system is structured, scalable, and accurate.

---