Development Scenarios

Illustrative Scenario: a Retailer Private-Label Range

Anonymised scenario 03

A private-label range from zero

An anonymised OBM brief of a kind that recurs in development work: several SKUs, one launch date and a supplier audit.

The brief: four SKUs — a cleanser, a moisturiser, a hand cream and a body wash — shelf-ready in 22 weeks, with a supplier pack that would satisfy the group’s procurement and technical teams.

Four SKUs share one artwork grid and one launch date

4SKUs launched together

22 weeksConcept to despatch

1Accountable project team

The constraint

Four formulas meant four safety assessments, four labels and four notifications, but one shared launch date. A delay in one document would hold the whole range in the warehouse.

What we changed

We ran the documentation in parallel on one shared template, agreed a single artwork grid across all four packs, and held a weekly status review with named owners and a red-amber-green risk column.

The compliance route

A Responsible Person was appointed for the range, each SKU received its own CPSR and SCPN, and the group received a supplier pack with the modern slavery declaration, ISO 22716 evidence from the site and batch release records.

Workstream	Weeks 1–8	Weeks 9–22
Formulation	Briefs and sample rounds	Lock, stability and scale-up
Documentation	PIF structure and assessor brief	CPSR, SCPN, artwork sign-off
Production	Site selection and audit	First run, QC release, despatch

What the scenario shows

One status table shared across SKUs makes dependencies visible. When a document is late, everyone can see which launch date it holds.

What this does not imply

Timelines depend on assessor capacity, laboratory booking and site availability. We quote a programme with dependencies and risks rather than promising a fixed date we do not control.

Where this sits in a real project

A range is a scheduling problem as much as a formulation one. Building the brand and the range together is described under OBM incubation, and the ownership question behind that route is compared in ODM vs OEM vs OBM. The gate sequence for every SKU is set out in our process and, for a first UK launch, in how to launch a skincare brand. Each SKU still needs its own compliance file.

Questions we are asked

Why does each SKU need its own CPSR and SCPN?

Each product placed on the Great Britain market is notified and safety-assessed separately. Variants of a shared base can sometimes be grouped in one assessment, but that is the assessor’s decision, not a scheduling shortcut.

Can one supplier audit cover the whole range?

Usually one site audit covers the site, but each pack and formula still needs its own specification, compatibility data and batch documentation. The audit answers “can this site make it”; the specification answers “did it”.

Do you guarantee a fixed launch date?

No. We publish a programme with named owners, dependencies and a risk column. Assessor capacity, laboratory booking and site availability sit outside our control, and we would rather show that than promise a date we cannot hold.

Similar project

Building a range, not a single product?

We will map the dependencies across SKUs and give you one realistic launch programme.

Request a review Back to selected work