· Saitami.bg

How to Work with an ERP System: A Practical Process

With an ERP system, employees no longer transfer the same information between Excel, email, warehouse software and accounting software. They move one order through clear stages, while each person sees only what they need for their work. Here is what this process looks like in a real business.

A warehouse employee prepares an order while a sales representative reviews a document at a desk.

An ERP system works as a shared workflow, not as a series of separate screens. The salesperson enters a customer and order, turns it into a quote, and the system creates an order when it is approved. From there, the warehouse, production team, field employee, accountant and manager all work with the same data. The status is changed once and visible everywhere.

How work begins: customer, order and quote

The process starts with the customer record. It stores the company, contact person, addresses, agreed terms, order history and conversations. When a new enquiry arrives by phone, email, website or in person, the salesperson records it under that customer. If the customer is new, they create a record instead of entering the details in a personal spreadsheet.

Next comes the order. It can be for a product sale, service, repair, installation or entire project. The salesperson adds products and services, quantities, deadline, address and special terms. For a business with different pricing, the ERP system can use a price list for a specific customer or customer group.

The quote is created from the order. This reduces retyping and errors in quantities, prices and addresses. After sending it, the salesperson changes its status to “sent”, “pending approval” or “declined”. When necessary, the manager can view and approve the quote without searching for an attachment in an email thread.

How a quote becomes an order and task

When the customer accepts the quote, the salesperson turns it into an order. The system preserves the link between the customer, quote and order. This makes it possible to see later what was proposed, what was accepted and what was actually delivered.

Tasks are created from the order. They can involve preparing goods, delivery, a site visit, installation, repair or issuing an invoice. Each task has an assignee, deadline, address, description and status. The field employee receives only their own tasks on a phone or tablet. They can add a photo, note, materials used and the customer's signature.

This model is important for field operations. In Ekovat, the ERP system covers orders, work orders, fleet, warehouse and documents for a company with field operations. The work order does not remain only in the dispatcher's folder—it is linked to the people, materials and subsequent invoicing.

How an ERP system manages the warehouse

Once an order is confirmed, the warehouse sees what needs to be picked or purchased. Stock levels are checked by item, warehouse and reserved quantity. If there is a shortage, a supplier request can be created without the employee having to run a separate report in Excel.

When a delivery is received, the supplier, items, quantities, batches and expiry dates are entered when necessary. When goods are dispatched, the warehouse employee confirms what has left the warehouse. This lets the salesperson see whether the order is ready, while the manager can see stock movements and inventory value.

In manufacturing, the warehouse is not just a list of finished goods. The system can link a recipe or production operation to a production batch. At Testen Dom, the process includes B2B orders from email, recipes, production batches, an FEFO warehouse with expiry dates, barcodes, invoices and reports. This shows the difference between a standard warehouse module and a process configured for a specific business.

How an invoice is issued and what the accountant sees

When the delivery or service is completed, the invoice is created from the order or work order. The customer, basis, amounts and items have already been entered. The accountant checks the document, adds the necessary accounting details and tracks the payment status.

Depending on the process, an invoice can be issued upon delivery, at a project milestone, monthly under a contract or after work is accepted. At LiftexPro, the system connects inspection scheduling, buildings, technicians and automatic invoicing for elevator companies. This is the practical meaning of ERP: the invoice appears as the next step after the work performed, rather than as a new manual entry.

What roles are there in an ERP system

A good system does not show everyone the same screens. It restricts access according to responsibilities and keeps a record of who changed the data. Roles can be configured to match the company's structure.

RoleDaily workWhat they see
ManagerMonitors sales, orders, overdue tasks, warehouse and resultsDashboards, reports, key variances and the overall picture
SalespersonEnters customers, orders and quotes; tracks dealsTheir customers, quotes, tasks and communication history
Warehouse employeeReceives, reserves, picks and hands over goodsStock levels, movements, batches, barcodes and warehouse tasks
AccountantChecks invoices, payments and documentsInvoices, liabilities, payments and document flow
Field workerCarries out visits, installations or repairsAssigned tasks, addresses, instructions, materials and photos

The Universal ERP demo brings together contacts, projects, tasks, invoices, a calendar and reports. The international transport demo shows a different approach: separate views for the owner, dispatcher, accountant and driver, along with trips, fleet, customers, invoices and expenses. This shows why ERP is not the same for every company.

How a manager gets real-time reports

