The operations platform behind Kansas City's diaper bank

HappyBottoms operations dashboard with a warehouse selector, inventory and partner tiles, orders awaiting fulfillment, a size-level inventory table, tasks, and notifications.
The command center. A chosen warehouse, inventory, children served, active partners, and orders awaiting fulfillment sit with tasks and notifications. Staff can show, hide, and reorder the board.
HappyBottoms report library with client, partner, distribution, inventory, and supplier reports, plus saved generated reports.
Reports. Client, partner, distribution, inventory, and supplier reports sit in one library, and a saved report can be opened again without rebuilding it.
Symfony
Finished the inherited Drupal work
Laravel
The platform now rolling out
Partners
Agencies and hospitals in one network
Ongoing
A four-month finish became a partnership

About the Client

HappyBottoms is Kansas City's diaper bank. Since 2009 it has worked to close the diaper gap for families in the metro area. HappyBottoms states the mission on its site: collaborate with the community to empower, connect and impact families by alleviating diaper need.

On its FAQ, HappyBottoms says it collaborates with more than 70 social service agencies and area hospitals. Eligible families can receive 75 disposable diapers or 50 training pants per month through those partner agencies. Bundles of Joy is the hospital program for newborns.

That network is an operation: clients and eligibility, partner agencies, warehouse inventory, incoming supply, distributions, and reporting. Active Logic first took over an unfinished platform and rebuilt it on Symfony. The platform now rolling out is a ground-up rebuild of that same operation, started in 2026, on Laravel and Vue.

The Challenge

HappyBottoms came to Active Logic with an incomplete inventory management system. The previous development partner had left critical work unfinished, and the organization did not have the tools it needed to run a partner-based diaper operation efficiently. The existing codebase was Drupal and needed significant rework.

They needed a partner who could take the project over, finish what was outstanding, and build a system around how a non-profit diaper bank actually works: eligibility and child records, partner agencies and hospitals, expiration and size, incoming donations and purchases, warehouse inventory, and the reports funders and staff rely on.

Immediate priorities for that first phase:

  1. Finish and stabilize the inherited work. Complete what was left unfinished before adding new scope.
  2. Migrate off Drupal. Move onto a foundation that can carry the workflows HappyBottoms actually runs.
  3. Build for the real operation. Partners, eligibility, sizes, expirations, supply, and reporting, not a generic inventory app.

The Symfony application that came out of that work is what the organization has run. In 2026 Active Logic started a ground-up rebuild on Laravel 13 and Vue 3. The platform now rolling out brings intake, warehouse inventory, partner ordering, distributions, eligibility, reporting, and communication into one modern system.

The Platform

Active Logic took over the codebase and migrated the first platform from Drupal to Symfony. That phase shipped one web application for the operation. The current phase is the Laravel and Vue platform now rolling out. Staff start from the dashboard above: a chosen warehouse, inventory, children served, active partners, orders awaiting fulfillment, tasks, and notifications. Staff can show, hide, and reorder those widgets, and the layout is saved for them.

The pairs below are the rest of the operation. The line under each screen is the job it does.

A child record holds the assigned partner, distribution tracking, and a QR client card. Age eligibility and distribution eligibility are calculated on the profile, with days remaining and a flag for whether the record is on track. Daily jobs expire records that have aged out and lift overrides that have lapsed. Staff can override a date when documentation is on file. At a pickup, scanning the card opens the family and whether they are still eligible.

Partner agencies and hospitals sit on one list, with a fulfillment period for how each site receives diapers. Partner staff work in the same system, limited to their own clients, orders, and distributions. Roles decide who can change a record and who can only read it.

