Collaborative Planning, Forecasting, & Replenishment Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Olipop" then THE ROLE". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate etc. We need to decide which sections to include based on content. We have: - About Olipop (company description) – could be "About the role"? Actually "About the role" is a heading for description of role. The company description could be placed maybe as a

before sections? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section that includes the description of the role (the paragraph after THE ROLE). The company description "About Olipop" maybe could be included as a

before sections, not as a heading. It's substantive info about company; we should preserve it. Not a heading. Then we have Responsibilities (list). Requirements (list). Then there is "Compensation $85,000 $95,000" – that is Pay. So we need a Pay section with that info. We have "How We Work", "What We Value", "What We're Looking For", "Startup life at OLIPOP", etc. Those could be considered as "Benefits"? Not exactly. There's no explicit Benefits section. The instructions: include a section ONLY when posting has real, specific content for it. So we could create a "Benefits" section if there is content about benefits. The posting includes "How We Work", "What We Value", "What We're Looking For". Those are more about culture, not benefits like health insurance etc. Could we treat them as a "Benefits" section? Probably not; better to not create a Benefits section unless there is explicit benefits like health, 401k, etc. There's none. So we skip Benefits. We have Pay section. Schedule? Not mentioned. So skip. Qualifications? The Requirements section may cover qualifications; but we could also have a Qualifications section separate if there is distinct content. The posting has "Requirements" and also "Nice To Have". Could treat "Nice To Have" as part of Requirements or Qualifications? The instruction list includes Qualifications as a possible heading. We could put the "Nice To Have" under Qualifications. But we need to avoid filler. The "Nice To Have" includes: Experience implementing AI and automation tools to improve process efficiency. Six Sigma Lean certification preferred. That's specific. So we could have a Qualifications section with those nice-to-have items. But we also have "Reports Into Manager, Supply Chain Customer Service". That's metadata; could be placed in a short

maybe under About the role? Or we could drop it as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include that line in a

maybe after About the role. We also have "Compensation $85,000 $95,000". That is Pay. We need to preserve all substantive info. So we need to include the company description paragraph(s) about Olipop mission. Also the role description paragraph after THE ROLE. Then Responsibilities list. Then Requirements list. Then Qualifications (nice-to-have). Then Pay section. Possibly also include "How We Work", "What We Value", "What We're Looking For", "Startup life at OLIPOP" as a section maybe "Culture" but not in allowed headings. Could we put them under "About the role"? Might be too much. But we need to preserve all substantive info; we could include them as

paragraphs under a section like "About the role" or maybe a separate section "About OLIPOP" but not allowed heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to add other headings if needed, but better to stick to those. We could incorporate culture info into a "Benefits" section? Not accurate. Could we treat them as part of "About the role"? The role description already includes a paragraph about fast-paced environment etc. The later sections about How We Work, What We Value, etc are more about company culture and values. Could be placed under a section "About OLIPOP" but not in list. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but suggests those as examples. Safer to stick to those headings only. So we need to fit all substantive info under those headings or as paragraphs without headings. We have: - Company description (About Olipop) – could be a

before any heading. - Role description (the paragraph after THE ROLE) – could be part of "About the role" heading. - Responsibilities list – under

Responsibilities

. - Requirements list – under

Requirements

. - Qualifications (nice-to-have) – under

Qualifications

. - Pay – under

Pay

with "$85,000 – $95,000" (preserve as is). - Maybe also include "Reports Into Manager, Supply Chain Customer Service" as a

under About the role or after. - The sections "How We Work", "What We Value", "What We're Looking For", "Startup life at OLIPOP" – could be placed under a heading like "About the role" as additional paragraphs, or maybe under a heading "Benefits"? Not appropriate. Could we create a "Benefits" section with those culture points? The instruction says never create Benefits sections unless posting actually states them. It does not explicitly state benefits like health insurance, but it does state culture and values. Might be considered benefits? Probably not. Safer to include them as paragraphs under "About the role" or maybe under a separate heading like "About OLIPOP" but that's not in the list. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. I'd assume we should only use those headings. So we need to fit culture info somewhere else. We could put them as

