Vendors Built

A vendor is a supplier AIR buys stock from — the master record that Purchase Orders and Goods Receipts will reference. It is the first piece of the new Purchasing area of the console.

What a vendor is

Where a Customer is someone AIR sells to, a vendor is someone AIR buys from — a printer, paper mill, binder or any other supplier that AIR raises purchase orders against and receives stock from. Each vendor record captures who the supplier is, how to reach them, their tax registration, and the payment terms AIR trades on. On its own the record does not yet move any stock or money; it is the reference data that the rest of the Purchasing module — Purchase Orders and Goods Receipts — will build on. Getting the vendor master right is therefore the foundation of everything that follows.

Where to find it & who can see it

Open Purchasing › Vendors in the left navigation — this is a new navigation group added alongside the vendor master.

Permissions

Viewing and listing vendors needs vendor.view (or super administrator). Creating, editing, deleting — and restoring or permanently removing a soft-deleted vendor — all need the single broader permission vendor.manage. There is no finer-grained permission than these two.

Creating / editing a vendor

Select New vendor from the list, or row Edit on an existing one. The form is grouped into five sections, matching the screen.

  1. Identity

    Who the vendor is and whether they are in active use.

    FieldTypeRequiredNotes
    nameTextYesThe supplier's name.
    codeTextYesA short identifier, unique across all vendors. Shown as the badge in the list.
    is_activeToggleNoDefaults on. Switch off to retire a vendor without deleting the record.
  2. Tax

    The supplier's GST registration, used later for purchase billing.

    FieldTypeRequiredNotes
    GSTINTextNoThe vendor's GST registration number (stored as gst_registration_number).
    GST registration typeSelectNoOne of Regular, Composition, Unregistered, Consumer, Deemed Export or SEZ. Defaults to Unregistered.
  3. Contact

    How to reach the vendor day to day.

    FieldTypeRequiredNotes
    contact_personTextNoThe named contact at the supplier.
    emailTextNoContact email address.
    phoneTextNoContact phone number.
  4. Address

    The vendor's postal address.

    FieldTypeRequiredNotes
    Address line 1TextNoStored as address_line1.
    Address line 2TextNoStored as address_line2.
    cityTextNo
    stateTextNo
    pincodeTextNoPostal PIN code.
  5. Terms

    The trading terms AIR deals with this vendor on.

    FieldTypeRequiredNotes
    payment_terms_daysNumberNoCredit period in days.
    notesTextareaNoFree text, full width. Internal notes only.

On create, the console also stamps created_by with your user ID automatically — there is no field for it on the form.

The list

ColumnShows
codeShown as a badge. Searchable, sortable.
nameVendor name. Searchable, sortable.
GSTINgst_registration_number. Toggleable column.
GST typegst_registration_type, shown as a badge.
Citycity. Toggleable column.
Activeis_active as a boolean icon.

Filters: Active status (yes/no/either on is_active), GST type (drop-down over the registration types), and a Trashed filter. The search box matches code and name.

Deactivated vs deleted

Switching is_active off simply retires a vendor while keeping it in the list. Deleting a vendor soft-deletes it — vendors use SoftDeletes, so a deleted record disappears from the default list but is not permanently erased. Use the Trashed filter to see soft-deleted vendors, then row Restore to bring one back or Force delete to remove it for good. Restore and force-delete both need vendor.manage.

Screenshot placeholderThe Vendors list — Code badge, Name, GSTIN, GST type badge, City and Active icon columns, with the GST type and Trashed filters open; and the vendor create/edit form showing the Identity, Tax, Contact, Address and Terms sections stacked in order.
Where a vendor is used

Vendors are the first piece of the Purchasing module, and the rest of it is live. Everything downstream hangs off this master: Purchase Orders raised against a vendor, Goods Receipts that add the received stock into a warehouse, Vendor Bills that apply GST and record what is owed, and Vendor Payments that settle it. The payment-terms days you set here are what a bill's due date is calculated from.

Related pages

See Customers & Categories for the sell-side counterpart to this master, Purchase Orders, Goods Receipts, Vendor Bills and Vendor Payments for the rest of Purchasing, Warehouses for where received stock lands, and Stock on Hand for how inventory is tracked.