Donations arrive in odd lots, equipment goes out on loan to program participants, and at grant time somebody has to prove where it all went. Knowledge ERP keeps the paper trail as a side effect of doing the work.
The donation nobody priced
Commercial inventory software assumes every item arrived on a purchase order with a price on it. Nonprofit inventory does not work that way. A pallet of coats shows up from a drive. A hospital clears out a storeroom and gives you forty walkers. Someone drops off three laptops that are two years old and perfectly fine.
None of it has a cost basis, and all of it has to be counted anyway, because your auditor and your Form 990 both want a number for in-kind contributions.
Knowledge ERP lets you receive stock without a purchase order and put your own value on it. Add custom fields for the donor, the drive it came from, the condition it arrived in and the valuation method you used, and those fields stay attached to the item for as long as you hold it. When the auditor asks how you arrived at $4,200 for the coat drive, the answer is on the records rather than in someone's memory.
Items that arrive together stay together. Receive the coat drive as one lot and you can still see, months later, which coats came from it and where each one went.
What the grant report actually asks for
Most funders want two things you cannot get from a stock count: who received the goods, and whether those people match the population you said you would serve.
That is a reporting problem more than an inventory problem, and it is where general-purpose inventory tools stop being useful. Knowledge ERP puts custom fields on people as well as on things. Service area, program, referral source, eligibility category, household size, whatever your grant agreement specifies. The fields live on the recipient record and come through into reporting alongside the items they received. We wrote about what that looks like in practice, including the board report side of it.
The same fields can go on a public questionnaire, so intake happens before someone is standing at your counter with a clipboard in their hand. Appointments feed the questionnaire, the questionnaire feeds the record, and the record feeds the report.
Every edit is logged with who made it and when, including changes made through the API. That log is the thing an auditor is really asking for when they ask how you know a number is right.
- Equipment loans with reserve, check-out, return and due-date reminders, at no charge to the borrower
- Custom fields on people and items, surfaced on public questionnaires
- Lot and expiry tracking for food and supply distribution
- Movement log showing every donation in and distribution out
- CSV import for the spreadsheet you are graduating from
Equipment that goes home with people
Lending programs are the case that breaks most systems. A medical equipment loan closet, a laptop program, a tool library and a durable goods bank all have the same shape: an item leaves the building, a specific person has it, and it is supposed to come back.
Knowledge ERP tracks that as a loan rather than a sale. Reserve an item, check it out to a named person, set a due date, and send reminders as it approaches. Nothing is charged, because a loan and a rental are different things and the loan side does not assume money changes hands.
Because the item is tracked at the unit level rather than as a quantity, you can answer the question that matters when something goes wrong: not how many walkers you have, but where walker number seven is, who has it, and since when. Serial numbers, asset tags and barcodes all work as lookups.
Stock that expires
Pantry and hygiene distribution has a constraint retail does not: some of the stock goes bad, and giving out expired goods is worse than giving out nothing.
Lot and expiry tracking is built in. Receive a donation with an expiration date, and the system knows what is aging. Expiring stock surfaces before it becomes waste rather than after, and if a product is recalled you can trace the lot to the distributions it went to instead of guessing.
Storage locations and bins map to how the space is actually organized, which matters when the shelf, the walk-in and the offsite storage unit all hold some of the same item.
Volunteers change every semester
The people doing the counting are often not staff. They turn over, they work one shift a week, and they should not have access to everything.
Roles can be scoped to a location, so a volunteer at the north site sees the north site. Someone who only receives donations does not need to see the distribution history, and someone doing a count does not need to change valuations. The permission model is granular enough to be useful without becoming a project to configure.
Barcode labels do most of the work of making a volunteer accurate on their first shift. Scan the shelf tag, scan the item, count what is there.
Getting off the spreadsheet
Almost every nonprofit we talk to is running some version of the same spreadsheet, and it usually works fine until two people need it at once, or until the person who built it moves on.
Import what you have as CSV. Rows that fail come back named, with the reason, so a messy export is something you fix rather than something that silently drops half your inventory. Start with one location and one program if that is easier, and add the rest once the shape is right.
You do not have to buy modules you will not use. Inventory on its own covers receiving, counting, lending and distribution. Appointments adds scheduling and intake questionnaires if you need them. Nothing else is required.
A 5-person team with Inventory pays $139 a month
$89 for the module plus five Starter seats at $10. Annual billing takes 10% off. See pricing.