From sketch to shelf: the licensed product approval process
A licensee sends a design on Monday. By Friday it sits in three email threads, there are two files called “final” and one key comment nobody can find. Multiply that by every product in the season and your launch window starts to close.
A clear product approval process fixes most of this. Below we walk through each stage from sketch to shelf, who does what, where approvals slow down and how modern licensing teams shorten the cycle.
The four stages of a licensed product approval process
Most programmes approve a licensed product in stages. The names vary by category, but the logic is the same. You catch problems while they are still cheap to fix.
- Concept. The licensee shares a sketch or design idea. You check that it fits the property, the style guide and the categories the agreement grants.
- Preproduction. Artwork, colours, materials and packaging are worked up in detail. This is where most comments land, so clear feedback here pays off later.
- Production samples. A sample shows how the design survived manufacturing. Colours, placement and finish are checked against the approved artwork.
- Final. The finished product and packaging are signed off for sale. Keep a photo of the approved product on file for future reference.
Some teams add stages for packaging, marketing materials or retailer exclusives. What matters is that everyone knows which stage a product is in and what comes next.
Who does what
Three roles usually share the work. Making them explicit removes a surprising amount of back and forth.
- The licensee creates and submits designs, responds to feedback and resubmits until the product is approved. The licensee also chooses the factory that will make it.
- Brand assurance at the licensor reviews each submission against the style guide and brand standards. They approve, reject or ask for changes, with a reason every time.
- The agent, where there is one, often handles routine reviews and day to day partner contact. The licensor then signs off the critical decision points.
Others may need to follow the work without acting on it. Think legal, marketing or a regional sales team. Give them a view, not a vote.
What slows approvals down
Approvals rarely stall because of one bad design. They stall because of the process around it.
- Feedback in email threads. Comments arrive in three separate emails, screenshots get lost and the licensee acts on half of them.
- Versions multiplying. Nobody is sure which file is the latest, so the factory works from the wrong one.
- Unclear stages. When a licensee cannot see where a product stands, they chase. Chasing creates more email.
- One person’s inbox. If every approval depends on a single reviewer, one holiday stops the whole queue.
Look at the products that went five or six rounds this year. The cause is almost always lost feedback or an old file, not a bad design.
A more efficient, faster approvals process, cutting out the need for email and having everything stored in one place has really cut down on unnecessary admin.
How to shorten approval cycles
The fixes are practical. Most of them are about structure, not extra effort from your team.
Set structured stages and real deadlines
Define your stages once and apply them to every submission. Agree the retail launch date early, then work backwards through manufacturing and shipping time. That tells everyone how long each review round can take.
Aim for one or two revision rounds per stage. Keep a list of the comments you write most often, so feedback stays consistent across reviewers.
Pin feedback to the artwork
Comments belong on the design itself, not in a separate email. A pin on the logo placement says more than a paragraph describing it.
One feature of Flowhaven that stands out is their annotation tool, because it allows us to swiftly review and feedback.
Explain every request, too. “Please change the base colour” with no reason costs a revision round and a little of the partner relationship.
Compare versions side by side
When version 3 sits next to version 2, reviewers see exactly what changed. Nobody rechecks the whole design every round, and nobody approves the wrong file.
All feedback within the Flowhaven platform is connected to a particular submission, allowing us to stay organized.
Give each role the right permissions
Map your people to four permissions: submit, review, approve and observe. Licensees submit, brand assurance reviews and approves, and colleagues who only need visibility observe.
Roles can change from stage to stage. An agent might approve concepts while the licensor signs off final samples. Nothing then depends on one inbox.
Only allow audited factories
A great design made in a factory without a valid audit is still a problem. Check compliance at submission, before a single sample is made. Our guide to factory audits in licensing covers this in detail.
Start from the right assets
Many rejections trace back to an old logo or last season’s palette. Share assets from one place so every licensee works from the latest version. More on that in Is your licensee using last season’s style guide?
Trust your proven partners
With licensees you know well, consider approving familiar product types from photos instead of physical samples. Keep physical samples for new partners and new categories.
Free tools for licensing teams
Royalty report templates, approval playbooks and agreement checklists.
Free to download, no strings attached.
From sketch to shelf in one flow
Here is how one scarf moves through Flowhaven, in a demo programme with fictional brands. Kelpline Apparel is making a scarf for Gullhaven FC.
- Brand assets shared once. Style guides, crests, fonts and kit patterns go out to every licensee from one place, always the latest version.
- Licensee submits in the partner portal. Only factories with a valid audit can be selected, so compliance is checked before a single sample is made.
- Feedback pinned right on the artwork. Every version stays side by side. No more feedback lost in email threads.
- Approved, partner notified. Version 3 is signed off and Kelpline knows instantly. Production starts on the right file.
Licensees work in the partner portal as guest users, and guest users are unlimited. Every comment and decision stays in one audit trail, so you can always see who signed off what.
For international programmes, the small things count. Users can pick their interface language, including Japanese, and a stable platform keeps daily approval work moving.
It’s amazing that we have not experienced any downtime with Flowhaven! This level of stability really helps our timely day to day approval work.
It’s great that Flowhaven offers language selections within its system. JPN users can select Japanese from the beginning. Also, the quality of Japanese translation is very good, natural and smooth.
What to do next
Write your current stages and roles on one page. Then count how many approvals this season went past two rounds, and note why each one did.
That list shows you where to start. To see a structured product approval process in action, explore Flowhaven product approvals.
Free download: Product Approvals Playbook
Four approval stages, turnaround targets, review checklists and the metrics that show your process works. Browse all free downloads.
See how licensing teams like yours run on Flowhaven
Bring one real workflow, an approval, a royalty report or a renewal, and we will walk through it with you in 30 minutes.
Approx 100 licensing teams run their programs on Flowhaven. No hard sell and no slide deck, we start with your situation.
