Warehouse Manager - Industrial Automation
- for any list of duties/requirements/benefits. So each essential function could be a
- with maybe subpoints? The bullet list includes sub-bullets. We can flatten: each main bullet as
- containing the description; sub-bullets could be separate
- inside? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll produce nested lists for clarity.
Then Required Experience, Education and Skills: list of required experience items. That's requirements/qualifications/skills. We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them together. We could split: Required Experience, Education and Skills as Requirements (maybe also Qualifications). Preferred qualifications separate.
We have Preferred: Bachelor's degree..., Lean Six Sigma certification..., Experience in [industry — e.g., distribution, manufacturing, wholesale] environments, Forklift certification or ability to obtain certification.
Physical Requirements: Ability to walk, stand, bend, and lift up to 30 lbs. for extended periods; Comfortable working in a warehouse environment with variable temperatures; Ability to operate warehouse equipment as needed.
Work Schedule: Monday–Friday, 7:00 AM–5:00 PM, with flexibility for operational needs.
What Success Looks Like In This Role: bullet points describing success metrics. Could be under "What Success Looks Like" but not a standard heading; we could treat as part of Responsibilities or maybe a separate section like "Performance Expectations". Not in allowed headings list. Probably we should incorporate into Responsibilities or maybe under "Qualifications"? Better to include as part of Responsibilities (outcomes). But we need to follow instruction: only include sections when posting has real specific content for it. The allowed headings list is just examples; we can also create other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? It says "use
for section headings (e.g. ...)" suggests those are typical but not exclusive? Safer to stick to those headings. We can map content: - About the role: company description + role overview. - Responsibilities: essential functions (leadership, continuous improvement, inventory, SOPs, systems, safety, facilities). - Requirements: required experience, education, skills (the "Required Experience, Education and Skills" list). - Qualifications: maybe the preferred qualifications? Or we could put preferred under Qualifications. - Skills: maybe we could separate skills like ERP, root cause analysis, Excel, communication, etc. But we already have them in Requirements. Could split: Requirements (experience), Qualifications (education/certifications), Skills (technical/soft). Let's do that. - Benefits: none specified (no benefits mentioned). So we should not include Benefits section. - Pay: not specified. So omit. - Schedule: we have Work Schedule. So include Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Check each for real content. About the role: company description + role overview paragraph. Responsibilities: list of essential functions with subpoints. Requirements: "5+ years of warehouse/distribution management experience, including direct people leadership (supervising teams of 8–15+)" etc. That's a list. Qualifications: Preferred: Bachelor's degree..., Lean Six Sigma certification..., Experience in [industry — e.g., distribution, manufacturing, wholesale] environments, Forklift certification or ability to obtain certification. Skills: maybe we can list: Hands-on experience with an ERP/WMS system; Epicor Prophet 21 (P21) experience strongly preferred; Strong root cause analysis and problem-solving skills (5 Whys, fishbone, PDCA, or similar methodologies); Excellent communication, coaching, and accountability-driven leadership style; Proficiency with Microsoft Excel and general office software. Also maybe physical requirements? But physical requirements could be under Requirements or separate. Since physical requirements are not experience/education, maybe they go under Requirements as well. But we already used Requirements for experience list. Could add physical requirements under Requirements as well. However we might want a separate section for Physical Requirements but not in allowed headings. Could include under Requirements. Schedule: Monday–Friday, 7:00 AM–5:00 PM, with flexibility for operational needs. We must not include boilerplate like EEO, accommodation, etc. Now produce HTML fragment. We'll wrap each section in
heading then content. For lists: use
- .
For prose:
. Let's craft. About the role:
Automation & Factory Solutions (AFS), a SunSource company, helps manufacturers improve productivity, efficiency, and performance through innovative automation technologies, industrial products, and engineered solutions. We partner with customers across North America to solve complex manufacturing challenges, optimize processes, and implement safe, efficient solutions tailored to their unique needs. Through our network of local branches, we provide customers with stocking inventory, technical support, training, and dedicated sales teams to keep their operations moving forward.
The Warehouse Manager is responsible for the overall leadership, safety, and operational performance of the Miamisburg, Ohio distribution/warehouse facility. This role owns the day-to-day execution of receiving, put-away, inventory control, order fulfillment, and shipping, while driving a culture of continuous improvement, accountability, and process discipline. The ideal candidate is a hands-on leader who can identify and eliminate operational bottlenecks, drive root cause problem-solving, and deliver consistently accurate inventory — while building the documentation and training infrastructure (SOPs and work instructions) needed to scale a well-cross-trained, accountable team.
Responsibilities: we need to list essential functions. We'll create- with each main bullet as
- . Inside each
- we can have
- for subpoints.
Let's extract:
Leadership & Team Management
- Directly supervise, coach, and develop a team of 10 warehouse associates, including scheduling, performance management, and disciplinary action as needed
- Set clear performance expectations and hold team members accountable to productivity, quality, and safety standards
- Build a culture of ownership, cross-training, and continuous improvement
- Conduct regular one-on-ones, team huddles, and performance reviews
Continuous Improvement & Process Optimization
- Proactively identify operational bottlenecks across receiving, put-away, picking, packing, and shipping processes
- Create a continuous improvement team mindset. Lead & Teach root cause analysis (e.g., 5 Whys, fishbone diagrams) for recurring issues and implement corrective and preventive actions (CAPA)
- Design, implement, and track continuous improvement initiatives using Lean, 5S, or Kaizen principles to improve throughput, reduce waste, and lower operating costs
- Establish and monitor KPIs (e.g., order accuracy, on-time shipment, dock-to-stock time, labor productivity) to measure and sustain improvements
Inventory Accuracy & Control
- Own end-to-end inventory accuracy for the facility, driving toward a best-in-class cycle count process & root cause analysis
- Implement and maintain robust cycle counting programs and reconcile discrepancies in a timely manner
- Partner with Purchasing, Customer Service, and Finance to resolve inventory discrepancies and prevent recurrence
- Ensure accurate, real-time transaction processing within Epicor Prophet 21 (P21), including receipts, transfers, adjustments, and shipments
Standard Operating Procedures (SOPs) & Training
- Optimize, document, and maintain SOPs and work instructions for all core warehouse functions (receiving, put-away, picking, packing, shipping, cycle counting, returns, etc.)
- Build and manage a cross-training matrix to ensure operational coverage, flexibility, and reduced single-points-of-failure across the team
- Use SOPs and work instructions as the foundation for onboarding, ongoing training, and accountability standards
- Regularly audit adherence to SOPs and update documentation as processes evolve
Systems & Reporting
- Utilize Epicor Prophet 21 (P21) as the primary WMS/ERP tool for inventory management, order fulfillment, and reporting
- Generate and analyze reports from P21 to monitor inventory accuracy, order status, and warehouse performance metrics
- Identify opportunities to improve system utilization and data integrity
- Manage NCRs(Non Conforming Receipts) quickly and accurately to ensure supplier operations have accurate date to drive improvements
Safety & Compliance
- Ensure the warehouse operates in full compliance with OSHA regulations and company safety policies
- Lead safety training, incident investigations, and corrective actions
- Maintain a clean, organized, and safe working environment (5S standards)
Facilities & Equipment
- Oversee the maintenance and proper use of warehouse equipment (forklifts, pallet jacks, etc.)
- Manage facility housekeeping, organization, and space utilization for a :20,000 sq. ft. operation.
Note there is a typo ":20,000". We'll keep as is.
Now Requirements: list:
- 5+ years of warehouse/distribution management experience, including direct people leadership (supervising teams of 8–15+)
- Demonstrated experience driving continuous improvement initiatives with measurable results (throughput, cost reduction, accuracy improvements)
- Proven track record of achieving and sustaining high inventory accuracy
- Experience developing SOPs, work instructions, and training/cross-training programs
- Hands-on experience with an ERP/WMS system; Epicor Prophet 21 (P21) experience strongly preferred
- Strong root cause analysis and problem-solving skills (5 Whys, fishbone, PDCA, or similar methodologies)
- Excellent communication, coaching, and accountability-driven leadership style
- Proficiency with Microsoft Excel and general office software
- Ability to walk, stand, bend, and lift up to 30 lbs. for extended periods
- .
For prose:
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll produce nested lists for clarity.
Then Required Experience, Education and Skills: list of required experience items. That's requirements/qualifications/skills. We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them together. We could split: Required Experience, Education and Skills as Requirements (maybe also Qualifications). Preferred qualifications separate.
We have Preferred: Bachelor's degree..., Lean Six Sigma certification..., Experience in [industry — e.g., distribution, manufacturing, wholesale] environments, Forklift certification or ability to obtain certification.
Physical Requirements: Ability to walk, stand, bend, and lift up to 30 lbs. for extended periods; Comfortable working in a warehouse environment with variable temperatures; Ability to operate warehouse equipment as needed.
Work Schedule: Monday–Friday, 7:00 AM–5:00 PM, with flexibility for operational needs.
What Success Looks Like In This Role: bullet points describing success metrics. Could be under "What Success Looks Like" but not a standard heading; we could treat as part of Responsibilities or maybe a separate section like "Performance Expectations". Not in allowed headings list. Probably we should incorporate into Responsibilities or maybe under "Qualifications"? Better to include as part of Responsibilities (outcomes). But we need to follow instruction: only include sections when posting has real specific content for it. The allowed headings list is just examples; we can also create other headings? It says "use
- inside? The instruction: Use