Naming Conventions

Vruksha ERP auto-generates human-readable identifiers for the records you create most often — projects, subprojects, quotations, and sales/purchase documents. Naming conventions let you control the prefix at the front of each generated ID so they match your company's standards (for example PRJ-001 versus VRK-001).

Where to find it: Settings → Naming Conventions.

:::tip Configure this before creating records Prefixes only affect IDs generated after the change. Existing records keep the ID they were given when they were created. Set your prefixes once, early in setup, and leave them alone. :::

How an auto-generated ID is built

Every generated identifier follows the same simple pattern:

<PREFIX> + <separator> + <zero-padded sequence number>

For example, with the Project prefix set to PRJ, the first three projects you create become:

PRJ-001
PRJ-002
PRJ-003

The prefix is what you configure on this page. The sequence number is maintained automatically by the system and increments by one for each new record of that type within your organization. You never set the sequence yourself — you only choose the prefix.

Configurable prefixes

Record type	Setting	Default prefix
Project	Project prefix	PRJ
Subproject	Subproject prefix	SP
Quotation	Quotation prefix	QT
Sales Order	Sales Order prefix	SO
Sales Invoice	Sales Invoice prefix	SI
Purchase Order	Purchase Order prefix	PO
Purchase Invoice	Purchase Invoice prefix	PI

If you never visit this page, the system uses the default prefixes shown above, so IDs are generated correctly out of the box. Configuring the page simply lets you override those defaults.

:::note SVG and group identifiers The same settings area also holds a few optional layout-related identifiers — an SVG Unit prefix, an SVG Amenity prefix, a Unit Group ID, and an Amenities Group ID — used when working with subproject SVG layouts. These are optional and have no default prefix. :::

Prefix rules

When you enter a prefix, keep these constraints in mind:

• Length: up to 10 characters.
• Characters: alphanumeric only (letters A–Z and digits 0–9). No spaces, dashes, or symbols.
• Casing: prefixes are stored in UPPERCASE and trimmed automatically, so prj and PRJ produce the same result.

If a prefix breaks these rules, the form shows an inline error on submit (for example, "Project prefix must contain only alphanumeric characters.").

Sequence and preview

• The sequence for each record type is independent. Projects, quotations, and sales orders each have their own running counter.
• Changing a prefix does not reset the sequence. If you have already created QT-014 and then change the quotation prefix to QUO, the next quotation becomes QUO-015, not QUO-001.
• The preview shown next to each field demonstrates what the next ID will look like with your current prefix, so you can confirm the format before saving.

Saving changes

Edit only the prefixes you want to change and save — every field is optional, and unspecified fields keep their current value. The change is recorded in the audit log (created on first configuration, updated thereafter), so there is a trail of who set each prefix and when.

Worked example

An administrator wants all sales documents to share a VRK family of prefixes:

Setting	New prefix	Next generated ID
Quotation prefix	VRKQ	VRKQ-001
Sales Order prefix	VRKSO	VRKSO-001
Sales Invoice prefix	VRKSI	VRKSI-001

After saving, the next quotation, sales order, and sales invoice created in the organization use these new prefixes, while any documents created earlier keep their original IDs.

Related pages

• Organization Setup — the previous setup step.
• Reference Data — master data setup, the next step after numbering.