What is behind the purchase request?

Have you ever thought about what’s behind the «Purchase request» internal service?

Sometimes it’s hundreds of working hours in messy conditions, sometimes it’s a well-structured business process. Let’s imagine that someone asked to buy a new office equipment. Printers, let’s say. What comes after a service ticket is created?

1 probably, the request should be approved by a budget owner(s) depending on the purchase amount

2 a procurement specialist have to check if a company has an approved supplier for this kind of equipment. If there is one, a new order is placed, then it comes to the step 4

3 If there is no approved suppliers, procurement team have to conduct a tender which includes steps such as request for information, request for proposal and choosing a right one

4 When a contract (or an order) is agreed, the delivery SLA starts. Procurement team asks a supplier and a requestor if the delivery is done

5 When the equipment is delivered, it’s time to close the deal depending on the local legislation

6 Last, but not least is collecting requestor’s opinion on how purchasing team have worked

As you may see, the are a lot of subprocesses behind. Why am I telling you that?

Because Jira Service Management can suit you well in this case too — a simple, clear interface for the requestor (and maybe for suppliers too), and a powerful and flexible environment for those who handle the process. Plus, built-in way to check the reference data, easy integrations, reporting on customer satisfaction rate and many other opportunities to build user-friendly purchasing service.