Four order types carry the product. A partner order is a site requesting stock from the bank. A supply order receives donations and purchases into a warehouse. A transfer order moves stock between warehouses. An adjustment order corrects a count for damage, loss, or a miscount. Distributions record what a partner actually handed to a family. An inventory ledger sits behind every receipt, shipment, transfer, and adjustment, so on-hand and available quantities come from the same history. A received supply order stores each size with a quantity and a unit cost. The catalog runs from Newborn through Size 7 and pull-ups, with agency packs and hospital packs, so size matching follows how partners and hospitals give diapers out.

Client, partner, distribution, inventory, and supplier reports live in one library. People can build, save, and share a custom report, and the main lists export to Excel or CSV. A mailbox lets staff write to partners, guardians, and coworkers, start from a template, and keep replies on the same thread. The interface ships in English and Spanish, and staff can edit those translations in the app.

Sign-in supports passkeys and two-factor authentication. Changes on major records are written to an audit trail. An import pipeline brings clients, partners, inventory, and the rest of the legacy system across, then checks the result against record counts.

HappyBottoms client roster with search, status, partner, expiration, age, and ZIP filters, and an eligibility flag on each child.
01. The client roster. Staff search and filter the children served through partner agencies, see who is eligible, and open a record without leaving the workflow.
HappyBottoms child profile with age and distribution eligibility dates, an assigned partner, distribution tracking, and a QR client card.
02. One child record. Age and distribution windows, the assigned partner, distribution tracking, and a QR client card for pickup sit on a single profile.
HappyBottoms partner list of agencies and hospitals, with type, fulfillment period, and status for each site.
03. The partner network. Agencies and hospitals, the fulfillment period for each site, and status are managed in one list.
HappyBottoms supply orders with supplier, receiving warehouse, status, line items, and received date.
04. Supply orders. Donations and purchases are received into a warehouse, with supplier, status, and the date each order was received.
A received HappyBottoms supply order with a quantity and unit cost for each diaper size.
05. A received order. Each size lands with a quantity and a unit cost, so the warehouse can see exactly what came in.
HappyBottoms product catalog from Newborn through Size 7 and pull-ups, with agency packs and hospital packs.
06. The catalog. Newborn through Size 7 and pull-ups, with agency packs and hospital packs, so distribution matches how partners and hospitals actually give diapers out.

One Path

Leaders do not need a system diagram. They need to see that enrollment, supply, distribution, and reporting are one operation. HappyBottoms runs that work in five steps.

  1. 01

    Enroll. A child is enrolled and assigned to a partner. Partner staff work their own clients in the same system.

  2. 02

    Eligibility. Age and distribution windows live on the record. A QR client card is what staff scan at pickup.

  3. 03

    Receive. Supply arrives from donors and vendors and is received into a warehouse, with the ledger behind the count.

  4. 04

    Distribute. Partner orders and distributions move product to families, and eligibility is checked at the handoff.

  5. 05

    Report. The library, custom reports, and spreadsheet exports show what moved and what remains.

How We Work

Active Logic took over an incomplete build, finished the inherited work, and remained on as the engineering partner. The first engagement ran four months. It became an ongoing partnership. That partnership is now rolling out the Laravel and Vue platform as the HappyBottoms operation grows. The engineers are senior and 100% U.S.-based.

The Outcome

Active Logic delivered 100% task completion on the inherited codebase and consolidated the work into one Symfony web application. Tens of thousands of diapers have been donated through the system since launch. A four-month engagement to finish incomplete work became an ongoing partnership. The platform now rolling out is the ground-up Laravel and Vue rebuild of that operation, and Active Logic continues to build it as the HappyBottoms operation grows.

Technology

The platform now rolling out is Laravel 13 and Vue 3, with TypeScript on the front end, PostgreSQL for the data, and Tailwind for the interface. Automated tests run in Bitbucket Pipelines. The first phase remains part of the story: PHP on Symfony, after the inherited Drupal codebase.

Built by Active Logic, a U.S.-based custom software development company with 200+ projects delivered since 2014.

Get your project scoped

Schedule a call with a knowledgeable team member about a platform that has to match how your organization actually works.