Chestnuts – sustainably wash laundry

The idea of washing laundry with chestnuts initially sounds like a natural home remedy. For operations managers, facility managers and decision-makers in non-profit housing projects or small hotels, however, it is a concrete option: local raw materials can reduce consumption costs, improve environmental metrics and increase supply chain resilience. At the same time, the use of natural extracts introduces new requirements for quality assurance, operations, data management and legal assessment. This article examines mode of action, production, operational integration, scaling issues and a concrete pilot approach.

Washing laundry with chestnuts: Why horse chestnuts and Soapnuts are technically relevant

Chestnuts (here primarily horse chestnuts, Aesculus hippocastanum) and Soapnuts (Sapindus mukorossi) contain saponins—natural molecules that act as surfactants. Surfactants are substances that connect fat and water so that fat particles can be emulsified and released from the fabric. Compared with synthetic surfactants, saponins have lower foam formation, different interfacial tension and higher sensitivity to water hardness (calcium, magnesium) and pH. For operations this means: saponin-based extracts provide adequate cleaning performance but require controlled dosing, pH monitoring and, where appropriate, water softening in regions with hard water.

Standardization of extract production: process and quality specifications

For production-capable operation, an ad hoc ‚brewing‘ approach is no longer sufficient. Define mandatory quality parameters that each batch must meet, for example:

• Saponin concentration (e.g., target range in mg/L or relative unit versus an in-house reference standard)
• pH range (practical target e.g. 5.5–7.5)
• Turbidity/particle content (NTU or solid content in g/L after filtration)
• Microbiological minimum requirement (e.g., mesophilic counts < defined threshold after storage testing)
• Sensory criteria: odour, colour

Plan standardized test protocols: benchmarks with defined textiles and stain types, reference loads with a conventional eco product, and protocols documenting dosage increase where needed. For measurement, small users can suffice with a pH meter, turbidity testing (light transmission) and simple foam standards. Larger users should consider photometric methods or HPLC analyses for saponin quantification.

Raw material acceptance and drying standard

Robust raw material management starts with recording: origin, harvest date, moisture content and visible contaminants. Drying reduces microbial growth and standardizes yield; a storage moisture band (e.g., < 12% residual moisture) is sensible. For collection networks define handover protocols and simple checkpoints before the batch enters production.

Batch traceability and data model

Transparency is important economically and regulatorily. A lean data model can look like this:

• Batch ID (alphanumeric)
• Raw material source / collector / supplier
• Harvest and delivery date
• Drying level / moisture content
• Extraction method and batch size
• Measurements (saponin, pH, turbidity) and release status
• Storage conditions, expiration date, consumption statistics

This data can be maintained in a spreadsheet, a simple LIMS (Laboratory Information Management System) or in your existing operational software. For medium to large operations, integration into the CMMS or BMS (building management system) is recommended: dosing pumps, temperature sensors and alarms should log automatically and trigger alarms when thresholds are exceeded.

Automation: suitable components and interfaces

When scaling, the following components are relevant:

• Batch reactor (20–500 L) with agitator, temperature control and optional heat recovery.
• Mechanical pre-separation (screen) and fine filtration (5–100 μm), possibly membrane filtration for suspended particles.
• Activated carbon or ion-exchange stages for odor reduction and color improvement, if required.
• Peristaltic or metering pumps with flow meters; interfaces: analog 4–20 mA, digital relays or simple switching outputs for washing machine integration.

Pay attention to material compatibility: some rubbers and elastomers react with plant extracts. Use chemically resistant hoses (e.g. PTFE or high-quality silicones) and keep spare wear parts in stock. Document maintenance intervals in the CMMS and store standard operating procedures (SOPs) for replacement and cleaning.

Water hardness, additives and boosters

Water hardness significantly affects saponin performance, because calcium and magnesium partially deactivate surfactants. In regions of medium to high hardness, the following are recommended:

• Water softeners (ion exchangers or chemical softeners) upstream of the machine.
• pH stabilization (if required) using safe, standardized additives.
• A defined booster regime (e.g. oxygen bleach) for heavily soiled or whites-only loads.

A hybrid approach—chestnut extract for the majority of standard washing, boosters as needed—is pragmatic for many organizations and reduces operational risk.

Economics: sensitivity, payback and economies of scale