paragraphs after the Pay section, without a heading. That would preserve info. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose." So we can have prose paragraphs anywhere. Thus final HTML:

  About Olipop ... (the long mission paragraph)

  About the role

  OLIPOP is looking for an authentic, eager, and highly motivated individual to join the team as our Collaborative Planning, Forecasting, and Replenishment Analyst. This is a great opportunity to have a front row seat at a fast growing start up and new emerging category within functional beverages. In this role, you’ll be responsible for driving customer supply chain performance through collaborative forecasting, replenishment planning, inventory management, and service optimization. This role partners closely with Sales, Demand Planning, Customer Service, Logistics, and key retail customers to improve forecast accuracy, in-stock performance, inventory productivity, and OTIF metrics. If you're looking for a fast-paced environment, an opportunity for personal growth, and enjoy having fun along the way, then this is a role you'll thrive in!

  Reports Into Manager, Supply Chain Customer Service

  Responsibilities

  • Independently manage day-to-day customer operations in partnership with the Supply Chain Manager, proactively flagging risks and surfacing recommendations rather than waiting on direction.
  • Own the end-to-end order stream, driving toward a 95% no-touch order-to-cash process and identifying process improvements that reduce manual intervention.
  • Partner with Logistics to ensure on-time delivery and truckload consolidation, using data and stakeholder input to reduce cost to serve.
  • Manage EDI systems and order management processes; break down recurring fulfillment roadblocks into root causes and implement solutions that reduce repeat issues rather than one-off fixes.
  • Own the logistics non-compliance and fines process end-to-end, from identification through resolution.
  • Own customer fill rate reporting, using trend analysis to drive root-cause investigation, track corrective actions, and develop long-term, scalable solutions.
  • Support onboarding of new customers in their early stages while cultivating and deepening relationships with existing accounts.
  • Monitor inventory levels closely, proactively manage potential inventory cuts, and communicate directly with customers when needed to preserve trust and transparency.
  • Contribute to building SOPs that scale with the team, sharing knowledge and best practices as the function grows.

  Requirements

  • 5–8 years of customer-facing management experience within a Supply Chain environment, demonstrating full proficiency in core function responsibilities.
  • Skilled at breaking down complex, ambiguous problems into manageable parts, interpreting information from multiple sources, and making sound recommendations.
  • Proven ability to work independently with minimal oversight, while knowing when to loop in others at key milestones.
  • Comfortable operating in a fast-paced, highly collaborative environment; works effectively across functions and can act as a resource for less experienced colleagues.
  • Dynamic problem solver who adapts quickly, manages multiple priorities, and addresses issues in real time.
  • Transparent, empathetic communicator who listens actively and reads between the lines with both internal partners and customers.
  • Strong attention to detail, high ownership mentality, and the organizational skills to manage competing deadlines and priorities.
  • Proficiency with Google Workspace, Salesforce, and other leading CRM platforms.
  • CPG industry experience preferred.

  Qualifications

  • Experience implementing AI and automation tools to improve process efficiency.
  • Six Sigma Lean certification preferred.

  Pay

  $85,000 $95,000

  Then after that we can include the culture paragraphs as

  without heading:

  How We Work ...

  What We Value ...

  What We're Looking For ...

  Startup life at OLIPOP ...

  We need to ensure we preserve all substantive info from those sections. Let's extract them. From posting: "How We Work We may be fully remote, but we’re anything but disconnected. OLIPOP has grown from a few passionate people around a table to a nationwide team, and we’ve done it without losing our collaborative spirit or sense of purpose. Connection here is intentional. From cross-functional projects and IRL offsites to thoughtful Slack threads and spontaneous gifs, we make the effort to stay close, even across time zones. Sure, we move quickly, but we lead with trust, transparency, and a shared commitment to doing work that matters. We value thoughtful debate. We give feedback with