From request to decision, following head office rules
An example of a store purchase that needs approval. Your company rules decide who is involved and which steps apply.
1
The store records the request
It specifies what work or equipment is needed, for which store and by when.
2
The buyer checks the contract terms
The related contract and its terms are available alongside the request. If there is no suitable partner, onboarding a new provider can start from here.
3
The designated person decides on the request
The request goes to the person who can decide on it, according to the rules you set. The decision and any comment are recorded with the request.
Store request
1
Deep cleanBudaörs, store 12
2
Cleaning framework contractItem outside the contract: cleaning behind the refrigerated counters
Regional managerApproved · 21 Oct, 10:05“One-off extra work, with the existing partner.”
Illustrative example
What stays on record?
Who asked, on what terms, who decided, when and with what comment. Head office sees not only the outcome but also how the decision was reached.
Contracts
Up-to-date agreements for day-to-day operations
The framework contracts your stores use, and their amendments, are available in one place.
Validity
The contract shows which amendment applies, and from when.
Deadlines
Expiry and notice deadlines are visible on the contract.
Notifications
The designated person is notified before a deadline, so the decision to renew or renegotiate can be prepared in time.
Alongside your existing systems
Start with a single purchasing category
Fluenta One can be used alongside your ERP and merchandise management system. You can try it out in one category, such as maintenance or cleaning, with a few stores, following your own approval rules.
Let’s look atone of your store purchases
Using a real example, we’ll walk through how Fluenta One handles contract terms, the documents you need and approvals.