Part-Time Retail Specialist

We need to output HTML fragment with sections: About Us, Why Join Us?, Job Summary, Essential Functions (maybe with subheadings? but we only use

for section headings). The posting includes headings: About Us, Why Join Us?, Job Summary, Essential Functions, Reasonable accommodations..., Core Functions (list of subfunctions), Requirements, Physical Requirements, Tools And Equipment, Work Environment, Required Skills/Abilities. We need to decide which sections to include based on real content. We must not include sections with placeholder text. All sections have content. We must not repeat job title as heading. No Job ID etc. We need to use

for each section heading. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none obvious. We need to include sections only when posting has real specific content. All sections have content. We need to prefer a few substantive sections over many thin ones. But we must include all headings that have content? The instruction: "Prefer a few substantive sections over many thin ones." Means we could combine related content under fewer headings if appropriate. However we must follow rule: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not strict list. We can choose headings that match content: About Us, Why Join Us?, Job Summary, Essential Functions, Requirements, Physical Requirements, Tools And Equipment, Work Environment, Required Skills/Abilities. But maybe we can combine Physical Requirements and Tools And Equipment under Requirements? However they are separate sections in posting. The instruction says "Prefer a few substantive sections over many thin ones." Could combine but risk losing specificity? Might be okay to keep them separate as they are substantive. We need to output only HTML fragment. Let's structure:

  About Us

  Empire Marketing Strategies has been a leader in delivering exceptional in-store execution for over 40 years, enhancing the customer experience in grocery retail. Operating in all 18 Kroger divisions across the U.S., we partner with some of the world's top brands to optimize their presence in over 2,500 store locations. Our team thrives on tackling diverse challenges in the fast-paced retail industry. We value dedication, talent, and a passion for excellence.

  Why Join Us?

  Flexible, M-F Work Schedule, 9 Holidays off Earn a competitive salary plus 80% employer-covered benefits Full-Time Associates: Eligible for medical, dental, vision, life and AD&D insurance, disability coverage, a retirement program, mental health support, paid time off, and 9 paid holidays annually. Part-Time Associates: Eligible for our retirement program and access to mental health support resources A dynamic work environment where you’ll make a real impact.

  But note: The "Why Join Us?" includes bullet-like sentences but not list. Could keep as paragraph.

  Job Summary

  Empire supports Meat/Seafood, Deli/Bakery, Produce, and Grocery suppliers in the Kroger stores which includes calling on all the stores in assigned territory within the established call frequency. The Retail Specialist will sell and ensure best in class in store merchandising to include building displays, packing out product, and replenishing permanent secondary displays and maintain salability of all authorized items.

  Now Essential Functions: The posting lists "Essential Functions Reasonable accommodations may be made to enable individuals with disabilities to perform these essential functions:" then list: Shelf Maintenance, Product Analysis & Reporting, Promotional Display Maintenance, Customer Support and Training, Other Administrative Duties, Physical Requirements, Core Functions. Actually "Physical Requirements" and "Core Functions" appear as subheadings under Essential Functions. Then under Core Functions they list subfunctions: Shelf Maintenance, Product Analysis & Reporting, Promotional Display Maintenance, Customer Support and Training, Other Administrative Duties. This is confusing. We need to preserve all substantive information. Could treat Essential Functions as a section with subheadings? But we only allowed

  for section headings. Could we use

  for Essential Functions and then within that use

  ? Not allowed per instruction? They only said use

  for section headings (list). They didn't forbid other headings, but to be safe we could avoid other heading levels and just use

  and

  . However we need to represent the list of essential functions. We could output:

  Essential Functions

  • Shelf Maintenance
  • Product Analysis & Reporting
  • Promotional Display Maintenance
  • Customer Support and Training
  • Other Administrative Duties
  But we also need to include details under each essential function (the bullet points under each). The posting includes details for each: under Shelf Maintenance: Rotate product..., Conduct regular checks..., Ensure..., Keep sections..., Maintain 100% distribution..., Sell and service... etc. Under Product Analysis & Reporting: Maintain..., Review..., Maintain..., Report..., Utilization..., etc. Under Promotional Display Maintenance: Set up..., Coordinate..., Execute..., etc. Under Customer Support and Training: Establish..., Perform..., etc. Under Other Administrative Duties: Timely communication..., Maintain..., Attend..., Exercise..., Other duties as required. Thus we need to preserve those details. Could make each essential function a subheading? But we only have

  . Could we use

  for each essential function? That would be many sections but maybe okay. However instruction: "Prefer a few substantive sections over many thin ones." So maybe we should keep Essential Functions as a section and within it use

  • where each
  • contains a

    with details. That is acceptable: list items can contain paragraphs. Thus:

    Essential Functions

    • Shelf Maintenance: Rotate product as required by manufacturer for perishable merchandise and for merchandise requiring freshness checks. Conduct regular checks of store shelf tags to ensure continued distribution and assist with reordering of product. Ensure that all retail objectives and shelf standards are met and maintained in assigned territory. Keep sections set to customer’s schematic or stocking plan as is required or beneficial to manufacturer or clients. Maintain 100% distribution of all manufacturer-client products approved by the Kroger family of companies or Planogram (POG) team. Sell and service all principal accounts represented by Empire to ensure all the authorized items are on shelf and priced and tagged properly.

    • Product Analysis & Reporting: Maintain and update all territorial records. Carefully review all sales reports to maintain awareness of progress toward assigned goals. Maintain competitive awareness and promptly report all information through proper channels. Report completely and on time using forms supplied and with the frequency requested. Utilization of reporting tools such as PowerBI or Go Spot Check to report on specific goals and targets.

    • Promotional Display Maintenance: Set up displays of manufacturer or client brands while working within the guidelines of customer regulations and manufacturer/client display objectives. Coordinate activities and cooperate with Operations regarding the execution of promotional programs, including reporting and future order requirements. Execute point-of-sale material and Instant Redeemable Coupons to stores as required by the manufacturer or client and approved by the retailer.

    • Customer Support and Training: Establish and maintain rapport with all store personnel in assigned territories. Perform training demonstrations for customer employees regarding proper preparation and/or display of product.

    • Other Administrative Duties: Timely communication requirements including email and telephone. Maintain territory files and company owned office equipment. Attend and participate in all scheduled company meetings. Exercise expense control within guidelines. Other duties as required.

    Now after Essential Functions, the posting includes "Physical Requirements" and "Core Functions" but we already covered core functions as the list above. Actually the "Physical Requirements" appears as a separate heading after Essential Functions. Then "Tools And Equipment", "Work Environment", "Required Skills/Abilities". Also there is a "Requirements" section earlier: Education and Experience, etc. Thus we need sections: Requirements, Physical Requirements, Tools And Equipment, Work Environment, Required Skills/Abilities. We must not include Pay or Schedule unless stated. The posting mentions schedule: "The expected schedule is 15–24 hours per week." That's schedule info. Should we include a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule: expected schedule 15–24 hours per week. Also mentions "Flexible, M-F Work Schedule, 9 Holidays off" under Why Join Us?. So we have schedule info. Should we create a Schedule section? The instruction says prefer few substantive sections over many thin ones. We could incorporate schedule info into Why Join Us? or Job Summary? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid including them if they exist; it says do not create them unless posting actually states them. So we can include a Schedule section if we want, but we should prefer few sections. Since we already have schedule info in Why Join Us? (Flexible, M-F Work Schedule, 9 Holidays off) and also explicit expected schedule 15-24 hours per week, we could add a Schedule section to capture that detail. However we might just keep schedule info in Why Join Us? and not create a separate Schedule section to keep few sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to avoid extra Schedule section if we can incorporate schedule info elsewhere without losing detail. The schedule detail is specific: expected schedule 15–24 hours per week. The Why Join Us? mentions flexible M-F schedule and 9 holidays off but not the hours. So we could add that detail to Why Join Us? paragraph. Thus we can update Why Join Us? paragraph to include: Flexible, M-F Work Schedule, 9 Holidays off; expected schedule 15–24 hours per week; earn a competitive salary plus 80% employer-covered benefits; etc. Now Benefits: The posting mentions benefits: Full-Time Associates: eligible for medical, dental, vision, life and AD&D insurance, disability coverage, a retirement program, mental health support, paid time off, and 9 paid holidays annually. Part-Time Associates: eligible for retirement program and access to mental health support resources. Also earlier: "earn a competitive salary plus 80% employer-covered benefits". So we have benefits info. Should we create a Benefits section? The instruction says prefer few sections; we could incorporate benefits into Why Join Us? or maybe a separate Benefits section. Since we already have Why Join Us? covering some benefits, we could add benefits details there. However the Benefits section would be substantive; but we already have many sections. Let's see count: About Us, Why Join Us?, Job Summary, Essential Functions, Requirements, Physical Requirements, Tools And Equipment, Work Environment, Required Skills/Abilities. That's 9 sections. If we add Benefits, that's 10. Could we merge Benefits into Why Join Us? to reduce sections? The Why Join Us? currently includes flexible schedule, holidays, competitive salary plus 80% employer-covered benefits, full-time benefits list, part-time benefits, dynamic work environment. That already covers benefits. So we can keep Why Join Us? as is and not create separate Benefits section. Pay: The posting mentions "competitive salary" but no specific numbers. Not to create Pay section unless stated; we have mention but not specific. Could incorporate into Why Join Us? as we already did. Thus we will not create separate Pay, Schedule, Benefits sections. Now we need to include Requirements section: Education and Experience