Storeman

for intro paragraphs and general text,

for section headers,

• for list items. Must preserve all original content word-for-word, no additions, deletions, rephrasing. Must not add any extra commentary. Must not use
  ,
  , inline styles, CSS classes. Must not use markdown fences. Just raw HTML. We need to identify sections: likely headings like "Minimum Requirements:", "Duties & Responsibilities:" etc. Use

  for section headers. The original text includes "Minimum Requirements:" then list items? Actually it's a paragraph with bullet-like items separated by spaces. But we need to preserve word-for-word. However we can convert list items into

  • . The instruction: Use
    • for list items (duties, requirements, qualifications, skills). So we should treat the content under "Minimum Requirements:" as a list? It is not bullet points but we can still wrap each line? The original text: "NQF Level 4 Grade 12 or Matric Equivalent Certificates or N (C) V Level 4 Cost & Inventory certificate / Stores & Inventory certifictae / Any related supply chain or procument certificate 2-5 years experience in Stores Operations and stock Management 2-3 years supervisory experience within the stores department". That's a long sentence. Probably we should keep as a paragraph, not list. But the rule says use
      • for list items (duties, requirements, qualifications, skills). If there are no explicit list items, we can just keep as paragraph. However the "Duties & Responsibilities:" section contains many items separated by periods and maybe bullet-like. We can split into
      • items? But must preserve word-for-word. If we split into separate
      • items, we would be adding line breaks and bullet markers, but we are not adding new content, just reorganizing? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". So we cannot change the text. We can only wrap existing content in tags. If we split a paragraph into multiple
      • items, we would be altering the text (adding line breaks, maybe extra punctuation). That would be considered adding? Not adding new words, but we would be breaking the paragraph into separate items, which changes the structure but not the words. However the instruction says "do not add, remove, summarise, or rephrase". Breaking into separate
      • items might be considered rephrasing? It might be okay if we just wrap the whole block in
        • ... but the content includes periods and maybe multiple sentences. We could treat the whole block as a single
        • item? But
          • expects list items; we could have a single
          • containing the whole paragraph. That would preserve the text exactly. That seems safe. Thus we can have:

            Minimum Requirements

            NQF Level 4 Grade 12 or Matric Equivalent Certificates or N (C) V Level 4 Cost & Inventory certificate / Stores & Inventory certifictae / Any related supply chain or procument certificate 2-5 years experience in Stores Operations and stock Management 2-3 years supervisory experience within the stores department

            But the heading should be

            Minimum Requirements

            (no colon?). The original has "Minimum Requirements:" with colon. Should we include colon? The heading text should be exactly as appears? The rule: Use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we can use "Minimum Requirements" without colon? The example includes "Requirements". Probably we should use the heading text without colon. But must preserve original content word-for-word? The heading is part of the content. The original has "Minimum Requirements:" with colon. If we output

            Minimum Requirements

            we are removing the colon. That would be removing a character, which is a change. Must preserve all original content word-for-word. So we need to include the colon? The heading should be exactly "Minimum Requirements:"? But the example says "Requirements" without colon. However the instruction says preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase. So we must keep the colon. But we also need to use

            for section headers. So we can put

            Minimum Requirements:

            . That includes the colon. That matches original text exactly (including colon). Good. Similarly "Duties & Responsibilities:" includes colon. So we can use

            Duties & Responsibilities:

            . Now the content under that heading is a long paragraph with many sentences separated by periods. We need to preserve word-for-word. We can wrap the entire block in

            ... but the rule says use

            • for list items (duties, requirements, qualifications, skills). The "Duties & Responsibilities:" section contains duties and responsibilities. It might be considered a list. But we cannot add bullet points or split sentences. We could treat the whole block as a paragraph. That would be okay. But maybe we can split into
            • items by preserving the original sentences? That would require adding line breaks and maybe extra punctuation? Actually we could wrap each sentence as a separate
            • but that would add
            • tags and maybe extra punctuation? The original sentences end with periods. If we put each sentence inside
            • , we would have to separate them with line breaks, but that would be adding new markup, not new words. The content inside
            • would be the sentence text. That would preserve the words. The only change is adding
            • tags and maybe line breaks. That's allowed? The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". Adding tags is not part of the content; it's markup. So it's okay. But we must not alter the text inside. So we could split the block into multiple
            • items each containing a sentence (including the period). That would be preserving the words. However the original block is a single paragraph with many sentences separated by spaces? Actually it's a long paragraph with many sentences separated by periods and spaces. Let's examine: "Liaising with supply chain teams to ensure timeous delivery of materials, both ingredients and packaging. Receiving and off-loading all incoming materials. Uphold Safety, Good Housekeeping and GMP standards as per requirements. Communication with Contractors, Suppliers, Buyers and Production Accuracy of information captured in Syspro Timeous releasing of Finished Goods through liaising with quality teams. Control of stock on hold. Inspection of material received from contractors and Suppliers, returns from production. Ensure First Expired, First Out (F.E.F.O) stock management is maintained. Ensure all material movements from and to Supplier/ Production/Daily, weekly, and monthly stock counts. Accurate stock control and issuing. Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro. Making effective decisions and solving problems. Assigning tasks and responsibilities to others. Developing a sense of unity and collaboration among team members. Demonstrating professional behavior and attitudes. Understanding how different functions within an organization interact. Maintaining high standards of accuracy in administrative tasks to avoid errors that could impact customers and production." That's a series of sentences separated by periods. Some have extra characters like "7\]\]098." maybe a typo. We need to preserve exactly. So we could split into
            • items each sentence. But that would add
            • tags and maybe line breaks, but not alter the sentence text. That seems permissible. But the instruction: "Use
              • for list items (duties, requirements, qualifications, skills)". So we should use
                • for list items. The "Duties & Responsibilities:" section is a list of duties. So we should output:

                  Duties & Responsibilities:

                  • Liaising with supply chain teams to ensure timeous delivery of materials, both ingredients and packaging.
                  • Receiving and off-loading all incoming materials.
                  ...
                  But we must preserve the original text word-for-word. The original includes "7\]\]098." which seems like a stray artifact. It appears after "dispatch advices." Actually the original: "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." There's a weird "7\]\]098." maybe a formatting artifact. We must preserve it exactly. So we need to include that exact string as part of the text. So we need to split accordingly. Thus we need to parse the block and split into sentences exactly as they appear, including the stray "7\]\]098." as a separate sentence? It appears after a period: "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is "7\]\]098." as a separate token? Actually it's "7\]\]098." with no space before? The original shows "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is "7\]\]098." directly after "advices." with no space? Might be a formatting artifact. We must preserve it exactly. So we could treat "7\]\]098." as part of the same sentence? It is attached to "advices." with no space? Actually there is a period after "advices", then "7\]\]098." then a period? Let's read: "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is "advices.7\]\]098." then a space then "Receive". So the string "7\]\]098." is a separate token with a period at end? Actually it's "7\]\]098." includes a period at the end? The original shows "7\]\]098." then a period? Wait there is a period after "098"? The snippet: "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So after "advices." there is "7\]\]098." then a period? Actually there is a period after "098"? The text shows "7\]\]098." then a period? Let's parse: "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is "advices." then "7\]\]098." then a period? Actually there is a period after "098"? The snippet shows "7\]\]098." then a period? The text shows "7\]\]098." then a period? It's ambiguous. But we must preserve exactly as given. So we will keep the exact substring "7\]\]098." as part of the text. So we can split into sentences: "Complete and file dispatch advices." then "7\]\]098." then "Receive, mark and allocate materials into the correct bin locations as per Syspro." But the original has "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is no space between "advices." and "7\]\]098."? Actually there is a period after "advices", then "7\]\]098." then a period? Let's assume it's "Complete and file dispatch advices.7\]\]098. Receive, mark and allocate materials into the correct bin locations as per Syspro." So there is "advices." then "7\]\]098." then a space then "Receive". So we can treat "Complete and file dispatch advices." as a sentence, then "7\]\]098." as a sentence (just that token), then "Receive, mark and allocate materials into the correct bin locations as per Syspro." as a sentence. That preserves the exact characters. Thus we need to split the block into sentences exactly as they appear, preserving punctuation and spacing. That is tedious but doable. Given the complexity, maybe it's simpler to keep the entire block as a single

                  paragraph, not using

                  . The rule says use
                  • for list items (duties, requirements, qualifications, skills). It doesn't mandate that we must use
                    for duties; it's recommended but not required? It says "Use
                    • for list items (duties, requirements, qualifications, skills)". So we should use
                      • for list items. The duties section is a list of duties, so we should use
                        • . So we need to convert the duties into list items. But we must preserve word-for-word content. We can split into
                        • items each containing a sentence (or phrase) exactly as appears. That is permissible. Thus we will produce:

                          Duties & Responsibilities:

                          • Liaising with supply chain teams to ensure timeous delivery of materials, both ingredients and packaging.
                          • Receiving and off-loading all incoming materials.
                          • Uphold Safety, Good Housekeeping and GMP standards as per requirements.
                          • Communication with Contractors, Suppliers, Buyers and Production Accuracy of information captured in Syspro Timeous releasing of Finished Goods through liaising with quality teams.
                          • Control of stock on hold.
                          • Inspection of material received from contractors and Suppliers, returns from production.
                          • Ensure First Expired, First Out (F.E.F.O) stock management is maintained.
                          • Ensure all material movements from and to Supplier/ Production/Daily, weekly, and monthly stock counts.
                          • Accurate stock control and issuing.
                          • Complete and file dispatch advices.
                          • 7\]\]098.
                          • Receive, mark and allocate materials into the correct bin locations as per Syspro.
                          • Making effective decisions and solving problems.
                          • Assigning tasks and responsibilities to others.
                          • Developing a sense of unity and collaboration among team members.
                          • Demonstrating professional behavior and attitudes.
                          • Understanding how different functions within an organization interact.
                          • Maintaining high standards of accuracy in administrative tasks to avoid errors that could impact customers and production.
                          But we must preserve the original text exactly, including punctuation and spacing. The original sentences may not have trailing spaces. The above includes periods at end of each sentence. That's fine. Now the "Minimum Requirements:" section: It is a single paragraph with no bullet points. We can wrap it in

                          . That's okay. Now the rest of the job description: There is "Company:" etc. The raw text includes "Company:" line, "RCL Foods". Then "Functions:" etc. We need to preserve all original content word-for-word. The instruction: "Return ONLY the HTML. No markdown fences, no explanation, no preamble." So we need to output HTML that includes all the original content? The job description includes many lines: "Company:", "Functions:", "Job Type Classification:", "Permanent", "Location - Town / City:", "Molteno", "Job Description:", then the description paragraph, then "Minimum Requirements:", then the paragraph, then "Duties & Responsibilities:", then the list. We need to output HTML that includes all that content, structured with appropriate tags. The instruction says "Use

                          for introductory paragraphs and general text". So we can wrap the initial lines (Company, Functions, Job Type Classification, Location ...) as paragraphs. Then "Job Description:" maybe a heading? It is not a section header like responsibilities; it's just a label. Could be a heading? Not listed in allowed headers. The allowed headers are examples: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. "Job Description:" is not in that list, but we can treat it as a paragraph? It might be a section header but not required to be

                          . The rule: Use

                          for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So "Job Description:" is not one of those, so we should not use

                          for it. We can just wrap it in

                          as part of general text. But we need to preserve the colon? The original has "Job Description:" with colon. So we need to include that colon in the paragraph. Thus we will produce HTML that includes all lines in order, preserving them. Let's outline the original text exactly as given: Company: RCL Foods Functions: Operations/Manufacturing Job Type Classification: Permanent Location - Town / City: Molteno Job Description: To physically inspect materials and quantities received from suppliers and reconcile it for delivery/ returns notes from the suppliers. To exercise control of packaging stores and ingredient stores and ensure that quantity and location accuracy is maintained all of which must be controlled within the boundaries of the Syspro system. To physically inspect materials and quantities received from supplier/s. To assist with physical stock counts and investigate, trace and resolve inconsistent material movements to improve inventory accuracy. To ensure the correct storage and issuing of ingredients is in accordance with food safety, FIFO (First In First Out) and FEFO (First Expired First Out) principles. To monitor stock levels and inform management of low stock, excess stock or close to expiry plus slow-moving inventory To identify and report damaged, expired or non-conforming materials and ensure proper segregation and disposal procedures are followed To ensure all stock transactions, transfers, returns and adjustments are captured accurately and timeously in the Syspro system. Minimum Requirements: NQF Level 4 Grade 12 or Matric Equivalent Certificates or N (C) V Level 4 Cost & Inventory certificate / Stores