Digisoftech

Custom software development in Kolkata

When the sheet and the desk disagree

This is customised software, built around the desk the company already runs, from the Kolkata office. Digisoftech builds the system a company uses to run work it already does. Open a job. See what is free. Send people. Produce the papers accounts expects. It is not a generic package renamed for the logo.

The break usually shows up mid-morning. One booking has been copied into a sheet, a challan, and an invoice by hand. A second person edits the sheet. The loading bay is working from a printout that is already wrong. By the time accounts asks for the invoice, nobody is sure which version is the job.

A clear example is a rental company with a large warehouse, a crew on the order of a hundred people, and several jobs leaving on a typical day. The same pattern fits any desk that has outgrown a folder of spreadsheets. The rental version, including stock counts and the document set, is on the Industries page.

What the system holds

A job record being planned

The job

One record the office and the supervisor both open. Customer, date, site, lines, and the state of the job from enquiry to closed.

Stock held for an operating company

The stock

What is in the warehouse, what is allocated, and what is due back. A unit cannot be promised to two jobs for the same hours.

A crew assigned across the day's jobs

The people

Who is on which job. A large crew means overlap, and the record shows the clash before the vehicle moves.

Documents from the same lines

The papers are not a separate typing job. They are views of the lines already on the job.

Proforma invoice

The customer confirms value before anything moves. The PI uses the booked lines, the rates, and the taxes the desk already applies.

Delivery challan

The gate and the site get a list of what left. A short count on the way out changes the challan, not a second sheet.

Tax invoice

Raised from the confirmed lines once the job is done. Accounts does not retype what the warehouse already checked.

How an enterprise project runs

Nine steps. The old spreadsheet stays in use until a real day has run on the new record.

  1. 1

    Walk the desk

    We sit with the people who open the day. Which sheet is the source, who is allowed to edit it, and which printout the loading bay trusts. The software starts from that walk, not from a module list.

  2. 2

    Collect the papers already in use

    Proforma invoices, challans, tax invoices, and the booking sheet. We mark which fields are typed twice and which fields accounts will not accept if they are missing. Those fields become the record.

  3. 3

    Name the records

    Job, customer, stock unit, person, and document. Each one has a state. A stock unit is in the warehouse, on a job, or due back. A job is enquiry, confirmed, out, or closed. States are agreed before any screen is drawn.

  4. 4

    Draw the office screens

    The day needs a list of jobs, one job, the stock that can still be promised, and the people still free. You review those screens against yesterday's bookings. A field that the desk cannot find in ten seconds is redesigned before the build.

  5. 5

    Put stock and people on the job

    Allocation is the part spreadsheets lose. The system refuses a unit that is already out, and it shows a person who is already on another site. The rule is the one your warehouse already believes. The software only enforces it.

  6. 6

    Raise the documents from those lines

    PI, delivery challan, and tax invoice are generated from the job. A change to a line changes the papers. Nobody keeps a parallel Word file "just in case" once this step is trusted.

  7. 7

    Open the same job on a phone

    If a supervisor or a field user has to update the job away from the desk, that update is a mobile app on this same record. The phone is not a second system. It is the job, away from the office.

  8. 8

    Run one real day before the sheet is retired

    A chosen day is entered in the new system while the old sheet still exists. At close of day the two are compared: jobs, stock out, people, and the documents that were sent. Differences are fixed. The sheet is retired only after that comparison is dull.

  9. 9

    Stay on after go-live

    The first month shows the exceptions the walk did not catch. There is a named way to report them, a fix cycle, and a short handover so the desk knows how a new field or a new document is requested.

Who sits at which screen

  • The booking desk opens the job and sends the proforma invoice.
  • The warehouse allocates stock and prints the delivery challan.
  • The supervisor checks people against the day's jobs, in the office or on a phone.
  • Accounts raises the tax invoice from the confirmed lines and does not retype them.

Each role sees the fields that role is allowed to change. A warehouse edit of a rate, or an accounts edit of a loaded quantity, is a mistake the screen should not offer.

Online selling, when you need it

Some operating companies also sell online. Digisoftech still builds that store, including Magento when the catalogue and checkout call for it. The store sits next to the office tools. It is not a separate promise, and it does not replace the job, the stock, or the documents.

Call or WhatsApp to start with a walk of the desk. That is step one, and it is the part that decides everything after it.

Call +91 8296304632 WhatsApp