ERP ADMINISTRATOR

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Include only sections when posting has real specific content. Must preserve all substantive info. We need to parse the job posting. Let's extract content: Summary Of Position Mission: description: "The Epicor ERP Administrator will take part in implementation and maintenance of Epicor (CMS) v 6.1 ERP system by assisting in training super users on application components, liaison with Century Arms and Epicor for support and projects. This is a full-time, position located in West Palm Beach FL. Relocation assistance is available for the right candidate." That's about the role. Key Responsibilities: multiple bullet-like paragraphs. We need to format as list items under Responsibilities. Responsibilities sections: ERP System Administration, Distribution & Operations Support, Business Analysis & Process Improvement, Reporting & Data Management, ERP Projects & Integrations, User Support & Training, Cross-Functional Collaboration. Each has sub-bullets. We need to preserve all details. Required Qualifications: list of bullet points. Preferred Qualifications: list. Working Conditions: description. Physical Demands: description. Disclaimers: boilerplate, remove. We need to decide which sections to output: About the role (Summary), Responsibilities, Requirements (maybe combine Required Qualifications?), Qualifications (maybe Preferred?), Skills (maybe from required/preferred?), Benefits (Relocation assistance), Pay (none), Schedule (none). Since Pay and Schedule not mentioned, we should not create those sections. Benefits: relocation assistance mentioned. So we can have Benefits section with that. Skills: maybe we can extract from required qualifications: strong knowledge of inventory management, purchasing, order fulfillment, warehouse operations, experience with SQL and ERP reporting tools, proven ability to gather requirements and improve business processes, strong communication, documentation, cross-functional collaboration skills. Those could be Skills. Qualifications: maybe Required Qualifications as Qualifications section. Preferred Qualifications could be another section? But we have only one Qualifications heading allowed? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Requirements and Qualifications separate. So we can have Requirements (maybe required qualifications) and Qualifications (maybe preferred qualifications). Or we could treat Requirements as required qualifications and Qualifications as preferred qualifications. We'll do that. Skills: maybe we can extract specific skill set like Epicor CMS, SQL, reporting tools, etc. But we already have those in qualifications. Might be redundant. However we can still create Skills section listing technical skills: Epicor CMS v6.1, SQL, ERP reporting tools, inventory management, purchasing, order fulfillment, warehouse management, etc. But we need to avoid duplication? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay as long as we preserve info. But we should avoid filler. It's okay to repeat. But we need to decide sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe technical skills), Benefits (relocation assistance). No Pay, Schedule. We must not create sections with filler like "not specified". So we omit Pay and Schedule. Now we need to format. We'll produce:

  About the role

  The Epicor ERP Administrator will take part in implementation and maintenance of Epicor (CMS) v 6.1 ERP system by assisting in training super users on application components, liaison with Century Arms and Epicor for support and projects. This is a full-time position located in West Palm Beach, FL. Relocation assistance is available for the right candidate.

  Responsibilities

  • ERP System Administration
    • Manage day-to-day Epicor CMS 6.1 administration, including user accounts, roles, permissions, and security.
    • Configure and support key modules including Inventory, Purchasing, Sales Orders, Pricing, Warehouse Management, and Financials.
    • Coordinate with Epicor support and third-party vendors on upgrades, patches, and system enhancements.
    • Maintain development, test, and production environments.
  • Distribution & Operations Support
    • Optimize ERP workflows within a manufacturing environment, including:
    • High-volume SKU management and part supersession
    • Vendors lead times and backorder management
    • Manufacturer programs
    • Multi-warehouse inventory management
    • Ensure ERP workflows support fast order turnaround, accurate inventory availability, and efficient logistics operations.
  • Business Analysis & Process Improvement
    • Partner with departments, Epicor and third‑party vendors along with Company Sales, Purchasing, Warehouse, Finance, Customer Service, and Marketing to map business processes.
    • Identify process gaps and operational inefficiencies and support system improvements.
    • Support business requirements into ERP configuration or technical changes.
    • Oversee and maintain process documentation and SOPs.
  • Reporting & Data Management
    • Assist in maintaining dashboards, operational reports, and KPIs.
    • Utilize SQL, and Epicor reporting tools to deliver actionable insights with department needs.
    • Support data imports, exports, and migrations.
  • ERP Projects & Integrations
    • Lead or support ERP enhancement projects, integrations, and module rollouts.
    • Coordinate testing, training, go‑live activities, and change management.
    • Support Epicor and third‑party vendors in integrations with systems such as:
    • Warehouse Management Systems (WMS)
    • EDI systems
    • MRP
    • Shipping/receiving systems
  • User Support & Training
    • Serve as the primary point of contact for Epicor CMS system support.
    • Troubleshoot issues for both remote and onsite users.
    • Develop and deliver ERP training sessions and user onboarding materials.
    • Create training documentation and knowledge base content.
  • Cross‑Functional Collaboration
    • Work closely with business leaders and operations teams to align ERP capabilities with company goals.
    • Collaborate with IT teams on infrastructure, security, and integrations.
    • Facilitate communication between technical resources, users, and external vendors.
  Now Requirements (required qualifications):

  Requirements

  • 3+ years of ERP administration, configuration, or business analysis experience.
  • Hands‑on experience with Epicor CMS (preferred) or similar ERP systems for manufacturing.
  • Experience in manufacturing, high‑volume SKU environments.
  • Strong knowledge of:
  • Inventory management
  • Purchasing and supply chain operations
  • Order fulfillment workflows
  • Warehouse operations
  • Experience with SQL and ERP reporting tools.
  • Proven ability to gather requirements and improve business processes.
  • Strong communication, documentation, and cross‑functional collaboration skills.
  Qualifications (preferred):

  Qualifications

  • Experience with Epicor Business Rules, API, or EDI integrations.
  • Experience with SQL, Crystal Reports or similar.
  • Participation in ERP upgrades, migrations, or implementations.
  • Experience in firearms industry (big plus).
  Skills: maybe we can list technical skills extracted. But we already have many skills in Requirements and Qualifications. To avoid duplication, we could still create Skills section listing: Epicor CMS v6.1, SQL, ERP reporting tools, Crystal Reports, Epicor Business Rules, API, EDI, etc. However that repeats info. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. However it's okay as long as we don't invent or summarize away detail. Duplication preserves detail. But we might be better to not create Skills section if it would be thin. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section because the skills are already covered in Requirements and Qualifications. However the instruction says we can use Skills heading if there is real specific content. We have specific content for skills (e.g., strong knowledge of inventory management, purchasing, etc.) but those are already in Requirements. If we create Skills, we would be repeating. Might be considered thin? Not sure. Given the instruction to prefer few substantive sections, I'd omit Skills section. Benefits: relocation assistance.

  Benefits

  • Relocation assistance available for the right candidate.
  We should not include Pay or Schedule. Now ensure we removed boilerplate: Working Conditions, Physical Demands, Disclaimers. Those are substantive? They are details about work environment. Should we preserve them? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Working Conditions and Physical Demands are substantive. Should we include them? The allowed headings list does not include Working Conditions or Physical Demands. But we could incorporate them into a section like "Working Conditions" but not in allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the allowed headings. It doesn't explicitly forbid other headings, but likely they want only those. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section for Working Conditions if we want, but the heading would not be in the list; maybe they'd consider it not allowed. Safer to stick to allowed headings. Thus we omit Working Conditions and Physical Demands. However that would lose substantive info. But maybe they consider those as boilerplate? Not exactly; they are details about work environment. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Working Conditions is not those. So we should preserve it. But we lack a heading for it. Could we incorporate it into another section like "About the role" or "Responsibilities"? Might be okay to add a paragraph under About the role? But that would mix. Alternatively, we could create a section with heading "Working Conditions" even though not in the example list; the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exhaustive list. So we can use other headings as needed. However they also say "Prefer a few substantive sections over many thin ones." So we could add a Working Conditions section. But we also have Physical Demands. Could combine Working Conditions and Physical Demands into a section "Work Environment". But we need to decide. Given the instruction to preserve ALL substantive information