Skip to main content

Key Terminology

In one sentence: ServCraft uses specific terms for things — knowing what each term means prevents misunderstandings with customers and between teams.



Core Concepts​

Job / Job Card​

The central record in ServCraft. A job card represents a piece of work that needs to be done for a customer. It contains everything about that work: what's needed, who's doing it, what parts are used, what it costs, and what the outcome was.

The terms "job" and "job card" are used interchangeably in ServCraft. In the mobile app, these are often just called "jobs". In the web app, the detail page is called a "job card".

Think of it like: A physical job sheet or work order that follows a piece of work from start to finish — except it's digital and connected to everything else.


Job Status​

Every job has a status that shows where it is in the process. Statuses are fully customisable per business — each business defines its own list, order, and colours. When a new business is set up, ServCraft creates a starting set of statuses based on their industry type:

Workshop-style businesses (work comes to you):

StatusWhat It Means
Job CreatedThe job has been logged — this is the starting status
Work In ProgressA technician is actively working on the job
Work CompletedWork is done — this closes the job

Field-service-style businesses (you go to the customer):

StatusWhat It Means
Job BookedThe job has been logged and booked — this is the starting status
On Way To SiteThe technician is travelling to the customer (can automatically notify the customer)
Work In ProgressThe technician is on site working (can automatically start the job timer)
Work CompletedThe work itself is finished (can automatically stop the timer)
Invoice and CloseThe job is invoiced and closed

Each status can carry special behaviours: one status is the start status for new jobs, one or more are close statuses that end the job, and statuses can automatically start or stop the job timer or send a customer notification.


Workflow / Advanced Workflows​

A workflow is the set of job statuses a job moves through. Every account has one workflow called Default, and on it a job can move to any other active status.

Advanced workflows is an account feature that lets a business run several workflows side by side, each with its own statuses, for example a "Default" workflow for site jobs and a "Repair" workflow for workshop jobs. Each job type is linked to a workflow, and a job follows the workflow of its job type. A workflow can be enforced: each status then lists its Next Statuses, and staff changing a job's status can only pick from those, so jobs go through the steps in order. Employees with a login also get a Job Statuses tab, where you can limit which statuses that person may pick. It appears when the account has Advanced workflows or advanced permissions.

Not the same as automation. Rules that run by themselves, such as emailing the customer when a job is completed, are triggers. Some people call those "workflows" too. See Trigger / Workflow / Automation below.


Appointment​

A scheduled block of time for a specific type of interaction. Appointments in ServCraft can be:

  • On-Site — a technician visiting a customer's location
  • Phone Call — a scheduled call with a customer
  • In-Store — a customer coming into the business's premises

Appointments are linked to a specific technician (or team member) and appear on the scheduling calendar. They can be linked to a job.

Key distinction: An appointment is the scheduled time. A job is the work to be done. A single job might have multiple appointments (e.g., an assessment appointment and then a repair appointment).


Quote​

A formal price proposal sent to a customer before work begins. In ServCraft, a quote:

  • Is created with specific line items and pricing
  • Can be sent to the customer via email with a link to accept or decline
  • Has an expiry date
  • Once accepted, can be converted into an invoice or job

Quote statuses:

  • Draft — being prepared, not sent yet
  • Approved — reviewed internally and ready to send
  • Accepted — customer said yes
  • Declined — customer said no
  • Invoiced — quote was accepted and converted to an invoice
  • Expired — nobody responded before the expiry date
  • Cancelled — withdrawn before the customer responded

Invoice​

