Kit 4.0 is an Argentine support programme for small and medium industrial companies that want to bring technology into their process. It is not a loan and it is not a supplier discount: it is a contribution granted on a project that was approved beforehand, with its own paperwork and deadlines. This page explains the mechanism in plain language, which projects usually qualify, what documents it asks for and why you apply before buying rather than after. Amounts, caps and application windows change with every call, so you read them in the one open when you build your project.
What is Kit 4.0?
It is a public support line aimed at small and medium industrial companies that want to bring technology into their production process. The underlying idea is simple: the programme covers part of the cost of a modernisation project and the company covers the rest with its own funds. That support is not repaid like a loan, but it is not automatic either: you present a project, wait for the evaluation and then execute exactly what was approved. In a warehouse the scope can run from a warehouse management system (WMS: the software that knows where every item is and tells the operator what to do next) to the storage and handling equipment that the change requires. What is in and what is out is defined by the text of the call, not by the supplier or the integrator.
How the mechanism works, step by step
The usual circuit has five stages. First, the company proves it qualifies as a small or medium industrial firm. Second, it builds the project: which problem it solves, what will be bought, what it costs and how long it takes. Third, it files within the window of an open call. Fourth, it waits for evaluation and the formal decision. Only in the fifth stage, with the project approved, does it buy, install and report the spending with invoices. The order matters more than any other detail, because the contribution is calculated on expenses that occur after approval. The percentage covered, the cap per project and the company own share are read in the call that is open when you file: they are not fixed from one edition to the next, and planning them from memory is a bad idea.
Which warehouse projects usually qualify?
The ones that can be told as a process leap, not as an isolated purchase. A project that says “we are buying racking” competes badly. One that says “today we pick with a spreadsheet and a printed route sheet, and with this software and this equipment we move to unit-level control and batch traceability” explains itself and can be measured. Good fits include digitising inventory control, traceability, integration between the warehouse software and the company management system (ERP: the system where sales, purchasing and accounting live) and the equipment that makes that change possible. STOKA builds the technical side: the site survey, the design, the schedule and the itemised budget the project needs. Filing and administrative framing stay with the company and its accountant.
Why you apply before buying, not after
Because the contribution rests on eligible expenses, and an expense is eligible when it occurs inside the period that the approval decision enables. If the purchase order, the advance payment or the invoice predate it, that outlay falls outside the report even if the project is flawless. This is the most expensive and also the most common mistake: the company closes the purchase because a supplier holds a price for a limited time, and later finds out it can no longer count it. The correct sequence is the reverse: first you define and file the project; the purchase order is signed once there is a decision. If the operation cannot wait for the call, you decide without the programme and run the numbers without that income. Buying first and looking for the framing afterwards never works.
What documents does Kit 4.0 ask for?
The exact list is set by each call, but the package repeats itself: registration and proof of status as a small or medium industrial firm, the economic information the form requests, a project memorandum with diagnosis and objective, supplier quotes itemising what is being bought, an execution schedule and an investment plan with the company own contribution identified. The memorandum is the part most often underestimated: it is where you explain the situation you start from and the one you reach, with measurable indicators. A quote without a memorandum is just a price list. It also pays to ask for quotes dated and valid long enough to cover the evaluation period, because an expired quote forces you to redo paperwork right when the file was already moving.
When Kit 4.0 is not the right path
When the project does not stand up without the contribution. A support programme improves a project that already adds up; it does not rescue one that does not. If the numbers only turn positive assuming the grant is approved, what you have is not a fundable project but a project that depends on an outcome you do not control. It is also the wrong path when the warehouse problem is about process rather than equipment: if the mess comes from a poor layout, from locations assigned without criteria or from a receiving routine nobody follows, adding technology with public support leaves the same problem inside, now with more machines. First you fix the process and measure it for a few months. If volume then justifies robotics, the programme makes perfect sense.
How it meets the real project schedule
Payback is calculated using the full investment and your operation’s net savings. Separate genuine expense reductions from capacity available for growth; freeing space or time does not automatically save cash.
What to do with this
Kit 4.0 is good news for a project that already makes sense on its own. The right order is always the same: survey, design, run the numbers and, if they add up, check whether an open call lets you file before buying. Amounts, caps and dates are read in the current call, not in an article. And the framing is confirmed by your company tax and accounting adviser: STOKA contributes the engineering and the technical documentation of the project, not tax advice.
Frequently asked questions
It is an Argentine programme supporting technology adoption in small and medium industrial companies. It covers part of the cost of a previously approved modernisation project, and the company puts in the rest. It is not repaid like a loan, but it does require filing a project, waiting for the evaluation and later reporting the spending with invoices.
It is a bad idea. The contribution is calculated on eligible expenses, and eligible ones occur inside the period enabled by the approval decision. A purchase order, an advance payment or an invoice dated before that decision falls outside the report. The correct sequence is to file the project first and buy afterwards.
The percentage covered, the cap per project and the share the company must put in are set by each call and change between editions. That is why they are not planned from memory: they are read in the text of the call open when you file the project, and confirmed with the company tax adviser.
It depends on how it is framed and on what the current call admits. Projects that show a measurable process leap fit better: moving from manual control to unit-level traceability, integrating warehouse software with the management system, digitising inventory. An equipment purchase without that story competes worse.
The typical package includes proof of small or medium firm status, the company economic information, a project memorandum with diagnosis and measurable objectives, itemised supplier quotes, an execution schedule and an investment plan identifying the company own contribution. The exact list is defined by each call. Ask for quotes valid long enough to cover the evaluation.