An ERP report is not just a month-end snapshot if the team enters information as the work is carried out. The manager can see which quotes are awaiting a response, which orders are overdue, what is in stock, which invoices have not been paid and how many tasks are open for each team.

This does not mean that every report is automatically useful. If employees skip statuses or use different names for the same item, the result will be inaccurate. That is why implementation defines mandatory fields, responsible people and clear rules for when a task is considered complete.

Saitami ERP combines CRM, a ticketing system, integrated SIP telephony, AI emails and process automation. This type of system is useful when a manager wants to connect customer communication with the actual work, rather than maintain separate lists for calls, tasks and sales.

How to replace Excel spreadsheets and rekeying

Excel remains useful for one-off analysis or data imports. The problem arises when the spreadsheet becomes the main operational system. Then there are different versions, no change history, formulas get damaged, and information does not reach the warehouse or accounting department on time.

ERP replaces this with a single record and a consistent sequence of actions. The customer is entered once. The quote uses their data. The order inherits the quote. The warehouse receives the task from the order. The invoice uses what was completed. The report is calculated from the same records.

When external systems are involved, an API integration can connect the ERP to an online store, courier, payment system, telephony, email or accounting software. The goal is not to replace every program, but to move data automatically wherever this is secure and justified.

How to implement the ERP process in your company

Do not start with a catalogue of features. Start with one real order and track what happens from the first contact through to payment. Record who enters the information, who checks it, what gets printed, where delays occur and which report is missing.

  1. 01
    Documenting the actual process

    Break the work into stages: request, quote, order, warehouse or production, fulfilment, invoice and payment. Note the exceptions, because these are often what create manual work.

  2. 02
    Defining roles and rules

    Specify who creates the customer, who approves the price, who reserves stock, who closes the task and who has the right to issue or cancel a document.

  3. 03
    Configuring and connecting the data

    Create fields, statuses, templates and reports. Then decide which external systems need to be connected via API and which data will be exchanged.

  4. 04
    Testing with real-world scenarios

    Test a normal sale, a rejected quote, an out-of-stock item, a returned delivery, an overdue task and an invoice correction. This helps identify problems before launch.

  5. 05
    Gradual implementation and monitoring

    Start with the process that involves the most manual work. Monitor whether the team enters data correctly, adjust the screens and add the next modules once the core workflow is stable.

When a standard ERP system is not enough

A standard product is a good choice when the company can work with a predefined process and does not need specific roles, documents or integrations. It is usually implemented faster, but it imposes limitations on how the company works.

A custom ERP makes sense when the company has field teams, production, complex contracts, different customer types, specific pricing or many systems to connect. The cost and timeline depend on the number of roles, modules, data migration, integrations and required checks. The important thing is for the proposal to describe the workflow, not just a list of menus.

Practical examples can be found in the demos for banitsa and pastry production, pergolas and canopies, and international transport. Each starts from different business logic. This is why the ERP system is configured to suit the company, instead of forcing the team to work around the software with new spreadsheets.

Frequently asked questions

Is it difficult to work with an ERP system?
No, not if the screens and roles are adapted to the actual work. The difficulty usually comes from an unclear process, unnecessary fields or a lack of training, not from the idea of ERP itself.
Can an ERP system replace Excel?
Yes, for daily requests, orders, inventory, tasks, invoices and reports. Excel can remain useful for one-off analysis or data exchange, but it should not be the primary place for operational information.
What does a field worker see in an ERP system?
They see their assigned tasks, the address, deadline, instructions and required materials. After the visit, they can add a status, note, photo, parts used or the customer's signature.
Can an ERP system be connected to an online store and accounting software?
Yes, when the specific systems have a suitable API or another reliable way to exchange data. In advance, you define which data is sent, in which direction and which system is the source of truth for each record.
How long does ERP implementation take?
It depends on the scope, number of roles, data migration, integrations and process complexity. The safest approach is to implement one core workflow first and add the remaining modules after testing.

What do you want us to build?

You describe the project, we come back with questions and a price range, then a demo and a written proposal.

Clients we have worked with

  • KMP Build
  • FIX Bulgaria
  • UnitGold
  • Akbari Perfume House
  • Baytown Machinery
  • Vida Luxe
  • Pro Structura
  • Crypto.bg
  • MysteryBet
  • AGA Transfer
  • Avanta
  • Unit.Estate
  • ZapaziChas
  • Labimex
  • National Elevator Company
  • Camélia Désir
  • Elite Call Center
  • Videoto