A request for payment issued to a customer after work is completed (or sometimes in advance). In ServCraft, an invoice:

  • Can be created from a job, from a quote, or manually
  • Can be set to recur automatically (e.g., monthly maintenance billing)
  • Can be paid in multiple instalments
  • Is sent to the customer via email (and tracked — ServCraft shows when it's been opened)

Customer​

In ServCraft, a "customer" is the business or person that the service company does work for. This is the entity at the top level — everything hangs off it (contacts, locations, jobs, quotes, invoices).

Note on language: ServCraft customers (businesses that subscribe to ServCraft) also have their own customers inside the platform. To avoid confusion: when we say "customer" in these docs, we mean the client of the service business — not the service business itself.


Contact​

A specific person at a customer. A customer record might be a company (e.g., "ABC Manufacturing"), and there might be multiple contacts within it — the procurement manager, the maintenance coordinator, the accounts payable person, etc.

Jobs and appointments are usually linked to both a customer (the company) and a contact (the specific person to deal with).


Location​

A physical address belonging to a customer. A single customer can have multiple locations — for example, a retail chain that uses a service business might have 20 branches, each as a separate location. Jobs are assigned to a specific customer location.


Technician / Employee​

Used interchangeably in most contexts. In ServCraft:

  • Employee is the system term for any staff member
  • Technician is the common term for a field or workshop worker

All employees (including admin and managers) are set up in the same system — the difference is their role and what they have access to.


Inventory / Stock​

Inventory in ServCraft refers to all the physical items the business buys, stores, and uses:

  • Products — items sold to customers (e.g., a replacement part)
  • Parts — components used during a repair (may or may not be charged to customer)
  • Services — non-physical items on invoices (e.g., "Labour: 2 hours @ R350/hr")

Inventory is tracked by quantity in warehouses or locations (including van stock for mobile technicians).


Warehouse​

A physical location where stock is stored. This could be:

  • The main workshop store room
  • A satellite office
  • A technician's van (tracked as a "Mobile" warehouse)

When a technician uses a part on a job, the stock is deducted from their assigned warehouse (their van stock).


Purchase Order (PO)​

A formal document sent to a supplier to request and track the purchase of goods. When a business orders parts, they create a PO in ServCraft. When the parts arrive, the PO is received, which adds the stock to the relevant warehouse.


Supplier​

A company from which the service business buys parts or materials. Suppliers in ServCraft have their own records, including contacts, price lists, and purchase history.


Query​

A customer inquiry, complaint, or service request that doesn't necessarily result in a job. Queries are tracked with their own statuses and can be assigned to staff for follow-up. Think of them as a lightweight support ticket within ServCraft.


Project​

A container that groups multiple related jobs together under one umbrella. Useful for large contracts where a customer has hired the business for an extended body of work (e.g., "Refurbish all 15 branches" — each branch visit is a separate job, all grouped under one project).


Recurring Job​

A job that is automatically created on a schedule — daily, weekly, monthly, or on custom intervals. Commonly used for maintenance contracts (e.g., air conditioning serviced every 6 months). ServCraft creates the job automatically at the right time, assigns it to the right technician, and even sends reminders.


Fault Code / Fault Reason / Fault Cause​

Three layered terms used in workshop and repair businesses to describe the nature of a problem:

  • Fault Code — a short code identifying the type of fault (e.g., "PWR-001" for a power fault)
  • Fault Reason — the specific reason identified during assessment
  • Fault Cause — the root cause of the fault (e.g., "Power surge", "User damage", "Manufacturing defect")

These are particularly important for businesses that do warranty repairs, as manufacturers often require structured fault reporting.


Warranty​

The term "warranty" is used in ServCraft in the context of assets and job statuses, but the specific types listed below are not standard built-in concepts:

Important: "Manufacturer Warranty" and "Workshop Warranty" as defined types do not exist as standard in ServCraft. These can be created as custom fields on the Assets module if a business needs to track them, but they are not built-in fields. A job status named "Warranty" can be configured by any business to represent warranty work.


Assessment / Assessment Fee​

In workshop-based businesses, before a repair begins, a technician assesses the item to diagnose the fault and determine if it can be fixed and what it will cost. The business may charge a fee for this assessment — this is the assessment fee.

If the customer decides not to proceed with the repair after assessment, they still pay the assessment fee.


Stocktake​

A periodic physical count of all inventory items to verify that what is physically in the warehouse matches what the system says. ServCraft supports structured stocktakes with templates, schedules, and confirmation workflows.


GRV (Goods Received Voucher)​

The document/transaction in ServCraft that records the arrival of goods from a supplier. When stock arrives from a purchase order, a GRV is created to formally receive it into the warehouse. This is what increases the stock count in the system.


Stock Transaction​

Any movement of stock in the system. Types include:

  • GRV — goods received from supplier (stock in)
  • Transfer — stock moved between warehouses (e.g., from main store to van)
  • External Transfer — stock sent out of the business, e.g. a warranty repair going to a supplier
  • Adjustment — manual correction to stock quantity
  • Initial — the opening stock quantity when an item is first set up
  • Used — stock consumed on a job or invoice (stock out)
  • Return — stock returned from a job or from a customer

Customer Zone​


Trigger / Workflow / Automation​

ServCraft has an automation engine where businesses can set up rules like:

  • "When a job is marked Complete, send the customer an email with a link to pay their invoice"
  • "When a quote hasn't been responded to in 7 days, send a reminder"

These are called triggers or workflows. They run automatically in the background without staff needing to take any action.


Integration​

A connection between ServCraft and another software system. Common integrations include:

  • Sage One — accounting software (the most common)
  • Xero — accounting software
  • QuickBooks — accounting software
  • PayFast — payment processing
  • SendGrid — email delivery

When an integration is active, data (like invoices and customers) syncs between ServCraft and the connected system automatically.


Multi-Store / Multi-Branch​