Economic assessments should cover scenarios: raw material costs (own harvest vs. purchased), energy for extraction, personnel, plant and disposal. Key metrics:

• Unit cost per wash load (material + energy + prorated capital investment)
• Break-even period (annuity calculation for capital costs)
• Rewash rate (costs for re-washing due to insufficient cleaning)
• CO2-equivalent savings compared to the standard product (if available)

Example: At 100 loads/week and material costs of €0.60 per load compared to €1.00 for purchased eco-laundry detergent, an annual savings potential results. Calculate conservatively: additional costs for lab testing, storage, and boosters reduce net benefits. Perform a sensitivity analysis with +/-20% assumptions.

Regulation, wastewater and safety data

Natural products are not automatically regulation-free. Clarify the following points early:

• Discharge to the sewer: municipal regulations may set limits for organic load. Saponins are biodegradable but can cause foaming in wastewater treatment plants.
• Safety data sheet (SDS): prepare an internal SDS with ingredients, toxicological information (horse chestnuts contain toxic glycosides) and handling recommendations.
• Signage and first-aid instructions at production sites.

Carry out a simple wastewater assessment: measure BOD5/COD, foaming tendency and pH before and after treatment. If necessary, install foam separators or post-treatment stages.

Risk analysis: allergies, material compatibility, machine warranty

Key risks:

• Allergens: horse chestnuts can cause skin reactions. Training and personal protective equipment reduce the risk.
• Material attack: long-term use can put greater stress on seals and hoses; plan for a higher replacement frequency.
• Machine manufacturers: check warranty conditions. Some manufacturers require specific approvals for liquid dosing.

Document these risks in your operational risk assessment and define mitigation measures.

Pilot project: detailed KPIs, tests and decision criteria

A structured pilot minimizes estimation uncertainty. Supplement the previously outlined 8‑week plan with clear, measurable KPIs:

• Cleaning performance: share of stains completely removed in the stain catalogue > 85 %
• Rewash rate: target < 3 % (compared to baseline)
• Cost delta per load: target < 10 % compared to reference
• Release time of a batch: time between extraction and availability < 24–48 hours
• Wastewater indicators: BOD5/COD within an acceptable range for local regulations

Test design: run comparative wash lines (A/B test), with one machine using standard detergent and the other running on chestnut extract. Use standardized test textiles (white, colored, synthetic, cotton) and document visually and by measurement.

Training, change management and user communication

Technology alone is not enough. Training content should cover practical SOPs, safety rules, fault scenarios and handling complaints. Communicate to users transparently:

• „Natural alternative; reduced foaming possible“
• Behavior for heavy stains (booster or additional treatment)
• Point of contact for complaints and procedure (rewash protocol)

A change board or stakeholder panel can help resolve acceptance issues and adjust pilot parameters in an agile manner.

Maintenance, hygiene programs and long-term monitoring

Implement a maintenance program with the following elements:

• Filter replacement schedules (e.g. weekly or after tested solids loading)
• Regular flush programs for dosing hoses (thermal or chemical) to prevent biofilm
• Control measurements (pH, turbidity) after every second batch
• Monthly archive review of batch data and cross-check with user feedback

Long-term monitoring should reveal trends: increasing turbidity, clustered complaints or rising maintenance costs are early indicators for necessary process adjustments.

Procurement and seasonal supply

Chestnuts are seasonally available. Strategies:

• In-house collection drives during the season reduce raw material costs and create community engagement.
• Long-term storage as dried raw material or concentrate in small batches.
• Contracts with local collectors or traders for seasonal delivery.

Account for quality differences between harvests: moisture, degradation and origin affect yield and odor. Define delivery conditions in your procurement documentation.

Decision matrix and recommendations for different types of operations

A simple matrix helps with the decision:

• High raw material availability + medium-sized washing volume + willingness to innovate = pilot recommended.
• Large laundries with strict hygiene standards (e.g. hospitals) = hybrid operation or only supplementary use.
• Very small and residential projects = particularly suitable economically and sustainably.

Recommendation: Start with a clearly delimited pilot (building/wing/floor) and expand in stages after achieving the KPIs.

Conclusion: sustainable and operationally viable rather than nostalgic

