Glossary
The key SimpliServ terms from A to Z, explained briefly
→ Open the overview in SimpliServ
A short reference to the key terms in SimpliServ. Each entry explains the term in a sentence or two — grounded in how it actually works in the system — and links to the matching guide where one exists. Sorted alphabetically.
The full flow from request to invoice — and which documents convert into one another — is described in the guide Document types & flow.
C
Case (Customer Flow / customer job) — The bracket that holds all documents of a customer case together: service request, proposal/estimate, order, delivery notes, invoices and the communication. It carries its own continuous number as well as a scannable code and a public tracking token. See Customer Flow.
Channel / Connector — A connection to an external system such as Shopify, Wix or JTL-Wawi. A channel connection holds the credentials and can be pending, connected or disconnected; the connector syncs products, orders and stock in both directions. See Channel sync as well as the guides for Shopify, Wix and JTL.
Contact — A customer, supplier or business partner with addresses, contact persons and the entire document history. Central master data that orders, invoices and cases hang off. See Contacts.
Contact group — A grouping of contacts with shared defaults such as payment term (days), a default discount and SLA duration. Not to be confused with the contact type (e.g. business customer, supplier, dropship partner). See Contact groups & types.
Credit note — An invoice flagged as a credit note (reversal/correction document) that credits an amount back to a customer. In the system it's an invoice with the is_credit_note flag. See Invoice correction & credit note.
D
Delivery note — Documents the delivered items, typically when dispatching an order. See Delivery notes.
E
Estimate — The same document type as a proposal, but marked as an estimate. Optionally you can attach an inspection/diagnosis fee that can later be billed as its own estimate invoice. See Create an estimate.
F
Form — A public or internal input form (e.g. the service registration form). Submitted forms land in the system as submissions and, via field mappings, can populate contacts or cases directly. See Forms.
I
Inventory / stock — A warehouse is a physical storage location; the inventory tracks, per product and warehouse, the available, reserved and total quantity as well as the minimum stock. Every quantity change is logged as a stock movement. See Manage inventory.
Invoice — The payment-relevant document with an invoice number, dunning level and status (Draft, Open, Paid, Cancelled). The end of the document chain. See Invoices.
L
Lead — A sales opportunity in your pipeline that moves through freely definable stages (e.g. New, Qualified, Won, Lost). A lead doesn't automatically turn into a document. See Leads & pipeline.
O
Order — The confirmed order. Here you manage line items, handle shipping and track delivery status. From an order you can create a delivery note and an invoice. See Orders.
N
Number range — The template by which document numbers are assigned — with format, variables and digit count, per document type and with its own running counter. See Number ranges.
P
POS / cash register — Selling at the point of sale with cash sessions, cash and card payments and receipts. In Austria coupled to the RKSV signature. See Set up the register and Point of sale (POS).
Proposal — A price offer with line items, discounts and a validity date that the customer can view via a public link. Technically the same document type as an estimate, distinguished only by a type flag (offer or estimate). See Proposals.
R
Receipt — A cash receipt from a sale at the register. With RKSV active (Austria) each receipt is part of the signed receipt chain; alongside these there are special receipts such as the start, monthly and annual receipt. See Receipts (RKSV).
RKSV — The Austrian cash-register security regulation. With RKSV active, receipts are signed and kept in an unbroken receipt chain (via Fiskaly). See RKSV logic & fiscalization.
S
Schedule (roster) — The weekly shift planning for your team. Shifts are assigned to staff, optionally created from shift templates. See Roster & shifts.
Service request — An incoming request, usually via the public service form, with customer details and the issue. It's the starting point of a case and moves through statuses like Pending, Accepted, Converted, Completed or Rejected. See Handle service requests.
Time clock — Attendance time tracking via a terminal (tablet) or app: staff clock in and out. Separate from job-based time tracking. See Time clock.
U
Urgency (SLA) — The traffic light per case that shows how much of the agreed handling time is left. The duration is inherited via default, contact group, contact and case; the clock can be paused while waiting on the customer, on parts or on an email reply. See Urgency & SLA.
V
Variant — A specific version within a product family (e.g. size or colour). Each variant is a standalone product with its own SKU, price and stock, which you create and assign to the family along with its option values; the option combinations only define the possible variants — they're created individually. See Product variants & families.
Voucher — A prepaid voucher (value voucher) that a customer buys and later redeems at payment. Internally handled as a coupon of type voucher (as opposed to the discount coupon); its status derives from the remaining balance and validity — e.g. active, partially redeemed, fully redeemed, expired, inactive or cancelled. See Vouchers.
W
Workflow — An automation that, on a trigger (model event, schedule, manual or webhook), runs a chain of steps — such as sending emails or setting a status. See Workflows.
How is this guide?