TRIAL Trial run - not yet ready for production use. InvoiceNET® ERP and this website are open to everyone for trial and testing, and are not yet ready for production use. Please do not keep real business records here: data entered during the trial may be reset, and features may change. Tell us what you find through Suggestions & Feedback. Open the feedback form
InvoiceNET®ERP Software for Business

Colour

These are the themes of InvoiceNET® ERP itself. Your choice is remembered on this device.

Help centre / Masters

Brand Master

A Brand identifies the maker or label of a product (e.g. Samsung , Nike , Dell ) for selection and reporting.

1How to work in this page #

  1. Find (F2): search by name or description.
  2. Add (F3): create a new brand. Cursor lands on Name.
  3. Modify (F4): edit the loaded brand.
  4. Delete: remove the current brand (view mode), with confirmation.
  5. Save (F5): commit the add / modify. Name is required and must be unique.
  6. Cancel (Esc): discard the current edit.

2Step by step #

Brands identify the maker or label a product carries, for selection and brand-wise reporting.

  1. Press Add (F3) and type the brand name — Samsung , Dell — with an optional description.
  2. Press Save (F5) and confirm; F3 for the next.
  3. Products pick the brand on the Product master; discount schemes can target it brand-wise.

Once products or voucher lines carry the brand, delete is refused by the database — use Inactive to retire it from pickers instead.

3Rules and integrity #

  • The brand name must be unique; a duplicate is refused before saving.
  • Brands are chosen on products. Deleting a brand that is still in use can leave those products without one, so retire an obsolete brand rather than deleting it.

This is the help InvoiceNET® ERP shows beside the Brand Master screen. Whether you have the screen depends on the modules of your licence and the rights your administrator has given you.

See this screen for yourself

The demo is the real product, with a company of your own.

Something went wrong. Please reload the page. Reload ×