Washing laundry with chestnuts is more than a nice experiment: with standardized production processes, clear metrics, documented batch traceability and carefully planned automation, it can become a viable, ecological alternative or a meaningful supplement to existing detergents. Crucial are risk analysis, regulatory review and disciplined pilot management. For many small and medium operators a hybrid approach is advisable: chestnut extract for routine loads and standardized booster treatments for special cases.

If you want support in designing operational processes, data modeling for batch traceability or integrating a dosing and monitoring solution into your building technology, contact us. We advise on operating concepts, interfaces and modernization paths.

IT architecture, interfaces and operational reliability

When chestnut extract is integrated into regular laundry operations, the technical integration is often as important as the chemical standardization. IT managers should make architectural decisions that cover automation components, operational data and compliance requirements — from the field to the management level.

A pragmatic architectural principle is: Keep the edge simple, keep the logic central. Edge devices (dosing pumps, flow meters, temperature sensors) collect raw data and perform simple control tasks locally. The overarching control, batch release, long-term archiving and KPI evaluation run centrally in an application that is connected via a standardized API.

• Communication protocols: For new installations use REST‑APIs for batch operations and MQTT/AMQP for low-latency telemetry. Where possible, industry-wide standards like OPC UA are also suitable to facilitate future extensions.
• Time‑Series data: Store sensor data (pH, throughput, temperature, turbidity) in a Time‑Series‑DB with configurable resolutions (e.g. per minute, per batch) and a short-term retention (e.g. 90 days) plus aggregated long-term values for trend analysis.
• Batch data and metadata: Use relational tables for batch IDs, raw material source, measurement values and release status. A hybrid model (SQL for master data, Time‑Series for sensors) is robust and performant in practice.

Security aspects are critical: edge devices must be protected against tampering, telemetry transmitted encrypted (TLS) and APIs equipped with strong authentication (OAuth2 or mTLS). Role-based access control ensures that only authorized personnel can release batches or change dosing parameters. Log data should be audit-proof and record changes to release values in a traceable manner.

For operational stability define SLAs and emergency procedures:

• Fallback rule: If the central server is lost, the edge logic switches to a locally configured emergency mode (e.g. conservative dosing) and continues to record all actions.
• Monitoring & Alerting: Include metrics (e.g. failure rate, deviation of pH values, dosing errors) in your monitoring (Prometheus, Grafana or commercial tools) and configure escalation levels for operators and IT.
• Patch‑ and update strategy: Firmware and software updates for dosing hardware should be signed, staged and tested via CI/CD in staging before they are deployed to production.

Integration details that often delay projects should be clarified early: API contracts (OpenAPI/Swagger), data formats (JSON Schema for batches), timestamp convention (UTC), error codes and idempotent endpoints for repeated calls. Documented simulators for pump and sensor behaviour accelerate tests without interrupting production.

Backup, compliance and data protection should be handled pragmatically: batch and supplier data are generally not subject to special data‑protection requirements, whereas supplier information and contact details are. Define retention periods (e.g. batch data 5–10 years), automate backups and verify recovery times (RTO/RPO) appropriate to operational requirements.

In conclusion: Plan integration tasks as a separate project package with clear acceptance criteria — API tests, failover scenarios, security reviews and a documented rollback. Those who consider these IT aspects from the outset increase availability, traceability and compliance and create a foundation on which biological detergents can be transferred into scalable, secure operational processes.

Operational resilience, secrets and audit evidence

Besides API and telemetry issues, three operational areas are critical: secret management, measurement and reconciliation processes, and audit evidence for audits. Use a central secret management solution (e.g. Vault, Azure Key Vault) for API keys, certificates and dosing configurations; plan automated key rotation and access controls.

Sensors need calibration intervals and a metric reconciliation: compare dosed volumes from the controller with meter readings at the machine in regular batch runs and log deviations as tickets. Implement a Dead‑Letter‑Queue for telemetry failures and a periodic reconcile job that fills in or flags missing measurements.

• Define SLOs for dosing accuracy (e.g. ±5 %) and MTTR for hardware faults.
• Conduct „Game‑Days“ (chaos tests) to verify fallbacks and recovery runbooks.
• Provide exportable audit packages (CSV/PDF) so compliance and supply‑chain evidence can be reviewed quickly.

Discuss project or modernization initiatives with Net-Base.