Returned-jar zone
Provide receiving, draining, sorting, reject storage and wash entry without routing returns through clean storage.
Factory planning for water bottling projects
Returnable containers create a different factory
A 5 gallon water bottling plant joins a returnable-container operation to water treatment, washing, filling, capping and delivery handling. Its layout needs a returned-jar intake and a protected clean route; its production plan needs enough suitable jars circulating through customers, transport and the factory.
Answer first
Add returned-jar receiving and inspection, removal of old closures, the appropriate external/internal washing route, protected transfer to filling and new closures, then coding and dispatch handling. Provide washing services, drains and segregated container movement. Balance output against washer duty and the complete jar-return cycle: a faster filler cannot replace containers that are still with customers.

01
A volume label such as 18.9 L, 19 L or 20 L does not prove mechanical compatibility. Use the actual container and closure. The routes below keep reusable-container cleaning and protected handling visible without prescribing a wash recipe.
| Incoming population | Production route | Equipment and site implication | Boundary that matters |
|---|---|---|---|
| Suitable returned jars from the managed fleet | Inspect, remove old closure, apply the selected wash/disinfection and rinse process, then protected filling and new closure | Receiving/sorting, decapping and washing duties, clean transfer, compatible filler/capper and wash services | Keep dirty intake and waste movement separate from the cleaned-container and product route |
| New jars introduced to the same fleet | Inspect and apply the preparation appropriate to their condition before filling | A protected new-jar supply route and handling parts compatible with the actual jar | New containers do not eliminate inspection or the agreed hygiene controls |
| Damaged, unsuitable or suspect-history returns | Segregate for the defined rejection or evaluation process; do not feed them as accepted stock | A separate holding/reject area and a route out of production | Washing equipment is not evidence that every returned jar is safe to reuse |
| Filled, closed jars ready for delivery handling | Code and apply the selected sleeve, bag, rack or other dispatch arrangement | Compatible conveyors/handling, staging and delivery access | Keep released product separate from returned jars and maintain batch identity |
02
Illustrative steady-state arithmetic: assume average dispatch of 400 jars per calendar day and a complete dispatch-to-next-dispatch cycle of 5 calendar days. The cycle includes customer holding, return transport and factory turnaround. It is not just the time outside the factory.
| Planning case | Calculation or stock treatment | What the result tells you |
|---|---|---|
| Base circulating serviceable jars | 400 jars/day × 5 days = 2,000 jars | The assumed steady-state route ties up this base stock across customers, transport and the factory |
| The complete cycle extends to 7 days | 400 × 7 = 2,800 jars; 800 more than the 5-day case | Slower returns increase the stock needed for the same dispatch rate without changing filler speed |
| Quarantine, damage and permanent losses | Exclude unavailable jars from the serviceable pool; plan replacement separately | A physical stock count can overstate the jars available to support production |
| Delivery peaks and uncertain returns | Add a separately justified usable buffer to the base case, using the actual route variation | The average-cycle example is not a peak-stock guarantee or a recommended buffer percentage |
| Washer and dispatch balance | Compare accepted-return arrival, wash output, filling, rack handling and deliveries on the same calendar | Increase the limiting duty or improve the return cycle before increasing only filler speed |
03
The layout should prevent uncontrolled crossings by containers, water, people, tools and vehicles.
Provide receiving, draining, sorting, reject storage and wash entry without routing returns through clean storage.
Define the controlled boundary between dirty operations, final rinse and the protected filling area.
Protect caps, sleeves, bags and cleaned racks from returned containers and wash chemicals.
Remove damaged jars, old caps, labels, debris and wash discharge without crossing released product.
04
Returned containers require explicit rejection rules, wash controls and traceability before startup.
| Control | Question to close | Project output |
|---|---|---|
| Jar acceptance | Which damage, odor, residue or history makes a jar unacceptable? | Inspection and rejection standard |
| Wash process | Which sequence, conditions and checks demonstrate the intended cleaning result? | Validated procedure and operating limits |
| Filling hygiene | How are clean transfer, caps, room access and sanitation controlled? | Hygiene and monitoring plan |
| Line acceptance | Which returned-jar condition, product, duration and measurements form the test? | FAT/SAT basis and records |
R
Reviewed 9 September 2026. Codex supports inspection, appropriate container preparation and protection before filling for drinking waters other than natural mineral waters. It is not a machine-compatibility or wash-performance certificate. The jar-cycle example is planning arithmetic, not a measured customer operation.
Buyer questions
They usually refer to a similar returnable large-container market, but actual jar volume, neck, cap, material and equipment compatibility must be confirmed from samples or drawings.
Not as a normal format change. Returnable jars use different handling, washing, filling, capping, layout and logistics systems.
Returned-jar condition, sorting, washing, treatment water, clean transfer, rack handling, delivery cycles and available jar inventory can all become constraints.
Send jar and cap samples or drawings, expected return condition, target hourly and daily output, treatment basis, packaging route, site data, utilities, destination and required services.
Move this project question forward
The layout should prevent uncontrolled crossings by containers, water, people, tools and vehicles.
Not sure which data matters? Send what you have and state the decision you need to make.
Send target capacity and SKUs, source-water report, site utility schedule, building layout and required project milestones.
The project desk can identify missing inputs and a practical next step. Final engineering, configuration, compliance and commercial terms remain project-specific.
Allot Tech (Suzhou) Co., Ltd. · sales@allottech.com · Project telephone: +86 186 6213 1120 / +1 818 262 0958